DarkCircle Suite Docs
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

AppContractsAudit status
DarkCircleDarkCirclePool.sol + unshield.circom are reference implementations, deployed nowhereUnaudited dev trusted ceremony; compliance (PPOI, C8) not enforced on chain
Circleswapinteracts with live Quaiswap pools; ships no new AMM contractsInternal only SECURITY_AUDIT.md is AI-assisted, not external
DarkSafeDarkSafeVault v2 + factory (ERC-1967 proxies)Unaudited mainnet creation gated behind VITE_ALLOW_MAINNET_VAULTS; audit package in docs/AUDIT_SCOPE.md
Dark QuestateQuestateDeed, QuestateBrokerage — not deployedUnaudited 38 Hardhat suites + Foundry fuzz/invariants are not an audit
DarkOrderGuildFactory, GuildHall, TokenStackDeployer — not deployedUnaudited fuzz, invariants and Slither in CI are not an audit

Known limitations

DarkCircle

Circleswap

DarkSafe

Dark Questate

DarkOrder

Portal and suite-wide

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.