A trading venue’s settlement problem has two faces, and they point in opposite directions. Clients pull toward speed: markets that trade continuously, withdrawals that clear at 02:00 on a Sunday, capital that never waits on a backlog. Regulators pull toward proof: evidence that execution was orderly, that settlement followed the rules the venue declared, that nothing moved for a sanctioned party or past a limit. Most settlement infrastructure was built for neither demand, and venues have been meeting both with headcount, reconciliation, and after-the-fact reporting.
The proof demand is getting formal
In the EU, MiCA has moved venue oversight from principle to regime: authorization, market-integrity obligations, custody and conduct rules, with stablecoin provisions live since mid-2024 and full enforcement since July 2026. The FATF’s standards push in parallel; its 2025 targeted update again pressed jurisdictions to implement the Travel Rule, under which originator and beneficiary information must accompany transfers between providers. The common thread is evidencing. It is no longer enough for a venue to run controls; it must be able to show that the controls ran, transaction by transaction.
Today that showing is expensive. Controls live in systems bolted around the matching engine and the settlement stack: screening before, surveillance beside, reconciliation and reporting after. When a regulator or auditor asks whether the rules held, the venue answers with extracts, samples, and attestation letters, which cost weeks and reveal more than anyone is comfortable revealing. Order flow is the venue’s commercial crown jewel, and most forms of proof amount to handing it over.
What settlement can do about it
The alternative design moves the checking into settlement itself. Each transaction settles only if it satisfies the policies that govern it: counterparty permissions, limits, jurisdiction rules, screening status. The settlement event and the compliance event become the same event, which has two consequences worth separating.
First, exceptions stop settling. A transfer that cannot satisfy its conditions does not need to be caught afterward, because it never completed. The backlog of after-the-fact investigation shrinks toward the cases that genuinely need judgment.
Second, settlement produces evidence as a by-product. A cryptographic attestation that conditions were met can be verified by a third party without exposing the orders, positions, or identities underneath. For a venue, that is the difference between proving integrity by disclosure and proving it by construction. The BIS’s work on the future of settlement has pointed the same direction for years: when settlement logic is programmable, properties like atomicity and finality stop being aspirations coordinated across systems and become properties enforced in the transaction itself.
The speed face of the problem is solved by the same move. Settlement that runs continuously, with finality in seconds, closes the gap between a market that never stops and a back office that does. Obligations stop accumulating over weekends; client capital stops queueing behind cut-offs.
What to evaluate
For a venue assessing settlement infrastructure, four questions do most of the work. Where is policy enforced, inside settlement or around it? What evidence does a settled transaction carry, and can a third party verify it without seeing commercially sensitive data? Does the layer span rails, so the venue can settle fiat, stablecoin, and tokenized-deposit legs without a separate stack for each? And does it operate at the venue’s clock, continuously, rather than at banking hours?
Where Frame fits
Frame is the settlement layer for modern finance. Through configured integrations, Frame Rules checks the institution's policy before release, and Frame Proof seals the outcome reported by the customer's execution platform.
The customer's platforms execute the transaction. Rail coverage, execution timing and finality depend on the configured integration and the underlying systems. The institution remains responsible for its policies, permissions and operating controls.
See how a rail-neutral settlement layer is designed: the Frame Blueprint.
Common questions.
What does MiCA mean for trading venues?
The EU's Markets in Crypto-Assets Regulation brings venues trading crypto-assets into an authorization regime with obligations on market integrity, custody arrangements, and conduct, with stablecoin provisions applying since mid-2024 and the framework in full enforcement from July 2026. The direction of travel matters as much as the detail: venues are expected to evidence that their operations are orderly, and evidencing is a settlement-layer problem as much as a policy one.
What is verifiable settlement?
Settlement that produces cryptographic evidence that a transaction met its governing conditions: who was permitted, what limits applied, which checks passed. A third party, an auditor, a regulator, or a counterparty, can verify the evidence without being shown the underlying business data. It converts questions that today require data-room access and weeks of sampling into questions the evidence answers directly.
Can a venue prove integrity without revealing order flow?
That is what attestation-based designs are for. The venue's systems produce a cryptographic record proving that execution and settlement followed the declared rules, and the proof can be checked without disclosing the orders, positions, or client identities behind it. Order flow is commercially sensitive, so any integrity proof that requires handing it over is a proof most venues cannot afford to give.
Why does 24/7 settlement matter for a trading venue?
Because the market it serves never closes. When trading is continuous and settlement is not, exposure accumulates in the gap: obligations pile up over weekends and cut-offs, counterparty risk grows with the backlog, and capital sits against unsettled positions. Settlement that is continuous and final in seconds keeps the venue's risk window close to zero and its clients' capital working.