verify it yourself
don't take our word for it
Latch's protection is a hash-based one-time signature that the on-chain program checks before any latched token moves. This page runs the same math in your browser, so you can confirm it without trusting this site's server.
1 · the answer key
test vectors
A fixed set of inputs and every output the scheme produces from them: signatures, one-time keys, the key tree and the exact messages that get signed. The on-chain program's tests, the command-line client and this page are all checked against the same file, so all three compute the same bytes.
Writing your own checker? Each rule is spelled out in the file's scheme and digests.formulas fields. SHA-256 is the only primitive.
2 · a real transaction
check a latched transaction
Paste the signature of any latched send, sell, lift or renew. The server fetches the raw transactions: that one, the uploads that carried its one-time signature, and the one that registered the key set. Your browser checks their wallet signatures, reads every value out of the signed bytes, rebuilds the signed message, walks the 67 hash chains and climbs the key tree to the registered root.
3 · what this proves
what a pass means
- it proves
- A one-time key from the set the holder registered signed exactly that action: that amount, to that account, at that point in the account's history. Change any byte and the climb ends at a different root. The site's server can't fake a pass: it only hands over wallet-signed transactions, and this page checks them.
- it does not prove
- That the transaction succeeded (the explorer shows that), or that nobody else holds the holder's backup. This page's own code comes from this site; if you'd rather not trust that either, every rule is in vectors.json.
- why hashes
- A quantum computer breaks the elliptic-curve keys Solana wallets use. It does not break SHA-256 in any practical way: the best known attack only halves the security, leaving 128 bits.