ChainScore Labs
All Guides

Understanding Coverage Limits and Partial Payouts

LABS

Understanding Coverage Limits and Partial Payouts

Chainscore © 2025

Core Concepts of DeFi Coverage

Foundational principles that define how protection works in decentralized finance, from policy mechanics to claim adjudication.

Coverage Limit

The maximum payout a policy can provide for a single claim. This is a hard cap denominated in the covered asset.

  • Typically set as a percentage of the user's deposited value (e.g., 80% of TVL).
  • Defines the protocol's maximum liability per event.
  • Users must understand this cap to assess their effective protection level against total loss.

Partial Payout

A proportional settlement where the payout is less than the full coverage limit, based on the severity of the loss event.

  • Triggered when a hack or exploit results in incomplete fund loss (e.g., 30% of a pool drained).
  • Payout = (Lost Value / Total Value) * Coverage Limit.
  • Ensures capital efficiency for coverage providers and fair compensation for users.

Coverage Trigger

The pre-defined condition that must be verified to initiate a claim and potential payout.

  • Often requires an on-chain proof of a smart contract failure or a validated oracle report.
  • Must be objective and cryptographically verifiable to prevent fraudulent claims.
  • Examples include a governance-confirmed hack on a specific contract or a depeg event below a set threshold.

Claim Assessment

The process of verifying a loss event and calculating the owed payout amount.

  • Involves decentralized committees, dispute resolution protocols, or automated on-chain logic.
  • Determines if the trigger was met and assesses the scale of the loss for partial payout calculations.
  • Critical for maintaining the system's trustlessness and financial integrity.

Policy Exclusions

Specific scenarios or risks explicitly not covered by the protection policy.

  • Common exclusions include losses from private key compromise, governance attacks changing protocol parameters, or market volatility.
  • Clearly defined exclusions are essential for managing the capital pool's risk exposure.
  • Users must review these to understand the boundaries of their coverage.

Capital Pool & Reserves

The underlying liquidity backing the coverage promises, provided by stakers or reinsurers.

  • Payouts are made from this pooled capital, which must be overcollateralized to remain solvent.
  • The size and composition of the pool directly influence coverage capacity and pricing.
  • Understanding pool health is key to assessing a coverage protocol's reliability.

Models for Setting Coverage Limits

Understanding the Basics

Coverage limits define the maximum amount a protocol will pay out for a claim. Think of it like an insurance policy's maximum payout. The limit is not the value of your deposit, but the value of the protection you receive.

Key Models Explained

  • Static Model: A fixed, protocol-wide limit is set, like a $5 million cap per incident. This is simple but may not scale with TVL.
  • Dynamic Model: The limit adjusts based on the protocol's Total Value Locked (TVL) or a reserve pool. As more users deposit funds, the coverage limit increases proportionally.
  • Tiered Model: Different limits apply based on user or asset tier. A whale's large deposit might have a lower coverage percentage than a smaller user's deposit to manage risk concentration.

Real-World Example

Nexus Mutual uses a dynamic model where its coverage capacity is derived from its capital pool. If you stake NXM tokens, you are essentially backing the pool, and the available coverage for new policies is a function of this pooled capital.

How Partial Payouts Are Calculated

Process overview

1

Determine the Total Loss and Policy Coverage

Identify the incident's financial impact and the policy's maximum limit.

Detailed Instructions

The calculation begins by quantifying the total financial loss from the covered incident, such as a smart contract exploit. This is the Claim Amount. Simultaneously, the policy's Coverage Limit is retrieved. This is the maximum amount the policy will pay out, often denominated in a stablecoin like USDC. For example, a vault policy might have a coverage limit of 1,000,000 USDC. If a hack results in a loss of 1,500,000 USDC, the claim amount exceeds the limit, triggering a partial payout scenario. The insurer or protocol's claims assessor will verify both figures on-chain, referencing transaction hashes and wallet balances to establish the loss event's validity and scale.

Tip: Always verify that the loss event is within the policy's defined coverage parameters and occurred during the active policy period.

2

Apply the Proration Formula

Calculate the claimant's proportional share of the available coverage pool.

Detailed Instructions

The core of partial payout calculation uses a proration formula. The key variables are the individual claimant's Verified Loss and the Aggregate Loss across all valid claims for the same incident. The formula is: Payout = (Verified Loss / Aggregate Loss) * Coverage Limit. This ensures the limited coverage pool is distributed fairly proportional to each claimant's share of the total loss. For instance, if the total coverage limit is 1,000,000 USDC, the aggregate loss is 2,000,000 USDC, and your verified loss is 200,000 USDC, your payout would be (200,000 / 2,000,000) * 1,000,000 = 100,000 USDC. This step is typically executed by the claims smart contract or the insurer's backend system after all claims are submitted and validated.

Tip: Understand that your recovery rate is Coverage Limit / Aggregate Loss. If the pool is insufficient, this rate will be less than 100%.

3

Account for Policy Deductibles and Coinsurance

Subtract any applicable deductibles and apply coinsurance factors before proration.

Detailed Instructions

Before the proration formula is applied, policy-specific terms are factored in. First, the Deductible is subtracted from the claimant's verified loss. If your loss is 200,000 USDC with a 10,000 USDC deductible, the adjusted loss for calculation is 190,000 USDC. Second, Coinsurance may apply. A 90% coinsurance clause means the policy covers only 90% of the loss after the deductible. So, 190,000 USDC * 0.90 = 171,000 USDC. This adjusted amount is then used in the proration formula as the claimant's share. These terms are defined in the policy's smart contract or legal wording and are non-negotiable during a claim. They directly reduce the potential payout amount even before aggregate limits are considered.

solidity
// Simplified logic snippet for adjustment uint256 adjustedLoss = verifiedLoss - deductible; adjustedLoss = (adjustedLoss * coinsurancePercentage) / 100; // e.g., 90 for 90%

Tip: Carefully review your policy's deductible and coinsurance terms before purchasing, as they significantly impact net recoverable amounts.

4

Execute the Payout via Smart Contract

The calculated amount is disbursed on-chain according to the protocol's rules.

Detailed Instructions

Once the final payout amount for each claimant is determined, the disbursement is executed. In a decentralized insurance protocol, this is typically done by a Claims Payout Smart Contract. This contract holds the coverage pool funds (e.g., in a vault) and, upon successful approval of a claims assessment, transfers the calculated amount to the claimant's address. The contract will call a function like processPayout(uint256 claimId), which internally performs the transfer using IERC20(usdcAddress).transfer(claimantAddress, payoutAmount). The transaction is immutable and verifiable on-chain. In traditional insurer setups, this might be a manual bank transfer, but the on-chain traceability is a key advantage of DeFi insurance, providing transparency that the prorated amount was paid as calculated.

Tip: Always verify the transaction on a block explorer after a payout is initiated to confirm receipt and finality.

5

Analyze Payout Scenarios and Recovery Rates

Evaluate how different loss scenarios affect the final payout percentage.

Detailed Instructions

Understanding potential outcomes requires analyzing Recovery Rates. The recovery rate is the percentage of your adjusted loss that is actually paid out, calculated as Payout Amount / Adjusted Loss. This rate is constrained by the sufficiency of the coverage pool. For example:

  • Scenario 1 (Adequate Pool): Aggregate Loss = 800,000 USDC, Limit = 1,000,000 USDC. Recovery Rate = 100%.
  • Scenario 2 (Insufficient Pool): Aggregate Loss = 2,000,000 USDC, Limit = 1,000,000 USDC. Recovery Rate = 50%.

Your final recovery is further reduced by deductibles and coinsurance. A key insight is that in large-scale events, even policies with high individual limits can result in low recovery rates if the protocol's total capital is overwhelmed. This analysis highlights the importance of the protocol's Capital Efficiency and Reinsurance Backstops in mitigating this risk for claimants.

Tip: When comparing policies, consider the provider's total capital available for claims relative to the potential aggregate loss of the protocols they cover.

Coverage Models Across Major Protocols

Comparison of key parameters defining security and payout structures.

Coverage ParameterNexus MutualInsurAceUnslashed FinanceBridge Mutual

Coverage Type

Parametric (Smart Contract Failure)

Parametric + Custodial

Parametric (Protocol Failure)

Discretionary + Parametric

Max Coverage per Protocol

Up to 50,000 NXM

Up to $2M

Up to 1,000,000 USDC

Up to $1.5M

Payout Trigger

Successful Governance Vote

Claim Assessment + Vote

Oracle Committee Vote

Claim Assessor Vote + DAO

Partial Payouts

No

Yes (Scaled by loss ratio)

Yes (Proportional to TVL loss)

Yes (Case-by-case)

Staking Requirement for Assessors

1,000 NXM

10,000 INSUR

50,000 USDC

5,000 BMI

Claim Assessment Time

~30-60 days

~14-30 days

~7-14 days

~30-45 days

Coverage Purchase Fee (Annualized)

~3-5% of cover amount

~2-4% of cover amount

~4-6% of cover amount

~3.5-5.5% of cover amount

Key Factors Influencing Limits and Payouts

Coverage parameters are not arbitrary; they are determined by a combination of protocol design, risk assessment, and market dynamics. Understanding these factors is essential for evaluating policy effectiveness and managing expectations for potential claims.

Protocol Risk Assessment

The underwriting model continuously evaluates the security and economic design of covered protocols. Factors include smart contract complexity, governance centralization, and historical incident rates. For example, a novel DeFi protocol with unaudited upgrades would face stricter limits than a battle-tested lending market. This dynamic pricing ensures the coverage pool's solvency.

Capital Pool Depth & Utilization

The total value locked (TVL) in the coverage pool directly caps the maximum liability for any single protocol. High utilization rates during market stress trigger automatic limit reductions to prevent overexposure. A pool with $50M TVL cannot sustainably offer a $100M per-incident limit. This factor ensures the protocol remains solvent and can honor claims.

Incident Verification & Scope

Payouts depend on the verified cause and impact of a security incident. Coverage typically excludes market volatility, frontend issues, or governance decisions. A partial payout occurs if an exploit is contained or only affects a specific vault, not the entire protocol. This precise scoping prevents fraudulent claims and aligns payouts with actual loss.

Policy Terms & Exclusions

The coverage parameters defined in the smart contract policy are binding. These include explicit exclusions for certain attack vectors, a clearly defined claims process, and a waiting period. For instance, a policy may exclude losses from oracle manipulation or require a 14-day assessment before payout. Users must understand these terms to avoid unexpected claim denials.

Staking & Governance Influence

Coverage stakers (underwriters) vote on key parameters like premium rates, coverage limits for new protocols, and claims adjudication. Their economic incentive is to balance risk and reward. A governance proposal might lower limits on a protocol after a near-miss incident. This decentralized mechanism allows the system to adapt to emerging threats collectively.

SECTION-FAQ

Frequently Asked Questions

Ready to Start Building?

Let's bring your Web3 vision to life.

From concept to deployment, ChainScore helps you architect, build, and scale secure blockchain solutions.