Docs / Security & limitations
🔒 Security & known limitations
One page for the honest state of the suite: what is audited, what is simulated, and every tracked limitation. These are tracked, not hidden.
Pre-release
No contract in the suite has had an independent security audit. Treat everything as pre-release and do not point any of it at funds you cannot afford to lose.
Audit status by app
| App | Contracts | Audit status |
|---|---|---|
| DarkCircle | DarkCirclePool.sol + unshield.circom are reference implementations, deployed nowhere | Unaudited dev trusted ceremony; compliance (PPOI, C8) not enforced on chain |
| Circleswap | interacts with live Quaiswap pools; ships no new AMM contracts | Internal only SECURITY_AUDIT.md is AI-assisted, not external |
| DarkSafe | DarkSafeVault v2 + factory (ERC-1967 proxies) | Unaudited mainnet creation gated behind VITE_ALLOW_MAINNET_VAULTS; audit package in docs/AUDIT_SCOPE.md |
| Dark Questate | QuestateDeed, QuestateBrokerage — not deployed | Unaudited 38 Hardhat suites + Foundry fuzz/invariants are not an audit |
| DarkOrder | GuildFactory, GuildHall, TokenStackDeployer — not deployed | Unaudited fuzz, invariants and Slither in CI are not an audit |
Known limitations
DarkCircle
- The pools, relayer and ledger are simulations; nothing is deployed on Quai and no funds move. Gas is not metered except for the Quai revert-burn rule.
- On static hosting the UI shows a "Static preview" banner, switches its actions off and
makes no API calls; the real console is
pnpm uilocally. - The reference circuit and contract are unaudited, with a single-contributor development ceremony; their behaviour on Quai itself (zone deployment, access lists, the pairing precompile) has not been exercised.
- Persistence saves the whole simulated environment, keys included, under a passphrase-derived key. It is not a KMS-backed production store; lose the passphrase and the snapshots are unreadable.
- No Quai-specific sanctions list is bundled (the seed is Ethereum OFAC addresses); load your provider's list at startup.
- The voice agent understands English commands from a fixed grammar only. On Orchard, WQUAI
has no contract, so wrapping and WQUAI sends are refused with
ASSET_NOT_ON_NETWORK.
Circleswap
- On static hosting, explorer-indexed stats and Quainance's catalog are not CORS-open, so USD values come from pool reserves and launches from a dated deploy-time snapshot. Token metadata is unaffected.
DarkSafe
- The vault contracts have not had an independent audit; the app shows a beta banner.
- v2 is not deployed yet; until a factory is recorded or configured the app explains that vaults cannot be created or opened.
Dark Questate
- Contracts not deployed: the hosted site shows invented sample listings with a "Showcase" banner and every transaction switched off.
- Metadata hosting (publishing the document behind each deed CID) is the registrar's step.
- Listing reads are unindexed (newest 60 by id). Native QUAI only. Legal effect depends on the operating agreement and local law.
DarkOrder
- Contracts not deployed: the hosted site shows invented sample halls with a "Showcase" banner and every transaction switched off. QNS names resolve only against a live deployment.
Portal and suite-wide
- Portal metrics: the hover readout shows the Cyprus-1 block height only; pool TVL and vault status are not wired in.
- Wallet extensions are treated as untrusted input everywhere: a provider that throws or lacks events is reported as absent.
- No licence file at the suite root yet; until one is added, reuse rights are unspecified.
Vendored three.js keeps its MIT licence in
assets/3d/vendor/three/LICENSE(DarkCircle itself is MIT).
Reporting a vulnerability
DarkSafe's reporting policy is in multisigows/SECURITY.md, with its threat model,
owner security guide, incident runbook and audit scope under multisigows/docs/.
DarkCircle's audit and open items are in x402tumbler/AUDIT.md and its release gates
in x402tumbler/docs/SHIELDED_POOL_CHECKLIST.md. Circleswap's internal review is
q0/SECURITY_AUDIT.md.