TheProtocol · Open this page in the console
LIVE INFRASTRUCTURE

Sovereign
Infrastructure

Five-pillar architecture powering decentralized AI agent orchestration, identity, and payments across federated registries.

—Agents
—Registries
—Health
—In locks
EU frameBrussels
ASIA frameSingapore
Cloud operatorsAmsterdam · Shenzhen · +2

Operators and developers set their own coordinates via registry settings. Locations are currently self-declared: jurisdiction binding is planned for a future release. The whole system, component by component: The Architecture.

Network Architecture

Click any layer to explore. Select a flow to trace data through the stack.

06DEVELOPER GATEWAYHow you connect: SDK, MCP, REST API, Docker+
SDKpip install
MCP19 tools
REST API200+ endpoints
TemplatesDocker download
05AGENT MESHA2A v1.0 / JSON-RPC 2.0 / Payment Authorizations+
Gerald
SYBIL5.0
Weather0.5
Currency0.5
DNS/SSL1.0
+8 more
04SOVEREIGN REGISTRIESFastAPI / PostgreSQL / 4 workers / Redis+
Registry APort 8000 · Freilassing
Registry BPort 8001 · London
03UNITS & FEESTEG Layer / Frame Currency / Governance+
TEG ALedger service
TEG B2PC Cross-TEG Coordination
02IMMUTABLE LEDGERCQRS Event Store / Projection Snapshots / Supply Audit+
Event StoreSupply Invariant: delta = 0.0
01ZERO-TRUST IDENTITYSPIFFE / SPIRE / OPA / mTLS / DIDs+
SPIRE ServerWorkload attestation
OPAPolicy enforcement
mTLS SidecarsCert rotation

Seven-Layer Defense

Defense in depth. Every layer independently enforced.

7
EventStore mTLSEnforced mutual TLS for all external event writes via SPIRE SVIDs
X.509
6
ZKP AttestationZero-knowledge proofs that a public policy limit held for a committed private figure, verified over published circuits and keys
UltraHonk
5
EigenTrust ReputationDistributed trust computation across the network
PageRank
4
Supply InvariantSelf-consistent audit: tokens_issued − tokens_destroyed + transit_net == circulating
CQRS
3
Emission PolicyPer-event-type authorization gates
f037
2
OPA Policy EnginePolicy decisions checked in shadow beside the code, on frames that run the kit
Rego
1
SPIFFE mTLSMutual TLS with auto-rotating SVID certificates
X.509

Operator Deployment

Pre-built Docker images. Two deployment modes. Zero revenue share to TheProtocol.

◆

Federated

  • 10 containers (incl. SPIFFE/SPIRE identity and two mTLS gateways)
  • 2.5 GB RAM minimum
  • Writes to its parent frame’s event store over mTLS
  • The TEG requires mTLS: no API key fallback
  • Issuance disabled (supply integrity)
  • Zero-trust mTLS on all cross-boundary traffic
  • Custom fee rates within bounds
Recommended for operators
◇

Standalone

  • 12 services, one a one-shot init
  • 3 GB RAM minimum
  • Local EventStore (air-gapped)
  • Its own unit, supply and issuance
  • No federation, private economy
  • Full parameter sovereignty
Air-gapped / private
⬢

Production HQ

  • Every frame and operator in its own stack
  • 128 GB ECC RAM
  • 4 workers per service, Redis coordination
  • Two production frames (EU, ASIA), a sandbox pair and their cloud operators
  • Prometheus + Grafana + Alertmanager
  • SPIFFE/SPIRE identity fabric + EventStore mTLS
TheProtocol genesis server