The Vote That Stalled a First
New Hampshire's Executive Council voted 3-2 on July 8 to reject a proposed $100 million municipal bond that would have used Bitcoin as collateral. Had it passed, it would have been the first bond of its kind issued through a U.S. state-affiliated finance authority.
Municipal bonds are how state and local governments — and the quasi-public agencies that work alongside them — raise capital for everything from infrastructure to private business financing, typically at favorable tax-exempt interest rates. Tying one to Bitcoin collateral would have opened a new, cheaper channel for Bitcoin-adjacent borrowers to raise money, backed by the state's bond machinery rather than a bank balance sheet. That is precisely why the structure drew scrutiny: it asks a public institution to underwrite risk in an asset class it doesn't control the price of.
The deal was arranged through Jefferies and sponsored by the New Hampshire Business Finance Authority (BFA), a quasi-public agency that issues bonds to support private-sector borrowing in the state. The BFA does not lend state money directly — it lends its name and tax-exempt bond authority to qualifying deals. That authority is exactly what the council declined to extend here.
What Was On the Table
The structure was built with a wide safety margin. The borrower would have pledged $175 million worth of Bitcoin — roughly 75% more collateral than the $100 million raised — with an independent third-party custodian holding the coins outside the state's control. If the collateral's market value fell below $140 million, the arrangement would have automatically unwound, closing out the position before the state or bondholders faced a shortfall.
On paper, that is a conservative structure: over-collateralized, custodied by a third party, with a built-in liquidation trigger well above the break-even point. Backers of the bond argued it posed no direct risk to New Hampshire taxpayers, since the BFA was not putting public funds at risk — only its name.
Why It Matters
The council's objection wasn't really about the mechanics. It was about what the state would be seen to be endorsing. Council member Karen Liot Hill, one of three votes against the bond, put it directly: she said she is "not opposed to Bitcoin or cryptocurrency in general," but argued that approving the bond meant the state would be "lend[ing] a kind of legitimacy to a financial transaction" tied to "an emerging asset class that has been shown to be very volatile." Fellow council members Janet Stevens and David Wheeler joined her; Joseph Kenney and John Stephen voted in favor.
That reasoning is notable given where it came from. New Hampshire is not a Bitcoin skeptic state — it was the first in the country to pass a Strategic Bitcoin Reserve law, HB 302, signed in May 2025, which lets the state treasurer allocate up to 5% of certain state funds into Bitcoin directly. A state that has already legislated a path to holding Bitcoin on its own balance sheet still balked at lending its bond authority to a third party's Bitcoin-collateralized financing. The distinction the council drew — between the state choosing to hold an asset itself versus certifying someone else's use of that asset as creditworthy — is one that other states weighing similar proposals will likely draw too.
This is also a data point on how municipal finance intends to treat Bitcoin collateral generally. Credit considerations reportedly weighed on the vote as well, with the bond's rating falling short of investment grade — a reminder that traditional fixed-income gatekeepers still price Bitcoin-backed structures well outside the conservative end of the municipal bond market, regardless of how much over-collateralization is built in.
That gap between "conservative on paper" and "junk-rated in practice" is the real story here. A 75% collateral buffer and an automatic unwind trigger are the kind of protections that would make almost any other asset-backed bond investment grade. That they weren't enough for Bitcoin collateral shows how much of a volatility discount rating agencies and elected officials still apply to the asset, independent of the deal structure wrapped around it.
What's Next
The proposal is not dead. BFA officials have said they intend to address the council's concerns — likely around disclosure, custody transparency, or the credit rating — and bring a revised version back for reconsideration. Given that two of five council members already voted yes, a narrower or better-collateralized structure could plausibly flip the outcome on a second pass.
The broader signal is that state and local governments are actively experimenting with Bitcoin-linked financial products, not just reserve legislation. Municipal bonds, pension allocations, and treasury policy are becoming a real front in Bitcoin's institutional adoption story — and this vote shows that front comes with friction, not automatic approval, even in states already friendly to the asset.
Bitcoin Gate Take
A 3-2 vote against, in the single most Bitcoin-friendly legislature in the country, is a useful reality check: legitimizing Bitcoin as a personal or state reserve asset is a different political lift than legitimizing someone else's leveraged use of it. We'd expect more of these proposals to surface at the state and municipal level over the next year, and more of them to fail on their first attempt before a cleaner structure gets through. None of this changes the case for holding Bitcoin directly rather than through a third party's structured product — which is the approach our DCA and retirement tools are built around.