Economic Security
Staking bonds operators to the Blueprint services they run, so a service that breaks its rules can be slashed.
Operators, collateral, and slashing
Tangle uses economic security to back operators who run Blueprint services. Operators register for services and provide compute. Delegators stake assets to operators as collateral; a service can slash that collateral when its policy defines a fault.
The protocol does not make every workload safe by default. Each Blueprint defines the assets it accepts, the operators it needs, the service rules, and the evidence path for slashing. Staking gives the service an economic bond; the Blueprint still has to define what counts as a fault.
Tangle provides permissionless and asset-configurable staking for Blueprints, and participants earn rewards based on service usage and incentives. Staking aligns operators, developers, and stakers around service reliability and performance.
Start by Role
| Role | First question | Next page |
|---|---|---|
| Staker | Which operator and asset should I delegate to? | How Staking Works |
| Integrator | Do I need transferable staking positions? | Liquid Staking Vaults |
| Blueprint developer | What collateral and slashing rules does my service need? | Blueprint Pricing and Payments |
| Operator | Which services am I registered for and what can be slashed? | Operator onboarding |
Protocol Surfaces
| Surface | What it controls |
|---|---|
MultiAssetDelegation | Delegation, operator stake, unstaking, and vault-backed positions. |
ServiceManager | Blueprint registration, service requests, approvals, jobs, and lifecycle state. |
| Reward contracts | Service fee distribution and optional TNT incentives. |