Please check the build logs for more information.
See Builds for ideas on how to fix a failed build, or Metadata for how to configure docs.rs builds.
If you believe this is docs.rs' fault, open an issue.
Overview
Blueprints are Infrastructure-as-Code templates that allow developers to quickly build crypto services. The Blueprint SDK comes equipped with a variety of tools, from event listeners and p2p networking to flexible keystores, allowing you to rapidly prototype distributed systems. With these tools, developers can get started building anything from oracles to bridge security systems, zk prover networks, AI agent orchestration systems. Deploy these applications on the Tangle Network, Eigenlayer, or natively.
We also have a documentation site on all things Tangle to help you get started.
Features
Logging Targets
The SDK is split into multiple logging targets to make debugging different components easier.
When testing, by default, only ERROR, WARN, and INFO logs will be printed. This can be controlled
with the RUST_LOG environment variable.
An example use-case would be setting RUST_LOG=tangle-consumer=trace to determine the cause of a failing
job submission.
Producers
evm-polling-producer-PollingProducertangle-producer-TangleProducer
Consumers
tangle-consumer-TangleConsumer
Runner
blueprint-runner-BlueprintRunnerblueprint-router- [Router]blueprint-rejection- All [Job] call failures
Other
tangle-node- The stdout of a local Tangle node- These are spawned by both the
TangleTestHarnessandcargo tanglelocal testing commands.
- These are spawned by both the
build-output- The stderr ofcargo buildwhen deploying withcargo tangle- By default, the output of
cargo buildis hidden. If diagnosing a build error, useRUST_LOG=build-output=debug.
- By default, the output of