Tangle Network Protocol
These posts are about the Tangle Network protocol, a separate project from Tangle's infrastructure for AI agents. Introduction to Tangle covers the agent infrastructure.
The Tangle Network 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.
- 1 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.
- 2 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.
- 3 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.
- 4 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.
- 5 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.
- 6 Tangle Blueprints: How to Choose an Operator-Run Service
Tangle Blueprints are service definitions run by operators. Compare jobs, access, payment, evidence, and failures before choosing an agent service.
- 7 x402 Payments for AI Agents: v2 Safety Guide
How an agent reads an x402 price, avoids duplicate charges, and reconciles settlement with the work it paid for.
- 8 Deploy a Paid AI Agent Service: One Traceable Job
A practical path for exposing one paid AI job with discovery, authorization, payment, execution, recovery, and evidence that a buyer can inspect.
- 9 TEE Attestation for AI Services: What the Evidence Proves
Trusted execution environment (TEE) attestation ties a request to approved code on protected hardware, if the caller checks the report before sending data.
- 10 DeMo: Communication Reduction for Distributed Training
DeMo, a distributed training method, reports up to 85x less communication per GPU; a service still needs checkpoints, evidence, recovery, and evaluation.