Rbtc

What This Skill Does

Rbtc is a highly specialized OpenClaw agent skill designed to deploy and manage a Bitcoin Core-based blockchain node. Unlike generic implementations, Rbtc maintains a strict upstream-pinned architecture, ensuring the node stays synchronized with official Bitcoin Core release tags. The skill utilizes a single, immutable, scope-limited patch to establish a custom chain identity while leaving the core consensus and security protocols of the upstream Bitcoin codebase untouched. This allows developers and infrastructure operators to run a customized blockchain network while benefiting from the battle-tested stability of the standard Bitcoin software.

Installation

To integrate this skill into your environment, use the command: clawhub install openclaw/skills/skills/happybigmtn/rbtc. Once installed, the primary interface for setup is the install.sh script, which handles GPG verification of upstream releases, checksum validation, and the automated compilation of the node. You can trigger the installation for a specific version tag by running ./install.sh v30.2. Configuration is flexible, allowing you to pass environment variables such as MINER_CPU_PERCENT or MINER_MAX_THREADS to tune resource allocation without modifying source code.

Use Cases

This skill is ideal for:

1. Private Network Development: Deploying custom sidechains or private testnets that require Bitcoin-compatible consensus mechanisms.
2. Security Auditing: Utilizing the provided agent_verify.sh and enforce_patch_scope.sh scripts to conduct rigorous security reviews of the node's provenance and binary integrity.
3. Automated Infrastructure: Managing blockchain nodes in CI/CD environments where atomic updates, binary manifest verification, and automated rollback capabilities are mandatory.

Example Prompts

1. "OpenClaw, please install the latest version of Rbtc and verify the binary against the current manifest."
2. "Update my Rbtc node to tag v30.3 and ensure the CPU miner is configured to use only 25% of the total resources."
3. "Run a diagnostic check on the current Rbtc installation to confirm the patch scope remains within the allowed file set."

Tips & Limitations

Always use the provided scripts/updater.sh for version transitions to ensure atomic symlink swaps, which protect you from broken node states. If you are experimenting with custom network parameters, ensure that your bitcoin.conf file is correctly formatted for the specific network type (main, test, or regtest). Note that while this skill streamlines Bitcoin Core management, it does not provide custodial wallet services; users are expected to manage keys via standard RPC interfaces. Always audit the immutable.patch before deployment to ensure your specific use case does not exceed the intended patch scope.