Arbitrum treasury runway faces spot-price challenge

On Sept. 3, a post on the Arbitrum Foundation Forum made an argument treasury accountants probably don’t want to hear: the standard DAO runway calculation is built on an assumption that breaks the moment you try to act on it.

The author, solr, didn’t cushion the point. “Runway gets quoted as treasury divided by monthly burn, with the native token counted at spot price. That number is almost always wrong, and wrong in the same direction.” The mechanism isn’t complicated. Selling a large native-token position into an open market moves the price against you the whole way down — and the damage compounds rather than running linearly.

The worked example is where it gets uncomfortable. Nominal treasury of $16 million, monthly burn of $180,000. Mark tokens at spot: 89 months of runway. Haircut the price by half: 49 months. Model the actual market impact of liquidating — the selling pressure, the slippage, the price moving against you in real time — and you get 18. Solr put it plainly: “The runway you can actually finance is the one where you had to sell, not the one on the dashboard,” and separately noted that “the gap between the first and third figure is the one that matters for planning,” finding it exceeded half across most treasuries they’d modeled. That third figure, 18 months, is roughly 20.2% of the 89-month headline sitting in the dashboard.

A fourth scenario strips it back further: stablecoins only, no selling. Ten months of coverage — $1.8 million against the $180,000 monthly burn. Four answers from one nominal treasury: 89, 49, 18, 10. The spread is determined entirely by what you assume is actually sellable and at what price.

Timing makes this worse. Liquidity thins during market drawdowns, which is exactly when a cash-strapped DAO is most likely to reach for reserves.

Nothing in the forum record suggests Arbitrum DAO has moved to revise its methodology.