New Hampshire board conditionally approved a $100 million digital-currency bond

The New Hampshire Business Finance Authority voted on November 17, 2025 to grant conditional final approval for as much as $100 million of revenue bonds supporting a project to acquire and hold digital currency. The unanimous action created a pathway for cryptocurrency to serve within a state-authorized bond-financing structure, but it did not place a bond, transfer proceeds or commit taxpayer money on November 17.

The board’s official minutes recorded a motion under New Hampshire RSA 162-I, followed by affirmative votes from all nine directors listed for the decision. Approval was conditioned on receiving counsel’s opinion that the bond had been duly authorized and was permitted under the statute. The event-day record described “digital currency” without naming Bitcoin, a borrower, custodian, collateral ratio, interest rate or maturity.

Why the authorization mattered

Private crypto lenders had already accepted digital assets as collateral, but the November 17 vote brought that concept into public-finance infrastructure. New Hampshire’s Business Finance Authority is a state-created financing agency able to issue revenue bonds for eligible projects. Its involvement could give a private transaction access to an established issuance framework while separating the financing from a direct state investment in cryptocurrency.

That distinction is essential. The proposed bonds were not the same as New Hampshire buying Bitcoin for its treasury, and the authorization did not make Bitcoin legal tender or guarantee the debt with state tax revenue. Under RSA 162-I, a project user is generally responsible for payments sufficient to service the bonds. The statute also requires issued bonds to state that they are not indebtedness of New Hampshire or the authority except where the law specifically permits otherwise.

What was approved—and what remained unresolved

The board approved a resolution authorizing bonds up to a ceiling of $100 million. “Up to” did not establish the amount that would ultimately be issued, and authorization was not evidence that investors had purchased securities. No event-day offering document reviewed for this reconstruction disclosed a coupon, sale price, maturity schedule, borrower credit profile, liquidation mechanism or quantity of digital currency.

The counsel condition was substantive rather than ceremonial. The minutes required an opinion that the transaction was authorized and permitted under RSA 162-I. Separately, that chapter provides that the authority cannot issue bonds for an eligible facility until New Hampshire’s governor and Executive Council make required public-use, feasibility and financing findings. The November 17 board vote therefore represented an institutional approval milestone, not completed financing.

Details disclosed after November 17

In an announcement dated November 18 and posted on November 19, the authority identified the contemplated instrument as a $100 million Bitcoin-backed municipal bond. It named Wave Digital Assets and Rosemawr Management as structuring participants, Orrick as legal adviser and BitGo Trust as the intended custodian for Bitcoin collateral. The authority said issuance remained subject to approval by the governor and Executive Council and asserted that no taxpayer funds or state guarantee would be at risk.

New Hampshire Public Radio reported on November 21 that CleanSpark, a publicly traded Bitcoin miner, was the intended borrower and would use Bitcoin holdings as collateral for a private loan. The report also said a lender had not yet been selected. Those details were later clarifications attributed to the authority’s executive director; they were not contained in the November 17 public minutes.

The event-day conclusion

What the November 17 record establishes is narrow but consequential: a state financing authority unanimously authorized, subject to legal and governmental conditions, a bond project centered on holding digital currency. It did not establish that any bond had been issued, any Bitcoin had been pledged or any investor had assumed exposure. Those milestones required separate documentary verification after the board’s vote.