Blueprint Use Cases
This page links to maintained blueprint examples and templates. All links are pinned to the v2 branch.
Start Here (Examples)
Hello Tangle Blueprint
Minimal end-to-end blueprint: publish → register → run → submit jobs.
0
0
OAuth Blueprint
Reference blueprint showing OAuth-style flows and request authorization patterns.
0
0
API Key Blueprint
Reference blueprint showing API key issuance/validation patterns for services.
0
0
Incredible Squaring (Tangle)
More complete example: multi-job workflow, result submission, and local testing harness.
0
0
Incredible Squaring (EigenLayer)
Same runner and contexts, wired to EigenLayer as a reference integration.
0
0
Common Service Patterns
Blueprints are used to operationalize off-chain infrastructure with explicit on-chain authorization, payments, and slashing hooks. Common patterns include:
- Key management + signing (threshold signing, custodial APIs, signing relays)
- Secure compute (job execution, attestations, verifiable pipelines)
- Oracles and automation (event listeners, action routers, schedulers)
- Interop (relayers, message verification, bridge co-processors)
Most teams start from one of the examples above and then:
- Define job schemas and handlers in the runner.
- Decide how customers pay (pay-once, subscription, per-job).
- Decide what counts as misbehavior (and how evidence is produced) for slashing.
Related docs: