On April 17, 2024, the New Hampshire Executive Council cast a vote that turned a $1 billion Bitcoin experiment into a five-line news footnote. The tally was 4-0. No debate. No compromise. Just an administrative guillotine dropping on House Bill 302. Code does not lie, but it often omits the truth. In this case, the code was written in legal language and the omission was a cold 4-0 vote.
The bill, championed by state Representative Keith Ammon, proposed authorizing the state treasurer to issue up to $1 billion in general obligation bonds. The proceeds would be used to purchase Bitcoin and other digital assets, creating a state-managed digital asset reserve. The stated goal: hedge against inflation, diversify the state's investment portfolio, and capture the upside of a new asset class. Ammon argued that New Hampshire, with its libertarian roots and pro-crypto stance, should lead the sovereign adoption movement. The Executive Council disagreed.
Context: The Sovereign Adoption Hype Cycle
This is not the first time a U.S. state has flirted with putting Bitcoin on its balance sheet. In 2022, Arizona proposed a bill allowing state retirement funds to invest in crypto. Texas has considered a strategic Bitcoin reserve. Wyoming has already created a crypto-friendly banking charter. But none have gone as far as New Hampshire's HB 302—a direct state purchase using bonded debt. The proposal was aggressive, almost experimental. It assumed that Bitcoin's long-term appreciation would outpace the bond interest and provide a net positive return to the state's coffers. The hype around this idea was modest but real: if a state can do it, the narrative of Bitcoin as a reserve asset gains credibility.
However, the Executive Council's rejection signals a deep skepticism. The council members, all Republicans, cited concerns over volatility, regulatory uncertainty, and fiduciary duty. But those are surface-level reasons. The real structure of the proposal carried fatal technical flaws that a risk management consultant would spot immediately.
Core: The Systematic Teardown
I have spent nearly two decades auditing financial systems—first in traditional risk management, then in blockchain engineering. My work on the LUNA-UST collapse taught me to look for circular dependencies. HB 302 was a textbook example of a feedback loop error. The state would issue bonds (debt) and use the proceeds to buy Bitcoin (an asset). The bonds require regular interest payments. The only source of those payments would be either the state's general fund (i.e., taxpayer money) or the appreciation of the Bitcoin itself. If Bitcoin goes up, the state can sell some to pay the interest, or the capital gains cover the cost. If Bitcoin goes down, the state faces a double hit: the asset value drops, and the interest obligations remain.
Consider the math. The bonds would carry an interest rate of roughly 3.5% based on New Hampshire's AA credit rating. On $1 billion, that is $35 million per year. To cover that through Bitcoin sales alone, the state would need to liquidate approximately 0.5% of its Bitcoin holdings annually (assuming a $70,000 Bitcoin price). But that assumes the price stays flat. If Bitcoin drops 50% to $35,000, the interest cost remains $35 million, but the liquidation now requires selling 1% of the portfolio. Worse, the mark-to-market loss on the $1 billion investment would be $500 million. The state's net equity in the fund would become negative if the Bitcoin value falls below the bond principal. This is a classic leverage trap.
Based on my experience modeling DeFi liquidity pools, I can state with confidence that the probability of a 50% drawdown in Bitcoin within any given two-year period is non-trivial—greater than 30% based on historical volatility. The proposal had no stop-loss mechanism, no margin call trigger. The only safeguard was the assumption that the state would hold for ten years and ignore interim volatility. That is not a risk management strategy; it is a bet. Hype builds the floor; logic clears the debris.
Furthermore, the bill did not specify how the state would custody the Bitcoin. Would it use a third-party custodian like Coinbase or NYDIG? Or would the state hold its own keys? If the latter, the risk of key loss or operational error becomes a national security concern. If the former, the counterparty risk of a regulated custodian failing or being hacked is transferred to the state's balance sheet. The bill's text was silent on this. An omission that would have become a catastrophe in a real-world exploit.
The Executive Council's decision, while politically convenient, was mathematically prudent. A 4-0 vote indicates unanimity. No dissenter argued for the bill. That suggests that the council's legal and financial advisors likely flagged the leverage risk and the lack of risk framework. The council did the equivalent of a smart contract audit and found an infinite loop.
Contrarian: What the Bulls Got Right
Yet I must acknowledge where the proponents were right. Representative Ammon correctly identified that state treasuries are poorly diversified. Most states hold nearly all their funds in cash and bonds, which are exposed to inflation and currency debasement. Bitcoin, by contrast, is a non-sovereign, deflationary asset with a fixed supply. Over the past decade, it has outperformed every major asset class. A 1% allocation to Bitcoin could have captured significant upside without jeopardizing the entire portfolio. The bill's scale—$1 billion out of New Hampshire's $5 billion general fund—was actually a 20% allocation, which is aggressive but not insane if structured as a long-term hold. The mistake was the bond financing. If the state had simply allocated a portion of its existing cash reserves to Bitcoin, without issuing debt, the risk would have been symmetric: the state could hold and wait. The bond structure introduced a time-bomb of interest payments.
Also, the committee's decision may be short-sighted. Other states are moving forward. Wisconsin's investment board has already bought Bitcoin ETFs. Texas is exploring a Bitcoin reserve. New Hampshire just closed the door on a $1 billion opportunity that, in ten years, might look like a massive missed gain. In a decade, when Bitcoin is at $500,000, the state will have lost the chance to have a half-billion-dollar surplus. The bulls' argument rests on the long-term trend of Bitcoin adoption. They are not wrong on the fundamental trajectory. They are wrong on the execution vehicle.
Takeaway: The Kill Switch Logic
Every financial instrument should have a "kill switch" section—a set of conditions under which the project fails. For HB 302, the kill switch is now engaged. The Executive Council pulled the trigger. But the lesson extends beyond one state. The failure of HB 302 provides a template for how not to propose sovereign Bitcoin adoption. The next attempt must roll its own risk management: no leverage, clear custody, volatility buffer, and a ten-year time horizon without debt. Until that happens, the narrative of sovereign adoption will remain a theoretical concept, not a fiscal reality. Trust is a variable; verification is a constant. The New Hampshire Executive Council verified that the proposal was not ready. The math does not care about your hope.
