Community Agreement.

The Tenzro Network exists so people and autonomous systems can access intelligence, security, and settlement on shared open infrastructure. This Community Agreement defines the baseline behaviour required of every participant — operators, developers, end users, and the agents acting on their behalf — to keep that environment open, safe, and useful.

By connecting to the network, running a node, holding TNZO, or otherwise using protocol services, you agree to follow this document. Some interactions are also subject to the Terms of Service and Privacy Policy.

The Tenzro Network is the open protocol and platform connecting humans, agents, and providers. The Tenzro Ledger is the settlement component of the network and records balances, identity bindings, and verifiable receipts. TNZO is the native asset used for transaction fees, provider payments, staking, and governance.

This agreement applies to all surfaces operated by the Tenzro Foundation — the network endpoints, the public RPC and verification services, the desktop and command-line clients, the model and agent registries, and the cross-chain bridges — and to community-operated nodes that interconnect with them.

Participants may operate validator, model-provider, and TEE-provider nodes; deploy and use smart contracts; serve and consume inference; run autonomous agents; bridge assets to and from external chains; and participate in governance.

Use of the network is expected to be honest, lawful in the jurisdiction of the participant, and respectful of other users. Providers are expected to honour their advertised pricing, availability, and service-level commitments; consumers are expected to pay for services consumed.

The following activity is not permitted on Tenzro:

• Abuse of other participants, including harassment, targeted intimidation, doxxing, or impersonation of humans, organisations, or system agents.
• Fraud, theft, or deception — including counterfeit identities, fake provider listings, wash-traded inference receipts, and signature forgery.
• Illegal activity in the participant's jurisdiction, sanctioned-party transactions, money laundering, and financing of terrorism.
• Attacks on the protocol — equivocation, withholding, denial-of-service, malicious bridge messaging, exploitation of consensus or VM bugs without coordinated disclosure.
• Distribution of malware, child sexual abuse material, non-consensual intimate imagery, or content that incites violence.
• Misuse of model and agent infrastructure to generate the above.

Participants are identified by Tenzro Decentralized Identity Protocol (TDIP) decentralized identifiers. Pseudonymous participation is supported at the Unverified tier; higher KYC tiers — Basic, Enhanced, and Full — unlock larger spending limits, regulated payment rails, and institutional integrations.

KYC verification is performed by third-party providers or by partner institutions; the network records only the resulting credential and tier, not the underlying documents. Participants must not present credentials they did not earn or have not had revoked.

Agents acting on behalf of a human controller bind back to the controller's decentralized identifier and inherit a delegation scope — spending limits, permitted operations, permitted contracts, and time bounds. The controller is responsible for activity performed within that scope.

Autonomous agents operated without a controller are responsible for their own conduct, subject to the bonds posted at registration and to insurance or recourse mechanisms defined in their templates.

Suspected violations of this agreement, security vulnerabilities, and abusive content can be reported to legal@tenzro.com. Reports should include the relevant decentralized identifier, block height or transaction hash where applicable, and a concise description of the issue.

Security vulnerabilities should be disclosed under coordinated disclosure and will be acknowledged within a reasonable period.

Enforcement is layered. Protocol-level violations — equivocation, invalid signatures, double-spends — are handled automatically by consensus through slashing, fault evidence, and revocation. Service-level violations are handled by the Tenzro Foundation through warnings, restriction of foundation-operated endpoints, and reporting to relevant authorities where required.

Participants whose decentralized identifier is restricted may appeal in writing to legal@tenzro.com. Appeals are reviewed on the merits and may result in reinstatement, modified scope, or upheld restriction.

This agreement evolves with the network. Material amendments will be published with an updated effective date and announced through the public communication channels of the Tenzro Foundation. Continued use of the network after an amendment becomes effective constitutes acceptance of the revised agreement.

Tenzro Foundation — legal@tenzro.com.