Questions and answers

No. We have not launched a token, and there is no presale, airdrop or claim page. Anyone claiming to sell one is a copycat or a scam. Our only official accounts are @vaultZKprotocol on X and @vaultzkprotocol on Telegram. Any real announcement will appear here and there first.

Any transfer you want to happen later or on a condition: funds on Zcash, Bitcoin, Solana and EVM chains, or secrets like seed phrases, keys and documents. You choose the recipients and their shares, and the trigger: a date, a period of silence from you, or both, with guardian recovery on top. Inheritance and dead-man switches are just two of the plans you can build this way.

Vault ZK Protocol is the infrastructure: the registry contract, the zero-knowledge circuits and the custody layer. The Vault ZK app is the consumer app built on it. Other apps can build on the protocol too.

On BSC Testnet. Contact us at testnet@vaultprotocol.ai for access. The registry is live there and verifies real proofs generated in your browser. Threshold custody and privacy swaps are still in development. See status by chain.

A Poseidon2 commitment per vault, its release policy (inactivity period, unlock time, Merkle roots, guardian threshold), check-in times, used nullifiers, and claim and recovery events. No owner, beneficiary or guardian addresses. The security page has the full list.

From two things only: the unlock time you set, and how long it has been since your last check-in. There is no oracle, no death certificate upload and no AI monitoring, so nothing else can open it.

The vault becomes claimable once the inactivity period passes, and once anyone claims it cannot be changed. Pick a period you will reliably beat, anywhere from 2 days to 10 years. If you want a backstop, use an unlock time instead.

If you configured guardians, k of them can move your vault to a new secret you generate. If you did not, you cannot check in or change the vault any more, and it will open to your beneficiaries after the inactivity period. We cannot recover it for you: we never had the secret and the registry has no admin.

Only if k of them act together, and only while you are not checking in. Any check-in from you cancels the recovery round in progress. Choose guardians who don’t know each other, or a higher k, if that worries you.

No. Each claim reveals a nullifier derived from the beneficiary’s secret and the vault; the registry rejects any nullifier it has already seen. The share is part of the Merkle leaf, so it can’t be inflated.

Keepers are independent operators who together hold threshold key shares and execute payouts after a valid on-chain claim. No single keeper can move anything. If a threshold of them colluded, they could, which is why your policy can require your own or your guardians’ shares as well. The keeper network is in development.

Planned native custody covers Zcash (shielded), Bitcoin (Taproot), Solana and Ethereum/EVM. Anything else can be protected by putting its keys in an encrypted data vault. All of these are in development; see chains.

Because it doesn’t need any, and every script is something you would have to trust. The site is static HTML and CSS, sets no cookies, loads nothing from third parties and keeps no access logs. It is built to work with JavaScript disabled, including in Tor Browser’s Safest mode.