System Architecture
Tangle is the current protocol (EVM-based; legacy: Tangle Substrate) for instantiating and operating services (“blueprints”) secured by restaked capital. The system is intentionally split into:
- On-chain contracts (service lifecycle, payments, restaking, incentives, slashing)
- Off-chain runtime (operators running blueprint managers/runners that react to events and submit results)
Roles and How They Engage
- Blueprint developers publish blueprint definitions and optionally run a service manager contract.
- Operators register for blueprints, run the off-chain runtime, and submit results + heartbeats.
- Restakers / delegators delegate assets to operators and (optionally) constrain delegation to specific blueprints.
- Customers create services (by request/approve or by signed quotes) and submit jobs.
End-to-End Flow (High Level)
- Developer creates a blueprint (definition + schemas + execution sources).
- Operators register for that blueprint and advertise preferences.
- Customer creates a service via either:
- Request/approve (customer specifies operators + security requirements), or
- RFQ/quotes (operators sign quotes and the customer creates service from those quotes).
- Customers submit jobs; operators submit results.
- Protocol distributes fees (developer/protocol/operator/restakers) and tracks metrics.
- Operators submit heartbeats; authorized parties can propose slashes with a dispute window.
Code Map
On-Chain (tnt-core)
Off-Chain (Blueprint SDK)
| Component | Responsibility | Code |
|---|---|---|
| Manager | Loads services from chain, selects runtime sources, runs blueprints | https://github.com/tangle-network/blueprint/tree/v2/crates/manager |
| Tangle contexts | Provides typed clients + operator identity + env | https://github.com/tangle-network/blueprint/blob/v2/crates/contexts/src/tangle_evm.rs |
| Tangle producer/consumer | Event ingestion + result submission helpers | https://github.com/tangle-network/blueprint/tree/v2/crates/tangle-evm-extra/src |
The Entrypoint Contract (Composition)
The protocol is exposed as a set of facets registered on the Tangle router. The router maps function selectors to facet implementations and delegates calls.