ops-add-new-chain

Deploys Boundless infrastructure to a new blockchain via Pulumi stacks and CI/CD pipelines.

Updated Apr 11, 2026
One-click install
npx skills add https://github.com/Current-cmd/TrustMeBRO --skill ops-add-new-chain-current-cmd
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ops-add-new-chain
Source: https://github.com/Current-cmd/TrustMeBRO/tree/main/.claude/skills/ops-add-new-chain
Command: npx skills add https://github.com/Current-cmd/TrustMeBRO --skill ops-add-new-chain-current-cmd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Adding a new blockchain to Boundless infrastructure requires manually creating Pulumi stacks, copying config files, updating the ChainId enum, and wiring CodeBuild/CodePipeline stages across five services — an error-prone process this Skill automates as a guided workflow. ## Core Features & Use Cases - Interactive information gathering: Collects chain IDs, contract addresses, RPC URLs, and deployment blocks for staging and prod environments in structured batches. - Infrastructure provisioning: Creates Pulumi stacks with KMS secrets providers, copies config from source stacks, and overrides chain-specific values for order-stream, distributor, slasher, indexer, and order-generator. - Pipeline wiring: Updates the ChainId enum in TypeScript and adds CodeBuild projects and pipeline stage actions for the new chain. - Use Case: A Boundless team member needs to deploy services to Taiko mainnet (chain ID 167000). The Skill walks them through credential verification, stack creation, config overrides, and post-deploy service URL wiring. ## Quick Start Ask the assistant to add a new chain to Boundless infrastructure and provide the chain ID, contract addresses, and RPC URLs when prompted.

Frequently Asked Questions about ops-add-new-chain

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I deploy Boundless services to a new blockchain?▼

Run this workflow to gather chain IDs, contract addresses, and RPC URLs, then it creates Pulumi stacks for each service, copies config from existing Base stacks, and overrides chain-specific values. It also updates the ChainId enum and CI/CD pipeline definitions.

How do I create a new Pulumi stack with a KMS secrets provider?▼

Run pulumi stack init with the --secrets-provider flag pointing to the awskms ARN for the pulumi-secrets-key alias. Then use copy_config.sh to clone config from a source stack like l-staging-84532.

What AWS credentials are needed for Pulumi stack creation?▼

You need Ops Admin, Staging Admin, or Production Admin credentials exported as AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, and AWS_SESSION_TOKEN. The default dev account role only has read-only access to the Pulumi state bucket.

Why is INDEXER_API_URL set to blank during new chain setup?▼

The indexer URL does not exist until the indexer service is actually deployed on the new chain. You must deploy order-stream first, then indexer, and update the distributor and order-generator configs with the resulting URLs afterward.

Can this workflow delete or modify existing Pulumi stacks?▼

No. The workflow is strictly additive — it only creates new stacks and config files. It explicitly forbids pulumi destroy, stack removal, deleting Pulumi.*.yaml files, and any destructive AWS actions.