# The Nakamoto Test: five questions that measure any protocol against the original vision

> Canonical: https://blazephoenix.xyz/learn/the-nakamoto-test
> License: CC BY 4.0 (attribution + link) · © 2026 BlazePhoenix
> Updated: 2026-07-20

The Nakamoto Test: five falsifiable questions — settlement, verification, survival, permission, transparency — measuring any protocol against Satoshi's and Vitalik's founding vision, with BlazePhoenix's honest scorecard.

The Bitcoin whitepaper opens with its whole thesis in one sentence: "A purely peer-to-peer version of electronic cash would allow online payments to be sent directly from one party to another without going through a financial institution." Everything else — the mining, the chain, the incentives — exists to serve those words: remove the trusted third party. Ethereum's founding move, in Vitalik Buterin's 2014 whitepaper, was to generalise the same removal from PAYMENTS to COMPUTATION: arbitrary agreements that run exactly as written, with no institution in the loop.

Most of what wears the word "crypto" today would be unrecognisable to that opening sentence: exchanges holding customer funds like banks, "DeFi" frontends routing through private pricing servers, tokens with admin keys that can freeze what you own. The vision did not fail — it is simply optional now, and most projects quietly opt out. So here is a way to check who opted in: five questions, each falsifiable, each answerable from public state. We call it the Nakamoto Test.

## The five questions — and our honest scorecard

1 · SETTLEMENT: can value move without a trusted third party? Ours: yes — swaps settle wallet-to-contract; nothing is custodied, ever. 2 · VERIFICATION: can a user VERIFY instead of trust? Yes, and further than most: even the QUOTE is computed on-chain (previewPlan), staking solvency is a free function call (isSolvent()), and every claim on this site ends in a command. 3 · SURVIVAL: does it work if its creators vanish? Yes by architecture — stateless Core, no upgradeable proxy, no keeper, no server; fund-touching powers are renounceable through the One-Way Door. Honesty requires the caveat: renounceable is a spectrum, and the timeline is public. 4 · PERMISSION: can anyone use it, without asking? Yes — no account, no KYC, no whitelist; the same functions for whales and shrimps. 5 · TRANSPARENCY: is the operating state public? Yes — pools, balances, floors, emission curves: all readable, free, any block.

Where we do NOT get to claim perfection: no independent external audit has been completed yet — our safety argument is reproducibility you can check, not an attestation you must believe — and this website, like any frontend, is a convenience layer you should verify against the chain rather than trust. The test is not a trophy; it is a discipline. Run the same five questions against any protocol you use — including the famous ones — and notice how quickly "decentralized" becomes a marketing adjective. The original vision was never about price. It was about removing the need to ask permission and the need to believe. That is the lineage BlazePhoenix builds in: compute, don't trust is Satoshi's opening sentence, restated for a DEX.

**Verify it yourself:** run question 2 on us right now: cast call 0x3f60C7aa0c36a78D200405feBE143d2Cf3fA0c77 "isSolvent()(bool)" --rpc-url https://mainnet.base.org — then try to run ANY of the five on a custodial exchange

Related: https://blazephoenix.xyz/learn/ungovernable · https://blazephoenix.xyz/learn/web25-vs-web30 · https://blazephoenix.xyz/learn/invariant-driven-ai · https://blazephoenix.xyz/learn/cex-vs-dex