Stake & exposure

Locked capital per DEF. Zero-stake DEFs require stake exposure from a staked DEF.
TOTAL STAKE
1.80M
GRID across fleet
STAKED DEFS
8
providing coverage
ZERO-STAKE DEFS
6
rely on exposure
UNBONDING
1
in lock
Stake exposure
Who covers whom
PROVIDERDEPENDENT
PROVIDERS
DEPENDENTS
def:consensusactive
1,000,000 GRID
min 1,000,000 GRID · covers 3 DEFs
def:block-storage/archivalactive
400,000 GRID
min 0 GRID · covers 3 DEFs
def:block-storageactive
200,000 GRID
min 0 GRID · covers 3 DEFs
def:nieactive
100,000 GRID
min 0 GRID · covers 3 DEFs
def:xsr/renderactive
50,000 GRID
min 0 GRID · covers 3 DEFs
def:xsr/inferunbonding
50,000 GRID
min 0 GRID · covers 3 DEFs
def:dsf/contentactive
zero stake
zero-stake · rides on exposure
def:dsfactive
zero stake
zero-stake · rides on exposure
How exposure works

Any staked DEF can cover any zero-stake DEF.

Per DefConfig.requires_stake_exposure in node/src/core/primitives/def.rs and the lifecycle rules in def-lifecycle.md §Stake Exposure Gating: DEFs with min_stake: 0 require coverage from any staked DEF on the same operator. Leaving all your covering DEFs auto-triggers unbonding on every dependent zero-stake DEF.

CURRENT COVERAGE: 6 staked DEFs cover 3 zero-stake DEFs.