Blockchain, Government, and Institutional Authority: Governance Before Technology
- Ott Sarv
- Jan 2
- 5 min read
Updated: Feb 24
A procurement deck makes an irresistible promise. An immutable ledger. Shared truth across agencies. A future where fraud collapses because every step is recorded.
Then reality arrives, usually as a complaint, an audit query, or a court filing. The question is never about the elegance of the ledger. It is about who is empowered to act, who is accountable for the legal effect, and who can compel a correction when the system is wrong.
A blockchain can strengthen evidence. It does not create public authority.
This article uses The Seven Layer Model for Digital Public Infrastructure: A Governance Architecture for Lawful Digital Public Authority and refers to it as SLM from here onward.
Consensus is not a mandate
Distributed consensus answers a technical problem: how multiple participants agree on the next state without a single operator. A public mandate answers a different category of problem entirely: who may decide, under what legal limits, with what duties, and with what remedy when a person contests the outcome.
A ledger can be internally consistent and still be institutionally void. That void becomes visible the moment someone needs revocation, suspension, correction, or compensation.
For a clean boundary, separate evidence from effect. Evidence is a record that something was asserted at a time by a party operating under known controls, which is close to the framing in the NIST Blockchain Technology Overview. Effect is the binding consequence in public administration: a decision that changes rights, obligations, or access, and remains attributable and reversible through oversight.
When programmes treat consensus as legitimacy, they produce governance theatre: impressive traces with no enforceable authority behind them.
Where blockchain fits in the SLM sequence
SLM is useful because it forces programmes to locate technology inside a chain of lawful action. A ledger can strengthen certain layers, yet it cannot substitute for any layer that assigns authority, responsibility, or remedy.
SLM layer | What must exist for lawful public action | Where blockchain can help | What blockchain cannot do |
Layer 1: Legal authority | The function, its legal effect, and its limits are defined | Preserve integrity evidence supporting investigations and disputes | Provide the legal basis for issuing, enforcing, or reversing decisions |
Layer 2: Institutional mandate | A named custodian holds responsibility and can be compelled | Support multi-party transparency in inter-institution workflows | Create accountability, budget authority, or lawful delegation |
Layer 3: Canonical records | Authoritative registers exist with provenance and correction at source | Provide integrity anchors for record events and cross-party receipts | Replace the canonical register owner or the correction procedure |
Layer 4: Service logic | Rules are authorised, versioned, and traceable to institutional instruction | Record rule versions and decision traces for later reconstruction | Legitimate rules, approve changes, or make logic appealable by itself |
Layer 5: Execution layer | Controlled runtime, traceable operations, and incident response exist | Strengthen tamper-evidence for operational logs | Deliver certified execution controls or segregation of duties |
Layer 6: Public interface | People can understand, access, and contest outcomes | Provide verifiable receipts and submission timestamps | Deliver procedural rights, accessibility, or due process |
Layer 7: Oversight and remedy | Independent bodies can compel evidence and correct outcomes | Improve evidential packages for audit and review | Provide remedy, correction propagation, or compensation powers |
The research literature reaches a similar conclusion from a different angle. A stock-taking of public sector uses of blockchain finds many efforts remain limited pilots, and often lack clear advantages over conventional digital record-keeping when governance is missing, as summarised in Government by Code? Blockchain Applications to Public Sector Governance.
The recurring failure: decentralising accountability instead of strengthening it
Many public programmes adopt permissioned or consortium designs and describe them as decentralised. In practice, power shifts into membership rules, upgrade rights, key custody, and governance committees. The ledger distributes write operations while accountability dissolves into shared ownership.
That is not a technical defect. It is a governance defect.
Public administration cannot run on shared responsibility without clear compellability. Someone must be answerable for the decision. Someone must be obligated to correct the authoritative record. Someone must be able to reverse downstream consequences. A ledger that spreads participation while blurring responsibility simply scales confusion.
A public management perspective reinforces this point: blockchain governance choices are not neutral and must align with policy objectives, public values, and institutional frameworks, which is the central argument of Blockchain governance in the public sector: A conceptual framework for public management.
Governance gates before procurement
Before selecting any ledger technology, the programme should be able to state three things precisely.
The first is legal effect. If the ledger output is meant to be binding, then the legal instrument that makes it binding must be identified and the competent institution must be named. If legal effect is not intended, the programme should say so, because evidence support and decision authority are different procurement categories.
The second is correction at source. When something is wrong, which institution corrects the authoritative record, and what is the operational path for that correction to propagate. If correction requires negotiation between participants, the system is not governance-grade.
The third is remedy. If a person contests an outcome, the complaint route must reach an institution that can change the result, not merely annotate a log. Remedy is where public authority proves itself.
These gates are not unique to blockchains. They are the same gates that apply to data exchange, wallets, and other trust plumbing. A platform may carry traffic without inheriting sector authority, which is why data exchange platform legal authority matters as a pattern, and why mandate gating must be explicit before interoperability is treated as entitlement.
A safer pattern: blockchain as evidence support, not decision authority
There are constrained roles where a blockchain can be valuable.
Inter-institution workflows can benefit from shared integrity evidence, provided each institution remains accountable for its own public acts and the canonical records remain institutionally owned.
Public submissions and handovers can benefit from strong receipts and timestamping, provided correction and reversal remain available through normal supervisory channels.
Audit trails can be strengthened when a ledger is used as an additional integrity anchor for evidence-grade logs produced by controlled execution environments, rather than as a replacement for those controls.
Where these constraints are ignored, the ledger becomes an expensive diary of unresolved governance questions.
The legal scholarship makes the same warning with more direct language: law and governance are not optional add-ons, which is the core thesis in Trust, but Verify: Why the Blockchain Needs the Law.
Why regulators are building dialogue environments, not endorsing ledgers
Public authorities increasingly treat blockchain as a legal certainty problem before it is treated as a scaling problem. That framing is visible in the European Blockchain Regulatory Sandbox, which is designed around regulatory dialogue, identification of legal obstacles, and practical guidance. The existence of such initiatives is a signal worth reading correctly: the state is testing governance conditions, not outsourcing authority to technology.
----
A blockchain can support trustworthy evidence. It cannot be the source of lawful public power.
If a programme wants speed without losing legitimacy, it must sequence its authority chain first. The baseline remains law before code. The strategic test remains whether the state can reverse and correct outcomes in practice, which is why digital sovereignty through sequence treats remedy as the signature of public control.
When that sequence is intact, a ledger can play a supporting role. When the sequence is missing, the ledger merely records the absence of authority at scale.
