Community research · Posted article

Project Research Dossier — Miden (pre-TGE ZK privacy rollup)

By Kalhintz

Open original Discord thread

Project Research Dossier — Miden · by kalhintz (Aquila Vanguard) · 2026-09-27 Full PDF attached. Text posted below in parts, sources at the end as [n].

TL;DR Miden is the ZK privacy rollup spun out of Polygon Labs with a private $25M seed. Still pre-TGE with no public sale; testnet v0.16 is billed as the "last stop before mainnet" [1][2][3]. Engineering signal is strong (daily commits, founders match the commit history, OpenZeppelin + Trail of Bits audits) [8][12][13][14], but almost none of the tokenomics are public and mainnet fees will be paid in USDCx, not the token [2]. My read: back the tech, treat the token as unpriceable until supply, vesting and utility are published.

0. Eligibility (pre-TGE / no public raise)

  • No public sale: only disclosed raise is a private $25M seed (a16z crypto, 1kx, Hack VC), 2025-04-29 [1]. No sale on the official blog/docs [16][19].
  • No TGE: official Kaito article (2026-01-06) calls it "Pre-TGE" and rewards are "granted on TGE" [3]. v0.16 is the "last major testnet release before mainnet"; only fee asset is faucet "testnet MIDEN" [2]. No official token contract published.

1. Goal ZK rollup ("edge blockchain"): users execute and prove transactions on their own devices, the network only verifies and settles, so state can stay private [16]. Bridges to Ethereum via Agglayer [2][7]. Target: compliant private payments — a private-by-default USDC-backed stablecoin (USDCx) via Circle's xReserve [4], plus programmable assets for regulated issuers [7].

2. Tokenomics — what is and isn't published

  • Total supply, TGE price, FDV, circulating at TGE: not published
  • POL-staker airdrop: "expected to airdrop around 10% of native tokens to POL stakers" [1]; snapshot rules + lockup not published
  • Kaito creator rewards: "0.2% of the total token supply, fully unlocked at TGE" [3]
  • Team / investors / Polygon Labs / treasury / ecosystem (~90% of supply): not published
  • Seed instrument (equity vs token rights) and valuation: not published [1]
  • Emissions / inflation: not published
  • Token utility: not published. Mainnet fees "will be denominated in USDCx" [2] and the fee asset is fixed at genesis [5]; the 2025 roadmap had fees "in the native token" [6], so the design moved away from gas demand for the token.

3. Unlock + dilution risk (modelled only from published figures)

  • Day-1 float from known buckets: at least 0.2% (Kaito) up to ~10.2% if the POL airdrop is also liquid day 1 (undisclosed) [1][3].
  • At ~10% circulating, FDV ≈ 10x market cap; every unpublished bucket is future overhang.
  • No insider schedule is published, so the first insider cliff can't be dated — that gap is itself a risk signal.

Questions I'd want answered before sizing:

  1. Total supply and TGE circulating %?
  2. Team/investor %, cliff, linear length? Did the seed carry token rights, at what FDV?
  3. Polygon Labs allocation? Is "around 10%" final and locked?
  4. Emissions for validators/provers when fees are paid in USDCx?
  5. Token utility (staking, governance, prover collateral)?
  6. Issuing entity, jurisdiction, any planned public sale?

4. Team verification signals Verifiable:

  • Named co-founders: Bobbin Threadbare, Dominik Schmid, Azeem Khan [1].
  • bobbinth: #1 contributor to miden-vm (1,529 commits) and protocol (476); author of the roadmap and engineering updates [6][7][8][17].
  • Dominik1999: 151 protocol commits [8][17]. Azeem Khan: co-founder per own LinkedIn [18] (business role).
  • Engineering depth: 161 miden-vm contributors; in the 30 days to 2026-09-27: 122 commits (VM), 95 (protocol), 92 (node), 212 (compiler); node v0.16.0 shipped 2026-09-07 [8][11].
  • Audits: OpenZeppelin standards library (0 crit / 0 high / 11 med / 17 low, 50 of 60 resolved) [12]; OpenZeppelin multisig (2 high, both resolved) [13]; Trail of Bits found a way for a malicious prover to "forge Falcon signatures and drain any Miden account", fixes merged Mar–Apr 2026 [14][15].

Marketing / unverified:

  • "Ex-Facebook blockchain team" [1] — lead founder is pseudonymous, no primary source ties him to that record.
  • Spearbit audit claimed [7] but no public report found.
  • "Guardrails would have made most issues un-exploitable" [7] is the team's own assessment.

5. Key risks

  • Technical — core crypto still changing before mainnet: founder wrote Poseidon2 "was found to have serious security vulnerabilities in March" [7]; Eidos hashing added in v0.33.0 (2026-09-16) with Poseidon2 still available [9]; v0.34.0 (2026-09-26) closed decoder soundness gaps, invalidating older proofs [9]; VM SECURITY.md still says it "has not been audited" [10]; every audit covers a snapshot that has since changed.
  • Execution — repeated delays: mainnet due "later this year" (Apr 2025) [1], then "mainnet alpha by the end of July" (Apr 2026) [7]; still testnet in Sept 2026 [2][11].
  • Centralization: team runs the validator after mainnet; third-party Gateway runs RPC, explorer, remote provers and AggLayer proxy [7]. No governance framework published [6].
  • Incentives: USDCx fees remove gas demand for the token [2][5]; USDCx depends on Circle's xReserve [4]; the ~10% airdrop is built-in sell pressure [1].
  • Legal/regulatory: private-by-default payments draw scrutiny; issuer entity and jurisdiction unpublished.

6. Disclosure No holdings, no position, no compensation from the project. Written as part of a rewarded Legion Republic education quest (Eastern Campaigns). Challenges welcome — happy to defend or correct any claim.

Sources (primary only) 1/2 [1] https://polygon.technology/blog/miden-raises-25m-from-a16z-crypto-1kx-and-hackvc-to-build-the-edge-blockchain [2] https://www.miden.xyz/blog/testnet-v0-16 [3] https://x.com/0xMiden/status/2008524030215622820 [4] https://www.miden.xyz/blog/usdcx-on-miden-stablecoins-with-privacy [5] https://github.com/0xMiden/protocol/blob/next/docs/src/fees.md [6] https://hackmd.io/@bobbinth/ByhShQBEgg [7] https://hackmd.io/@bobbinth/rk_YT47AZx [8] https://github.com/0xMiden [9] https://github.com/0xMiden/miden-vm/blob/next/CHANGELOG.md

Sources (primary only) 2/2 [10] https://github.com/0xMiden/miden-vm/blob/next/SECURITY.md [11] https://github.com/0xMiden/node/releases [12] https://www.openzeppelin.com/news/miden-smart-contracts-audit [13] https://www.openzeppelin.com/news/miden-multisig-cryptography-audit [14] https://blog.trailofbits.com/2026/09/18/auditing-in-the-age-of-good-enough-ai/ [15] https://github.com/0xMiden/miden-vm/pull/2808 , https://github.com/0xMiden/miden-vm/pull/2968 [16] https://docs.miden.xyz/ [17] https://github.com/bobbinth , https://github.com/Dominik1999 [18] https://www.linkedin.com/in/theazeemkhan [19] https://www.miden.xyz/blog

Attached source files