Skip to content
EN
Digital assets

DEFI-SURE

A strategy earns its yield from the market. It carries its risk from the infrastructure underneath it, the contracts it touches, the protocols it routes through, the vaults it sits in, the oracles it trusts and the keys that can move it. DEFI-SURE is written against that infrastructure. 1B assesses what a strategy actually depends on, and the defined events that can be transferred are transferred. The investment itself is not insured.
Overview
Cover for deployed DeFi capital
What it protects
The infrastructure a strategy depends on, not the return it is trying to earn.
Written against
The approved perimeter: the named protocols, contracts and vaults a strategy may use

Cover for deployed DeFi capital

The infrastructure a strategy depends on, not the return it is trying to earn.

What a strategy stands on

Yield comes from the market. Risk comes from the infrastructure.

A position is never only a position. It is the contracts it touches, the protocol it routes through, the vault it sits in, the oracle it is priced by, the keys that can move it and the bridges it inherits from. Any one of them can fail while the strategy itself is working exactly as designed.
Assessed
Every dependency the strategy actually touches, named before anything is priced.
Inside the perimeter
What the assessment approved. This is what the policy is written against.
Outside it
What was not approved. It stays on the drawing, because cover you do not have is the part worth knowing about.
Illustrative. The dependencies drawn here are the classes 1B assesses, not any particular strategy.

The boundary

Insurance does not make DeFi risk-free.

DEFI-SURE responds to defined insured events. It does not guarantee performance and it does not stand behind every way capital can be lost. The line between those two is the product.

Yours to carry

  • Token price movement and market volatility
  • Strategy performance, including a strategy that simply does not earn
  • Opportunity cost and yield foregone
  • Where to deploy, how much, and when to leave

Potentially insurable

  • Covered smart-contract events
  • Defined protocol failure and exploit
  • Oracle failure and manipulation
  • Selected cyber, wallet and key-management events
  • Defined governance and privileged-access incidents
  • Specifically insured asset and stablecoin events

Getting covered

Four steps, and the first is a conversation.

  1. 01

    Tell us the strategy

    What the capital does, and what it depends on to do it. Enough to see the shape of the exposure.

    • Protocol and venue
    • Vault or strategy
    • Intended exposure
    • Custody and key architecture
  2. 02

    We assess the infrastructure

    1B goes through what the strategy touches and how each part can fail, contracts, protocols, vaults, oracles, governance, custody and the dependencies behind them.

    • Technical review
    • Dependency mapping
    • Failure modes
    • What can be transferred
  3. 03

    You get a structure, not a slogan

    If the strategy is eligible, the cover is written: named events, a named perimeter, and the numbers that go with them.

    • Insured amount and limits
    • Covered events
    • Retention
    • Exclusions and policy period
  4. 04

    Deploy inside the perimeter

    Once cover is bound the capital can move within the approved set. Step outside it and tell us first: the perimeter is the policy.

    • Cover attaches
    • Ongoing monitoring
    • Change notification
    • Defined response route

What it costs

Price follows the assessment, not a rate card.

There is no published rate for this, and a number quoted before anyone has looked at the strategy would be worth nothing. What sets the price is what the assessment finds and how much of it you ask us to carry.
The strategy
What it does, how it earns, and how many moving parts it needs to do it.
The perimeter
How many dependencies are inside the approved set, and how they fail.
Insured amount
How much of the position is covered, against what limits.
Retention
How much of a loss you carry before the policy responds.
The assessment
What the technical review found, and what it could not get comfortable with.
Premium, limits, retentions and exclusions are agreed per counterparty and are not published here. Investment returns are neither guaranteed nor insured.

Deploy for yield. Insure the infrastructure underneath.

Tell us where the capital is going and what it will depend on when it gets there. We will tell you what of that can be insured, and what cannot.
Request coverAsk about a strategy

Cover modules

  1. Smart contract

    Defined losses from covered smart-contract events in the contracts an approved strategy touches.

  2. Protocol

    Protocol-level failure and exploit, where the protocol is named in the policy and inside the approved perimeter.

  3. Oracle

    Failure or manipulation of a price or data feed that an eligible strategy depends on to value or settle.

  4. Vault

    Defined risks in the approved vault structures a strategy is deployed through, including their upgrade paths.

  5. Governance

    Privileged control, governance capture and compromised administrative access over an insured position.

  6. Cyber and custody

    Selected cyber, wallet and key-management events, and the operational failures around them, where included.

  7. Stablecoin and asset

    Specifically insured asset and stablecoin events, where that exposure is named rather than assumed.

  8. Cross-protocol

    Bridges, dependencies and the protocols an approved strategy inherits risk from without holding a position in them.

Perils covered

  • Covered smart-contract events in the contracts an approved strategy touches
  • Defined protocol failure and exploit, where the protocol is named in the policy
  • Oracle failure and manipulation affecting an eligible strategy
  • Selected cyber, wallet and key-management events
  • Defined governance and privileged-access incidents
  • Specifically insured asset and stablecoin events

Never covered

  • Token price movement, market volatility and any investment outcome
  • Strategy performance, including a strategy that simply does not earn
  • Opportunity cost and yield foregone
  • Protocols, contracts and venues outside the approved perimeter
  • Loss arising after capital leaves the insured pathway
  • War, terrorism, nuclear energy, pandemic and sovereign acts

Conditions of inception

These are conditions of inception, not matters of claim. Where the evidence is not in place, cover does not attach.

Written against

  • The approved perimeter: the named protocols, contracts and vaults a strategy may use
  • Key-management and approval discipline on the wallets that can move an insured position
  • Insured amount, limits, retentions and exclusions, agreed per counterparty

  1. Strategy definition

    The protocols, vaults and contracts in scope, named before cover attaches. What is not named is not inside the perimeter.

  2. Infrastructure assessment

    1B's technical assessment of the contracts, oracles and dependencies the strategy relies on, and of how they can fail.

  3. Custody and key architecture

    How keys are held, who can move value, and under what approvals.

  4. Change notification

    Notice when a strategy moves to a protocol or contract outside the approved set, before the capital does.

  5. Monitoring access

    The read-only access the ongoing monitoring runs on, for the duration of the policy period.

Built for

  • Crypto and digital-asset funds
  • Family offices and professional investors
  • Treasury and asset managers
  • Institutions deploying into DeFi

Capacity, limits, wordings and commercial terms are not published. They are structured per counterparty and shared directly under engagement.

All productsMICASURANCE
Products

The structureis built.The terms areset with you.

Talk to 1BAll products