The US Labor Department’s proposed 401(k) rule reached the White House for final review on Thursday, placing crypto assets led by Bitcoin at approximately $1.5 trillion in market capitalization and Ether at approximately $273 billion closer to retirement-plan consideration without dictating which digital assets qualify.
The proposal is not a blanket approval for direct crypto exposure in retirement accounts. It is a framework intended to make alternative investments easier to offer while extending some legal protection to employers and plan managers. The unresolved issues are the ones that will shape real implementations: asset selection, product structure, liquidity controls, valuation methodology, and the legal accountability that remains when investment decisions are challenged.
Key takeaway: The proposed US Labor Department rule would make crypto access in 401(k) plans more feasible, but it shifts the decisive burden to plan managers to demonstrate disciplined asset selection, product governance, and documented decision-making.
What has the US Labor Department proposal actually changed?
The US Labor Department proposal has moved crypto from an area constrained by earlier guidance toward a principles-based retirement-plan assessment, but the proposal does not identify approved digital assets or remove liability for individual investment decisions. The rule reached White House review after a March proposal that directs plan managers to assess performance, fees, liquidity, valuation, benchmarks, and complexity.
The proposal’s practical relevance comes from its broad wording. Rather than setting a list of permitted cryptocurrencies, a minimum market-capitalization threshold, or a strict requirement to use exchange-traded funds or managed funds, the proposal outlines decision factors. That structure gives plan managers flexibility, but flexibility also raises the standard for internal governance.
A 401(k) provider assessing crypto exposure would need to explain why a chosen asset or product meets each of the stated considerations. The absence of an eligible-asset list means selection decisions cannot be outsourced to a government-approved catalogue. The absence of a market-cap floor means scale alone cannot serve as a complete suitability test.
Bitcoin and Ether illustrate the difference between market prominence and retirement-plan eligibility. Bitcoin was approximately $1.5 trillion by market capitalization at 20:01 UTC on Nov. 6, while Ether was approximately $273 billion. Those figures establish their relative scale in the digital-asset market, but the proposed framework calls for additional analysis of liquidity, fees, valuation, benchmarks, complexity, and performance.
For plan managers, the core question is not simply whether an asset is widely recognised. The question is whether the plan can document a repeatable process for selecting, monitoring, changing, or removing an investment option. That process must work when markets are calm and when market conditions test the assumptions recorded during product approval.
| Proposal element | What the March proposal says | Governance consequence for a 401(k) plan |
|---|---|---|
| Eligible digital assets | The proposal does not specify which digital assets could be included | A plan manager must maintain an asset-selection rationale rather than rely on a named eligibility list |
| Market capitalization | The proposal sets no minimum market-capitalization requirement | Bitcoin at approximately $1.5 trillion and Ether at approximately $273 billion do not receive automatic preference solely from scale |
| Investment vehicle | The proposal does not limit crypto investments to ETFs or managed funds | A plan manager must assess the structure of each proposed product, including direct crypto exposure |
| Selection criteria | Performance, fees, liquidity, valuation, benchmarks, and complexity | A plan manager needs evidence and documented review across all six stated factors |
| Litigation protection | The proposal offers some protection from lawsuits but does not bar suits over investment decisions | Process quality and contemporaneous records remain central to legal defensibility |
The policy direction is therefore permissive rather than prescriptive. That distinction matters: a permissive framework can support responsible crypto access, but it does not replace the controls needed to make that access suitable for retirement-plan participants.
Why are ETFs and managed funds likely to appear before direct crypto holdings?
ETFs and managed funds are likely to be offered before direct crypto holdings because they can place custody, trading, valuation, and operational decision-making within a defined product structure, even though the Labor Department proposal does not require those vehicles. The proposal leaves direct holdings in scope, while industry expectations point toward structured products as the earlier route for plan availability.
A retirement plan does not need to treat all forms of crypto exposure as equivalent. Direct holdings, exchange-traded funds, and managed funds can all reference the same underlying market while creating different operational responsibilities for the plan manager. The proposal’s six-factor framework makes those distinctions more consequential.
Direct crypto exposure puts sharper focus on how assets are held, valued, accessed, and monitored. A managed vehicle can define those functions within its product design. An ETF can similarly offer a familiar wrapper for a retirement-plan menu. Neither structure eliminates risk, but each can make the investment process easier to define and review.
The proposal does not state that ETFs or managed funds are safer. It also does not prohibit a plan from considering direct crypto holdings. The key compliance issue is that the chosen structure must match the plan manager’s ability to assess complexity and preserve evidence of that assessment.
In Soken’s smart-contract and Web3 risk work, the strongest control is rarely a single technical feature. It is a documented system of responsibilities: who selects the exposure, who verifies the mechanics, who monitors the assumptions, and who can act when those assumptions fail.
For a crypto product entering a 401(k) environment, that responsibility map should cover both traditional product governance and blockchain-specific dependencies. A product review should ask what participants own, how the exposure is priced, what triggers a suspension or replacement decision, and what information is available to the people approving the option.
This does not require plan managers to become blockchain protocol operators. It does require them to understand where their obligations begin and end. For instance, a plan manager may not control a digital asset’s network, but the plan manager remains responsible for the rationale used to select a product that references that network.
Soken’s technical security and development services can support the technical side of such diligence, especially where product structures involve smart contracts, custody flows, pricing integrations, or permissions. A technical review cannot decide investment suitability, but it can establish whether operational claims made by a crypto product have credible security foundations.
How should plan managers apply the six stated selection factors?
Plan managers should apply performance, fees, liquidity, valuation, benchmarks, and complexity as a connected decision record, not as six isolated boxes on an approval form. The Labor Department proposal specifically identifies those six factors, and each factor can alter the conclusion reached under the others when a retirement plan assesses Bitcoin, Ether, an ETF, a managed fund, or direct crypto exposure.
Performance should not become shorthand for historical price appreciation. For a retirement-plan decision, the useful question is whether the performance information used in an assessment is understandable, consistently measured, and relevant to the exposure being offered. Any assessment should distinguish the performance of a digital asset from the performance of a particular product that references that asset.
Fees require the same precision. A plan manager should identify the fees participants see and the costs embedded in a product’s operation. Different product structures may distribute costs differently, which makes direct comparison difficult unless the evaluation records what is being compared.
Liquidity is especially material because retirement-plan participants need an investment option whose dealing and valuation processes are comprehensible. Liquidity analysis should address the asset market, the product mechanism, and the conditions under which participant transactions are processed. A liquid underlying asset does not automatically make every vehicle that references it equally liquid in practice.
Valuation should address the source, frequency, and governance of pricing. Crypto markets operate through multiple venues and products may use their own calculation methods. A plan manager should be able to state how a product’s value is determined and how the process responds to disrupted or inconsistent market data.
Benchmarks require a clear reference point. A benchmark should enable meaningful comparison rather than create a superficial impression of objectivity. Complexity ties the other factors together: the more intricate the product structure, the more carefully a plan manager should test whether fees, liquidity, valuation, and benchmarks remain intelligible.
A useful review sequence is:
- Define the proposed crypto exposure precisely, including whether it is direct crypto, an ETF, or a managed fund.
- Record how the proposal performs against performance, fees, liquidity, valuation, benchmarks, and complexity.
- Identify the assumptions that must remain true for the option to remain appropriate.
- Assign responsibility for monitoring those assumptions after approval.
- Define what evidence would prompt reassessment, replacement, or removal of the option.
- Retain the decision record and the materials used to form it.
This approach turns the six factors into a living governance process. It also makes the plan manager’s decision more explainable if the investment later receives scrutiny.
Does lawsuit protection remove legal and fiduciary exposure?
The proposed rule would provide plan managers with some lawsuit protection, but it would not prevent lawsuits over investment decisions, meaning legal exposure remains tied to the quality of each selection and oversight process. The proposal’s protection is therefore not a substitute for documented governance, product diligence, participant disclosures, or clear allocation of decision-making responsibility.
This limitation should shape implementation from the start. A legal protection that does not bar suits over investment decisions does not reward passive adoption. It rewards plan managers who can show that their decision followed an informed process aligned with the proposal’s stated criteria.
The legal question is also inseparable from product architecture. A plan manager considering crypto access must understand whether the plan offers a direct holding, an ETF, or a managed fund, because the selected structure affects how risks, fees, valuation, and operational responsibilities are presented. Legal review and technical review should assess the same product facts, even if each discipline reaches a different conclusion.
The proposal’s history adds another reason for careful documentation. The article states that 2022 guidance was reversed in 2025. A fiduciary making a long-term plan-design decision must therefore account for the possibility that the current policy direction could later change again. A durable process should not depend exclusively on a favourable regulatory moment.
For organisations operating across different regulatory environments, the US retirement-plan analysis should also remain distinct from MiCA regulation and EU crypto regulation. A retirement-plan rule, a product-compliance framework, and a technical security assessment answer different questions. Combining them without clear boundaries can obscure rather than reduce risk.
Legal advisers should test the plan’s governance language, responsibility allocation, and disclosures against the actual crypto product under review. Soken’s legal and compliance services are relevant where a business needs a structured view of crypto-related legal documentation, commercial terms, and regulatory positioning. The essential point is not to treat legal review as a final signature after product selection. Legal analysis should inform the product decision before it reaches participants.
What should crypto providers and plan sponsors do during White House review?
Crypto providers and plan sponsors should use the White House review period to build evidence for the proposal’s six factors, define the intended product structure, and test whether their governance would remain defensible if regulatory guidance changes. The proposed rule creates an opening for crypto in 401(k) plans, but it leaves product design and investment accountability with the organisations offering and approving that exposure.
For providers, the immediate task is to replace broad claims with operational evidence. A product intended for retirement-plan distribution should be able to describe its fees, liquidity model, valuation approach, benchmark, and complexity in language that a plan manager can use in a decision record. If a product cannot explain those points clearly, the product is poorly positioned for a framework built around them.
For plan sponsors and managers, the task is to prepare an approval model before a specific product is marketed aggressively. That model should state the minimum information required for review, identify who is authorised to make decisions, and establish the monitoring expected after an option reaches the plan menu.
The table below separates the responsibilities that should be considered before a crypto option is introduced.
| Participant | Decision to document | Proposal factor most directly engaged | Evidence to retain |
|---|---|---|---|
| Plan manager | Why a crypto option belongs in the 401(k) menu | Performance and benchmarks | Product comparison and documented selection rationale |
| Plan manager | Whether a product can support participant transactions | Liquidity | Liquidity analysis and review conditions |
| Crypto provider | How the product’s value is calculated | Valuation | Valuation methodology and supporting product materials |
| Crypto provider | What participants pay for exposure | Fees | Fee schedule and explanation of product costs |
| Legal reviewer | How legal protection and remaining lawsuit exposure are described | Complexity | Responsibility map, disclosures, and approval records |
| Technical reviewer | Whether product mechanics match operational claims | Complexity and valuation | Architecture review, control descriptions, and dependency assessment |
This is also the stage to consider technical assurance. Where a retirement product uses blockchain applications, smart contracts, tokenised representations, automated pricing, or external infrastructure, a security review should examine the system that sits behind the investment proposition. Technical weaknesses can become governance weaknesses when they undermine a product’s stated custody, valuation, or transaction model.
Readers looking for additional security and compliance analysis can review Soken’s research hub, where the recurring theme is consistent: Web3 adoption succeeds when commercial access, technical design, and accountable governance are evaluated together rather than in separate silos.
The White House review should be treated as a preparation window, not as a reason to rush crypto products into 401(k) plans. The Labor Department proposal offers flexibility, while its six-factor test and limited lawsuit protection make clear that flexibility requires evidence.
Build the decision record now: define the proposed exposure, assess it against performance, fees, liquidity, valuation, benchmarks, and complexity, then assign a named internal owner for ongoing review. That concrete step gives plan managers a stronger basis for action whether the proposed rule proceeds unchanged, is modified, or later faces the same policy reversibility seen between 2022 and 2025.