Verify

Don't trust this site; check it. Both checks run in your browser.

Check a vault

Choose a vault card or a backup file. From a backup file only the card part is read; the recovery words are never looked at or sent anywhere.

What this proves: the vault and waiting-room addresses really are the published contracts with these keys, which key can rescue the vault (the watcher's), and where an emergency sends the money (the backup wallet).

Lost access to your vault?

If you can't open your vault any more (no words, no backup file, no browser), the watcher can still send everything to your backup wallet. It emails a rescue link, but only to an address already confirmed for that vault.

Vault address Your confirmed email

Check this website

The vault code this site is serving right now has this fingerprint (SHA-256 of kaspa-vault.min.js):

calculating…

Build the same file yourself from the public source and compare. The build is reproducible: the same source always gives the same fingerprint.

git clone https://github.com/kasperolabs/kaspa-vault
cd kaspa-vault && npm ci
npm run build:widget        # prints the SHA-256 of widget/dist/kaspa-vault.min.js

If the two differ, this site is not serving the published code. Don't use it, and tell us.

Check the contracts

The contracts are compiled into byte templates once, with SilverScript's own compiler, and the repository proves the templates equal the compiler's output for thousands of random keys (npm run test:equality). From a vault card's .ksm files, npx [email protected] verify checks them without any website.