bitcoin-core-operations
Running Bitcoin Core in production: bitcoin.conf reference, sections, pruning, signet, dbcache, mempool tuning, network bind, Tor, IBD considerations, debug.log analysis. USE WHEN: deploying a node, tuning performance, debugging IBD issues, configuring multi-network nodes.
What this skill does
# Running Bitcoin Core ## Configuration file `~/.bitcoin/bitcoin.conf` (Linux/macOS) or `%APPDATA%\Bitcoin\bitcoin.conf` (Windows). Optional `-conf=` flag. ### Section markers ```ini # Top-level: applied to all networks dbcache=4096 [main] # Mainnet-only prune=550 [test] # Testnet [signet] # Signet [regtest] # Regtest ``` The `chain=test/signet/regtest` cmdline flag selects active network. Without `[section]`, top-level options apply universally. ### Key options | Option | Effect | |--------|--------| | `dbcache=4096` | UTXO cache MB. Default 450. Larger = faster IBD; 4-8 GB ideal during sync, can drop to 450 after. | | `prune=550` | Min disk MB. 550 keeps last ~3 days. After IBD, reduces from ~600 GB to ~5 GB. Mutually exclusive with `txindex`. | | `txindex=1` | Maintains full tx index. Required for `getrawtransaction` of arbitrary txs. ~80 GB extra disk. | | `blockfilterindex=1` | BIP157/158 filters; needed for Electrs/Neutrino. ~6 GB extra. | | `coinstatsindex=1` | Pre-computed UTXO set stats. ~1 GB. | | `assumevalid=<hash>` | Skip script validation up to this block. Default in source. | | `assumeutxo=...` | Fast IBD via committed UTXO snapshot. | | `maxmempool=1000` | Mempool MB. Default 300. | | `mempoolfullrbf=0` | Default in 28.0+ is 1 (true). | | `permitbaremultisig=0` | Reject bare multisig outputs (default). | | `rpcbind=127.0.0.1:8332` | RPC interface bind. | | `rpcallowip=192.168.1.0/24` | Subnets allowed to call RPC. | | `bind=0.0.0.0:8333` | P2P listen interface. | | `listen=1`, `listenonion=1` | Listen for inbound. | | `[email protected]` | Privileged peer (disable rate limits, etc.) | | `proxy=127.0.0.1:9050` | SOCKS5 proxy (Tor). | | `onlynet=onion` | Tor-only (no clearnet peers). | | `i2psam=127.0.0.1:7656` | I2P SAM bridge. | | `cjdnsreachable=1` | Treat fc00::/7 IPv6 as reachable via CJDNS. | ## Initial Block Download (IBD) Phases: 1. **Header sync** — fast, all headers from a single peer. 2. **Block download** — parallel download from multiple peers. 3. **Block validation** — script verify, UTXO set update. Tips: - Use a fast SSD; HDD adds days. - `dbcache=4096` (or higher with RAM) speeds up phase 3 dramatically. - Bandwidth: ~600 GB. Restrict via `maxuploadtarget=` if metered. - After IBD, you can shrink dbcache to 450. ## Pruning vs txindex - **Pruned (550-15000 MB)**: - Fast disk usage; minimal historical access. - Cannot serve old blocks to peers (becomes `NODE_NETWORK_LIMITED`). - Cannot run Electrs / serve historical `getrawtransaction`. - **Full (no prune)**: - ~700 GB disk + growing. - Can serve any block to peers. - Required for indexers. - **txindex=1**: - Adds ~80 GB. - Required for arbitrary `getrawtransaction`. - Cannot combine with prune. For a Lightning node: full + `blockfilterindex=1` is typical (no txindex needed; LDK/CLN use filter scan). ## Tor configuration ```ini proxy=127.0.0.1:9050 onlynet=onion listenonion=1 bind=127.0.0.1 ``` `bitcoind` auto-creates a Tor v3 hidden service via `torcontrol` (needs `controlport=9051` + cookie auth or password in torrc). ## debug.log Located at `~/.bitcoin/debug.log` (or `~/.bitcoin/<chain>/debug.log`). Categories: `getrawtransaction`, `mempool`, `net`, `prune`, `validation`, `zmq`. Enable verbosity: ```ini debug=mempool debug=validation ``` Or all: `debug=1`. Performance impact moderate. Key patterns: - `UpdateTip:` — new block. - `received block` — block arrival. - `txn-already-known` — duplicate broadcast. - `bad-txns-inputs-missingorspent` — invalid input. - `Pre-allocating up to ...` — file allocation messages. ## systemd unit ```ini [Unit] Description=Bitcoin Core After=network-online.target [Service] ExecStart=/usr/local/bin/bitcoind -daemon -conf=/etc/bitcoin/bitcoin.conf ExecStop=/usr/local/bin/bitcoin-cli stop Type=forking PIDFile=/var/lib/bitcoind/bitcoind.pid User=bitcoin Group=bitcoin Restart=on-failure [Install] WantedBy=multi-user.target ``` ## Backup considerations - `wallet.dat` (legacy) or `wallets/<name>/wallet.dat` (descriptor). - For descriptor wallets: backup is just the descriptors + private keys (`listdescriptors true`). - Stop bitcoind before file copy or use `backupwallet` RPC for consistent snapshot. ## Common bugs - Setting `dbcache=8000` on a system with 4 GB RAM → OOM. - Using `txindex=1` and `prune=N>0` simultaneously → bitcoind exits on startup. - Multi-wallet without explicit `rpcwallet` parameter → RPC fails with "Wallet file not specified". - `rpcbind=0.0.0.0` without firewall → exposes RPC to internet. Always pair with `rpcallowip=` or use SSH tunnel. - Insufficient `dbcache` during IBD → 4x slower sync. ## See also - [rpc/SKILL.md](../rpc/SKILL.md) - [indexes/SKILL.md](../indexes/SKILL.md) - [zmq/SKILL.md](../zmq/SKILL.md) - [../../infrastructure/node-distros/SKILL.md](../../infrastructure/node-distros/SKILL.md)
Related in Backend & APIs
jfrog
IncludedInteract with the JFrog Platform via the JFrog CLI and REST/GraphQL APIs. Use this skill when the user wants to manage Artifactory repositories, upload or download artifacts, manage builds, configure permissions, manage users and groups, work with access tokens, configure JFrog CLI servers, search artifacts, manage properties, set up replication, manage JFrog Projects, run security audits or scans, look up CVE details, query exposures scan results from JFrog Advanced Security, manage release bundles and lifecycle operations, aggregate or export platform data, or perform any JFrog Platform administration task. Also use when the user mentions jf, jfrog, artifactory, xray, distribution, evidence, apptrust, onemodel, graphql, workers, mission control, curation, advanced security, exposures, or any JFrog product name.
cupynumeric-migration-readiness
IncludedPre-migration readiness assessor for porting NumPy to cuPyNumeric. Use BEFORE substantial porting work begins when the user asks whether code will scale on GPU, whether they should migrate to cuPyNumeric, which NumPy patterns transfer cleanly, what must be refactored before porting, or mentions pre-port assessment, scaling analysis, or refactor planning. Inspect the user's source code, look up NumPy usage, cross-reference the cuPyNumeric API support manifest, and distinguish distributed-scaling-friendly patterns from blockers such as unsupported APIs, scalar synchronization, host round-trips, Python/object-heavy control flow, shape/data-dependent branching, and in-place mutation hazards. Produce a verdict of READY, LIGHT REFACTOR, SIGNIFICANT REFACTOR, or NOT RECOMMENDED, with concrete refactor pointers.
alibabacloud-data-agent-skill
IncludedInvoke Alibaba Cloud Apsara Data Agent for Analytics via CLI to perform natural language-driven data analysis on enterprise databases. Data Agent for Analytics is an intelligent data analysis agent developed by Alibaba Cloud Database team for enterprise users. It automatically completes requirement analysis, data understanding, analysis insights, and report generation based on natural language descriptions. This tool supports: discovering data resources (instances/databases/tables) managed in DMS, initiating query or deep analysis sessions, real-time progress tracking, and retrieving analysis conclusions and generated reports. Use this Skill when users need to query databases, analyze data trends, generate data reports, ask questions in natural language, or mention "Data Agent", "data analysis", "database query", "SQL analysis", "data insights".
token-optimizer
IncludedReduce OpenClaw token usage and API costs through smart model routing, heartbeat optimization, budget tracking, and native 2026.2.15 features (session pruning, bootstrap size limits, cache TTL alignment). Use when token costs are high, API rate limits are being hit, or hosting multiple agents at scale. The 4 executable scripts (context_optimizer, model_router, heartbeat_optimizer, token_tracker) are local-only — no network requests, no subprocess calls, no system modifications. Reference files (PROVIDERS.md, config-patches.json) document optional multi-provider strategies that require external API keys and network access if you choose to use them. See SECURITY.md for full breakdown.
resend-cli
IncludedUse this skill when the task is specifically about operating Resend from an AI agent, terminal session, or CI job via the official resend CLI: installing/authenticating the CLI, sending/listing/updating/cancelling emails, batch sends, domains and DNS, webhooks and local listeners, inbound receiving, contacts, topics, segments, broadcasts, templates, API keys, profiles, or debugging Resend CLI/API failures. Trigger on mentions of Resend CLI, `resend`, `resend doctor`, `resend emails send`, `resend domains`, `resend webhooks listen`, `resend emails receiving`, or agent-friendly terminal automation.
alibabacloud-odps-maxframe-coding
IncludedUse this skill for MaxFrame SDK development and documentation navigation on Alibaba Cloud MaxCompute (ODPS). Helps answer MaxFrame API, concept, official example, and supported pandas API questions; create data processing programs; read/write MaxCompute tables; debug jobs (remote or local); and build custom DPE runtime images. Trigger when users mention MaxFrame, MaxCompute with MaxFrame, ODPS table processing, DPE runtime, MaxFrame docs/examples, DataFrame/Tensor operations, or GPU runtime setup. Works for both English and Chinese queries about Alibaba Cloud data processing with MaxFrame.