RestakingTangle Restaking

Introduction to Restaking

Restaking on Tangle means depositing assets into the on-chain restaking system and delegating them to operators who run blueprint services. In return, restakers can earn:

  • TNT incentives (if enabled for the asset)
  • A share of service fees from blueprint services they help secure

Benefits of Tangle Restaking include:

  • Multi-asset restaking with configurable deposit policies
  • Market-driven security for blueprint services and applications
  • Fee revenue from real customer payments (not just incentives)
  • Optional incentive programs funded by explicit budgets

How Tangle Uses Restaking

High-level restaking flow: deposits → delegation → service activity → fees/rewards → (optional) slashing.
Restakers
  • Deposit assets
  • Delegate to operators
  • Choose exposure scope (All vs Fixed)
MultiAssetDelegation (on-chain)
  • Tracks deposits, shares, delegation
  • Enforces blueprint selection constraints
  • Applies slashes to exposed pools
Operators
  • Register and advertise preferences
  • Run blueprint manager/runner
  • Submit results + heartbeats
Customers
  • Request or create services (RFQ)
  • Pay fees (pay-once/subscription/per-job)
  • Submit jobs to permitted services
Tangle (on-chain)
  • Service lifecycle + jobs
  • Quotes / RFQ validation
  • Fee splits and slashing proposals
Fee Routing
  • Operators accrue earnings
  • Restaker share via ServiceFeeDistributor (optional streaming)
  • Optional TNT incentives via budgets

Tangle’s restaking system coordinates four roles:

  1. Developers publish blueprints (service templates).
  2. Operators register for blueprints and run services for customers.
  3. Customers request services from a set of operators and pay fees.
  4. Restakers delegate assets to operators, earning fees and incentives while accepting slashing risk.

Lifecycle of a Service

  1. Developers create blueprints that define jobs, pricing, and optional service-manager hooks.
  2. Operators register and run the off-chain runtime that watches events and executes jobs.
  3. Customers create services (request/approve or RFQ/quotes), set TTL, permitted callers, and payment terms.
  4. Operators execute jobs, submit results, and emit heartbeats; payments route to operators/restakers per policy.

Restakers choose their exposure using All vs Fixed blueprint selection, which determines which blueprints their delegation can earn from and be slashed by.

See Core Concepts and Restaker Risks.