Public claims are part of the architecture. A technically narrow protocol can still be misread if copy sounds like an exchange, hosted wallet, stablecoin sponsor, universal anonymization service, bridge custodian, or finished compliance product. These boundaries prevent that drift.
The rule is evidence first. If a sentence cannot be backed by the whitepaper corpus, current source, release artifacts, or approved policy documents, do not publish it as fact. If the sentence is true only with a maturity or responsibility caveat, include the caveat in the sentence.
Safe Claim Formulas
Use formulas like these when they remain accurate in context:
| Topic | Safe formula | Why it is safer |
|---|---|---|
| Protocol identity | The Z00Z Protocol is published privacy-preserving settlement software and rules, not an unidentified company or service operator. | Describes infrastructure and excludes an invented legal actor. |
| Wallet posture | The wallet role is integral to Z00Z. z00z_wallets is an open-source reference/demo implementation, and custom wallets may conform to the same network-facing contract. The self-custodial user controls keys and wallet-local records and remains responsible for duties applicable to the user’s own conduct. |
Separates the required architectural role from one physical implementation without shifting an operator’s duties to the user. |
| Privacy | The Z00Z Protocol is designed to minimize base-layer public observability while preserving settlement validity. | Avoids absolute anonymity and unidentified-operator claims. |
| Disclosure | Disclosure is scoped and purpose-bound: each actor provides or retains records required for its own conduct or operated function, using only lawful authority and data it possesses. | Avoids both a universal backdoor and a universal opt-out claim. |
| Assets | Protocol compatibility does not establish an asset’s legality, reserves, custody, or redeemability; those matters remain with the issuers, custodians, bridges, lockers, and other actors that actually provide them. | Separates protocol validity from external asset and service legitimacy. |
| Responsibility map | In self-custodial use, the user controls keys, profile, local history, records, and disclosures and remains responsible for duties applicable to the user’s own conduct. Project-linked and independent operators retain duties arising from what they actually distribute, operate, or control. | Prevents responsibility from being assigned to wallet software or shifted from an operator through self-custody language. |
| Enterprise use | Corporate and audit-capable overlays may exist above the core without redefining the core. | Keeps optional overlays out of consensus. |
Short public copy can be positive, but it must stay bounded. “Privacy-preserving settlement protocol” is stronger than “untraceable money” because it is both more accurate and more defensible.
Claims Requiring Caveats
Some claims are usable only when paired with precise status, scope, or responsibility limits.
| Claim | Required caveat |
|---|---|
| Digital cash or cash-like privacy | Say self-custodial, privacy by design, and still subject to ordinary legal obligations. |
| Selective disclosure | Say which primitives or workflows are live and which remain target overlays. |
| Configurable jurisdiction or corporate-audit profile | Say it is an above-core tool, identify what is not yet implemented, and state who supplies, maintains, selects, and relies on it. |
| External assets, lockers, or wrappers | Say custody, reserves, redemption, and issuer duties remain external unless separately proven. |
| Transport privacy or Onion routing | Say it is an edge-layer or future-ingress surface where applicable, not a universal base-layer guarantee. |
| Useful-work rewards or AI evaluation | Say rewards must be evidence-bound, capped, challengeable, and separated from final value movement. |
| Country, regional, geoblocking, or restricted-jurisdiction profiles | Say they are user-configured tools, not legal certification or complete shields; the user selects, verifies, updates, and relies on the profile and keeps the resulting records. |
A 90-day or 1,555,200-block retention window |
Say it applies only to expressly temporary challenge material, starts at da_publication_ready, creates deletion eligibility only after every condition in the versioned profile, and does not erase settlement, replay, anchor, wallet-local, or independently retained records. |
| Post-quantum migration | Say current transaction cryptography is not end-to-end post-quantum secure unless and until the migration gates are completed. |
If a caveat feels too long for a headline, the headline is probably too broad.
Forbidden Or Near-Banned Phrases
Avoid these phrases in official material:
| Do not say | Prefer instead | Reason |
|---|---|---|
| Anonymous stablecoin | Independent issuer asset or private settlement asset where accurate. | Implies reserve, redemption, payment, and AML exposure at once. |
| Official DEX, official marketplace, or official NFT marketplace | Third-party marketplace or independent venue. | Makes the project sound like a market operator. |
| Official bridge or official launchpad | External integrator or independent bridge provider. | Implies direct responsibility for high-risk service surfaces. |
| Official wallet when no corresponding operator role is documented | Z00Z reference wallet or named conforming custom wallet, with its actual developer, support, control, and affiliation model stated. | Preserves the implementation relationship without inventing custody or service promises. |
| Untraceable, untouchable, regulation-proof, impossible to stop | Confidential settlement, user-controlled possession, limited base-layer observability, and scoped disclosure. | Turns legitimate privacy into anti-law marketing. |
| No-KYC, AML-resistant, sanctions-resistant, Travel-Rule-proof, or compliance optional | Controls depend on actual functions and are mandatory for the relevant operator or user where applicable. | Markets avoidance of lawful controls or states a false universal exemption. |
| Trails disappear forever | Eligible temporary challenge material may become deletion-eligible under the active retention policy; current settlement state, required replay or spent-state records, anchors, finality evidence, wallet-local history, and independently retained copies are outside that claim. | Avoids implying a complete public transaction-history archive or universal erasure. |
| Z00Z makes users or services compliant | A wallet may provide user-configured jurisdiction policy tools, but no software certifies compliance. The user remains responsible for profile selection and duties applicable to the user’s own conduct and records; each operator retains duties arising from the functions and claims it supplies or controls. | Avoids automatic legal conversion or using wallet software and self-custody to reallocate responsibility. |
| Z00Z can reconstruct hidden user history on demand | An identified publisher or maintainer may explain defined validity predicates; records exist only where actually retained. | Contradicts technical non-possession. |
| Approved, safe, or recommended asset | Descriptive risk labels only. | Implies endorsement and curation. |
When a phrase would make a careful reviewer infer service operator, exchange, stablecoin sponsor, asset curator, or evasion tool, reject it.
Corrected Wording Examples
| Risky copy | Corrected copy |
|---|---|
| Z00Z is an untraceable payment network. | The Z00Z Protocol is designed to reduce base-layer public observability through confidential settlement objects and wallet-local possession; privacy remains subject to the documented threat model, implementation, surrounding operators, and scoped disclosure rules. |
| Z00Z will launch the official bridge. | Independent bridge providers may build Z00Z-compatible routes; custody, reserves, redemption, and service obligations remain with those providers unless a specific operating model says otherwise. |
| Our wallet makes every user compliant. | Where supplied, a Z00Z reference or conforming custom wallet may provide country, regional, or custom policy tools and scoped disclosure, but no software certifies compliance. The user selects and maintains the profile and meets recordkeeping or disclosure duties applicable to the user’s own conduct; each operator retains duties arising from the functions it supplies or controls. |
| The token model guarantees sustainable yield. | Tokenomics describe proposed fee, bond, treasury, and incentive roles with explicit market, liquidity, governance, and capture risks. |
| Z00Z is post-quantum secure. | Z00Z has a PQ-friendly settlement and storage boundary, while current transaction cryptography requires explicit migration gates before end-to-end post-quantum claims are safe. |
| The protocol approves this issuer. | A conforming verifier can validate a compatible state transition; issuer reserves, redemption, legal status, and commercial promises remain issuer responsibilities. |
Corrected copy does not make the project smaller. It makes the claim exactly as large as the evidence allows.
Approval Workflow
Use this workflow for public-facing copy before publication:
- Identify the claim category: privacy, maturity, token economics, external assets, support, governance, legal posture, or implementation status.
- Link the claim to a concrete source: whitepaper section, source code anchor, release artifact, policy page, or approved disclosure.
- Apply the responsibility map in the Compliance Framework: base Protocol, wallet role, reference or custom implementation, publisher or steward if any, project-linked operator, independent service, user, auditor, or authority.
- Add maturity language when the claim is target architecture or research.
- Replace banned or near-banned phrases with safe formulas.
- Escalate to counsel or governance review when the claim touches custody, exchange routing, stable assets, redemption, compliance posture, restricted jurisdictions, treasury movement, or legal-order response.
- Re-read the sentence out of context. If it would be misleading as a quote, rewrite it.
Immediate Escalation Triggers
Do not approve copy locally when it implies any of these:
- exchange, bridge, ramp, launchpad, market maker, redemption desk, or hosted-wallet operation without a documented and approved operator model;
- stable-value sponsorship, reserve guarantee, issuer approval, or project-backed redemption;
- universal anonymity, universal deanonymization, hidden backdoor, or impossible legal inquiry;
- token value, yield, liquidity, or economic-outcome guarantee;
- founder, steward, model, or agent control over treasury movement without published caps, challenge windows, and authorization rules;
- implementation maturity that the current corpus or code cannot prove.
Those claims may require a changed product model, counsel review, governance artifacts, or removal. They should not be solved by adding a vague disclaimer at the bottom.
Read Next
- Legal Architecture for the layer-by-layer responsibility firewall.
- Compliance Framework for the canonical wallet-role, implementation, and actor-specific compliance model.
- Legal Architecture Companion for evidence packages, standing reports, and document coherence.
- Disclosures for risk categories that should be stated directly.
Evidence and Further Reading
- Legal Architecture section 17 and appendices A-B define safe formulas, claims requiring caveats, banned claims, red-line questions, and launch-blocking conditions.
- DAO appendix E supports bounded governance and future-parameter caution, including AI and model-control wording limits.
- Privacy Threat Model And Metrics section 6 supports the prohibition against absolute privacy claims and the need to disclose operational privacy anti-patterns.
- Post-Quantum Migration section 12 provides the safe present-tense post-quantum communication formula and unsafe migration claims.
- Main Whitepaper section 10 supports the protocol-versus-service split used by the claim approval workflow.