>07 // risks

Risks & disclaimer

Hash-based signatures fix one specific threat. They do not make experimental software safe. Here is what can go wrong.

R01

Unaudited

The program, SDK, relayer, keeper and this site have not been audited or formally reviewed. Bugs could lock or lose funds. Assume they exist.

R02

Devnet only

Noxvault v3 runs on devnet. Devnet can be reset and devnet SOL has no value. The program is still upgradeable; the upgrade authority is to be burned only at mainnet launch.

R03

Your words are the vault

Anyone with enough signer phrases (the threshold) controls the vault, limited only by the whitelist, instant limit and delay, and by your recovery key. Without a recovery key, co-signers or heirs, lost words mean lost funds.

R04

Escape Hatch is a race

It protects the moment it is triggered. If someone breaks your wallet key and moves first, it is too late. Tokens received after approving are not covered until you approve again, and using the wallet's nonce account voids the stored SOL escape. Keep most funds in the vault itself.

R05

The stored SOL escape is public

Anyone can broadcast it at any time. It can only move your wallet's SOL into your own linked vault, but that can happen when you did not plan it; getting the SOL back out then needs a hash signature.

R06

The canary is an alarm, not a guarantee

Someone who can break ed25519 may never touch the bounty, and does not need to in order to attack your wallet. Use panic when in doubt; it does not wait for the canary.

R07

Session keys are ordinary keys

A budget's session key (Phantom, a phone wallet) is ed25519. Whoever holds it can spend up to the budget every period until it expires. Keep budgets small and short, and cancel lost ones.

R08

Recovery, co-signers and heirs

Whoever holds the recovery phrase can cancel your pending withdrawals any time, and takes full control after the recovery delay of inactivity. Heirs receive everything after the testament delay. Choose holders and delays with care, and ping if you go quiet for long.

R09

Keepers are best-effort

The site's keeper runs once a day; a long-running keeper may run more often or not at all. Due schedules, testaments, migrations and escapes happen when someone sends them. Anyone, you included, can.

R10

Browser signing

Keys are derived and used inside this web page. A malicious extension, a compromised device or a tampered copy of the site could steal the words. Use a trusted device and the real domain, or sign on an offline device with /offline.

R11

Never reuse a key

A one-time key may sign one message, ever. The app reads the vault's whole history before signing and refuses if it cannot. Offline signing cannot read the chain: always take the leaf from a fresh prepare step and never sign a different action with the same leaf. Other tools may not follow this rule.

R12

Tokens can be frozen by their issuer

A token with a freeze authority can be frozen in the vault, a wallet or an heir's account by its issuer. Tokens with transfer fees, hooks, permanent delegates or confidential transfers are not supported.

R13

Only the vault is post-quantum

Wallets, session keys, validators and other programs still use elliptic-curve cryptography. Noxvault protects what is locked inside a vault, not everything around it.

R14

Not financial advice

Nothing here is investment advice or an offer of anything. $NOX is planned but does not exist yet; ignore anyone selling it.