Setting up the Insurance Pool
Create the Insurance Pool farm
If your vault doesn’t already have a farm, create one first. The Insurance Pool is configured as a dedicated farm on your vault — technically an escrow account.
Configure token
Set the deposit token. The Insurance Pool has a mandatory 30-day cooldown on withdrawals — this is not configurable.
KaminoManager class). It is not currently available via CLI or API.
Farm ownership
As the curator, you own the Insurance Pool farm. After creation, transfer farm ownership to a multisig and add Kamino as a signer — this aligns with the 2/2 multisig model used for emergency withdrawals.Key parameters
| Parameter | Type | Description |
|---|---|---|
InsurancePoolFarm | Public key | The escrow account holding the insurance pool capital |
| Token | Token type | The asset deposited into the insurance pool |
| Cooldown Period | 30 days | Fixed cooldown — capital cannot be withdrawn for 30 days after initiating withdrawal |
Withdrawal mechanisms
There are two ways to withdraw from the Insurance Pool. Understanding both is important — they serve fundamentally different purposes.Normal withdrawal (30-day cooldown)
Initiate a standard withdrawal to remove your insurance commitment. The mandatory 30-day cooldown begins when you initiate, and the withdrawal is a public, on-chain signal — depositors and anyone monitoring the vault will see that you are exiting. This is the expected mechanism for curators who wish to exit their insurance position. The 30-day window gives depositors time to assess and react.Emergency withdrawal (instant, 2/2 multisig required)
Emergency withdrawal is designed for one purpose: quickly accessing Insurance Pool funds to compensate depositors after a loss event. It bypasses the 30-day cooldown. Because of this, emergency withdrawal is gated behind a 2-of-2 multisig:- Kamino’s security council wallet
- A curator-nominated wallet (set by you)
How loss compensation works
When your vault incurs bad debt, the compensation process is manual. There is no automated on-chain loss detection — this is consistent with industry practice, as fully automating loss detection and distribution is complex and without precedent.Process
- Kamino socializes the loss — Kamino calls
socialize_losson klend, which distributes the bad debt across the vault. Depositors incur the loss at this point. - Detect and estimate the impact — you (and/or Kamino) assess what happened, which reserve incurred bad debt, and how much was lost.
- Release funds from the Insurance Pool — either via normal release or emergency withdrawal (with the 2/2 multisig) if urgency is required.
- Identify affected depositors — a point-in-time snapshot determines which depositors held positions when the loss occurred.
- Distribute compensation — funds from the Insurance Pool are distributed to affected depositors via a script, making them whole for the socialized losses.
The Insurance Pool covers losses up to its full balance. Only if the pool is fully depleted do depositors bear any remaining loss.