Blueprints

Getting Started

Blueprints are on-chain service definitions, and Services are their on-chain instantiations. Developers build Blueprints using the Blueprint SDK and deploy them to Tangle v2. Customers discover Blueprints, create Services, and pay for execution. Operators run Services with the Blueprint Manager, earning fees and TNT incentives defined by the core protocol contracts in tnt-core.

A Blueprint Service is a reusable computational service. Each Service instance can select a different operator set, security configuration, and payment token while sharing the same underlying blueprint logic.

A Tangle Blueprint is defined by:

• A manager contract (Blueprint Service Manager) that defines registration, request, and job verification logic.
• A blueprint definition (metadata URI, job schemas, artifact sources) used by the Blueprint Manager.
• Executable artifacts (native binary, container image, or WASM) for operators to run.

Blueprints specify their runtime preferences so operators can execute services natively, in containers, or inside a VM.

Detailed Interactions

Developers

Developers deploy the blueprint manager contract and register a blueprint definition that points at the artifacts and job schemas operators should run. The on-chain manager contract handles:

1. Registration: Specifies how Operators register for the Blueprint, allowing the developer to add additional fees, access control, KYC, and any other EVM-deployable functionality to the registration process.
2. Request: Defines how customers create Services and fund them (pay-once or subscription).
3. On Job Hooks: Allows developers to specify custom logic to be executed when a job is created.
4. On Job Result Hooks: Allows developers to specify custom logic to be executed when a job is completed, such as verifying a job’s output.
5. Custom slashing conditions: Allows developers to define slashing logic for misbehavior, scoped to their Service.

Blueprints let developers define monetizable services (MPC, ZK proving, AI infrastructure, oracles) with on-chain verification and off-chain execution handled by operators running the Blueprint Manager.

Customers

Customers discover blueprints, configure services, and select operators based on requirements (security, resources, price, or reputation). They fund services in ETH or ERC20 tokens and can choose a one-time payment or subscription model.

To initialize a Service, a customer typically:

1. Chooses an operator set and any service parameters required by the blueprint.
2. Provides metadata required by the Service instance.
3. Funds the service fee required by the blueprint manager contract.

Operators

Operators register for blueprints, accept service assignments, and run the service artifacts through the Blueprint Manager. They earn an operator share of service payments (claimable from the Tangle contract) plus TNT incentives.

Payments and Incentives

Service payments are split by the core protocol contracts in tnt-core:

• Developer + Treasury shares transfer immediately.
• Operator share accrues as pending rewards in the Tangle contract.
• Staker share flows to ServiceFeeDistributor for later claims.

Inflation incentives (TNT) are distributed separately via InflationPool and RewardVaults. For details, see https://github.com/tangle-network/tnt-core/blob/v2/PAYMENT_FLOW.md and https://github.com/tangle-network/tnt-core/blob/v2/docs/rewards-system.md.

Composability and Ecosystem

Blueprints can be composed and linked together to create sophisticated, interoperable applications, fostering innovation and collaboration within the Tangle ecosystem. The Tangle architecture is uniquely suited for complex cryptographic applications, such as multi-party computation (MPC) and zero-knowledge (ZK) services, as well as oracles, custody solutions, bridge co-processors, and proving networks. Developers are encouraged to collaborate and contribute to expanding the library of apps and services on Tangle, and will be rewarded with incentives for their valuable contributions.