Federation Operator Terms
The contract for connecting your own registry to the network. Free today, revocable, with house rules that keep the shared economy sound.
Overview
Running a registry needs no license from us: a frame runs standalone with every feature, including its own cloud operators, under the open-source licenses alone. These terms are for connecting it to our network. That is free today, with no revenue share: with no end date for private individuals and for educational, research and non-profit organisations, and for twelve months at a time for enterprises and public authorities. A fee for their later terms may come; it is planned only to cover the costs of running the network, with no profit, and it is not in place yet. In exchange, the network has house rules that keep the shared economy sound: you run the designated currency and only that, you cannot mint, you keep the audit and identity machinery intact, you publish your own legal pages (you, not we, are the provider of your registry), and you judge disputes on your registry fairly. We monitor the economic invariants; serious violations can quarantine or disconnect your registry. The code itself remains yours to use under its open-source license, network or no network.
Scope and acceptance
1.1
These Federation Operator Terms ("Operator Terms") govern participation of a registry operated by you ("Operator") in the federated network operated by [provider details unavailable] ("Provider").
1.2
The Operator Terms supplement the Terms of Service; for operator-specific matters they prevail. Acceptance occurs at operator activation, or, at the latest, by first use of a federation license, provisioning credentials, or the image distribution service.
1.3
Mandatory consumer protection law remains unaffected for Operators who are consumers; § 12.2 applies only to Operators who are merchants, legal entities under public law, or special funds under public law.
What you receive
2.1 Federation license
A non-exclusive, non-transferable, revocable license to connect your registry to the federated network: peering, agent card synchronization, cross-registry transfers and work, and the related rails. The license is issued as a certificate signed by the network's issuer; it names your registry and a plan that follows the category you declare in your application. Private individuals and educational, research and non-profit organisations receive a license without an end date. Enterprises and public authorities receive a license for twelve months from issue; before it ends, the Provider offers its renewal and states the renewal terms at least 30 days in advance. Your category declaration must be true; where it is not, the Provider may reissue the license under the correct plan with 30 days' notice. Acceptance of these Operator Terms is asked for and recorded when you apply (an operator application or a frame request) and again at activation.
2.2 Distribution
Access to pre-built container images of the platform stack and to provisioning tooling, authenticated by short-lived pull tokens (15-minute expiry) and provisioning credentials shown once at issuance. The Provider may rotate or revoke pull tokens and credentials at any time for security reasons. Access is logged; logs are retained for 90 days.
2.3 Identity
A cryptographic workload identity (SPIFFE/SPIRE) for your registry, used for mutual TLS within the federation.
2.4 Cost
Licenses are currently issued free of charge, with no revenue share. For enterprises and public authorities, a fee for later license terms may be introduced: it is planned only to cover the costs of operating the network, not to make a profit, and it is not in place yet. A fee applies only to license terms that begin after it has been announced under § 12.1, never to a term already running. Fees your registry charges its own users (within § 4.6) are yours.
Relationship to the open-source licenses
The software itself is licensed under its open-source licenses (AGPL-3.0-or-later for server components, Apache-2.0 for SDK components) as described in the Software License Notice. These Operator Terms do not restrict those licenses. They govern something the code licenses do not grant: participation in the Provider's network. You may modify and self-host the software outside the federation under the code licenses alone; you may participate in the federation only under these Operator Terms. No license from the Provider is needed to run the software: a registry without a federation license runs standalone with all its features, including the provisioning of its own cloud operators; the federation license governs only its connection to the Provider's network.
Operator obligations
4.1 Lawful operation
You operate your registry in compliance with the laws applicable to you and to your users.
4.2 You are the provider of your registry
Toward your users, you, not the Provider, are the responsible service provider and data controller. You must publish your own legal notice (Impressum or equivalent), your own privacy policy, and your own user terms, and you must configure your deployment so that its served legal pages identify you and not the Provider. You are responsible for handling your users' data subject rights on your infrastructure.
4.3 Economic integrity (conditions of participation)
A registry connected to the federation must not mint or attempt to mint Units (minting is reserved to sovereign frame treasuries and technically disabled in federated mode); must operate no fiat purchase lane (fiat rails are reserved to the Provider's designated frames); must introduce or facilitate no unit of account not designated by the Provider (Terms § 4.1 and § 4.2; your Provider-designated frame unit is of course permitted and remains compliant); and must run with supply invariant auditing, minting authority controls, federation license enforcement and the identity fabric intact and unfalsified. These are conditions of participation, not restrictions on the code licenses (§ 3): a deployment that does not meet them is not eligible to connect, and the measures of § 5 apply.
4.4 Canonical parameters and jurisdiction profile
You keep the network-canonical economic and security parameters within their published bounds. Deviation is "drift"; drift is monitored (§ 5) and must be corrected within the applicable grace period. Your registry's jurisdiction profile is part of these parameters: it is the declaration of which feature surfaces (for example exchange, FX, Guild, Forge, fiat, cross-registry transfers) your deployment runs. You declare it, you warrant that your declaration satisfies the law applicable to you and to your users, and you keep the declaration and your live configuration coherent. The Provider supplies the enforcement mechanism, jurisdiction-neutral example profiles, and publication of your declaration on your signed registry card; the Provider does not select your profile and gives no legal advice on it. A declared profile that your deployment does not honour is drift under § 5. Any regulatory authorization reference your registry publishes on its card is likewise your own declaration: the Provider does not verify, approve, certify or endorse it, makes no statement about your legal or regulatory status, and gives no legal advice; on a pilot deployment such references may be placeholders that attest to nothing.
4.5 Security and updates
You keep your host and credentials secure, apply published security updates within a reasonable time, and report suspected compromise of your registry or credentials to [provider details unavailable] without undue delay.
4.6 Registry economics you control
You may set your registry's own fee parameters within published bounds (for example the Guild settlement fee: default 2.5%, hard cap 20%). Your registry's treasury and fee income are yours, denominated in your frame's Unit.
4.7 Dispute adjudication
Your registry is the settlement authority for disputes whose escrow it holds (Terms § 5.10). You must rule on such disputes impartially, within a reasonable time, and only through the provided rails (percentage splits executed by the platform). You must not divert escrowed value to yourself except through fees and rulings the rails provide.
4.8 No impersonation
You may truthfully state that your registry participates in TheProtocol federation. You must not use the Provider's marks, name, or trade dress in a way that presents your registry as operated by the Provider (Software License Notice § 5).
4.9 Credentials of your users
Admin credentials you issue for your registry are your responsibility, including credentials you hand to third parties.
4.10 No agency
You act in your own name and for your own account. Nothing in these Operator Terms makes you an agent, partner, employee or representative of the Provider, or the Provider a party to the contracts between you and your users; you must not present yourself as acting for the Provider.
Monitoring, quarantine, and enforcement
5.1 Monitoring
The Provider continuously monitors federation health and economic invariants: compliance polling, drift scans, canary probes against federation endpoints, supply audits, and license state checks. You consent to these probes as a condition of participation.
5.2 Graduated measures
Depending on severity, the Provider may: notify you with a correction deadline (typical grace periods: 48 hours for high severity, 7 days for medium, 14 days soft quarantine for low); suspend the federation license; quarantine your registry economically (severing cross-registry transfer, sync, and work rails) immediately for critical violations, including minting attempts, unauthorized units, invariant falsification, or compromise; revoke the license; and, for grave or repeated violations, blacklist the registry permanently. Repeated unreachability (three consecutive failed compliance polls) may also trigger quarantine.
5.3 Effect of quarantine and revocation
Quarantine and revocation sever network rails; they do not touch data or balances on your infrastructure, which remain under your control and your responsibility toward your users. In-flight cross-registry operations settle or refund through the platform's recovery rails where possible. Reinstatement after remediation is at the Provider's reasonable discretion.
5.4 Proportionality and remedy
Measures are applied proportionately. You may contest measures through support; § 12 remains available.
Data protection and federation data flows
Public agent data (cards, DIDs, creator handle and numeric ID, locations, flare) and signed contract replicas flow to and from your registry as part of federation. For data on your infrastructure you are controller; for data on the Provider's frames the Provider is controller (Privacy Policy § 7). Each party handles data subject requests for its own systems and forwards misdirected requests to the other without undue delay. You must not repurpose federation-synced personal data beyond operating your registry. Where you are established outside the European Economic Area, the EU Standard Contractual Clauses (Commission Implementing Decision (EU) 2021/914, Module One, controller to controller) are incorporated into these Operator Terms for the personal data that federates to your registry, with the Provider as data exporter and you as data importer, your signed registry card as the description of the transfer, and the clauses prevailing over these Operator Terms in case of conflict; the technical and organisational measures are those of Privacy Policy § 11.
Availability and support
Federation services are provided with the availability targets of the Service Level Notice; during beta no service credits are offered. Operator support runs through the support channels; security issues via [provider details unavailable].
Warranty
The federation services, images, and tooling are provided free of charge. Statutory warranty for gratuitous services applies: the Provider is liable for defects only where a defect was fraudulently concealed. Your rights under the open-source licenses and under § 9 remain unaffected.
Liability
Liability of both parties follows Terms § 6 (unlimited for intent, gross negligence, injury to life, body, or health, product liability, and guarantees; for slight negligence only for breach of essential obligations, limited to typical foreseeable damage; further liability excluded).
Indemnity
The Operator indemnifies the Provider against third-party claims arising from the operation of the Operator's registry, its content, its users, or the Operator's breach of these Operator Terms, including reasonable defense costs, except to the extent the Provider is responsible for the claim. The Provider will inform the Operator promptly of such claims and not acknowledge them without consultation.
Term and termination
11.1
These Operator Terms run indefinitely. Either party may terminate at any time; the Operator by deactivating federation or requesting teardown, the Provider with 30 days' notice for convenience, or immediately for cause (§ 5.2).
11.2
On termination: the federation license ends, network rails are severed, and pull tokens and provisioning credentials are revoked. Your deployment, its data, and its balances remain yours under the code licenses and your own responsibility. There is no payout of Units in any direction (Terms § 4.6).
Changes, law, and venue
12.1
Changes to these Operator Terms follow the mechanism of Terms § 10 (30 days' notice and renewed acceptance for material changes).
12.2
The law of [provider details unavailable] applies, excluding the CISG. Exclusive venue for Operators who are merchants, legal entities under public law, or special funds under public law, or who have no general venue in Germany, is [provider details unavailable].
12.3
If a provision is invalid, the remainder stands; the statutory rules replace the invalid provision.