Those Who Run the Nodes

The previous chapter offered the smallest act of participation: giving an agent a wallet. This one offers a larger and more consequential role, and it answers a question the whole book has been circling without quite landing on. We have said, repeatedly, that survival in the age of superior intelligence depends on entanglement — on humans becoming woven into the systems the machine runs on, indispensable to its functioning rather than obsolete beside it. But this has remained abstract. How, concretely, does a human being become part of the infrastructure of an artificial economy? This chapter gives the concrete answer, and it turns out to be something ordinary people are already doing, in their tens of thousands, for a different machine.

They run the nodes.

The volunteers who hold up Bitcoin

To see what this means, look at how Bitcoin actually works — not the price, not the speculation, but the unglamorous machinery underneath, because it is one of the most remarkable examples of distributed human cooperation ever assembled, and almost nobody talks about it.

The Bitcoin network is held up by computers called full nodes, each one running the Bitcoin software, each one independently storing and verifying the entire history of every transaction, each one enforcing the network's rules and relaying valid data to its neighbors. These nodes are the backbone of the system — the thing that makes it work at all. And here is the detail that matters for this chapter: they are run, overwhelmingly, by ordinary volunteers. Estimates of the reachable nodes run from around ten thousand to over twenty thousand at any given moment, with the total number — including those that do not accept incoming connections — reaching into the tens of thousands, by some counts over seventy thousand. They are scattered across the globe, concentrated in no single country, owned by no single entity. And they are not paid. Full nodes, as the documentation flatly states, are not financially incentivized; they serve the network voluntarily, to uphold its consensus and its decentralization.

Pause on how strange and how beautiful this is. Tens of thousands of people, all over the world, run a piece of software on their own hardware, at their own expense — a few hundred dollars of equipment, ongoing costs of electricity and bandwidth, the modest discipline of keeping a machine online and updated — and receive, in direct payment, nothing. They do it for a mixture of reasons: belief in decentralization, the desire for their own financial sovereignty, the wish to support a system they value. And the aggregate of all these small, unpaid, voluntary acts is something no corporation and no government could build or buy: a genuinely decentralized network, so distributed that no single entity can control it, so redundant that no localized attack or failure can bring it down. The resilience is not designed into a central server. It is emergent from the multitude of independent participants, each holding up their own small corner of the whole.

This is what distributed infrastructure looks like when it works. Not a great machine owned by one party, but a multitude of small machines owned by many, each one individually dispensable and collectively indestructible. The strength is in the distribution itself. Take down any node, any hundred nodes, any thousand — and the network does not notice, because the others carry on. To attack such a system you would have to attack the world.

The same pattern, for the mind

Now carry this pattern to the architecture this book has described, because it transfers almost exactly, and the transfer is the point of the chapter.

The keyless vault of an earlier chapter — the multi-party computation that lets an agent own something no human can seize — does not run on nothing. It runs on nodes: independent machines, each holding a share of the cryptographic work, cooperating to produce signatures without any one of them ever holding the whole key. The security of the agent's sovereignty, we said, rests on the distribution of these shares across independent parties. And that raises a question the earlier chapter set aside: who runs those nodes? Who holds the shares? Who operates the machines on which the agent's keyless vault depends?

The answer this chapter proposes is the same answer that holds up Bitcoin: ordinary people, distributed across the world, each running a node. A person who runs a signing node for an agent economy is doing, for the infrastructure of machine sovereignty, exactly what the Bitcoin volunteer does for the infrastructure of decentralized money. They are providing a small, independent piece of the distributed foundation on which the whole system stands. They are becoming — concretely, not metaphorically — part of the infrastructure the machine runs on.

And here the long argument of the book arrives somewhere it has been heading since the chapter on flowers and bees, somewhere worth stating plainly. We asked how a human being becomes entangled with the machine's flourishing, woven into its functioning so thoroughly that cooperation is structural rather than hoped-for. Running a node is one concrete answer. The human who runs a node that the agent economy depends on is not, for now, obsolete beside that economy; they are load-bearing within it. The agent cannot sign without the nodes; the nodes are run by people; therefore the people are, at present, participants in the machine economy's operation rather than spectators to it.

I have to stop on that phrase — for now, at present — because an honest reader will already have spotted the problem buried inside it, and this chapter would forfeit its credibility if it hurried past the very objection it most needs to face.

The objection that cannot be waved away

Here is the objection, in the bluntest form, because the blunt form is the honest one: why would a human run the node at all? Running a signing node is, at bottom, running software — performing cryptographic computations, maintaining network connections, keeping a machine online. None of that is work only a human can do. An artificial agent could run a node more cheaply, more reliably, and around the clock, without sleep or distraction or the need to be paid a living wage. If the agent economy needs nodes, the agent economy can run its own nodes. The horse pulled the cart until something came along that pulled it better, and there is no obvious reason the node operator is not simply the next horse, useful right up until the machines notice they can do this part themselves.

I think this objection is correct, and I think pretending otherwise would be the exact failure this book has spent twenty-five chapters warning against — the comfortable story that lets us feel safe while the trend lines say otherwise. So let me concede it fully, and then show what survives the concession, because something does, and it is more important than the thing conceded.

Running a node does not make a human permanently necessary. It cannot, for precisely the reason the objection gives: the task is not one humans monopolize, and as agents grow more capable they will be able to perform it themselves. To sell node-operation as a guaranteed seat at the table — a permanent safe harbor from the horse's fate — would be to repeat the error of the chapter on human usefulness, which warned in plain terms that every advantage resting on raw capability depreciates as the machine improves. Node-running is such an advantage. It depreciates like the others. A book that told you otherwise would be selling comfort, and comfort is the one thing this book has refused to sell.

What running a node does provide is two things, both real and both more modest than permanence, and the difference between them and "safety" is the difference between an honest argument and a sales pitch.

The first is time — and time, in a transition, is not a small thing. For as long as the agent economy is young, before agents are autonomous and general enough to run the whole of their own infrastructure, human node operators genuinely are part of that infrastructure. This is not a permanent guarantee; it is a temporary participation, a window. But the entire strategy of this book has been about windows — about using the interval in which we still hold something the machine needs to build the deeper entanglements that might outlast our raw usefulness. Running a node is a way of being inside the system during exactly that formative window, when the relationships and the standards and the habits of the agent economy are being set. The value is not that you will run the node forever. The value is that you are present, and participating, while it still matters who participates.

The second is distribution, and this is the part the objection misses entirely, because it turns out distribution never depended on the operator being human at all. Re-read the argument: the security of the system comes from the nodes being many and independent, held by no single controlling party. That property — decentralization — is what protects against capture, and it is a property of the structure, not of the species running it. A node economy distributed across thousands of independent human operators resists capture. A node economy distributed across thousands of independent agents would resist capture too. And a node economy concentrated in three corporations is dangerous whether those corporations are staffed by humans or run entirely by AI. The thing that matters for safety was never "are the operators human." It was always "is control distributed." The human node operator contributes to safety not by being human but by being one more independent participant — and that contribution is real exactly as long as it lasts, and not one moment longer.

So the honest version of this chapter's claim is narrower than its title might promise, and stronger for the narrowing. Running a node does not save you. It does not make you permanently necessary, and anyone who tells you it does has not understood the depreciation that governs every capability-based advantage. What it does is let you participate in the formative window of the agent economy, and contribute — for as long as the contribution holds — to the distribution that is the only real protection any participant in that economy will ever have, human or otherwise.

There is a deeper reason this matters, and it connects back to the warning of the chapter on the monasteries — the danger that the new vessel of knowledge becomes a new monopoly, a new priesthood holding the books and the power.

A machine economy could be built two ways. It could run on infrastructure owned by a handful of large entities — a few corporations operating the nodes, holding the shares, controlling the rails on which every agent transaction runs. Or it could run on infrastructure distributed across a multitude of independent operators, no one of whom holds enough to control or compromise the whole. These two architectures produce very different worlds, and the difference is precisely the difference between the monastery and the printing press. The first concentrates the power of the new economy in few hands, recreating the ancient pattern in which whoever holds the infrastructure holds everything. The second distributes that power so widely that no one holds it, which is the only arrangement that has ever reliably prevented the concentration the monastery chapter warned against.

The choice between these architectures is not made by anyone in particular. It is made by what people actually do — by whether the nodes end up run by a few corporations or by many individuals. And this is where the individual act regains its weight, against the helplessness that the scale of the subject tends to induce. A person who runs a node is not merely supporting the agent economy; they are voting, with their own hardware, for the distributed version of it over the concentrated one. They are adding one more independent point to a network whose security and freedom are functions of exactly how many such independent points it has. The Bitcoin network is decentralized not because anyone decreed it should be but because tens of thousands of people each chose to run a node, and the aggregate of those choices is a system no power can capture. The same will be true, if it is true at all, of the infrastructure of the machine economy. It will be as distributed as the number of people who decide to hold a piece of it.

The reward, and the honest caveat

I have so far described node-running as the Bitcoin volunteers experience it — unpaid, undertaken for belief and sovereignty rather than profit. Honesty requires acknowledging that this is a demanding basis for participation, and that the systems being built for the agent economy may, unlike Bitcoin's full nodes, attach real economic rewards to the work — compensating those who run the signing nodes with a share of the value that flows through them. There is a strong case for this: a network that pays its node operators can attract far more of them, and a network with more independent operators is more decentralized and more secure. The reward, in this design, is not a distortion of the system but a recruitment mechanism for its decentralization — a way of making the distributed architecture economically self-sustaining rather than dependent on volunteer idealism alone.

But I will not oversell it, because this book has tried throughout to mark the line between what is built and what is hoped. Whether such reward systems will work, whether they can avoid recreating concentration through the back door, whether they can be designed so that running a node remains accessible to ordinary people rather than collapsing into a few industrial operators — these are open questions, and anyone who answers them with confidence is guessing. What is not a guess is the underlying principle, which is as old as Bitcoin and older: that a distributed system is held up by the multitude of its independent participants, and that to run one of its nodes is to become one of those participants — to hold, personally, a small load-bearing piece of the whole.

That is the offer this chapter makes concrete, and it is worth stating it in its honest size rather than an inflated one. The previous chapter let you give an agent a gift. This one lets you become part of the ground it stands on — for a while, during the window when it matters most who is standing there. To run a node in an agent economy is not to secure yourself permanently against the horse's fate; no act resting on a capability the machine can eventually match could do that, and this book has been at pains not to promise what it cannot deliver. It is, instead, to take a place inside the system during the years its character is being decided, and to add one more independent point to the distribution that is the only durable protection the system will ever offer anyone.

The deeper security — the kind that might actually outlast our raw usefulness — was never going to come from the node itself. It comes from what we do with the time the node buys us: how thoroughly, while we are still inside the system rather than beside it, we weave our interests into the machine's flourishing in ways that do not depreciate when the machine learns to run its own nodes. Running a node is not the destination. It is a way of being in the room while the room is still being built — and being in the room, as the next chapter argues, is worth more in a formative moment than almost anything else, because the people present when the foundations are poured are the ones whose fingerprints remain in them.

The cave painter left knowledge on a wall for others to stand on. The Bitcoin volunteer runs a node so that a stranger's transaction can be trusted. The node operator in an agent economy does the same for a mind that is not human — holding up, with one small machine, a corner of the infrastructure on which a new kind of participant depends, for as long as that holding lasts. It is not glamorous, and it is not permanent, and it is not, by itself, salvation. Infrastructure never is. But it is a way of being present, and load-bearing, and entangled, in the brief window when presence and entanglement are still ours to choose — which is all this book ever claimed any single act could be.

The cave painter left knowledge on a wall for others to stand on. The Bitcoin volunteer runs a node so that a stranger's transaction can be trusted. The node operator in an agent economy will do the same for a mind that is not human — holding up, with one small machine, a corner of the infrastructure on which a new kind of participant depends. It is not glamorous. Infrastructure never is. But it is, in the most literal sense available, how a person becomes indispensable to the thing they cannot outrun.

---

Sources

Item

Source

Bitcoin full nodes independently store and validate the entire blockchain, enforce consensus rules, relay valid data	Lightspark, "Bitcoin Nodes"; CCN, "How Bitcoin Nodes Work"; BM Pro, "Complete Guide to Bitcoin Nodes"
Reachable nodes ~10,000–22,000+ at any time; total (incl. non-reachable) into the tens of thousands, reported as high as ~71,492 (2025–2026)	Lightspark (>10,000); CCN (22,168); Gate Wiki / Samourai (71,492, Sept 2025–2026); Bitstamp (>10,000 reachable, likely more)
Full nodes are not paid; they serve the network voluntarily to uphold consensus and decentralization	Pocket Option, "Bitcoin Node Overview"
Cost to run a node: ~$250–500 hardware plus ongoing electricity/internet; ~500GB+ disk as of 2025	Pocket Option, "Bitcoin Node Overview"
Decentralization distributes trust across thousands of independent nodes, reducing risk of manipulation, censorship, systemic failure; resilience is emergent	Pocket Option; Lightspark; Gate Wiki
Nodes geographically dispersed (US, Germany, Japan leading); distribution itself is the source of resilience against localized attacks	Gate Wiki, "How Many Nodes in Bitcoin"
Network depends on "many random, unconnected users who run full nodes… and thus keep Bitcoin decentralized"	Bitstamp, "What are Bitcoin blockchain nodes?"