/ˈprəʊ.tə.kɒl ˈkæp.tʃər/From Greek protokollon ("first sheet glued to a manuscript," later
"official record, diplomatic procedure") + Latin captura ("a catching, seizure"). The
compound names the seizure of a decentralized protocol's intended distribution by concentrated
deployment patterns that reproduce the centralization the protocol was designed to prevent.
Definition
The condition in which a decentralized protocol's deployment reproduces the centralization its design was
intended to prevent. A protocol may be genuinely decentralized in its specification — designed so that
any node can participate, no single node is authoritative, and control is distributed across the
network. Protocol Capture occurs when the actual deployment of that protocol concentrates participation,
authority, and infrastructure in a small number of nodes, operators, or hosting providers, recreating at
the ecosystem level the centralization that the protocol level was designed to eliminate.
The Fediverse as Case Study
The ActivityPub protocol is genuinely decentralized in specification. Any server can implement it, any
instance can federate with any other, and no central authority governs participation. In deployment, a
small number of large instances host the majority of users, those instances depend on the same
concentrated hosting infrastructure (AWS, Hetzner, OVH) as centralized platforms, and the practical
experience of most fediverse users is mediated by a handful of operators whose decisions about
moderation, federation, and infrastructure shape the network as decisively as any centralized platform's
policies. The protocol distributes. The ecosystem concentrates. The sovereignty claim — "we are
decentralized" — describes the specification, not the reality.
Why Protocols Are Not Enough
Protocol Capture reveals that decentralization is not a property of a protocol but a property of a
deployment. A protocol can enable decentralization without producing it. The production of genuine
decentralization requires not only a distributed specification but distributed infrastructure,
distributed governance, distributed funding, and distributed technical capacity — conditions that are
expensive, difficult, and boring in exactly the same way that genuine sovereignty is expensive,
difficult, and boring. Protocol Capture is what happens when the community invests in the specification
and neglects the stack.
Excavation Note: Protocol Capture was identified as the third of four Sovereignty Theater
mechanisms in "Sovereignty Theater" (2025). The term draws an implicit parallel with regulatory capture —
the condition in which a regulatory agency comes to serve the interests of the industry it was designed to
regulate. In Protocol Capture, a decentralized protocol comes to serve the concentration patterns it was
designed to prevent.