QuaiVault has DailyLimit, Whitelist, and SocialRecovery modules, a ProxyFactory for deterministic deployment, Zodiac IAvatar compatibility, and a Supabase indexer tracking 27 event types. That's a lot of surface area. Before DAOs, treasuries, and real capital flow through it, the contracts need to be battle-tested by real users with real stakes.
RageQuit is recursive: it uses QuaiVault to audit QuaiVault. Members fund a shared multisig, then deliberately probe edge cases, attack surfaces, and governance failures. When something breaks or a design flaw is found, the DAO forks — one branch patches, another continues probing.
Each fork sheds unnecessary complexity. Each rage quit tests the withdrawal mechanism. Each cycle produces documented findings. The DAO that survives all the rage quits is the audited product.
The final surviving entity commissions a professional third-party security audit with the accumulated treasury — $50,000 USD.
Members contribute to the QuaiVault treasury. Non-transferable weight tokens track proportional ownership.
Deliberately probe edge cases — zero-value txs, module conflicts, concurrent proposals, adversarial guardian scenarios.
When a flaw is found, the DAO forks via ProxyFactory. One branch patches, another continues probing.
Each fork strips away fragility. Code, modules, and governance that proved unnecessary get removed.
The final surviving entity commissions a professional audit. The report is published publicly.
Multisig logic, proxy pattern, upgrade safety, threshold enforcement
DailyLimit, Whitelist, SocialRecovery — module isolation and interaction
Deployment logic, salt collision resistance, deterministic addressing
Module execution paths, guard bypass vectors, execution result handling
Withdrawal logic, voting integrity, fork mechanics, proportional exits
Batched transaction safety, delegate call risks, encoding validation