InsureDAO

  • Name: InsureDAO
  • URL: https://www.insuredao.fi/
  • Category: decentralized insurance marketplace / segmented underwriting protocol / Curve-style governance insurance stack
  • Tags: ethereum-ecosystem
  • Summary: InsureDAO is a segmented insurance market with a vote-locked governance shell, not a shared-capital mutual. The useful part is the split: isolated or indexed pools handle underwriting shape, while veINSURE governance and ReportingDAO handle policy and payouts. That makes it a good contrast note for insurance designs where market structure itself is the control surface.
  • What it does:
    • Lets users create or use insurance markets where buyers pay premiums and underwriters lock liquidity to take payout risk
    • Organizes coverage through single pools for isolated protocol-specific risk and index pools for diversified, leveraged exposure across several single pools
    • Prices cover dynamically with an AMM-like curve that rises as available insurance capacity falls and prorates cost by coverage duration
    • Uses INSURE token locking into veINSURE for governance participation and mining boost, with voting on Snapshot and execution through Aragon
    • Splits governance roles across ReportingDAO for payout decisions, CommunityDAO for broader governance and treasury matters, and EmergencyDAO for fast emergency actions
  • Key claims:
    • The user and developer docs describe InsureDAO as an open insurance protocol where anyone can create a market, buy cover, or underwrite crypto risk
    • Single pools isolate one protocol’s risk, while index pools bundle multiple single pools, diversify underwriting exposure, and can leverage liquidity to increase capacity and premium earnings
    • Premium pricing is explicitly dynamic and AMM-like: the docs describe a utilization-sensitive premium curve derived from an AMM-style framing and integrated over the purchased amount, then scaled by coverage length
    • The governance layer is explicitly Curve-inspired: INSURE holders lock for up to four years to receive veINSURE, vote via Snapshot, and route execution through Aragon
    • Payout and control authority are not fully unified: ReportingDAO decides whether incidents should trigger payouts, CommunityDAO handles gauges, upgrades, treasury allocation, and Reporting member selection, while EmergencyDAO can act quickly in extraordinary situations
    • Compared with shared-capital mutuals like Nexus Mutual or discretionary voting systems like Bridge Mutual, InsureDAO is especially useful for showing how insurance design changes when risk is segmented into pools and governance power is routed through a Curve-style vote-locking stack
  • Whitepaper: No fully accessible canonical whitepaper surfaced in this pass. The strongest accessible primary materials were the official user docs, developer docs, and public governance/pool repositories; see ../whitepapers/insuredao-primary-sources-2026-05-08.md.
  • Sources:

Internal linkages

Control surface

  • Authority sits in pool segmentation, premium-curve design, ReportingDAO payout judgments, and the veINSURE governance machinery that steers upgrades, gauges, and emergency action.

  • Read it as market-structure-heavy insurance design, not as a generic mutual.

  • Last reviewed: 2026-05-08 UTC