Skip to main content

Community Blueprints

Community blueprints are externally maintained Node Runners blueprints created by the community. They follow the same architecture as built-in blueprints but are published and maintained independently.

Four new community blueprints available

The community blueprint system now welcomes Robinhood Chain, Avalanche, Arbitrum, and Arc. Want to add another? See Creating Your Own Blueprint.

Catalog​

Community blueprints are listed here as they are published and submitted for inclusion.

ProtocolPackageMaintainerDocsNetworksInstall
TRONaws-bnr-blueprint-tron@TristenyangREADMEMainnet, Nilenpm install github:Tristenyang/aws-bnr-blueprint-tron --legacy-peer-deps
Robinhood Chainaws-bnr-blueprint-robinhood@karimakacemREADMEMainnet (chain ID 4663), Testnet (chain ID 46630)npm install github:karimakacem/aws-bnr-blueprint-robinhood --legacy-peer-deps
Avalancheaws-bnr-blueprint-avalanche@karimakacemREADMEMainnet, Fuji testnetnpm install github:karimakacem/aws-bnr-blueprint-avalanche --legacy-peer-deps
Arbitrumaws-bnr-blueprint-arbitrum@karimakacemREADMEArbitrum One (chain ID 42161), Arbitrum Nova (chain ID 42170), Arbitrum Sepolia (chain ID 421614)npm install github:karimakacem/aws-bnr-blueprint-arbitrum --legacy-peer-deps
Arcaws-bnr-blueprint-arc@karimakacemREADMEMainnet (chain ID 5042), Testnet (chain ID 5042002)npm install github:karimakacem/aws-bnr-blueprint-arc --legacy-peer-deps

Using a Community Blueprint​

  1. Install the package:

    npm install aws-bnr-blueprint-<protocol> --legacy-peer-deps

    Or from a GitHub repository:

    npm install github:org/aws-bnr-blueprint-<protocol> --legacy-peer-deps
    Why --legacy-peer-deps?

    Blueprints declare a peer dependency on the aws-blockchain-node-runners framework, which is not published to the npm registry. Without this flag, npm's strict peer resolution (npm 7+) fails with a 404 Not Found for aws-blockchain-node-runners.

  2. Configure your .env file using the blueprint's sample configs (check the blueprint's README for available networks and options).

  3. Deploy with the AI workflow (recommended):

    @deploy using <protocol> blueprint on <network>

    Or deploy manually with npx cdk deploy.

  4. Security review: On first use of any community blueprint, the AI workflow performs an automated security review of its configuration scripts before deployment. See the Security Review Guide for details.

Community blueprints are NOT officially vetted by AWS

Community blueprints are maintained by their respective authors. They have not been reviewed or endorsed by AWS. The automated security review helps catch common issues, but you should review any blueprint's source code before deploying to production.

Creating Your Own Blueprint​

Want to add support for a new blockchain protocol? Community blueprints use the same pluggable NPM package system as built-in ones — there is no distinction at runtime.

Resources​

  • About Blueprints — Architecture overview, directory structure, package.json format, and the pluggable NPM system explained.
  • Add Protocol with AI — Step-by-step AI-assisted workflow for creating a new blueprint. Covers both core maintainer (Path A) and community developer (Path B) flows.
  • Dummy Blueprint — The canonical reference implementation. Use it as your starting template.
  • Contributing Guidelines — General contribution process, PR etiquette, and licensing.

Quick Summary​

  1. Create your blueprint package following the structure in About Blueprints
  2. Include the "aws-blockchain-node-runner" field in your package.json (see format reference)
  3. Publish to NPM or a public GitHub repository
  4. Submit for catalog listing
Use the AI workflow

The fastest way to create a new blueprint is with the @add-protocol AI workflow. It guides you through the entire process interactively — from fetching your protocol's docs to generating all required files. See Add Protocol with AI for details.