Neptune Mutual

Neptune Mutual runs parametric cover pools where payouts trigger when predefined on-chain conditions are met (e.g. protocol TVL drops beyond a threshold). NPM governs pool parameters and risk frameworks.

Parametric, on-chain-trigger payouts — no member claims vote — enabling faster settlement when cover conditions are objectively met.

- Parametric Cover Marketplace: The core product: a marketplace of parametric cover policies covering DeFi protocols, CEXes and custodians. Payouts trigger on the resolution of a predefined incident rather than on individual member claims, so policyholders of an affected protocol are all paid out without submitting evidence. - Cover Pools (Dedicated & Diversified): Liquidity providers deposit stablecoins into either dedicated pools (single project) or diversified pools (a basket of projects), choosing leveraged or unleveraged exposure to earn premiums and NPM incentives. - Incident Reporting & Resolution System: A community-based, NPM-staking mechanism to report and dispute incidents that trigger payouts. Pre-TGE this operated under an interim Proof of Authority model with the Neptune Mutual Association able to pause the protocol and perform emergency resolutions. - NPM Token: Governance and staking token whose primary utility is governing the incident reporting and resolution system via staking and voting; also used for staking to create covers and provide reporting incentives.

- Neptune Mutual (NPM) — Token, Governance token

- Oracle: Payouts depend on objectively resolving whether a predefined incident occurred. An incorrect, delayed or manipulated incident-resolution outcome (the parametric trigger) could deny valid claims or trigger unwarranted payouts. - Governance: Under the interim Proof of Authority model the Neptune Mutual Association could pause the protocol and reverse incident-reporting decisions via emergency resolutions, concentrating significant discretionary power. OpenZeppelin also flagged that the protocol has a large number of very privileged roles requiring careful key management. - Smart Contract: A complex 44-contract codebase with intricate storage and access-control patterns. Audits (OpenZeppelin, BlockSec, Hacken) found high-severity issues that were subsequently addressed, but residual smart-contract risk remains inherent. - Reserve / Depeg: Cover pools are funded with stablecoin liquidity; the protocol's ability to pay claims depends on pooled reserves. OpenZeppelin flagged risk of insufficient liquidity when computing policy coverage commitments, and a stablecoin depeg would impair reserve value. - Counterparty: Cover Creators are approved at the team's discretion and covers reference third-party protocols and exchanges; the value of a policy depends on the correct scoping of the covered counterparty and event.

- Parametric insurance (e.g. weather / flight-delay index insurance): similar — Both pay out automatically when a predefined, objectively measurable trigger condition is met, rather than requiring the insured to file and prove a loss claim.; differs — Neptune Mutual covers crypto-native perils (protocol hacks, exchange/custodian failures), is funded by permissionless stablecoin liquidity pools, and resolves incidents through on-chain community reporting and NPM staking rather than a licensed insurer and actuarial loss adjuster.