Skip to the content
nullroute
Browse the docs

The five things you can check

What How Catches
The build matches the source Reproduce it and compare hashes Build tampering, a backdoored release binary
The device runs that build Compare the lock screen root hash A swapped or reflashed device
The code matches its specs make verify and read the report Code that quietly stopped doing what it documents
A signature hides nothing Recompute it from the seed Key exfiltration through nonce grinding
Your funds do not depend on us Recover in Bitcoin Core Lock-in, and nullroute disappearing

The last is the most important, and the one people skip.


Rendered from docs/VERIFICATION.md, the same bytes that ship with the code. SHA-256 15ae2ba12417b4691f63d9a4777eba2c328ff694961efea68f5e7dec4ae2e0bd