{
  "url": "https://blockindex.ai/coin/mina",
  "name": "Mina Protocol",
  "links": {
    "github": "https://github.com/o1-labs",
    "website": "https://minaprotocol.com/",
    "whitepaper": "https://docs.minaprotocol.com/"
  },
  "dScore": 66,
  "market": {
    "priceUsd": 0.04109736179231021,
    "marketCapUsd": 52902554.83642598,
    "volume24hUsd": 3183809.47874045,
    "priceChange7dPct": -3.11946829,
    "priceChange24hPct": -3.27619051
  },
  "source": "BlockIndex.AI",
  "supply": {
    "max": null,
    "circulating": 1287249412.8400393,
    "circulatingPct": null
  },
  "ticker": "MINA",
  "founder": "Izaak Meckler, Evan Shapiro, Xiang Xie",
  "vcFunded": true,
  "updatedAt": "2026-06-19T06:00:27.517589+00:00",
  "fairLaunch": false,
  "launchYear": 2017,
  "description": "Mina Protocol is a succinct layer‑1 blockchain designed to keep the entire chain state tiny and verifiable via recursive zk‑SNARK proofs. From its origins as the Coda research project in 2017, Mina’s defining architectural goal has been to enable full verification of the network in milliseconds on low‑resource devices by maintaining a constant, small state (on the order of ~22 KB). This design lowers the barrier to participation: anyone can act as a full verifier without the hardware requirements typical of other layer‑1 networks. The protocol supports privacy‑preserving, composable smart contracts (zkApps) written with a TypeScript SDK, and the platform emphasizes developer ergonomics, privacy first principles, and broad decentralization through lightweight node operation.\n\nTechnically, Mina departs from conventional stateful chains by using recursive SNARKs produced by a market of provers (snarkers) and a PoS‑based block producer selection mechanism derived from the Ouroboros family (Ouroboros Samasika). Block producers choose SNARK proofs to include in blocks; snarkers produce succinct proofs and are compensated for prover work. This separation of proving and block production enables Mina to scale proof generation off‑chain while preserving on‑chain succinctness. The stack includes a TypeScript‑centric zkApp SDK, Mina Attestations for selective disclosure patterns, and protocol optimizations such as a convertible Merkle variant introduced in recent releases. Mina’s v3.x release series (v3.1.0 through v3.3.0) and the Mesa upgrade work reflect active engineering to expand on‑chain state limits, improve zkApp account semantics, and make zkApp development more expressive.\n\nIn terms of use cases and ecosystem applications, Mina targets privacy‑preserving identity, credential attestation, lightweight dApps, NFTs, and composable off‑chain computation where proof reuse matters. The network’s constant‑size state is particularly attractive for mobile and embedded environments where full node operation would otherwise be impractical. The project has introduced an NFT standard and a Token Launchpad (mainnet beta in 2025) and promotes adoption through the Mina Ecosystem Funding program and Mina Builders Grants. Exchange and wallet coverage (including major CEX listings and hardware wallet support via Ledger) provide market accessibility; at the same time, the protocol’s limited suite of publicly validated bridges and oracle integrations (as of the supplied sources) means much DeFi composability will arrive as integrations are implemented or validated.\n\nTokenomics and governance reflect a hybrid model of foundation stewardship and on‑chain voting. Mina is a native token on a layer‑1 PoS chain; circulating supply is reported around 1.26–1.3 billion MINA across sources, and an initial supply figure of 1,000,000,000 MINA is cited in some documentation. Precise maximal supply and emission schedule details are referenced in Mina’s economic whitepaper but are not consolidated in the supplied inputs. Governance is active and increasingly on‑chain: Mina Improvement Proposals (MIPs), Mesa Upgrade snapshot votes, and on‑chain voting processes have driven protocol changes in 2025. Operational and funding functions are split between a Mina Foundation (stewardship) and o1Labs (core development/execution), and the project has completed major fundraising rounds to support ecosystem growth. Looking forward, Mesa upgrades, expanded zkApp capability, and broader oracle/bridge adoption are the principal vectors for ecosystem growth and real‑world use-case expansion.",
  "methodology": "https://blockindex.ai/dscore",
  "classification": {
    "layer": "Layer 1",
    "isToken": false,
    "consensus": "PoS",
    "parentChain": null
  },
  "dScoreComponents": {
    "autonomy": 5,
    "ageHistory": 13,
    "governance": 20,
    "nodeDistribution": 28,
    "initialDistribution": 0
  },
  "decentralizationVerdict": "Decentralized"
}