blueprint

Blueprint SDK

A comprehensive toolkit for building, deploying, and managing blueprints on the Tangle Network.

Overview

The Blueprint SDK is a modular Rust toolkit for building decentralized services—called Blueprints—that run against [Tangle], an EVM protocol deployed on EVM chains.

Blueprints turn complex on-chain and off-chain infrastructure into reproducible, deployable units of logic—think Infrastructure-as-Code for crypto systems. With one SDK, you can design anything from oracles and MPC networks to agent-based AI services or zk-proof markets, and deploy them seamlessly.

The SDK unifies:

• Job orchestration and routing across async, event-driven systems
• P2P networking with secure message handling and round-based protocol support
• Cryptographic primitives and keystore management for signing, verification, and MPC
• EVM extensions for direct smart contract integrations
• Testing and benchmarking utilities for reproducible environments and performance tuning

In short, Blueprints let developers move from concept to distributed protocol with minimal friction.

We also have a documentation site on all things [Tangle] to help you get started.

SDK Components

The following components make up the SDK, providing everything from job creation and routing utilities to specialized tools for networking and testing.

• blueprint-sdk - Main crate for the [Tangle] Blueprint SDK, re-exporting all of the following
• blueprint-benchmarking - Utilities for benchmarking blueprints
• blueprint-build-utils - Utilities for simplifying build-time tasks (e.g., building contracts, installing dependencies)
• blueprint-chain-setup - (Meta-crate) Utilities for setting local testnets
  • blueprint-chain-setup-anvil - Utilities for setting up [Anvil] testnets
• blueprint-clients - (Meta-crate) Clients for interacting with [Tangle] and other networks
  • blueprint-client-core - Core client primitives and traits
  • blueprint-client-tangle - Client for interacting with the [Tangle] EVM contracts
  • blueprint-client-evm - Client for interacting with the EVM Network
• blueprint-contexts - Extensions for adding functionality to custom blueprint context types
• blueprint-context-derive - Derive macros for implementing context extension traits
• blueprint-core - Core components for building blueprints, primarily job system primitives
• blueprint-crypto - (Meta-crate) Cryptographic utilities
  • blueprint-crypto-core - Core cryptographic utilities (traits, types)
  • blueprint-crypto-bls - Utilities for working with BLS signatures and keys
  • blueprint-crypto-bn254 - Utilities for working with BN254 signatures and keys
  • blueprint-crypto-ed25519 - Utilities for working with Ed25519 signatures and keys
  • blueprint-crypto-hashing - Cryptographic hashing utilities
  • blueprint-crypto-k256 - Utilities for working with [secp256k1] signatures and keys
  • blueprint-crypto-sr25519 - Utilities for working with sr25519 signatures and keys
• blueprint-keystore - Flexible keystore implementation, supporting local and remote signers
• blueprint-macros - Utility macros for simplifying blueprint development
• blueprint-manager - A program executor that connects to a [Tangle] deployment and runs protocols dynamically on the fly
  • blueprint-manager-bridge - IPC bridge for manager-blueprint communication
• blueprint-metrics (Meta-crate) Utilities for collecting metrics
  • blueprint-metrics-rpc-calls - Utilities for collecting metrics from RPC calls
• blueprint-networking - P2P networking support for blueprints
  • blueprint-networking-round-based-extension - A networking compatibility layer for [round-based] MPC protocols
  • blueprint-networking-agg-sig-gossip - Aggregated signature gossip extension
  • blueprint-networking-gossip-primitives - Gossip protocol primitives
• blueprint-pricing-engine - Pricing engine for computing resource costs
• blueprint-producers-extra - Additional protocol-independent event producers
• blueprint-profiling - Profiling utilities for performance analysis
• blueprint-qos - Quality of Service monitoring and metrics
• blueprint-router - A job router for dynamically scheduling jobs
• blueprint-runner - The blueprint job runner, executing jobs in a protocol-specific manner
• blueprint-std - Standard library extensions, for use within the SDK
• blueprint-stores - (Meta-crate) Storage providers for blueprints
  • blueprint-store-local-database - A local JSON key-value database
• blueprint-remote-providers - Remote cloud provider integrations (AWS, GCP, Azure, etc.)
• blueprint-tangle-aggregation-svc - Tangle aggregation service for BLS signature aggregation
• blueprint-tangle-extra - Tangle-specific producers, consumers, and extractors
• blueprint-evm-extra - EVM specific extensions for blueprints
• blueprint-faas - FaaS (Function-as-a-Service) execution support
• blueprint-auth - Authentication and authorization utilities
• blueprint-testing-utils - (Meta-crate) Utilities for testing blueprints
  • blueprint-core-testing-utils - Core testing utility primitives
  • blueprint-anvil-testing-utils - Utilities for creating and interacting with Anvil testnets

Getting Started

Prerequisites

Ensure you have the following installed:

• [Rust]
• OpenSSL Development Packages

For Ubuntu/Debian:

sudo apt update && sudo apt install build-essential cmake libssl-dev pkg-config

For macOS:

brew install openssl cmake

CLI Installation

You can install the [Tangle] CLI in two ways:

Option 1: Install Script (recommended)

Install the latest stable version of cargo-tangle using the installation script:

curl --proto '=https' --tlsv1.2 -LsSf https://github.com/tangle-network/blueprint/releases/download/cargo-tangle/v0.1.1-beta.7/cargo-tangle-installer.sh | sh

Option 2: Install from source

Install the latest git version of cargo-tangle using the following command:

cargo install cargo-tangle --git https://github.com/tangle-network/blueprint --force

✨ Creating Your First Blueprint

After installation, you can create, build, register, and run your first blueprint against the [Tangle] EVM:

# Create a new blueprint named "my_blueprint"
cargo tangle blueprint create --name my_blueprint

# Navigate into the blueprint directory and build
cd my_blueprint
cargo build

# Deploy your blueprint to the [Tangle Network]
# Write the contract coordinates used by your service
cat > settings.env  **Note:** The harness loads `crates/chain-setup/anvil/snapshots/localtestnet-state.json` and falls back to the bundled `localtestnet-broadcast.json` if the snapshot is missing or fails validation. Refresh fixtures with `scripts/fetch-localtestnet-fixtures.sh`, and set `RUN_TNT_E2E=1` to opt into the longer suites.

For a keystore-to-runner walkthrough (keys, env vars, harness commands, and manual
`TangleClient` snippets) see [`docs/operators/anvil.md`](docs/operators/anvil.md).

For additional commands, advanced configurations, and complete CLI usage, see the [official CLI reference](https://docs.tangle.tools/developers/cli/reference).

##  Support

For support or inquiries:
- **Issues:** Report bugs or request features via GitHub Issues.
- **Discussions:** Engage with the community in GitHub Discussions.
- For real-time assistance and announcements:
    - Join our [Discord server](https://discord.com/invite/cv8EfJu3Tn)
    - Join our [Telegram channel](https://t.me/tanglenet)

---

## Key Concepts

**Blueprint SDK** is a Rust framework for building verifiable, decentralized services on [Tangle Network] with built-in x402 payment rails, multi-operator BLS aggregation, and TEE support.

**Blueprint** is a deployable service specification that defines computation logic, verification requirements, and payment flows in a single package. Operators stake TNT tokens to run blueprints, with slashing for incorrect results.

**x402** is an HTTP-native micropayment protocol built into the SDK that enables per-request payments for blueprint services. Agents pay with signed HTTP headers, no accounts or API keys required.

**Operator** is a node runner who stakes economic collateral (TNT tokens) to execute blueprint jobs. Multiple operators can verify the same job through BLS signature aggregation.

**TangleArg / TangleResult** are extractor types that decode on-chain job inputs and encode results for sub