How your keys are kept

Three locks, one inner key

Your keys and settings live in one locked document, the vault. A random inner key opens the vault, and that inner key is itself locked three ways. Any one of the three opens it.

Where the vault lives

The server never has your password, your 12 words or your passkey, so what it holds is a copy nobody can open.

While it is unlocked

Once unlocked, your keys exist in one place only: the key worker, a separate part of your browser tab. The page talks to it in short, named requests and gets back addresses, numbers and previews, never keys.

The worker builds every transaction itself from a plan. The page cannot hand it a transaction to sign. The one exception is a site’s request in Raven for Chrome, and only after the checks in Checks before you sign.

Your password

At least 12 characters. Raven turns down what attackers try first: one word with a number on the end, a keyboard run, the same few letters over and over. A strong password is what stands between a stolen copy of the vault and your keys.

Under the hood

WebCrypto only

Every lock uses the browser’s own cryptography. No third-party code touches a key.

A tag over the locks

The locks sit outside the locked data, so whoever stores a copy could try to swap them. The vault keeps a tag over its locks, made with the inner key, inside the locked data. A copy whose locks do not match its tag was not written by you, and Raven will not use it.

600,000 rounds

Each guess at your password costs an attacker 600,000 rounds of SHA-256. That is what makes a long password hold against a stolen copy.

The passkey lock

Face ID releases a secret through the passkey’s PRF extension, only on Raven’s own address. HKDF turns it into the key for that device’s lock. It never leaves your browser.