What is Mina?
- Author
- CRYPTO PORT Editorial
- Published
- Updated
- Reading time
- 6 min
In short
Mina is a blockchain designed so that verifying it does not require holding its full history. It compresses past state into zero-knowledge proofs, keeping the data needed for verification extremely small. The stated consequence is that a phone or browser can verify the chain completely.
Key points
- Recursive zero-knowledge proofs keep the data needed to verify the chain at a small, roughly constant size
- The current state can be checked as valid without storing every past transaction
- Applications, called zkApps, are written with a TypeScript-based library
- Runs on proof of stake, with block production and proof generation as separate roles
Definition
A proof-of-stake blockchain that uses recursive zero-knowledge proofs to compress ledger history and keep verification data small.
Mina's target is the cost of verification. Verifying Bitcoin or Ethereum yourself means downloading and replaying hundreds of gigabytes of history. In practice, most users end up trusting the responses of nodes someone else runs.
Mina's answer is recursion. Each new block produces a fresh proof asserting both that the previous proof was valid and that this transition is valid, replacing the old one. Verification then needs only the latest proof, and the data does not grow as the chain does.
Applications are called zkApps. Because computation runs off-chain and only a proof of correctness is submitted, the model suits cases where you want to show a condition was met without revealing the inputs. Development uses o1js, a TypeScript library.
Operationally, block producers and proof generators (called snarkers) are separate roles. Since generating proofs takes real computation, that work is carved out into its own market. Stake can be delegated, so holders can participate without running infrastructure.
Watch out for
- · Small verification data is not the same as high throughput; capacity is bounded by how fast proofs can be generated
- · Zero-knowledge implementations are complex, and a flaw in the proving system bears directly on asset safety
- · Writing zkApps differs from ordinary smart contract development, and existing EVM code cannot be reused
Frequently asked questions
Does a small chain mean transaction history is deleted?
No. Only the data needed for verification is small; the history itself is kept by archive nodes. The proof attests that the past was valid — if you want to read the contents of that history, the data has to be stored separately.