Summary: Cozy Finance is best cataloged as protocol-local safety-module infrastructure rather than as a classic mutual or discretionary cover DAO. Its current public materials center on prefunded Safety Modules that teams configure to protect user assets from hacks and exploits, with creators defining qualifying losses, payout mechanisms, payout caps, reward emissions, and withdrawal delays for capital suppliers. Historical Cozy v1 docs describe a broader “protection market” design built around trigger contracts and debt cancellation, which makes the evolution especially useful: Cozy has moved from generalized protection-market theory toward concrete reserve modules that protocols can bolt onto their own balance sheets and user flows. The reusable mechanism insight is that insurance-like trust shifts from mutual-wide claims governance into module creator discretion over triggers, handlers, payout rules, and reserve funding.
What it does:
Lets protocols create onchain Safety Modules that earmark capital to reimburse users after qualifying hacks, exploits, bad-debt events, or other configured losses
Allows module creators to define what counts as a qualifying loss, whether payouts are automated or DAO/discretionary, how shortfalls are allocated, and what payout caps apply
Attracts reserve capital from treasury funds, protocol fees, or third-party suppliers who deposit into modules and accept payout risk in exchange for rewards
Uses reward managers and stake-pool style incentives so deposit receipt tokens can earn additional emissions
Preserves an older, more generalized protection-market lineage where developers could encode trigger conditions and suppliers/borrowers could trade protection around defined onchain risks
Key claims:
The current site and CSM intro frame Cozy as a DeFi safety stack and describe the Cozy Safety Module as a way for teams to protect user capital from hacks and exploits
The user FAQ says module creators define qualifying losses, payout methods, payout-cap structure, and whether shortfalls are handled pro-rata or discretionarily, which means the critical governance surface is module configuration rather than a single global claims committee
The same FAQ notes that changes to the module are subject to a time delay and that suppliers face explicit payout risk plus withdrawal delays, making the reserve side of the market legible and protocol-local
The rewards-manager README shows that Cozy pairs protection reserves with separate incentive machinery, letting projects configure stake pools and reward pools so module depositors can be paid to supply backstop capital
The older v1 docs describe a more abstract protection-market model organized around liquidity pools plus trigger contracts, where borrowers paid for protected positions and qualifying losses cancelled debt; this provides useful historical context for how Cozy’s current product narrowed toward safety modules
Taken together, the materials show Cozy as insurance-adjacent infrastructure that packages coverage as configurable reserve software for protocols, not as a universal mutual with one shared balance sheet and one canonical claims process
Whitepaper: No canonical standalone whitepaper surfaced in this pass. The strongest primary materials were the current site, Cozy Safety Module docs, rewards-manager repo, and legacy v1 docs; see ../whitepapers/cozy-finance-primary-sources-2026-05-08.md.