CLARITY on the calendar — what actually governs tokenised dollars now

Where the legislation actually stands — the verified record

Precision matters here, because both of the convenient summaries are wrong. The Digital Asset Market Clarity Act has not been enacted, and it has not died. The record reads: passed the House 294-134 on 17 July 2025; received in the Senate and referred to the Banking Committee on 18 September 2025; ordered reported on 14 May 2026; reported with an amendment in the nature of a substitute and placed on the Senate Legislative Calendar, General Orders No. 423, on 1 June 2026. Updated merged Banking and Agriculture text was released on 22 July 2026.

What the bill lacks is floor time and sixty votes, in that order. Senate leadership has indicated the pre-recess window will most likely be missed, which pushes any realistic vote into the autumn at the earliest. So the accurate characterisation is neither passed nor stalled in committee: it is reported, calendared, and waiting. For an institution building a control estate, the practical planning assumption is that the existing regimes remain operative well into 2027 regardless of which way the floor eventually goes.

What is unusual is how much programme planning was quietly built on the bill passing. In the engagements we have reviewed this year, a meaningful share of tokenisation roadmaps contained a dependency that read, in effect, once the federal framework lands. That is not a control. That is a hope with a date on it.

The mirror-image error appeared this month: roadmaps rewritten on the assumption the bill is finished. It is not. An institution that de-scopes its market-structure readiness on a press read of the recess calendar will be rebuilding under time pressure if the autumn vote lands. Neither optimism nor obituary is a control position. The verified procedural status, restated on a fixed cadence, is.

The mistake institutions are making

The mistake is treating legislation as the source of the obligation. It rarely is. A statute usually names, consolidates and standardises obligations that already exist in fragmented form. While the statute waits, the fragments do not disappear — they simply stay fragmented, which is harder to manage, not easier.

A booking institution issuing or distributing a tokenised dollar instrument today still owes: authorisation for issuance, integrity of supply, segregation of client assets, demonstrable settlement finality, accurate disclosure to holders, a tested redemption path under stress, and conduct discipline wherever the instrument crosses a border. Those seven items are not a reading of any single bill. They are the intersection of every regime that has ever regulated a claim on money.

Path one — state trust charters and money transmission

The most operative US path remains the state one. Limited-purpose trust charters and state money-transmitter regimes already impose reserve, segregation, custody and reporting duties on entities issuing or handling redeemable dollar claims. Supervisors in these regimes have examination authority now, exercise it now, and do not require new legislation to ask an institution how it proves its reserve position.

For a distributing institution, the practical consequence is second-order but real: the issuer's charter conditions become the institution's third-party control requirements. If the issuer's segregation duty is a licence condition, the distributor's diligence must test that condition, not accept an attestation that references it.

Path two — federal prudential guidance

Federal banking supervisors have not been silent. Guidance and interpretive positions from the OCC, the Federal Reserve and the FDIC already frame how a supervised institution may engage in crypto-asset and tokenised-deposit activity, what notification is expected, and what risk-management standard applies. That framework is prudential rather than market-structural, which is precisely why it is unaffected by where the bill sits on the Senate calendar.

Prudential expectations are also the ones with teeth in an examination. A supervisor testing a tokenised deposit platform will ask about operational resilience, third-party concentration, model and AI dependencies in the transaction path, and the institution's ability to reconcile on-ledger positions to books and records. None of those questions required legislation to become askable.

Path three — MiCA and the cross-border overlay

For any institution with European activity, MiCA Titles III and IV are the most detailed operative text in the world on issuance, reserve composition, redemption rights and disclosure for tokenised dollar-equivalent instruments. It is in force. It is being examined against. And it is increasingly the de facto reference specification for institutions that need something concrete to design to.

We now routinely see US institutions design controls to the MiCA standard not because they are in scope, but because it is the highest published bar and designing to it means no future US framework can arrive as a surprise. That is a defensible strategy and worth saying plainly to a board.

Substantial similarity as an operating method

The method that survives legislative uncertainty is substantial similarity: build the control once, then attest that it satisfies the operative requirement in each regime that reaches the activity. A segregation control designed to a trust-charter condition can be mapped to the MiCA safeguarding requirement and to the prudential expectation on client asset protection — one control, three evidenced obligations.

This is not a compliance shortcut. Done properly it is more demanding than single-regime work, because the mapping must be defensible line by line and the gaps must be named rather than smoothed. But it produces an estate that does not need rebuilding every time a legislature changes its mind, and it produces an evidence set that a new supervisor can read without a translation exercise.

What a supervisor will ask in the next twelve months

Based on examination patterns across the regimes above, the questions cluster tightly. How many tokenised arrangements is the institution party to, and who owns each. What happens to client claims if the issuer, the custodian or the platform operator fails. Can the institution reconcile ledger positions to its own books on any given day, and how aged are the breaks. Has redemption been tested under a severe but plausible outflow rather than modelled under an average one. Which AI or model dependencies sit inside the transaction path, and who validated them.

Every one of those is answerable today with evidence an institution either has or does not. None of them becomes easier if a bill passes.

What to do before the next session

Three things. Remove legislative dependencies from the roadmap and re-anchor each control to a regime that binds today. Run the substantial-similarity mapping so the estate is regime-portable rather than regime-specific. And test the two controls most institutions have documented but never exercised — redemption under stress, and wind-down of a tokenised arrangement whose operator has failed.

Legislation was never the control. It was the label on the control. Institutions that understood that this spring did not lose a quarter waiting for the recess to end.