Governing the Settlement Stack: The Uncomfortable Truth About DLT in Finance
Published by Atom Consulting
The financial industry has spent a decade debating whether distributed ledger technology "works." As take up starts to increase the questions the industry needs to address are also evolving.
The hard question now is whether DLT can be governed like Financial Market Infrastructure (FMI)—because the moment a ledger becomes part of issuance, settlement, collateral mobility, or payments, its technology stops being the main risk.
The main risk becomes who holds the levers.
And here's the uncomfortable truth most "decentralisation" narratives avoid:
DLT doesn't eliminate governance. It hides governance inside infrastructure—until something breaks, and then governance becomes visible at the worst possible moment.
If we want the capital efficiency of atomic settlement and tokenised markets, we have to stop treating governance as a community preference and start treating it as a control plane.
The governance question every DLT platform must answer
In regulated markets, resilience isn't a slogan. It's a design requirement. So there are four questions that matter more than throughput, TPS, or developer tooling:
- Who can change the rules?
- Who can execute those changes safely?
- Who is accountable when changes cause harm?
- What happens in an exception—an exploit, a misconfiguration, a market integrity event, a run?
Most networks can answer (1) in marketing terms.
Very few can answer (2)–(4) in FMI terms.
The myth of decentralisation: power doesn't disappear, it relocates
Ignore architecture labels ("public", "permissioned", "L2") and map control points instead:
- Admission control: who can join, read, write, validate.
- Upgrade control: who holds upgrade keys, timelocks, admin permissions.
- Exception control: who can pause, rollback, quarantine, or enforce a fork.
- Economic control: who can change collateral rules, liquidity incentives, fee models, treasury spend.
This is where "decentralisation" often becomes an illusion—because even when execution is distributed, control is concentrated.
In DeFi, we've seen the pattern: turnout is low, whales coordinate, foundations execute, and legitimacy is retrofitted after the fact. In institutional platforms, the same forces appear—just with different clothing: committees, rulebooks, and regulated operators.
Stablecoins were the prototype. Tokenised deposits are the institutional endgame.
The next chapter of digital assets in finance is increasingly a story about what counts as money on-chain.
Stablecoins proved demand for 24/7 settlement instruments. But they also exposed the fragility of "private money as a bearer instrument." When reserves are questioned, pegs wobble, and risk transmits instantly across protocols.
Institutions are increasingly leaning toward tokenised deposits—bank liabilities represented on-chain, inside the regulated perimeter. This isn't just a product choice. It's a governance choice. Because once money is tokenised, the issuer's governance and the network's governance become entangled.
Case Study: the "same" stress event looks very different in stablecoins vs tokenised deposits
Consider a familiar trigger: a sudden credibility shock to a core banking counterparty (liquidity doubts, asset quality uncertainty, resolution risk).
If the settlement asset is a stablecoin
The market immediately asks: are reserves available, are they liquid, can redemptions clear, and who decides what happens next?
Even if the stablecoin ultimately "holds," the episode reveals the governance burden: disclosure cadence, redemption gating policies, banking partner concentration, and operational response speed.
The system behaves like a run-prone instrument: confidence becomes a real-time variable.
If the settlement asset is a tokenised deposit
The system behaves more like traditional money—because it is a bank liability, within the banking perimeter.
Stress is not magically eliminated, but the governance question is different: what is the bank's liquidity management, what is the supervisory response framework, and how do intraday flows interact with prudential constraints?
The risk transfers from "reserve verification and redemption mechanics" toward bank governance + supervisory infrastructure, which is precisely where institutions prefer it to sit.
The key insight: these are not two "technologies." They are two different answers to the same question: who governs money under stress?
The real battle isn't on-chain vs off-chain. It's governable finality.
DLT communities love absolutes: "finality," "immutability," "code is law."
Financial markets don't work in absolutes. They work in procedures—normal-time procedures and crisis-time procedures. When losses are existential, human governance reappears. The only question is whether it appears as a planned doctrine or as improvised panic.
FMI-grade DLT needs a pre-committed exception doctrine:
- what triggers emergency powers,
- who can use them,
- what tools they can deploy (pause, quarantine, rollback pathways, compensation processes),
- and how decisions are logged, audited, and reviewed after the event.
Without that, "code is law" is not ideology—it's an operational hazard.
What regulated platforms are really building: controlled rails, interoperable markets
This is why credible institutional platforms look less like "a DAO for capital markets" and more like permissioned infrastructure with explicit governance:
- participant permissioning and privacy controls,
- lifecycle management built for real instruments and real entitlements,
- operational playbooks aligned to incident response and change management,
- and accountability that maps cleanly to regulated functions.
These are not ideological decentralisation plays. They are attempts to answer governance questions that regulated markets can't avoid.
A governance model that's actually fit for FMI
To be usable as infrastructure, governance needs five layers—not four:
- Permissioning: identity, eligibility, role-based entitlements.
- Rulebook governance: explicit change control, voting/committee design, clear thresholds.
- Executable governance: timelocks, staged rollouts, audit requirements, key management.
- Validator accountability: known operators with enforceable duties and observable performance.
- Exception doctrine: crisis powers, dispute resolution, loss allocation, and post-mortems.
This doesn't "centralise" DLT. It makes DLT survivable as infrastructure.
The debate we should be having
The industry has spent years arguing about decentralisation as a moral preference.
The more serious debate is this:
"What governance standard must a DLT network meet before we call it market infrastructure?"
Because once tokenised money, tokenised deposits, and tokenised securities converge, the settlement layer becomes too important to be governed by turnout-driven token votes—or by consortium ambiguity.
The winners won't be the networks that market decentralisation best.
They'll be the networks that can prove governability under stress.