Testnet live · Mainnet launch
Privacy vaults. Privacy swaps.
Timelock any transaction and leak nothing. Release on a date, on silence or by guardian vote, and swap through the ZEC shielded pool. Onchain, your vault is one hash. No owner, no recipients, no amounts.
We have not launched a token. Anyone claiming to sell one is a copycat or a scam.
Noir circuitsUltraHonk ZK proofsFROST threshold keysZEC · BTC · SOL · EVMNo admin keys
| Field | Any timelock or escrow | Vault ZK Protocol |
|---|---|---|
| Owner | 0x7f3a…c019Doxxed forever | not storedNot stored. You prove a secret that never leaves your device. |
| Vault | Your address | 0x2f8a91…e07c41dOne Poseidon2 hash. That’s it. |
| Recipients | 0x91b0…5e2a, 0x44de…a7f3 | A Merkle root. Never named, not even after they claim. |
| Shares | Public | Hidden until each one is claimed |
| Payout address | Public | Hashed into the proof. Can’t be front-run or redirected. |
| Who sent the tx | Your wallet | A relayer, so your wallet stays out of it |
Three settings. Any release you can think of.
What
- ZEC, BTC, SOL and EVM assets
- Seed phrases, keys, documents
- Privacy swaps through the ZEC shielded pool
When
- A date and time
- After you go silent for 2 days to 10 years
- Whichever hits first
- k-of-n guardians if you lose your key
Who
- Up to 256 recipients
- Custom share each
- One claim each, enforced by nullifiers
One primitive. Endless releases.
- Dead-man switchGo quiet and your keys, funds or files go where you said.
- Inheritance without a public willYour heirs claim. Nobody can see who they are.
- Scheduled unlocksTreasury, payroll or OTC releases on a date. Recipients stay unlinkable.
- Social recoveryLost your key? Guardians vote anonymously. One check-in from you kills the vote.
- Sealed dataEncrypted on your device, drand-timelocked. Not even we can open it early.
Don’t trust. Verify the proof.
Secrets stay in your browser. The chain only verifies ZK proofs. Keepers co-sign payouts only after the chain says yes.
Createowner_auth
Generate a secret and a salt
vaultId = Poseidon2(ownerSecret, salt)Store vaultId and the policyInactivity period, unlock time, beneficiary root, guardian root
Check inowner_auth
Prove ownership for todayThe proof is bound to this action and this day
Verify, record the timeThe inactivity clock restarts
Claimclaim
Prove membershipThe payout destination is bound into the proof
Check the vault is releasable, record the nullifierEmits
Claimed(nullifier, share, H(dest))Keepers co-sign the payoutThreshold keys. In development.
Recoverguardian_vote
k anonymous votesFor a new owner commitment you generate
Rotate the vaultAny check-in from you cancels the round
Live on BSC Testnet
Real ZK proofs, verified onchain, right now. Want in? Contact us for testnet access.
| Component | Status |
|---|---|
| Vault registry and on-chain proof verification | Live on testnet |
| Noir circuits: owner_auth, claim, guardian_vote | Live on testnet |
| Proof generation in the browser | Live on testnet |
| Release on inactivity or unlock time | Live on testnet |
| Relayer that submits proofs for you | Testnet-ready |
| Threshold custody: ZEC (Ironwood shielded pool), BTC, SOL, EVM | In development |
| Zcash shielded payout rail | In development |
| Encrypted data vaults and drand time-lock | Testnet-ready |
| Vault ZK app: create, check in, claim, recover | Testnet-ready |
| Privacy swaps through the Zcash shielded pool | In development |
Trustless by construction
No admin keys. No upgrades. No msg.sender checks. One registry, three Noir circuits, and an SDK to plug private releases into any wallet or protocol. Read the docs.