Build a Tangle Blueprint

This guide walks through the minimum shape of a Tangle blueprint:

• One or more jobs (async handlers)
• A router that maps jobIndex → handler
• A runner (operator-side process) that consumes job calls and submits results

Prerequisites

• Rust toolchain: https://www.rust-lang.org/tools/install
• cargo-tangle CLI: CLI Installation

A Minimal Job + Router (Hello Tangle)

The following example defines a single job (CREATE_DOCUMENT_JOB) that accepts a DocumentRequest and returns a DocumentReceipt.

Run End-to-End (Local Harness)

The SDK includes an Anvil-backed harness that spins up a local chain seeded with a known protocol state, runs the blueprint runner, submits a job, and waits for JobResultSubmitted.

cargo test -p hello-tangle-blueprint --test anvil -- --nocapture

Run Against a Real Deployment

To run as an operator against a live RPC, you typically:

1. Configure contract coordinates and IDs (blueprint/service).
2. Start the runner via the CLI with the tangle-evm protocol selected (this flag denotes Tangle).

Deployment-dependent addresses and endpoints are published per environment:

• Endpoints and Integration

Next Reading

• Blueprint Runner
• Tangle Client Context
• System Architecture