Indiana Governor Mike Braun signed House Bill 1042 into law, putting the state on a defined path to embed cryptocurrency access inside certain public retirement and deferred compensation programs. The statute requires eligible plans to offer at least one crypto investment option through self-directed brokerage accounts, expanding participant choice while pushing administrators to operationalize new custody, valuation, and risk controls.
The legislature approved the bill by a 59–33 vote, and the implementation timeline is staggered. The retirement brokerage requirement is scheduled to begin on July 1, 2027, while most other provisions take effect on July 1, based on the statute’s effective-date language. That runway gives plan sponsors time to stand up vendor due diligence, participant communications, and auditable governance frameworks before crypto access becomes mandatory.
What the law requires from retirement plan platforms
At its core, HB 1042 directs public retirement boards, deferred compensation committees, and annuity savings programs to make self-directed brokerage accounts available with at least one cryptocurrency investment option. The law allows participants to allocate funds to Bitcoin, other cryptocurrencies, or crypto-linked exchange-traded funds, but it explicitly excludes stablecoin-related funds, narrowing the menu and reducing exposure to instruments the statute treats as out of scope.
The bill also preserves decision rights for fiduciaries. Boards retain authority to set allocation limits, oversee which options appear inside the brokerage lineup, and ensure valuations reflect prevailing market prices. In practice, that means boards can widen or tighten access based on volatility tolerance, participant suitability posture, and broader portfolio governance, rather than being forced into an unlimited “anything goes” model.
Administrators, however, inherit the heavy lift on execution. Accurate valuation and market-price integrity become non-negotiable operational requirements, which typically implies reliance on regulated custodians, robust market-data feeds, and reconciliation routines that can stand up to audit. Even with a self-directed brokerage structure, plan-level fiduciary duty still drives expectations around vendor selection, disclosures, and controls that prevent avoidable operational errors.
Privacy, mining, and implementation pressure points
HB 1042 also goes beyond investment access by laying out user-protection concepts around custody and legal process. The statute defines cryptocurrency as a virtual currency not issued by a central authority and includes provisions that protect self-custody of private keys while restricting courts from compelling key disclosure unless no other admissible information exists. Those provisions create clearer legal contours for participants who control keys, but they don’t remove the need for plan administrators to maintain sound AML/KYC alignment and custodial governance when integrating crypto options into institutional platforms.
Separately, the law includes language intended to protect miners and mining operations from “unreasonable restrictions” and to safeguard industrial zoning for lawful mining activity. That piece matters less for retirement plan menus and more for state-level infrastructure posture, but it underscores that the statute is trying to reduce friction across the broader digital-asset stack, from investment access to operational footprint.
The practical takeaway for plan sponsors and vendors is straightforward: July 1, 2027 is the hard operational deadline for brokerage availability, and meeting it will require updated governance playbooks, contractual controls with brokers and custodians, consistent valuation policies, and clear participant communications about volatility and allocation limits. The winners will be the teams that treat this as an implementation program—not a policy headline—and build the controls before the mandate arrives.