Blueprint Manager

On Tangle, blueprints have an on-chain lifecycle (creation, registration, service requests) and an off-chain lifecycle (running the actual service). The off-chain component is managed by the Blueprint Manager.

You can think of the Blueprint Manager as the operator-side agent that:

• Runs blueprint service instances for customers
• Talks to the chain for job calls, heartbeats, and service lifecycle events
• Coordinates payout “drips” for streamed payments (when enabled)

1. Operators must register for Blueprints onchain. This indicates an operators willingness to accept requests for Blueprint Instances of that type.
2. Operators (via the Blueprint Manager) fetch and verify blueprint artifacts and metadata based on the declared sources (native, container, WASM, etc.).
3. When a service is activated, the Blueprint Manager starts the service instance in the correct execution environment, and begins reporting liveness via heartbeats.

Blueprint and Service Instance Lifecycle

Blueprints interact with Tangle in several key ways:

1. Blueprints are deployed to Tangle, with their metadata and smart contracts stored and deployed on-chain.
2. Blueprints are instantiated, triggering the creation of a service (a customer-owned instance). The service runs until it is terminated or expires.
3. Services are terminated once they reach their time-to-live (TTL) or are explicitly terminated; the underlying blueprint remains available unless the developer deactivates it.

Blueprints provide a useful abstraction, allowing developers to define reusable service infrastructure with clear monetization and security hooks.

On-chain, the core objects live in the Tangle contract:

• Blueprints (creation, metadata, schemas)
• Operator registration (identity key + endpoint)
• Service requests and service lifecycle
• Payment splitting and slashing coordination

Security and delegation are handled by the MultiAssetDelegation restaking contract, and service-fee restaker payouts are handled by ServiceFeeDistributor.