Mina: Decentralized Cryptocurrency at Scale

Authors Joseph Bonneau, Izaak Meckler, Vanishree Rao, and Evan Shapiro
Document March 2020 technical paper
Project Mina Protocol
Document license No license statement identified in the paper
Official source Mina: Decentralized Cryptocurrency at Scale (PDF)

This page summarizes the 2020 paper and distinguishes it from later Mina implementations and network upgrades. It is an educational summary, not a reproduction or a current protocol specification.

Mina: Decentralized Cryptocurrency at Scale is a March 2020 paper by Joseph Bonneau, Izaak Meckler, Vanishree Rao, and Evan Shapiro. It proposes a “succinct blockchain”: instead of asking every verifier to replay the full chain from its beginning, recursively composed zk-SNARKs let a compact proof certify that a sequence of state transitions followed the protocol. The paper also presents Ouroboros Samasika, a proof-of-stake design for a succinct chain. Its claims and measurements describe that paper’s design and implementation at the time; they should not be read as a complete description or benchmark of Mina today.

What the paper means by a succinct blockchain

A normal block history grows as new blocks are added. A succinct design aims to keep verification data small by making each proof attest to earlier valid state and the next valid transition. Later verifiers can check the resulting proof instead of independently repeating every prior computation. This is a way to reduce the history needed for a particular verification task; it does not mean the transactions, account data, or every operational record cease to exist.

The paper’s key idea is recursive composition: a proof can include the statement that an earlier proof was valid, together with evidence that the next transition followed the rules. The proof represents a claim about the chain’s state and its valid evolution. Users still need the relevant account information and a path that connects it to the authenticated ledger state. The paper’s 2020 evaluation reports an 864-byte state proof and verification in about 200 milliseconds for the implementation it tested. Those are historical, implementation-specific measurements, not current Mina performance guarantees.

What the “22 KB” description does and does not mean

Mina’s public shorthand is that its blockchain is about 22 KB. A 2021 technical reference from the Mina Foundation defined what it counted for a usable, non-consensus verification setup: a proof, protocol state, an account record, a Merkle path, and a verification key. For that snapshot, the listed data totaled 8,807 bytes, plus a 2,039-byte verification key, or roughly 11 KB. The article said the estimate had changed as the cryptography became more efficient.

That historical measurement helps explain the slogan; it is not a timeless size for every node or a claim that all Mina data fits into one 22 KB file. The same reference says block producers need more information, including the full ledger, to produce blocks. Current documentation describes archive nodes that retain blockchain history for queries. Account state, application data, proof-verification data, and archival history serve different purposes and have different storage needs. The paper and later technical reference should therefore be cited with their dates and measurement scope.

Consensus: paper proposal and current protocol

The 2020 paper introduces Ouroboros Samasika and analyzes security properties under a formal model and stated assumptions. That is useful for understanding the proposal, but it is not a blanket guarantee against every attack, nor an independent audit of every current implementation. A paper’s proof applies to the model and parameters it analyzes; software, network operation, and later protocol changes require their own review.

Mina’s current documentation still describes a proof-of-stake network and its specialized node roles. The protocol has also changed since the 2020 paper. In September 2026, Mina announced that the Mesa mainnet upgrade had activated, reducing the configured slot time from 180 seconds to 90 seconds and changing zkApp capacity and upgrade handling. These are current project statements about a later network upgrade, not results contained in the 2020 paper.

How to interpret Mina’s proof-size claim

The small verification representation is valuable because it can make independent state checking practical with less downloaded history. It is different from storing every transaction for audits, exchange operations, or application history. A verifier checking a compact proof, a block producer constructing new blocks, and an archive node serving historical queries have different jobs. Calling each of them simply “a Mina node” can obscure those storage and trust trade-offs.

The distinction also matters when comparing Mina with other chains. A succinct proof may reduce the data a verifier must replay or retain to validate a current state, while operators and applications can still need larger datasets. A small proof does not by itself establish high transaction throughput, low proof-generation cost, broad hardware access, or decentralization. Those properties depend on the current protocol, node roles, network participants, and measured use.

Later proof systems are separate from the 2020 paper

The 2020 paper explains a recursive-SNARK construction. Later Mina material discusses systems such as Pickles and Kimchi and the Pallas–Vesta “Pasta” curve cycle. Those are later technical context, not details to retroactively attribute to every section of the 2020 paper. In particular, the old page’s description of Pallas and Vesta as a cycle of “pairing-friendly” curves was inaccurate; the important point here is that Mina uses a curve cycle to support recursive proof composition.

Keeping the timeline clear makes the page more useful: the paper records a research design and evaluation from 2020; later technical references describe subsequent proof-system choices; and current docs describe the live protocol and developer environment. These sources answer related questions, but they are not interchangeable.

zkApps, off-chain computation, and privacy

Mina’s zkApps use zero-knowledge proofs for smart-contract computation. Current developer documentation describes an off-chain execution and mostly off-chain state model. It says computation and state can be private or public, depending on the application. That is more precise than saying all zkApp execution is private by default or that sensitive data never leaves a user’s device.

A proof can establish that a computation met specified rules without revealing private inputs, but the application still determines which inputs, outputs, and state are published or stored elsewhere. Off-chain execution can reduce what is put directly on-chain; it does not automatically provide private hosting, protect data submitted to a service, or guarantee that an app’s design is secure. Developers must decide what is public, where state lives, and which parties can access it.

Limits and trade-offs

The paper’s succinctness goal addresses the cost of verifying chain history. It does not eliminate the work of generating proofs, maintaining account state, operating block producers, or supporting applications that need historical data. Some node roles may need more storage and computation than a user who only checks a current state. zkApp developers also work within the current protocol’s transaction and state limits, which can change through network upgrades.

Use the 2020 paper to understand the original construction and its stated security model; use later Mina technical references to understand size measurements and implementation choices; and use current docs and dated upgrade announcements for today’s network behavior. This avoids turning an early benchmark or a compact-proof slogan into a claim about every current workload.

Social Media Sentiment

A small sample of 2026 discussion in r/MinaProtocol was cautiously positive about Mesa and continued engineering work: one post highlighted upgrade rehearsals and testing while noting that operational validation remained. Another thread asked whether the public roadmap was still current; replies pointed to Mesa’s mainnet activation and expressed renewed, but qualified, optimism. These posts show a few community members’ reactions, not a representative survey or evidence of network performance. The subreddit is project-focused, and discussion volume was limited.

Last updated: 2026-10

Related Terms

See Also

Sources