Who Pays? The Ethics and Economics of Distributed Ledger Government

The Right to Remember made the case that a public ledger converts what would otherwise be a standing positive right — continuous, fundable, defundable preservation work — into something closer to a structural guarantee: a record that doesn't need an archivist to keep choosing, year after year, to keep it around. That essay was careful to flag its own limit on the way out the door: node operation is itself a positive-rights-shaped cost that doesn't disappear just because it's distributed rather than centralized. It's spread across more actors, not eliminated.

Spread across more actors is still a real bill, though, and somebody is still writing the check. Distributing a cost isn't the same as extinguishing it, and a ledger that never forgets is only as durable as whoever keeps paying to run the machine that remembers. The mechanism doesn't dissolve the "who pays?" question every public good eventually asks. It just changes who's being asked to answer it, and how visibly.

Three ways to pay for a ledger, and three different answers to who pays

Inflation, paid by everyone who holds the currency. A proof-of-work chain like Bitcoin pays its ledger-keepers — miners — with newly minted coins plus transaction fees, funded by diluting everyone else's existing holdings a little at a time. Nobody signs a check. The cost is real anyway: it shows up as a permanent, low-grade transfer from every holder to whoever's currently running hardware, and as very real electricity consumption borne partly by the miner and partly, researchers estimate, by neighbors on the same grid — mining has been shown to push up monthly electric bills for nearby households and small businesses, and U.S. mining operations alone are estimated to cost on the order of a billion dollars a year in electricity. It's a funding model that never asks anyone to vote on a budget line, which is exactly its appeal and exactly its evasion: the cost is real, it is just diffuse enough that no one individually feels responsible for having authorized it.

A line item, paid by taxpayers. A government-run ledger can simply be treated as infrastructure and funded the way roads and courthouses are — out of general revenue, appropriated, and defended in a budget hearing like anything else. This is the honest version of the positive right the earlier essay described: visible, contestable, and exactly as durable as the next administration's appetite for the line item.

Fees, paid by whoever uses it. A ledger can also charge its own users directly — per-transaction fees, filing fees, subscription access — funding itself the way a toll road funds itself, out of the people who actually cross it rather than out of the general public. This is the most self-limiting model and also the most regressive one: it puts the cost of a public record on precisely the citizens who need to transact with the record most often, which in a land registry or a court system tends to correlate with exactly the people George would have said are least able to absorb an extra toll.

None of these three is "the" way to fund distributed-ledger government. Each is a real, tried funding model, and each answers "who pays?" in a way that quietly encodes an ethical position about who should pay — dispersed holders, general taxpayers, or direct users — well before anyone in the room has said the word "ethics" out loud.

The ethics question is a tax-incidence question wearing a new coat

We've made the same argument once already, about land. Actual Modern Georgist Experiments traced how a land value tax survives exactly as long as three unglamorous conditions hold: assessments stay current, the public actually understands what it's being asked to pay, and the tax isn't asked to carry more political weight than a tax can carry alone. Swap "land value tax" for "ledger funding model" and the same three conditions transfer almost without editing. A funding source has to stay current with the actual cost of running the infrastructure — under-resourced nodes are the assessment-neglect failure mode, quietly degrading service until a crisis forces a reckoning nobody budgeted for. The public has to understand what it's paying and why, or the Altoona failure repeats: a fee or a tax line that reads as a burden because nobody explained what it replaced. And a ledger-funding decision shouldn't be asked to solve problems — corruption, distrust in institutions, chronic underinvestment in records-keeping — that the funding mechanism alone was never built to solve, the way Harrisburg's land tax succeeded at exactly what it was built for and still couldn't save a city being sunk by an unrelated debt crisis.

What's different, and worth naming honestly, is that a distributed ledger adds a fourth question a land tax never has to answer: whether the payer is even identifiable. Land value tax incidence is a solved problem in principle — economists can tell you who bears a land tax versus a building tax, because land and buildings are visible, located, and owned by someone with a name on a deed. Proof-of-work mining rewards are incidence smeared across every holder of a currency, present and future, with no vote and often no awareness that a transfer occurred at all. That's not a minor technical wrinkle. It's the difference between a tax a citizen can see on a bill and a tax a citizen pays without ever being told the rate.

What actually happened when governments tried to pay for this

Estonia's KSI blockchain — infrastructure built for free, run at no separate line item. Estonia's Keyless Signature Infrastructure, developed with the Estonian firm Guardtime starting in 2008, verifies the integrity of government data across e-Estonia's health records, court system, and business registry. The striking detail, on the funding question specifically, is that Guardtime built the original proof of concept without direct monetary compensation from the state — the ledger exists today less as a taxed public good than as donated private infrastructure that a government agency (the Information Systems Authority, RIA) subsequently adopted under a cooperation agreement. It's the cleanest real-world case of "who pays?" being answered with "mostly, for a while, a company that wanted to be first" — durable so far, but a funding story that doesn't generalize to a country without a Guardtime willing to build first and bill later.

Georgia's land registry — a taxpayer-funded agency paired with a private blockchain partner. In 2016 the Republic of Georgia's National Agency of Public Registry (NAPR) partnered with the Bitfury Group to anchor land-title hashes to the Bitcoin blockchain, giving citizens a way to verify a land title from a smartphone without trusting a registrar not to have quietly altered it. NAPR is a normal, taxpayer-funded government agency; Bitfury supplied the technical build as a partner rather than a vendor paid a flat public contract, and the underlying Bitcoin network's own miners — funded by the inflation-and-fees model above — did the actual proof-of-work that makes the anchoring tamper-evident. The Georgia case is really three funding models stacked on top of each other in a single system: general taxation for the agency, a negotiated partnership for the build, and diffuse global mining inflation for the tamper-proofing itself.

Sweden's land registry pilot — a taxpayer-funded pilot that priced its own upside and then didn't ship. Lantmäteriet, Sweden's land registry authority, ran a blockchain pilot with the startup ChromaWay from 2016 through early 2017, projecting savings of over €100 million a year for taxpayers and lenders once paperwork and settlement delays were eliminated. The pilot itself was a modest, publicly funded proof of concept. What's notable is what happened after: the projected savings were real enough to be widely cited, and the system still wasn't adopted into production, held back by legal questions about the validity of a smart-contract signature under Swedish law. Sweden's case shows that even a fully costed, taxpayer-funded pilot with an unusually credible savings estimate can stall — not on the funding question at all, but on the separate question of whether the law recognizes what the ledger produces.

Delaware's blockchain archive — a taxpayer-funded contract for exactly the "right to remember" problem, cancelled before delivery. In 2016 Delaware hired the blockchain firm Symbiont specifically to put the Delaware Public Archives on a ledger, aimed at the same preservation problem we described in an earlier essay — making historical public records durable and accessible rather than dependent on an archivist's ongoing budget. The relationship ended within a year over a dispute about scope, and the archive project never shipped. Delaware later signed a separate $738,000 contract with IBM to explore a blockchain-based corporate-filing system instead. Two paid contracts, two different vendors, and — as of the most recent reporting — no production blockchain running Delaware's archive. It's the sharpest available illustration that "the state appropriated money for this" and "the public actually got a durable ledger" are not the same fact, and that a taxpayer-funded contract can be cancelled exactly as easily as an underfunded archivist's line item can be — the positive right didn't get more secure just because a blockchain vendor was named in the contract instead of a records clerk.

Illinois's blockchain initiative — an extensive taxpayer-funded exploration that mostly stayed a pilot. Illinois launched one of the most ambitious state blockchain programs in the country in 2016, spanning five proof-of-concept projects across multiple agencies, including a Cook County pilot to record property transfers. It generated task-force reports, conference visibility, and genuine institutional learning. What it did not generate, years later, is a production land registry running on a blockchain in Illinois. Funded by ordinary state appropriations, it's a case where the money was real and the political will to keep funding the leap from pilot to production quietly wasn't.

What the record actually says

Line up the cases and a pattern shows up that the Georgist essay would recognize immediately: the funding model matters less than whether anyone stays committed to it past the pilot stage. Estonia's ledger has run continuously since the 2000s because a company front-loaded the cost and a government agency picked up ongoing operation afterward — an unusual, non-repeatable funding accident that happened to work. Georgia's land registry has run continuously because it stacked a stable taxpayer-funded agency underneath a one-time technical partnership, rather than betting the whole system on either party alone. Sweden's and Illinois's pilots ran on ordinary appropriated money and still didn't reach production, because the money was never the actual blocker — legal recognition and institutional follow-through were. And Delaware's case is the starkest: a signed, funded, taxpayer-backed contract for precisely the archive problem we've already written about, cancelled inside a year, proving that appropriating money for a ledger is not the same act as guaranteeing the ledger outlives the political moment that funded it.

The honest conclusion isn't that distributed ledgers solve government's funding problem, or even that they make it meaningfully cheaper. It's that they make the funding question harder to dodge than it is for an ordinary archive, precisely because the ledger's most-advertised property — permanence — draws attention to exactly the question a quietly underfunded records office lets a citizen forget to ask. A filing cabinet that slowly rots doesn't invite anyone to ask who's paying to maintain it; a blockchain that's supposed to be permanent invites the question immediately, because permanence is the one promise the technology is explicitly making. That's a genuine improvement in honesty, even where it isn't yet an improvement in outcomes: Estonia, Georgia, Sweden, Delaware, and Illinois collectively show every funding model tried so far — donated infrastructure, taxpayer appropriation, private partnership, diffuse mining inflation — and none of them, on its own, has proven durable enough to answer "who pays, forever?" the way the technology's own marketing implies it already has.

---

Sources: Guardtime: The use of the National Blockchain Infrastructure to support the E-Residency Initiative in Estonia; Invest in Estonia: KSI blockchain provides truth over trust; New America: Restoring Trust in Public Land Registries — Georgia; Eurasianet: Georgia Uses Blockchain Technology for Developing Land Registry; Computer Weekly: Sweden trials blockchain for land registry management; Quartz: Sweden's blockchain-powered land registry is inching towards reality; Technical.ly: What ever happened to the Delaware Blockchain Initiative?; StateScoop: Delaware inks $738,000 blockchain contract with IBM; GovTech: Illinois Doubles Down on Blockchain Promises; Haas News, UC Berkeley: Power-hungry cryptominers push up electricity costs for locals.