The HOP Optimisation Protocol

home/§7 Namespace & Trust Hierarchy

§7

Namespace & Trust Hierarchy

HOP uses a DNS-like namespace to manage cryptographic authority and prevent scam chains. The namespace is hierarchical, governed at each level, and inherits constraints from parent to child.

7.1 The Planetary Root

sol/earth/

The root namespace, designed for hard-fork survival. If earth/ is compromised (key leak, malicious takeover, governance failure), sol/ mints earth_v2/. The hard-fork mechanism is deliberately under-specified in v0.1; v0.2 must commit to a social mechanism (multi-signature threshold, ICANN-style international consortium, on-chain governance vote).

For v0.1, the planetary root is operated by a small consortium of HOP authors (Hopper, Beane, Yegge) plus the chain operators of the largest active Workchains. This is provisional and explicitly transitional.

7.2 Namespace Types

Closed (Attestation) Namespaces

sol/earth/governments/australia/identity/
sol/earth/medicine/registries/ahpra/
sol/earth/education/credentials/usyd/

Only the cryptographic key owned by the named authority can write or sign blocks here. The Australian Government is the only signer for sol/earth/governments/australia/identity/; AHPRA is the only signer for sol/earth/medicine/registries/ahpra/.

Closed namespaces are how regulated credentials enter the protocol. A medical license, a driver’s license, a security clearance — all live in closed namespaces signed by the relevant authority.

Open (Resolution) Namespaces

sol/earth/identity/private_certifiers/
sol/earth/work/general/

Public queries occur here to verify credentials. Anyone can write to an open namespace; consumers filter by which writers they trust. This is how, for example, private credentialing bodies (universities, online courses, professional associations) can issue credentials without implying government endorsement.

Private certifiers are deliberately kept in a separate tree from government attestation namespaces. sol/earth/identity/private_certifiers/coursera/ is unambiguously not government-issued; the resolution path makes this clear at lookup time.

Worker Sovereignty in Namespaces

Workers do not sit in institutional namespaces. There is no sol/earth/.../<institution>/<worker>/ — that would be the institution owning the worker’s identity. A worker’s identity lives in the open identity utility tree, sol/earth/identity/<jurisdiction>/<credential>/, and their chain is referenced by that identity but hosted wherever the worker chooses: primary device, personal backup, and optionally an authorised read-replica at an institution they have chosen to share with.

The institutional read-replica is constrained scope by the worker, not institutional ownership. The institution can read the parts the worker has chosen to share, and only those parts; the chain itself is the worker’s, and travels with them across jurisdictions and across employers. Anchor Blocks (§7.3) and the Federation Treaty Layer (§7.5) operate on this assumption — the worker is the sovereign in their own chain, and institutions interact with chains they do not own.

7.3 Anchor Blocks

Every Workchain must anchor to a parent chain via an Anchor Block. The Anchor Block is a public prospectus containing:

  • The chain’s published off-ramp tax rate
  • The chain’s Bean discount ratio (and v0.2 Bean Chain participation)
  • The chain’s governance rules (voting weights, dispute resolution mechanism, fee structure limits)
  • The chain’s currency name and issuance policy
  • The chain’s pointer to its parent chain in the namespace
  • The chain’s published cost transparency (validators, dispute resolution, agent hosting)

Anchor Blocks are read-once-and-trust. When a worker chooses to participate in a Workchain, they accept that Anchor’s terms for the duration. Workers can leave at any time (per the Forking Rule); the Anchor Block defines what they signed up for while they were there.

7.4 The Chain Hierarchy

The namespace is not flat. HOP supports a layered governance hierarchy:

🌎 World Chain (sol/earth/)
├── 🛠️ Utility Chains (identity, dispute resolution, crystallisation standards)
└── 🏭 Industry Chains
    ├── sol/earth/transport/
    ├── sol/earth/creative/
    ├── sol/earth/engineering/
    ├── sol/earth/medicine/
    └── sol/earth/...
        └── 🏢 Platform Chains
            ├── sol/earth/transport/<platform_a>/
            ├── sol/earth/transport/<platform_b>/
            ├── sol/earth/engineering/<firm_a>/
            └── ...
                └── 👤 Entity Chains (workers' Skillchains)

Each level has:

  • Stake requirements to participate at that level
  • Tax rate (cascading down through children)
  • Governance rules (inherited from parent and extended)
  • Exchange rates between chain-specific tokens

Stake-as-Governance Hierarchy

Stake at HOP is not a crypto deposit. It is rolling-average recent work quality plus accumulated chain-specific currency. Different stake levels grant different governance voices:

Stake Level What You Get
None Can bid on work, build CV, accept work, accumulate stamps
Platform-level Vote on platform governance (the platform’s tax rate, surge rules, dispute resolution policies)
Industry-level Vote on industry standards (Transport’s base insurance, accessibility requirements, cross-border rules)
World-level Vote on protocol fundamentals (the Five Laws, the planetary root governance, dispute escalation paths)

Stake is earned through work, but can be swapped up the hierarchy at exchange rates set by governance. For example: 1,000,000 platform-tokens might exchange for 1,000 World-Transport-tokens. The exchange rate is the barrier to entry and the ladder simultaneously.

The Small Operator Example

A small operator — say, four cars in a regional town — cannot afford to participate at World-Transport-chain level; the stake requirement is too high. But they don’t need to. They can:

  1. Operate as a small Workchain (their four drivers have CVs, the operation has its own chain).
  2. Bid on a ride-share platform’s chain (paying its tax rate, accumulating that platform’s tokens).
  3. Slowly accumulate platform-level stake through completed work.
  4. Eventually swap accumulated platform tokens for industry-level stake, gaining a voice in how transport standards are set.

This means small operators don’t need permission from incumbents to exist. The protocol provides the path from “four cars in a regional town” to “seat at the table”.

Tax Cascade Through the Hierarchy

A $15 ride in this hierarchy:

World Transport: 0.1% base tax    ($0.015) — funds standards body, dispute resolution
    └── Platform: 25% platform cut ($3.75) — funds platform ops, insurance, marketing
        └── Small operator: 10%    ($1.12) — funds operator's small business
            └── Driver: keeps the rest ($10.11)

Critically: all of this is visible on-chain. The rider knows exactly where their money went. The driver knows exactly what they’re keeping. No hidden fees. The tax cascade is the price of structured federation, paid transparently at every level.

Children Inherit, Cannot Remove

Child chains can overload parent chain rules — adding strictness — but cannot remove them. A construction Workchain anchored to sol/earth/engineering/construction/ can require police checks and trade qualifications; it cannot weaken the parent chain’s anti-discrimination rules. This is what makes the hierarchy meaningful: governance flows downward and is enforced by parent chains’ refusal to recognise non-conformant children.

A child chain that violates a parent rule loses its anchor; once unanchored, it is effectively delisted from the namespace tree. Workers and posters can still interact with it directly, but cross-chain federation breaks. This is the protocol-level mechanism for enforcing inherited governance.

7.5 The Federation Treaty Layer

Workchains at the same level can federate horizontally via federation treaties. Treaties define:

  • Mutual recognition of skill stamps (a driving stamp from one ride-share platform counts on another)
  • Currency swap rates and shared liquidity pools
  • Joint dispute resolution for cross-chain disputes
  • Worker mobility terms (how a worker carries reputation between treaty signatories)

Federation treaties become a first-class object of geopolitics. ASEAN labour mobility might mean South-East Asian Workchains sign mutual low-tax treaties. Two Tier-1 banks within a national banking sector might federate cleanly. Five Eyes might federate broadly. A nation that writes the standard treaty template — the Zollverein move — captures the network position without owning the network.

Gradient Federation

The Federation Treaty Layer’s deepest property, once named, is that federation has depth and breadth as two continuous axes, not a single binary recognition status. Depth is how foundationally two parties bridge — a treaty can cover only narrow technical interop, or it can extend to mutual currency convertibility, joint dispute adjudication, and shared identity recognition. Breadth is which categories are bridged — two sovereigns can federate on identity but not on currency; two can federate on identity for some chain types and not others. Each bridge is negotiated independently, operates at its own depth, and is revocable without revoking the others.

This is the post-Westphalian primitive of HOP. The 1648 Westphalian settlement made recognition binary on both axes: sovereign A either acknowledges sovereign B’s authority, or doesn’t; federation was either fully political or it wasn’t. Gradient Federation makes recognition continuous on both axes. Federation becomes the set of narrow trust-floor treaties parties choose to share at the floor, not a status they grant each other. Disagreement at the leaf does not prevent cooperation at the trust floor. Two sovereigns, two governments, two systems can coexist on the same protocol without either having to recognise the other’s authority over its own subjects.

See mythology/01-bismarck for the 1834→1871 worked counterfactual showing how Gradient Federation under HOP would have enabled the outcome of German unification — cross-state mobility, common standards, economic integration — without the costs of Bismarck’s three wars and the sovereignty extinction at Versailles.

7.6 The Utility Chain Layer

Utility Chains are special-purpose chains at the top of the hierarchy that provide protocol-wide services without being industry-specific:

  • Identity utility — proof-of-personhood, proof-of-not-banned, proof-of-citizenship (for chains that require it)
  • Dispute resolution utility — escalation path for disputes that exceed Workchain capability
  • Crystallisation standards utility — defines how new chains are minted, how Anchor Blocks must be structured, what governance forms are acceptable
  • Translation utility — cross-chain skill-vector translation attestations

Utility Chains are operated as commons; they do not extract tax from the work that flows through them. Their operating costs are funded by the Workchains that depend on them, paid as anchor fees.