RegVault Protocol
An institutional permissioned vault-share system on Solana. Vault shares are Token-2022 assets with transfer-hook enforcement, so compliance policy is enforced at the token layer instead of only in a front-end.
What makes it institutional-grade?
Key Features
The protocol is designed around four core pillars that work together to provide institutional-grade controls:
Token-Layer Enforcement
Compliance policy follows the asset via Token-2022 Transfer Hook. Transfers fail at the protocol level, not just the UI.
Learn moreEntity-Based Permissioning
Institutional identity is bound on-chain. Wallets map to entities with issuer-signed attestations—no PII stored.
Learn moreMaker-Checker Controls
Withdrawals flow through timelocked approval gates. Operator and compliance roles enforce controls before execution.
Learn moreImmutable Receipts
Every execution produces durable audit evidence with request ID, amount, destination, timestamp, and policy context.
Learn moreArchitecture at a Glance
RegVault consists of two on-chain programs that work together:
regvault program
Core vault logic: entity registry, wallet claims, attestations, deposits, withdraw queue with approvals, and immutable receipts.
share_hook program
Token-2022 Transfer Hook validator that enforces compliance rules on every share transfer: active entity, valid attestation, and approved destination.
Token Model
Deposit Token: USDC (or mock USDC on localnet/devnet). Users deposit USDC into the vault and receive share tokens representing their claim.
Share Token (rvUSDC): A Token-2022 mint with the Transfer Hook extension enabled. Every transfer is validated by the share_hook program before execution. This means shares cannot be transferred to unregistered wallets even if a user bypasses the UI.