Protocol Foundation

Tangle coordinates services that outside operators can run for users. Developers publish Blueprints, users request service instances, operators accept work, and protocol contracts track stake, lifecycle state, and payment terms.

Today vs Future

Today the network uses managed onboarding and a curated operator set. The protocol path is still the same one a larger market needs: register operators, request service instances, record commitments, and settle fees.

Build Composable Services

Blueprints package jobs, metadata, binaries, pricing, and optional service-manager logic. Developers build them with the Blueprint SDK, then users instantiate live service instances from registered operators.

Earn as a Service Operator

Operators earn service fees by running requested instances. They choose which Blueprints to register for, which endpoints to expose, and which resources or isolation modes they are willing to commit.

Maximize Resource Utilization

Operators can reuse one stake and operations stack across multiple Blueprints. That gives users a consistent way to select operators while each Blueprint keeps its own jobs, pricing, and runtime requirements.

Who This Is For

• Builders who want to package services as Blueprints and ship them on demand. Build with Blueprints
• Operators who want to run services reliably and earn service fees. Operator onboarding
• Stakers who want to back operators and earn from usage. Economic security

How Services Work

Tangle uses a modular service model:

Blueprints

A Blueprint is a service template, not a live service. It defines the runnable artifact, jobs, metadata, pricing hooks, and registration/request logic. Users create service instances by selecting operators and accepting the payment terms. Read more about Blueprints

Economic Security on Blueprints

Economic security backs operators who run services based on Blueprints. Operators register for services and agree through the smart contract logic to run Blueprint service instances when requested. Read more about economic security

Requesting Service Instances

Users create live service instances through a Blueprint request. The request names the operator set, payment terms, and service parameters the Blueprint supports.

Incentives

Operators earn service fees for running Blueprint instances and may earn optional TNT incentives if governance funds them. Developers earn a share of service fees and can also receive optional TNT incentives based on activity metrics.

This separation lets one Blueprint support many service instances with different operators, prices, endpoints, and runtime requirements.

Use Cases

Tangle is a protocol for reusable cryptographic, AI, and runtime services. The protocol handles operator commitments and payments; each Blueprint defines the actual workload. Common service areas include:

• Privacy infrastructure: MPC and zero-knowledge services where operators run key generation, signing, proving, or verification jobs.

• Oracles: data services that use threshold signatures, MPC, or attestation before posting off-chain information onchain.

• AI/ML: inference, fine-tuning, evaluation, and sandboxed agent work through operator-hosted runtimes.

• Custody: distributed signing and policy checks using threshold cryptography.

• Bridges: cross-chain message, verification, and asset-movement services backed by operator commitments.

• Zero-knowledge services: proof generation, proof aggregation, and verification jobs.

• Custom cryptographic services: any service that can be expressed as jobs, operator requirements, and settlement rules.

The point is simple: developers package services once, users instantiate them when needed, and operators get paid for work they can prove they accepted and served.