Every mature financial system has a layer that absorbs failure. In DeFi, that layer has largely consisted of audits and disclaimers. Firelight, live as of October 6th, is that missing layer. Today, its cover extends to the Kraken Protected Strategies USDC.

Firelight is an onchain cover protocol, incubated by Sentora and built on the Flare Network. It covers the infrastructure that onchain earn products depend on, with the scope, price, and capacity of each cover programme registered onchain and the eligible failure events named in advance. Platforms continue to operate as they do today, with Firelight enabling an added layer of protection underneath.

Firelight's cover is backed by a shared pool of staked capital that supports the protocol's full portfolio of cover programmes. That capital is held in an asset with low correlation to the DeFi venues it protects, so the funds behind a payout are not exposed to the event that triggered it. Stakers earn emissions generated by the protocol's operations, including the fees it captures from operators  electing cover on their program vaults, however, their staked positions remain subject to slashing if a cover event is confirmed.

Protecting the Kraken Protected Strategies USDC

Firelight cover is now enabled on the Kraken Protected Strategies USDC (formerly Boosted USDC) on Kraken DeFi Earn, curated by Sentora. The vault allocates across a specific set of blue-chip DeFi venues, such as Tydro.

The model rests on three principles:

• Adaptive terms. Scope, price, and capacity are registered onchain and reset with each 30-day epoch (i.e., coverage period) against the vault's live composition and risk profile. No lock-ins, no stale terms.

• Defined scope. Eligible failure events are named in advance and published onchain, so the vault operator knows exactly what is covered before cover begins.

• Active risk management. Continuous monitoring through Hypernative and Sentora's institutional risk infrastructure means exposure is tracked in real time rather than assessed once at inception.

Coverage Eligibility

Cover responds to six defined failure modes:

• Smart contract exploits. Code bugs such as logic errors, reentrancy, access control or upgrade flaws.

• Oracle failures. Stale, misconfigured, compromised or manipulated price feeds.

• Governance exploits. Flash-loan voting attacks, malicious upgrades or compromised governance contracts.

• Mechanism-driven bad debt. Liquidation or collateral mechanisms fail, leaving unrecoverable bad debt.

• Mechanism-driven depegs. A pegged asset breaks from its reference because its stabilisation mechanism fails.

• Redemption failures. A protocol defect blocks withdrawals or returns materially less than fair value.

Independent Review of Every Cover Event

Incidents are not adjudicated by a centralized team. When an exploit occurs, ZeroShadow, Firelight's designated security partner, publishes an exploit report. The Firelight Risk Consortium, a five-firm independent panel made up of Hypernative, Native, Credora, Cyfrin, and GFX Labs, then validates the event against published coverage criteria, confirms the existence of a loss, and publishes an onchain attestation. Validated payouts are programmatically released onchain to the applicable vault.

Firelight's own contracts are audited by OpenZeppelin, Coinspect, and 0xMacro, and were reviewed in a competitive audit through Immunefi.

Bridging the Gap for Onchain Capital

Onchain products stall when users cannot quantify the risk, and vague protection promises erode credibility rather than build it. Cover with published terms, independent review, and programmatic payouts turns that around: it makes the risk legible, and it makes safety something a platform can point to. Kraken Protected Strategies USDC joins Sentora's USD Protected Vault and Protected RWA Vaults, which have carried Firelight cover since launch. Full documentation on protocol functionality, including exploit validation and payouts is available here.