Labor Department rule on crypto in 401(k)s sent to White House for final review
Labor Department rule reaches White House for final review
A final Labor Department rule that could make it easier to include crypto in 401(k) retirement plans has arrived at the White House for review. Bloomberg Law reported the development on Thursday.
The review is described as a procedural step that usually comes before a rule is released to the public. The final text has not been published yet.
Rule at a glance
- The Office of Information and Regulatory Affairs logged the package on Nov. 5.
- The package is listed as a final rule and as economically significant.
- The March proposal would give legal protection to plan decision-makers who follow a set process.
- Following that process would not require any plan to offer crypto.
What the review filing shows
The filing lists the title as “Fiduciary Duties In Selecting Designated Investment Alternatives.” It uses reference number RIN 1210-AC38.
The Labor Department’s Employee Benefits Security Administration is listed as the office behind the rule. The filing says there is no legal deadline for the review to be completed.
What the March proposal would allow
The Labor Department unveiled the proposal on March 30. It covers alternative assets, including private equity, real estate and cryptocurrency.
Under the draft, fiduciaries — the people responsible for choosing investments for a plan — would receive a legal safe harbor under the Employee Retirement Income Security Act of 1974 if they followed a documented process. A safe harbor is a defined protection when stated conditions are met.
The proposal names six factors: performance, fees, liquidity, valuation, performance benchmarks and complexity. The Labor Department said prudence is based on process, and fiduciaries would keep discretion over what investments they select.
The rule would not force plans to offer crypto. It would lower legal risk for employers that choose to add private assets to a plan menu.
How earlier federal decisions led here
President Donald Trump signed an executive order on Aug. 7, 2025. It directed the Labor secretary to review ERISA guidance and, where appropriate, propose rules with safe harbors.
The order listed alternative assets including private-market equity and debt, real estate, actively managed vehicles that invest in digital assets, commodities, infrastructure and lifetime-income strategies.
In May 2025, the Labor Department rescinded a March 2022 compliance release. That release had told fiduciaries to use “extreme care” before putting cryptocurrency on a 401(k) menu. The department said that phrase was not in ERISA and restored a context-specific standard.
Deputy Labor Secretary Keith Sonderling said: “The department’s days of picking winners and losers are over.”
What is still not public
The final text is not yet public. It is not clear whether the six-factor safe harbor remained unchanged after comments.
It is also not clear how digital-asset vehicles are described in the final version or what effective date the Labor Department chose. Comment volume on the proposal was described as heavy, with industry and labor groups taking opposite positions.
Why this matters for plan menus
The review office checks the package before a final rule can be published. Bloomberg Law said the arrival of the package signals it is nearing completion.
The same office reviewed the proposed version in late March. That earlier review took about two months after a January submission, according to prior Bloomberg coverage cited in the report.
If the final rule keeps the March approach, plan committees would have a clearer process to follow if they want crypto exposure. The report notes this would not put bitcoin or crypto on every plan menu overnight. It also cites more than 90 million defined-contribution savers and a roughly $12 trillion 401(k) market.
What happens next in the review process
The review office must return the rule before the Labor Department can post it. The next step is how quickly that review is completed and whether the published rule still provides the process protection described in the March draft.