Security & trust model
What the protocol verifies, what it trusts, and what is still being validated.
Release reference · Updated 14 October 2026On this page
Current security status
As of 14 October 2026, independent security audit completion is not recorded for this release. Automated regression tests and local/fork demonstrations are engineering evidence, not an independent audit. Sourcify exact-match verification checks deployed bytecode correspondence.
Trusted receipt witnesses
The configured public deployment retains a single-operator, 1-of-1 receipt witness model. Finalized chain evidence is checked before the witness signs, but this is not a trustless cross-chain proof or independently decentralized validator network.
Governance and control
Administration uses two-step ownership transfer. Core admission and pause powers are governance trust. Admission binding checks do not automatically audit arbitrary Core code. The fixed current fee-sharing rule has no administrator percentage setter.
Identity is separate from spending
Page metadata and observed IDs are unverified discovery data. Claims need official X control evidence and wallet authorization. EIP-712 domains, nonces, expiry, controller revisions and ERC-1271 validity constrain signatures; discovery cannot grant spending or withdrawal.
Application data and privacy
Marketing and documentation pages do not connect wallets, collect login credentials or make trading requests. They store language and appearance preferences locally. The app separately uses Privy/X authentication and a hosted companion; chat uses server storage and is not end-to-end encrypted.