Public claims are part of the architecture. A technically narrow protocol can still be misread if the public copy sounds like an exchange, a hosted wallet, a stablecoin sponsor, a universal anonymization service, a bridge custodian, or a finished compliance product. This page is the writer-facing red-line guide that prevents 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 | Z00Z is a privacy-preserving settlement protocol. | Describes infrastructure rather than a managed financial service. |
| Wallet posture | Z00Z supports self-custodial ownership and reference implementations. | Preserves the software-versus-service boundary. |
| Privacy | Z00Z minimizes public observability while preserving settlement validity. | Avoids absolute anonymity claims. |
| Disclosure | Disclosure is optional, scoped, and controlled by the actor who needs it. | Does not imply a universal backdoor or universal public audit mode. |
| Assets | Third-party assets remain the responsibility of their own issuers. | Separates protocol validity from issuer legitimacy. |
| Steward role | The steward documents, audits, and supports the protocol but does not custody, exchange, redeem, or route user funds. | Keeps the steward boundary explicit. |
| Regulated services | Regulated actors using Z00Z remain responsible for their own compliance duties. | Avoids automatic-compliance claims. |
| 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. |
| Corporate-auditable mode | Say it is an optional overlay and identify what is not yet implemented. |
| 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. |
| Geoblocking or restricted-jurisdiction profiles | Say these are interface mitigations, not complete legal shields or protocol-wide constitutional rules. |
| 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 it is a client or demo | Reference wallet or reference implementation. | Creates unnecessary endorsement and customer-service expectations. |
| Untraceable, untouchable, regulation-proof, impossible to stop | Privacy-preserving, self-custodial, limited public observability, optional disclosure. | Turns legitimate privacy into anti-law marketing. |
| Trails disappear forever | Public history may be pruned while settlement validity is preserved. | Overclaims irrecoverability and contradicts evidence-package discipline. |
| Z00Z makes downstream services compliant | Downstream services remain responsible for their own compliance duties. | Falsely suggests automatic legal conversion. |
| Z00Z can reconstruct hidden user history on demand | Core explains validity; 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. | Z00Z is designed to reduce public observability through private settlement objects and wallet-local possession, while ingress, egress, service logs, and optional disclosures remain separate risk surfaces. |
| 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. | A wallet may offer optional compliance or disclosure features, but users and regulated services remain responsible for their own legal and recordkeeping duties. |
| 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. | The protocol can validate compatible state transitions; 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: protocol, steward, wallet, issuer, service, user, auditor, or regulator.
- 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:
- official exchange, bridge, ramp, launchpad, market maker, redemption desk, or hosted wallet operation;
- 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.
- 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 Whitepaper section 17 and appendices A-B define safe formulas, claims requiring caveats, banned claims, red-line questions, and launch-blocking conditions.
- DAO Whitepaper 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 Whitepaper 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.