BlackRock's BUIDL fund holds $2.3 billion in tokenized Treasuries and pays approximately 4.8% annually. The DTCC launches blockchain settlement for all Russell 1000 equities in October. The tokenized real-world asset market has crossed $39 billion. And your 401(k) cannot participate in any of it.
The barrier is not technological. It is regulatory, structural, and custodial — three overlapping layers of restriction that collectively block retirement savings from the tokenized asset market. Understanding each layer clarifies both why the barrier exists and what would need to change for it to come down.
Layer 1: ERISA Fiduciary Rules
The Employee Retirement Income Security Act of 1974 (ERISA) governs most private-sector retirement plans in the United States. ERISA's fiduciary standard requires that plan administrators act solely in the interest of participants and beneficiaries, and specifically that they invest in assets that are "prudent" — defined by what a knowledgeable investor would consider appropriate given the plan's needs.
The prudent investor standard does not explicitly prohibit tokenized assets. But it creates a practical barrier: fiduciaries who include novel asset classes without extensive documented due diligence face personal liability if those investments underperform. The Department of Labor (DOL) has issued guidance expressing skepticism about cryptocurrency in retirement plans, noting concerns about speculation, fraud, and the difficulty of performing adequate due diligence. While tokenized Treasuries are backed by US government obligations — not speculative assets — they are delivered through blockchain infrastructure that the DOL has not formally blessed for ERISA purposes.
A plan administrator who adds BUIDL to a 401(k) menu today would be taking a personal fiduciary risk that their lawyer would almost certainly advise against. The expected value may be positive, but the liability exposure before formal DOL guidance is too high for most fiduciaries to accept.
Layer 2: Plan Administrator Restrictions
Most 401(k) plans are administered by large recordkeeping platforms — Fidelity, Vanguard, Schwab, Empower, Principal — that maintain the participant accounts, process contributions and distributions, and provide the investment menu. These platforms have not built infrastructure to hold tokenized assets. Adding a tokenized fund to a 401(k) plan requires the recordkeeper to support it, which means building or licensing custody infrastructure, compliance workflows, and reporting systems that currently do not exist for tokenized products at the recordkeeper level.
The recordkeeper gap is a chicken-and-egg problem. Recordkeepers will not build the infrastructure until there is clear regulatory guidance and demand from plan sponsors. Plan sponsors will not demand it until recordkeepers support it. Regulatory guidance will not come until the DOL has enough data and industry engagement to formulate a position. Each party is waiting for the other to move first.
Layer 3: Custodian Limitations
Plan assets must be held by a qualified custodian — a bank, trust company, or registered broker-dealer. Digital assets present a specific custody problem for traditional custodians: blockchain-native assets require private key management, which is operationally and legally different from holding securities in a traditional book-entry system. The Office of the Comptroller of the Currency (OCC) has issued guidance permitting national banks to provide crypto custody services, but implementation across the custodian population has been slow and uneven.
For tokenized Treasuries specifically — where the underlying asset is a US government obligation held by a bank custodian, and the token is an on-chain representation — the custody problem is less acute than for native crypto assets. But plan custodians have not yet established the operational infrastructure to hold these instruments within ERISA plan structures.
What Would Need to Change
Three things need to happen in sequence. First, the Department of Labor needs to issue formal guidance addressing tokenized traditional assets (as distinct from speculative crypto) within ERISA plans — establishing a framework that plan fiduciaries can use to justify inclusion without personal liability exposure. Second, at least one major recordkeeper needs to build the operational infrastructure to support tokenized assets in plan menus, creating a reference implementation that others can follow. Third, plan sponsors need to demand the capability, creating commercial pull that accelerates the first two.
The DTCC's October 2026 launch is the most important enabling event for this sequence. When blockchain settlement is standard practice for Russell 1000 equities in institutional accounts, the argument that blockchain custody is operationally novel becomes significantly weaker. The technology risk that makes fiduciaries cautious diminishes as the DTCC normalizes blockchain settlement for the institutional mainstream.
The path from "BUIDL exists" to "your 401(k) can hold it" is probably a 3-5 year regulatory and infrastructure journey from today. But it is a journey with identifiable milestones — and the DTCC October launch is the first significant one.
→ The 0.5% vs 4.8% gap — why this matters for every saver
→ DTCC October Launch — the enabling infrastructure event
→ The 97% Problem — who the tokenized market currently excludes