Claim Execution
How LayerCover's live claim flow resolves payouts for launch pools
TL;DR: Launch pools use a deterministic claim flow. Policyholders surrender the covered distressed asset, the protocol validates the claim on-chain, and the payout waterfall funds as much of the claim as current liquidity allows.
Launch Claim Model
An American-style put option where the policyholder surrenders their distressed asset in exchange for a validated payout in USDC.
The live payout resolver returns the policy's covered amount subject to claim fees and available liquidity. The RiskManager enforces asset surrender via _collectSalvage() before the payout is released.
For the exact funding order after approval, see Payout Waterfall.
Examples: Stablecoin depeg cover (transfer depegged tokens → receive $1/unit), vault share cover (transfer exploited shares → receive snapshot value).
Asset surrender acts as a natural fraud deterrent — you can only claim if you actually hold the distressed asset.
How Claim Execution Works
Every launch pool is configured with the same live claim path. As a policyholder, you do not choose a payout mode; you buy coverage on a pool whose rules are already fixed on-chain.
| Contract | Role |
|---|---|
| PoolRegistry | Stores pool configuration and claim fee settings |
| RiskManager | Records incidents and enforces salvage collection |
| PayoutManager | Executes the payout waterfall |
| PolicyManager | Tracks policy status, debt, and policy burn/reduction |
Live Launch Pools
| Market Type | Claim model | Why |
|---|---|---|
| Stablecoin depeg cover | Asset surrender | Transfer the depegged token and receive covered value |
| Vault cover (ERC-4626) | Asset surrender | Transfer exploited shares and receive snapshot value |