Tangle Protocol
Tangle coordinates services run by independent operators. A Blueprint is the service template, a Service is one configured instance, and a Job is one unit of work; the actual computation runs off-chain.
For builders and buyers, this series separates provider selection, payment, privacy, staking, service lifecycle, and result checking so the protocol is not mistaken for proof of correctness.
Start here: Decentralized Compute Protocol: How Tangle Runs Services. Then continue in the order below.
Decentralized Compute Protocol: How Tangle Runs Services
An operator-run compute protocol turns a defined job into a service with a visible payment path, result record, and failure policy.
Anonymous LLM Usage: Shielded Payment Limits
Anonymous LLM usage depends on the observer and the request data in question, while shielded payments address only one part of the payment and logging path.
Blueprint Protocol: Define an Operator-Run AI Service
Define a Blueprint protocol service with a typed job, reproducible runtime, payment rule, evidence record, and operator runbook.
Operator Staking for AI Blueprints: What Stake Proves
Operator staking gives AI Blueprints economic accountability, but stake is not a service-quality score or proof that a model answer is correct.
AI Service Marketplace With Crypto Payments: Job to Result
An AI service marketplace with crypto payments lets agents discover a defined job, pay per request, validate results, and recover from failure.