Vault curators and platforms embed Firelight cover directly into their vaults, with terms fixed for each 30-day coverage period. Capital staked through Firelight backs that cover. As of October 26, Firelight has $38 million of active cover across three deployments, backed by $55.6 million from 3,478 stakers.

Capital deployed to Firelight has one clear role: backing protection for onchain products. Users depositing to Firelight are looking for a venue where the risk they take on is defined, priced and capped. In this article, we’ll detail why Firelight fits that requirement.

What Firelight Protects

Firelight cover is live on three implementations, each with a specific deployment scope. Sentora's USD Protected vault provides diversified access to USD-denominated yield strategies executed fully onchain across blue-chip DeFi protocols. Sentora's Protected RWA vault focuses on real-world asset strategies, including managed looping and lending across markets where RWAs serve as collateral. Kraken’s Protected Strategies USDC vault, available through Kraken DeFi Earn and curated by Sentora, allocates USDC across established DeFi venues. Firelight provides $30.5 million of cover on this vault.

Coverage applies to a named list of technical and economic failures: smart contract exploits, oracle failures and manipulation, governance exploits, bad debt from mechanism failure, depegs caused by a broken redemption or stabilization mechanism, and redemption failures. Events outside that list, such as ordinary price movements or a strategy falling short of its target, do not trigger a payout. In this first phase, covered vaults deploy only to established venues, Tydro (built on Aave) and Morpho, using assets with deep liquidity and long track records.

Capital backing cover sits outside the protocols it covers. An exploit in a covered lending market does not directly reach the FXRP in the Firelight vault. A validated claim draws first on the First-Loss Buffer, a protocol-owned stablecoin reserve. Only a loss that exceeds the buffer reaches staker positions, and it is shared pro rata across the vault. When an incident opens, new deployments pause, so capital arriving afterward does not absorb an earlier loss. Withdrawals follow windows tied to coverage periods, because capital backing an active commitment stays in place until that commitment ends.

In addition, Firelight limits how much cover it writes. Its capital adequacy framework caps coverage relative to the assets available to absorb losses and assesses concentration across protocols, assets, exposure groups and strategies. Shared dependencies, such as two markets relying on the same oracle, count as correlated exposure. A diversification adjustment then reduces available capacity where the book is concentrated, so each new vault is assessed against the portfolio as it already stands. Protocol leverage, the ratio of active cover to vault TVL, stands at 0.68x as of October 26, 2026.

Together, these mechanisms keep staker exposure defined and priced: named events on established venues, fixed 30-day terms, independent validation, a first-loss layer ahead of stakers, and capacity limits that hold the book to what its capital can support.

How Firelight Compares to Other DeFi Reward Opportunities

When comparing a headline rate, the most useful questions to ask are often where that rate comes from, how capital is deployed and who controls it, and what can be verified about the risk. Token-driven incentive programs and opaque strategies, including CeDeFi products, answer these questions differently from Firelight.

Token-driven incentive programs use token emissions to raise their headline rate above what fees alone would pay. The share funded by such an incentive budget falls away when emissions end or token prices fall. A depositor comparing headline rates alone may be weighing a temporary subsidy against a rate funded by premium income.

The other rates to watch out for involve opaque strategies. An example of this are CeDeFi strategies.

CeDeFi products typically accept deposits through an onchain vault, then move the capital offchain, where depositors can’t see it. On the exchange, the account belongs to the protocol, not the depositor, so depositors give up control of their funds. Withdrawals depend on operators returning funds within a stated timeframe, and nothing onchain enforces that schedule.

As strategies are not disclosed, depositors cannot see counterparties or exposure, or tell whether a position carries directional exposure or is delta neutral. Capital held offchain relies on proof of reserves for assurance. A credible report is attested by a named, trusted party and ties balances to identifiable entities. Statements from unnamed counterparties, or documents with key details redacted, offer limited evidence.

Firelight answers each of these questions onchain or in public. Rewards come from premiums paid for defined cover on blue-chip venues, not emissions or offchain trading. Deposits stay in the vault contract and leave it only in a slash event, and the vault contract processes withdrawals and returns funds only to the staker’s address. Firelight also maintains a public registry that breaks down the positions and strategies its vaults cover, the addresses that buy and hold cover, and the beneficiaries of any payout. Stakers can review the full record of exposure the vault backs before they deposit. Head to Audits and Security in our official documentation for more information.

Reading the Comparison

This table dives into the key distinctions between token incentive-driven programs, opaque strategies, and Firelight to illustrate a comprehensive comparison.

For more information on Firelight Protocol, head to our documentation which has a repository of technical details about the workings of the protocol, and as always, stay tuned to our official social media channels for the latest updates.