Used for Nano’s self-description as a low-latency, feeless cryptocurrency with a block-lattice architecture, balance-based transaction encoding, and ORV finality
Used for the split between user-selected representatives, locally determined quorum/cementing, PR rebroadcast policy, and the explicit differences from conventional PoS
Saved locally as ../whitepapers/nano-whitepaper.pdf
Key takeaways from primary sources
Nano’s main analytical value is not just feeless payments; it is the way the protocol relocates contention from one global chain into per-account chains. The docs explicitly frame this as replacing run-time agreement with design-time agreement because only an account owner can advance that account’s chain.
The send/receive split matters. A transfer is not a single shared-chain event but the composition of a send block on one account-chain and a receive block on another, which keeps account owners sovereign over their own chain state and lets recipients ignore unwanted dust.
ORV is useful because it is weighted voting without the usual staking bundle. Representatives do not build shared blocks, delegated funds are never locked, delegation can change at any time, and representatives do not earn transaction fees.
Nano’s local cementing model is a distinct control surface. Each node independently treats a transaction as irreversible once it observes enough representative vote weight to cross quorum, rather than waiting for globally sequenced block production.
The PR/non-PR distinction is also worth retaining. Principal Representatives are not a separate constitutional role so much as an implementation-level rebroadcast threshold chosen to manage bandwidth and accelerate convergence.
The ledger docs make pruning unusually legible because every state block contains the full current account state, which means history can be compressed far more aggressively than on UTXO chains or monolithic account-based blockchains.
Specific source signals worth retaining
The living-whitepaper introduction is the best concise source for Nano’s own framing of block-lattice, balance-based transactions, and deterministic finality.
The ORV page is the clearest source for how Nano differs from classic PoS: no leader selection, no shared block production, no locked stake, no fee rewards, and user-controlled delegation.
The ledger page is the best source for the design-time-agreement framing, the two-step transfer model, and the pruning implications of state-style account-chain blocks.
The original whitepaper is still useful as the canonical historical source for RaiBlocks/Nano’s original architecture, even though the docs now treat the living whitepaper as the current source of truth.
Why this entry belongs in the corpus
Nano gives the corpus a strong historical and mechanism-first comparison point for payment-focused chains that try to reduce fees and latency without adopting rollups, channels, or shared sequencers.
It sharpens comparisons among DAG-adjacent or non-monolithic-ledger systems by making per-account chain sovereignty, asynchronous transaction processing, weighted voting, and local irreversible finality explicit instead of bundling them together as generic fast payments rhetoric.
The durable insight is that Nano is really a consensus-and-ledger decomposition: per-account history, two-step transfer completion, fee-less operation, representative delegation, and local cementing are separate control surfaces, not one product feature.