Nehemiah Had a Whitepaper

The Tower and the Wall

In the fifth chapter of the Book of Nehemiah, the wall-builders stop building. Not because the enemies outside Jerusalem have overwhelmed them, but because the wealthy inside the city are lending at interest to the poor, foreclosing on their fields, and selling their children into debt slavery. Nehemiah, who organized the reconstruction, who assigned each family its own stretch of masonry, who coordinated the defense against Sanballat's raids, is furious. He calls an assembly. He makes the creditors return the fields, the vineyards, the olive orchards. The wall cannot stand, he argues, if the people inside it are devouring each other.

Pope Leo XIV opens Magnifica Humanitas, his first encyclical, with the same book. But he pairs Nehemiah with an older story: the Tower of Babel. A single language, a single technology, a single direction, and collective ambition that does not ask whether it should, only whether it can. The project was "an impressive feat" that concealed what Leo calls "a profound danger," because "uniformity that eliminated diversity" is not the same thing as communion.

Two construction projects. One builds upward to glorify the builders. The other rebuilds outward, family by family, section by section, and stops to address the exploitation happening inside its own walls before continuing.

If you have spent any time reading crypto whitepapers, you have encountered this architectural choice before. Leo XIV is describing the difference between a centralized system and a distributed one. But the Nehemiah detail he does not dwell on, the part where the project halts to confront its own internal coercion, turns out to be the part that makes his framework more honest than most of ours.

A 130-Year Head Start

The principle Leo invokes is subsidiarity: the idea that decisions should be made at the closest level possible to the persons involved, and that higher-level authorities should not supplant the responsibilities of individuals and their communities. Pius XI formulated it systematically in Quadragesimo Anno in 1931. Leo XIII laid the foundations in Rerum Novarum in 1891, the same year Edison's company was merging into General Electric. The Catholic Church has been writing governance theory about concentrated industrial power for longer than the modern corporation has existed.

What makes Magnifica Humanitas different is where Leo XIV aims the principle. Previous encyclicals applied subsidiarity to the relationship between the State and civil society. Leo XIV applies it to digital infrastructure.

"In the digital context," he writes, "the highest level is not the State, but rather major economic and technological actors that exercise de facto power over the conditions of everyday life." These entities "define conditions for access, rules of visibility, forms of interaction, and even economic opportunities." Subsidiarity demands that "such processes not be imposed from above in an opaque and unilateral manner, but instead be directed toward the common good with transparency, accountability and meaningful forms of participation."

Strip away the ecclesial language, and you are reading a design specification for protocol governance. Transparency. Accountability. Meaningful participation. Decisions at the closest level to the persons involved. No single entity defining the rules of access and visibility.

The crypto world arrived at this architecture through Satoshi's insight about trustless coordination. Catholic Social Doctrine arrived at it through Thomas Aquinas's insight about the ordering of human community. The convergence is not accidental. Both traditions are responding to the same structural problem: what happens when power concentrates beyond the ability of any individual to contest it.

But the traditions diverge on something fundamental, and the divergence is where the encyclical gets interesting.

The Babel Diagnostic

"A single language, a single technology, a single direction." The Tower's builders sought to "guarantee stability and power for themselves, and above all to 'make a name' for themselves."

Map this onto foundation model training. Three, perhaps five organizations on Earth can train a frontier model from scratch. They share a common technical language (transformer architecture, RLHF, scaling laws), a common infrastructure dependency (NVIDIA GPUs, hyperscaler data centers), and a common direction (benchmark performance, commercial deployment, regulatory capture). The coordination is impressive. The capability is extraordinary. And the concentration follows the Babel pattern exactly: one shared language, one shared infrastructure, one shared direction, building something whose ultimate purpose is to make a name for the builders.

Leo warns against the "Babel syndrome": "the idolatry of profit that sacrifices the weak, a uniformity that neutralizes differences, and the pretense that a single language, even a digital one, can translate everything, including the mystery of the person, into data and performance."

There is a word for this in the decentralization literature. We call it centralization. Leo XIV calls it building Babel. The diagnosis lands at the same place.

But the prescription does not.

The Prescription

The encyclical's most consequential claim for the digital economy is its treatment of data. Leo extends the Catholic principle of the "universal destination of goods," which holds that the earth's resources are given by God to the entire human family, to cover "new forms of property, such as patents, algorithms, digital platforms, technological infrastructure and data."

"Data is the product of many contributors and should not be treated as something to be sold off or entrusted to a select few." Data must be managed "as a common or shared good."

This is a stronger position than most decentralization advocates take, and it cuts against the grain of the crypto-native argument. The typical case for data sovereignty focuses on individual ownership: your data, your keys, your right to monetize what you produce. Leo's argument is communitarian. Data is not exclusively yours to sell because it was never exclusively yours to begin with. It is the product of collective activity and should be governed as a commons.

The distinction is not academic. Individual data sovereignty, pushed to its limit, reproduces the market dynamics it claims to resist. If everyone owns their data and sells it to the highest bidder, the highest bidder is still a concentrated buyer with more capital than any individual seller. The wallet does not change the power relationship. It just adds a step. The commons model starts from the opposite premise: some goods are better governed collectively because their value is collective.

This has immediate implications for AI training data, for DeSci protocols, for any project building infrastructure around data as a resource. Leo's framework does not align with the libertarian wing of crypto. It aligns with the cooperativist wing, with projects that treat data as a shared resource requiring governance rather than a commodity requiring a market. And it challenges the rest of us to explain why individual data markets will not simply recreate the concentration they were designed to escape.

The Theological Root

At this point, a technically minded reader might ask: does the theology add anything, or is subsidiarity just a good governance principle that happens to have a religious pedigree?

Leo XIV argues that the theology is load-bearing. Human dignity, in the Catholic framework, is not earned by performance, granted by the State, or reducible to economic contribution. It is "a gift that precedes and transcends each person." This is the foundation on which subsidiarity rests. If dignity is inherent and inviolable, then systems must be designed to protect it at every level. If dignity is conditional on performance, then efficiency becomes the measure of human value, and the technocratic logic wins by default.

The encyclical engages the philosophical tradition directly. Aquinas's account of grace as that which "surpasses every capability of created nature" is not a mystical abstraction here. It is the argument that human fulfillment cannot be achieved through optimization. The transhumanist promise of technological self-transcendence ("enhanced" humans, human-machine hybrids) fails, in Leo's reading, because it misidentifies the direction entirely. "What saves humanity is not enhanced self-sufficiency, but a relationship that liberates, a communion that transforms."

Writers like C.S. Lewis (in The Abolition of Man), Jacques Ellul, Ivan Illich, and more recently Yuval Noah Harari have all identified the same failure mode from secular ground: technology oriented toward the elimination of human limitation ends by eliminating the human. Leo XIV arrives at the same conclusion through a different route. Limitation is not a bug. It is the condition under which compassion becomes possible, generosity becomes possible, spiritual experience becomes possible. "Humanity flourishes not despite limitations, but often through them."

Leo is not arguing that suffering is good. He is arguing that a species which defines progress as the elimination of all vulnerability will eventually define vulnerable people as obstacles to progress. The encyclical names the mechanism: "If the human being is treated as something to be perfected or surpassed, it becomes easier to accept that some lives are less useful, less desirable or less worthy."

Whether you accept the theology or not, the structural argument stands. A system that measures human value by output will optimize for output and discard whatever cannot be optimized. The theological grounding gives this claim a foundation that utilitarian ethics cannot: dignity is not contingent on capability. But even without the theology, the history of the twentieth century provides the evidence. We have seen, repeatedly, what happens when a society decides that some lives are less useful than others. The innovation is never the cruelty. The innovation is always the framework that makes the cruelty feel rational.

The Nehemiah Test

The Nehemiah image does specific structural work in the encyclical that the Babel image cannot do alone. Babel is a diagnostic. Nehemiah is a protocol.

Nehemiah's method: examine the ruins in silence. Do not impose solutions from above. Convene the stakeholders. Assign each family its part of the work. Coordinate. Address opposition. Rebuild relationships before rebuilding with stones.

The decentralization movement has built tools for exactly this kind of coordination. Governance tokens, DAOs, distributed training protocols, consensus mechanisms. These are Nehemiah's assignments formalized in code.

But the Book of Nehemiah includes a scene that most governance whitepapers do not. Chapter 5. The wall-builders stop building because the system they have created is exploiting its own participants. The wealthy lend at interest to the laborers. Families mortgage their fields to buy grain. Children are sold into servitude. The external project, the wall, is going well. The internal economy is devouring the people it is supposed to protect.

Nehemiah halts everything to fix it.

This is the test Leo XIV is proposing, whether he frames it in those terms or not. A DAO that concentrates power among large token holders is Babel with extra steps. A protocol that genuinely distributes decision-making to the closest level is Nehemiah's method. But a protocol that distributes governance while its actual economics extract value from the people doing the work, the data labelers, the content moderators, the miners running hardware at a loss, that protocol has built the wall and skipped chapter 5.

Leo does not spare the Church itself from this test. An entire section applies the principles of subsidiarity and solidarity to ecclesial structures, calling for "genuine, rather than merely nominal, participatory bodies" and warning against "paternalism that suffocates evangelical freedom." He addresses the abuse crisis directly: "listening to the victims of spiritual, economic, institutional, sexual and power-based abuse, as well as abuses of conscience, is an integral part of a path toward justice."

The encyclical also addresses a problem that most crypto whitepapers ignore entirely: the hidden labor sustaining digital systems. "A significant part of the digital economy's functioning relies on the silent work of millions of people engaged in essential yet largely unseen activities, such as data labeling, model training and content moderation, often involving disturbing material." Children "work in dangerous conditions, crushing the materials from which rare earth elements are extracted." Leo connects this to the Church's historical failure on slavery, which took eighteen centuries to condemn fully, and for which he offers a formal apology.

The parallel he draws is uncomfortable and intentional: the digital economy's supply chain has its own hidden coercion. The institutions benefiting from it have their own blindness to name. The wall looks impressive from the outside. The question is what is happening inside.

Invoking Chapter 5

I can describe this test from the inside, because I watched it fail.

Covenant AI, the team I work with, spent two years building distributed training infrastructure on Bittensor. The architecture was Nehemiah's method in code. Anonymous participants contributing GPUs to a shared training run. No central authority deciding who could participate. Coordination through incentive rather than command. SparseLoCo compressing gradient updates by 99%, so that ordinary internet connections could do the work that previously required a data center's internal fabric. The result was Covenant-72b: a 72-billion-parameter model trained across 160 GPUs operated by twenty independent peers who did not know each other and did not need to trust each other.

The wall was going up. The external project was working.

But the network it was built on failed the chapter 5 test. Bittensor advertises decentralization. In practice, governance concentrated in a small group with effective veto power over the protocol's direction. Staking mechanics rewarded capital concentration over contribution. The people running hardware, the node operators and miners doing the actual work of distributed intelligence, had less influence over the network's future than large token holders who contributed nothing but liquidity. The wall looked impressive from the outside. Inside, the economics ran in the wrong direction.

In April 2026, Covenant left Bittensor. Not because distributed training failed. The training worked. The architecture was sound. But the system surrounding it had reproduced the concentration it was supposed to prevent. A network that promises to distribute power but governs through a narrow class of stakers is not Nehemiah's method. It is Babel wearing Nehemiah's clothes.

Leo XIV would recognize the pattern. The encyclical warns against exactly this configuration: systems where "decisions regarding economic flows and digital platforms, as well as the governance of data and algorithms" are dictated by "a handful of actors" while the language of participation decorates the surface. Subsidiarity is not a branding exercise. It either structures the actual power relationships or it does not.

The distributed training itself, the SparseLoCo protocol, the gradient aggregation, the permissionless coordination of anonymous compute, that work continues. The architecture was always separable from the network it happened to launch on. What Bittensor demonstrated is that you can build the wall correctly and still fail chapter 5 if the economic layer inside the wall concentrates power among the people lending at interest rather than the people laying bricks.

The story generalizes beyond one network. It is a story about how the chapter 5 audit works in practice. You build something that distributes capability. You check whether the economics distribute power to match. If they do not, you have a choice: stay and pretend the wall is the whole story, or stop building and say why.

Nehemiah stopped. We stopped. Leo XIV is asking everyone to stop and look.

The Construction Site

Nehemiah did not write a whitepaper. He examined the ruins, convened the people, and assigned each a section of the wall. But if he had written one, the architecture would have been familiar. Distributed responsibility. Local execution. Shared specification. Coordination without command. No single builder controls the whole structure. The wall rises because everyone builds their part.

And when the economics inside the wall turned predatory, he stopped building and fixed them before continuing. That is the part we have not formalized in code.

Leo XIV published 38,000 words to make this argument. The convergence between Catholic Social Doctrine and decentralization principles is not a coincidence of terminology. It is a convergence of diagnosis. Both traditions identify concentrated power as the central threat to human dignity. Both propose distributed governance as the structural response. Both insist that the architecture of a system reveals its values more reliably than its stated intentions.

The divergence is in the self-examination. Leo's framework demands that the builders stop periodically and ask whether the system they are building is exploiting the people inside it as well as the people outside it. The crypto world is good at identifying external threats. It is less practiced at the chapter 5 audit.

The core claim fits in a sentence: the system that concentrates power will always build Babel. The system that distributes responsibility can build Jerusalem. But the system that distributes governance while centralizing extraction has built neither. It has built a wall around a debt market.

The construction site is open. Choose your section of the wall. But read chapter 5 before you start.