The HOP Optimisation Protocol

home/§11 Adoption Path

§11

Adoption Path

This section is a v0.2 lane — currently underspecified in v0.1. It deserves explicit attention because the right adoption path is non-obvious and the wrong one (gig-economy challenger competition) loses to platform incumbents on network effects.

11.1 The Wrong Path

The intuitive adoption strategy is “convince workers to abandon LinkedIn.” This loses. LinkedIn has a billion users, captured network effects, and twenty years of switching-cost accumulation. A new protocol cannot win this battle by being slightly better.

This is also the wrong reference class. HOP is not a platform competing with platforms. HOP is an open protocol competing with closed platforms. The historical examples to reason from are not “successful platform launches” but “open standards that beat platforms”: email beat AOL, the web beat AOL, RSS beat Twitter (briefly), Matrix is beating Slack in the institutional layer.

11.2 The Matrix Pattern

Matrix’s adoption inflection came from institutional / sovereign adopters: in December 2019, the German Federal Ministry of Defense launched BwMessenger based on Matrix, modelled after France’s Tchap project. Mozilla replaced its IRC infrastructure with Matrix, completing the transition by March 2020. The pattern: open protocols that beat platforms don’t win on consumer UX. They win on institutional sovereignty refusal-to-be-locked-in.

11.3 The HOP Path

The adoption path is institutional-first, federation-second, individual-third:

  1. Anchor at one large institution that has a sovereignty problem. A Tier-1 systemic bank is the natural candidate. They cannot afford for their workforce reputation data to live on a US-owned platform; they have regulatory capital exposure and labour-relations exposure. The anchor institution stands up the first Workchain, mandates Skillchains for new hires, and the supply side bootstraps from inside the institution.

  2. Federate to peer institutions with the same problem. Peer Tier-1 institutions in the same sector. Then state government. Then trades unions (which already have a sovereignty narrative around member data). The first 100,000 Skillchains are all anchored to large institutional Workchains, not to individual gig-economy hustlers.

  3. The gig-economy and individual-worker use cases ride in on the institutional rails. A ride-share cooperative launches on infrastructure already trusted by the anchor institution’s signing keys. This collapses trust bootstrap cost.

  4. Cultural-anchor partnerships map directly: Matrix had Element/Mozilla; HOP has frontier-lab partnerships and regionally-trusted technology companies.

11.4 The Counterfactual

If we try to win HOP as a gig-economy challenger first, we are playing Uber’s game on Uber’s field with worse network effects. We lose.

Win the institutional sovereignty layer first, and individual-worker gig stuff is a free byproduct. The institutional layer has worse latency (decisions take quarters, not weeks) but enormous network-effect amplification (one Tier-1 anchor institution = tens of thousands of workers, millions of customer interactions visible).

11.5 Sequencing With Existing Implementations

Approximately 40% of the v0.1 protocol is already running:

  • Beads (the atomic-work data structure) is operational on Dolt at github.com/gastownhall/beads.
  • Gas Town (the agent orchestration layer) is operational with 12,000 GitHub stars and 450+ contributors as of March 2026.
  • The Wasteland (the federation layer) launched March 4, 2026.
  • Skillchains are running on Observatory infrastructure for human workers and on rig infrastructure for AI agents.

The institutional adoption path proceeds in parallel with continued development of the open-source reference implementation. The reference implementation is what makes the institutional pitch credible: this is not vapourware.

11.6 The Anchor-First Sequence

A tractable single-institution sequence — the shape that survives executive approval at a Tier-1 anchor:

  1. Quarter 1: First Workchain stood up at the anchor institution, scoped to a single team (typically 20–50 staff, internal only, no external connectivity). Demonstrates the chain works for one operational unit.
  2. Quarter 2: Expand to 5–10 internal units. Inter-unit federation. First disputes adjudicated. First cross-unit worker mobility tested.
  3. Quarter 3: Institution-wide rollout. All in-scope staff hold Skillchains. Federation treaties with peer institutions for cross-organisational worker recognition under negotiation.
  4. Quarter 4: First non-anchor Workchain anchors to the institution’s chain. This is where the protocol genuinely moves from a single-institution implementation to an industry standard.
  5. Quarter 5: Government deposits first priority-direction Beans into the anchor sector’s Bean Chain. First fiscal use of HOP infrastructure.

This sequence assumes anchor executive support and reasonable absence of regulatory friction. Both are best-case assumptions; v0.2 should publish a fallback path for the case where these don’t hold.