Florida’s HB 1039 Revives a State Bitcoin Reserve—Outside the Treasury and Under CFO Control
Florida’s HB 1039 would create a state crypto reserve outside the treasury, run by the CFO. A $500B cap rule effectively narrows it to Bitcoin. Target start: July 1, 2026.

Because Bitcoin
January 8, 2026
Florida is taking another swing at a state Bitcoin reserve—this time with a different chassis. HB 1039, filed this week by Rep. John Snyder, would establish a “Florida Strategic Cryptocurrency Reserve” outside the State Treasury and place custody and management squarely with the Chief Financial Officer. The bill follows two withdrawn efforts last year (HB 487 and SB 550) that aimed to allocate up to 10% of state funds into Bitcoin.
The new design matters more than the headline. Moving the reserve outside the treasury reframes it from a budgetary line item to a managed investment pool, with the CFO empowered to acquire, exchange, sell, or retain assets under a prudent‑investor standard. That structure can reduce appropriation friction, speed decision-making, and ring‑fence volatility from day‑to‑day budgeting—while also concentrating accountability and execution risk in one office.
The asset screen is intentionally tight. HB 1039 doesn’t name Bitcoin, but it requires any holding to maintain a market cap of at least $500 billion over the prior two years. Today, only Bitcoin clears that bar. Bitcoin’s market value sits above $1.8 trillion, while Ethereum is roughly $377 billion—well below the threshold. The two‑year lookback discourages flavor‑of‑the‑month rotates and signals a long‑duration policy intent without saying “Bitcoin only.”
Supporters will point to policy goals etched into the bill: enhance financial resilience, hedge inflation and macro volatility, and strengthen security for residents. The governance overlay is a five‑person advisory committee led by the CFO, with four appointees and at least three members possessing crypto investing experience. That mix could bring needed domain expertise but will require careful conflict‑of‑interest rules, clear decision rights, and transparent reporting to maintain public trust.
What I’m watching is execution architecture. A reserve like this lives or dies on operational hygiene: institutional‑grade custody, segregation of duties, multi‑sig with quorum policies, disaster recovery, audit trails, and incident response. If Florida treats the reserve like any other state investment pool—RFPs for custodians, independent auditors, and standardized valuation policies—it can mitigate a large chunk of tail risk. If it chases tactical trading to “outperform,” it invites headline risk that can swamp whatever diversification benefit Bitcoin might provide a sunbelt state’s balance sheet.
Politically, this construct gives legislators plausible deniability on timing and sizing. The statute doesn’t fix allocation percentages or mandate calendar‑based buys. It delegates discretion to the CFO under a prudent standard, which can be a strength (nimbleness) or a liability (second‑guessing after drawdowns). Communication discipline—think quarterly fact sheets, risk bands, and a clear objective function—will matter as much as price action.
Florida wouldn’t be alone. Only three states—New Hampshire, Arizona, and Texas—have passed crypto reserve legislation so far, while at least 17 others have bills pending and several have already rejected similar proposals. HB 1039 targets an effective date of July 1, 2026, if enacted, leaving time to build the rails before any allocation. That runway is useful; sober infrastructure beats hurried headlines.
Taken together, HB 1039 is less about bravado and more about governance. By isolating the reserve from the treasury, narrowing the asset universe through a durable market‑cap filter, and centralizing stewardship with the CFO plus an advisory committee, Florida is testing a model that could be copied if it performs—or quietly shelved if it doesn’t.