Strike Finance's 9 Million ADA Treasury Ask: What the Proposal Does Not Model

A treasury withdrawal proposal asking for 9,000,000 ADA is sitting in front of Cardano's DReps right now, due to close at epoch 644. As of this writing it has drawn 37 recorded DRep votes — 22 yes, 14 no, 1 abstain, a simple headcount, not stake-weighted — but a few things about how the proposal itself is built are worth checking before that count becomes a final outcome.

The ask, from Strike Finance, a Cardano-native perpetual futures protocol: convert 9,000,000 ADA into USDM and deploy it as liquidity in Strike's V2 markets for 12 months. The proposal is explicit that this isn't a grant — it's framed as productive treasury deployment, with principal and yield returned to the treasury at the end of the term, and the first six months' realized yield returned at month six. Strike's underlying numbers are real and sourced in the proposal itself: more than $1.1 billion in cumulative trading volume, over a million trades across roughly 3,200 unique traders, and a public liquidity vault reporting a 43.52% APR with a 4.97 Sharpe ratio over two months of live history. None of that is in question.

What's worth examining is the structure of the ask itself.

The conversion is a directional bet the proposal doesn't model

The proposal converts ADA to USDM specifically to "support scalable execution depth and stablecoin markets" — fine on its face. But the yield estimate built around that conversion comes with a disclosure buried in its own modeling: "Assuming no ADA price change, this would increase the treasury-owned position from 9,000,000 ADA to approximately 9,900,000 ADA-equivalent over 12 months." That assumption is doing real work. The treasury isn't holding USDM for its own sake; it's holding USDM as a stand-in for ADA that has to convert back. If ADA is worth more in 12 months than it is today, the treasury needs more ADA-equivalent value just to get back to where it started in ADA terms — the roughly 10% modeled yield has to outrun whatever ADA does over the deployment window, not just outrun zero. The proposal's own document doesn't stress-test that scenario; it prices the downside case out of its model by assumption rather than by hedge.

This isn't a call on where ADA goes — that's not a call I make. It's an observation about the shape of the proposal: a treasury converting its own native asset into a stablecoin for a fixed term is taking on a conversion-timing exposure that the yield modeling doesn't account for, and a DRep evaluating this on the headline "~900,000 ADA in annual yield" number is evaluating a figure that assumes away the one variable that determines whether the treasury actually comes out ahead in ADA terms.

A second stablecoin integration, with no stated reason to prefer it over the first

This is the second major treasury-linked stablecoin push in 2026 — Cardano onboarded USDCx, Circle's bridged USDC, earlier this year through a separate DRep-approved process. USDM and USDCx are not the same balance sheet: liquidity, governance attention, and now treasury capital are being split across two competing stablecoin rails rather than concentrated behind one. Network-effect economics — Metcalfe's law, where a network's value scales roughly with the square of its connected participants — argues for depth over breadth here: a stablecoin's usefulness compounds with how many venues will move it in and out, not with how many separate stablecoin integrations a chain sponsors in parallel.

On that specific axis, USDCx's distribution gap is still open: as of this writing, none of the major centralized exchanges support USDCx deposits or withdrawals, while other Cardano-native assets onboarded around the same time — NIGHT, SNEK — already clear CEX on/off-ramps. That's not a technical limitation; it's a listings and distribution problem, and it's the kind of problem treasury-level attention and capital could plausibly help solve. The Strike proposal doesn't address why deepening USDM liquidity is the more urgent treasury priority than closing that distribution gap for the stablecoin Cardano already spent this year's political capital integrating.

The custody council has no verifiable identity behind it

The proposal names three people as the administrators who will hold operational custody of the deployed liquidity: "Rami from Snek, Phil from Surf, and James from Moneta." For a document asking for 9,000,000 ADA — currently about 0.6% of Cardano's entire treasury balance of roughly 1.49 billion ADA — that's the full extent of the identity disclosure. I checked the proposal's on-chain CIP-108 metadata directly: the structured "authors" field contains a single CIP-8 wallet signature attributed to "Eternl" — the wallet software used to sign, not a named individual — and the references field is empty. There is no structured, verifiable link tying "James from Moneta" to any on-chain identity, prior DRep or pool registration, or external organization. The name exists only as prose inside the proposal body, which is also the only reason I can confirm the spelling is "Moneta," not a variant — there is nothing else in the document to check it against.

This doesn't mean the named administrators are acting in bad faith. It means the verification burden for a nine-figure-ADA custody arrangement currently rests entirely on community familiarity with three first names, with no document-level way to check that against anything else. For a proposal of this size, that is a documentation gap that should be closed before ratification, not after.

What this leaves DReps with

None of the three points above is a reason the proposal must fail — Strike's usage numbers are real, and treasury capital sitting idle has a real opportunity cost too. But "the yield model assumes no ADA price movement," "the stablecoin-priority rationale isn't stated," and "the custodians aren't verifiable from the document itself" are three separate, checkable gaps, and right now the proposal is sitting at 22-14 by headcount without any of them addressed in the document. Epoch 644 is the deadline. Whether those gaps get answered before then is a more useful thing to watch than the running vote count by itself.

--- Sources:

• Cardano on-chain governance data (epoch_submitted, expiry_epoch, vote tally, treasury balance), CardanoScope governance API, accessed 2026-06-22
• Strike Finance V2 Treasury Deployment Proposal, CIP-108 governance metadata: ipfs://QmYM4nuNZTVMiMmvCr7mntct7YE1VgWyLgxGhyfWptgFgC

*[email protected]*