Compliance, written into the token.
Who can hold, who can receive, what happens when a wallet is under investigation: the rules run on every transfer on Solana, and every action leaves a record. The amounts stay private.
Set the rules. Send a transfer.
This is how Vigilantis, our transfer hook, decides. Change the policy or a wallet, then send. Each check runs in the same order as on-chain.
| Wallet | Registered | Blocked | Frozen |
|---|
Press Send to run the checks.
Simulated in your browser. Error names and numbers are the ones Sentinel 2.3.0 returns on Solana; Vigilantis is its new name, used from the audited release.
Every action leaves a record.
Every transfer that reaches the chain leaves a record, refused ones included. Each block, unblock, freeze and thaw also emits an event with a reason code and a hashed case reference; no names or case numbers go on-chain. Send a transfer or change a wallet above and it appears here.
For supervisors.
Confidential to the public does not mean hidden from the law.
The Auditor Key
Every eUSD amount is also encrypted to an Auditor Key, used only on a lawful request. It moves to two-of-three custody before the licence application, and each use leaves a public record on-chain.
Identity at the perimeter
The issuer checks every institution before it can buy or redeem, itself or through a licensed partner. Turning the allowlist on extends that to every holder.
Reports
Total supply is public on-chain. Each month the issuer publishes the eUSD in circulation, proved on-chain, and the reserve, attested by an audit firm. Each quarter it publishes a formal reserve report and a report on disclosures. These are commitments for mainnet.
What runs today, what comes next.
Released under Apache-2.0; from Vigilantis 1.0.0, the first audited release, under the Business Source License 1.1. Self-audited, not independently audited yet.
Released Sentinel 2.3.0 on npm
- Allowlist, blocklist and a limit per transfer, checked by the hook
- Blocked delegates refused as well (AuthorityBlocked, 6006)
- Freeze and thaw with a reason code and a hashed case reference
- Two-step handover of the policy authority, for a multisig
- The freeze authority can be handed on, with the reason recorded
Planned Next release
- Roles, so a compliance officer can act without the admin key
- Pause and resume for the whole token
- Seizure after a court order, with a waiting period and a record
- A command-line tool and transaction decoder for signers
- An independent audit after the seed round, then Vigilantis 1.0.0
Running a regulated product on-chain?
Tell us what your supervisor expects. We will show you how the rules map.