Bypass-resistant controls
UI-only allowlists are brittle. RegVault blocks bad transfers with protocol-enforced checks on the asset path itself.
Institutional Solana Control Stack
Compliance enforced at the token layer.
RegVault is an institutional permissioned vault-share system for Solana. It combines Token-2022 enforcement, role-aware operations, and audit-grade evidence so controls survive beyond a single interface.
Why it matters
Institutional identity context
Wallets map back to regulated entities, attestations expire, and execution proofs remain discoverable after the workflow completes.
Control Surface
Token-2022 + Transfer Hook
Workflow
Registry, approvals, receipts
Operator View
Live dashboard + demo evidence
Core Protocol
Four on-chain primitives. One control chain that cannot be bypassed.
Each component operates independently on-chain. Compliance enforcement lives in the token, not the interface—so controls hold regardless of which front-end, program, or wallet initiates a transfer.
Transfer Hook Enforcement
Compliance policy is wired into the share mint via Token-2022 Transfer Hook. Every transfer validates entity status, active attestation, and destination approval before settling. No UI bypass is possible.
Wallet-to-Entity Registry
Institutional wallets are bound on-chain to regulated entities with issuer-signed attestations. Attestation expiry, KYC status, and sanctions flags gate investor actions automatically.
Maker-Checker Withdrawals
Withdrawal requests enter a bitmap-based dual-approval queue. Operator and compliance roles each hold one approval bit, with a configurable timelock enforced before execution.
Immutable Receipt PDAs
Every executed withdrawal writes a receipt PDA to chain—request ID, entity, destination, amount, and policy snapshot. Permanent, tamper-proof, and queryable via the open API.
Compliance Stack
Sanctions, KYC, and Travel Rule built in.
Every entity carries a risk tier, sanctions status, and KYC expiry. Velocity limits are enforced per entity per day. Transfers above the FATF threshold collect and hash counterparty data before the transaction proceeds.
Entity Risk Tiers
LOW · MEDIUM · HIGH with configurable daily withdrawal caps per tier
Sanctions Screening
Chainalysis, Elliptic, or TRM Labs — CLEARED / FLAGGED / PENDING status
KYC / KYB
Sumsub, Onfido — expiry-tracked with automatic access gates on lapse
FATF Travel Rule
Originator and beneficiary data hashed and submitted at the $1,000 threshold
Velocity Monitoring
Daily caps per risk tier with WATCH / ALERT / CRITICAL escalation alerts
Role Model
Five roles. Every action scoped to one.
Access control is enforced at the program instruction level. Each wallet is classified against the vault's role registry before any instruction executes.
Admin
Full protocol configuration, role assignment, and emergency controls
Compliance
Entity management, attestation issuance, and withdrawal approval authority
Operator
Withdrawal queue approval and post-timelock execution
Emergency
Pause-only authority for circuit-breaker scenarios
Investor
Deposit and withdrawal when entity is active and fully attested
Protocol Architecture
From registry state to final receipt, one control chain.
01
Registry binds entities, wallets, and issuer attestations on-chain.
02
Vault controls queue, approvals, timelocks, and execution state.
03
Transfer-hook policy validates destination rules at transfer time.
04
Receipt PDAs turn execution into permanent audit evidence.
Operations Console Preview
Designed for live review, daily operations, and audit inspection.
Hook wiring health and ExtraAccountMetaList validation
Role-aware operations status with read-only fallback
Withdrawal Queue rows with approvals and unlock windows
Immutable Receipts feed and operator failure simulations
Mission Control Snapshot
Hook Health
Healthy
Queue State
2 pending
Receipts
Audit ready
Wallet Mode
Role aware
Deployment Surface
Built for issuers, funds, custodians, and regulated operators
RegVault provides the on-chain infrastructure for institutions operating under regulatory obligations. Deploy on any Solana cluster—compliance enforcement runs at the protocol layer, not the operator layer.