Compliance and Disclosures

◉Canonical

---

Purpose

Treasury documentation must be transparent without making unsafe legal, financial, investment, yield, fund, or return claims.

Scope

This page defines public disclosure themes, prohibited claims, safe language, review triggers, and privacy or security boundaries.

Disclosure Themes

• Treasury documentation is for ecosystem transparency and operations, not personal investment advice.
• Treasury strategies and allocations do not guarantee returns.
• Treasury assets and strategies are exposed to market, liquidity, counterparty, smart contract, operational, custody, governance, and regulatory risk.
• Runway, revenue, PnL, exposure, or allocation estimates depend on assumptions.
• Public documentation may summarize information without exposing sensitive security details.
• Material treasury actions are subject to governance, policy, review, and approval paths.
• Some financial structures require qualified review before final public claims.

Prohibited Claims

Treasury documentation must not claim guaranteed returns, guaranteed APY, risk-free reserves, fixed income without legal review, ETF status without legal basis, audit completion unless a real audit exists, legal compliance unless qualified review exists, impossibility of loss, consistent trading profit, liquidity guarantees from fees, or token appreciation from burns.

Safe Language

Preferred wording includes treasury sustainability, risk-managed, governance-aligned, reportable, subject to market risk, subject to governance approval, subject to security review, estimated, planned, draft, active if verified, allocation policy, reserve policy, and accountability record.

Review Triggers

Review is required before public treasury reports, treasury strategy pages, DaaS or ETF DaaS financial claims, derivative or debenture claims, trading revenue claims, treasury fee claims, audit or compliance claims, public wallet or asset reports, incident reports, and governance proposals about treasury.

Privacy and Security Boundaries

Public materials may include approved asset category summaries, governance decisions, safe execution receipts, risk summaries, reporting periods, and high-level controls.

Public materials must not include private keys, seed phrases, sensitive signer operations, exploitable wallet procedures, risky incident details, or private user and client data.

Current Status

This page is a documentation guardrail. It is not legal advice and does not replace qualified legal, compliance, accounting, or security review.