Deploying Blueprints

In order for a blueprint to be instance-able, it’ll need to be deployed and have one or more sources defined.

If your blueprint has confidentiality requirements, also declare an execution policy in blueprint metadata. TEE is not a separate source type. See Execution Confidentiality.

Defining Sources

Before deploying, you must specify the sources from which to fetch the blueprint binaries. See Sources.

Testing Your Sources

To verify that your sources are valid, see Debugging Blueprints.

Deploying via the CLI

Once you’re ready to deploy your blueprint, simply:

Install the cargo-tangle CLI, if you haven’t already.

For testing, you can deploy to a local devnet:

export SIGNER="//Alice"
export EVM_SIGNER="0xcb6df9de1efca7a3998a8ead4e02159d5fa99c3e0d4fd6432667390bb4726854"
cargo tangle blueprint deploy tangle --devnet

See Tangle CLI reference for the current command flow and options.