bitcoin-core-indexes
Bitcoin Core indexes: txindex, blockfilterindex (BIP157/158), coinstatsindex. Disk costs, rebuild times, when each is needed. USE WHEN: choosing which indexes to enable, troubleshooting "txid not found", integrating with electrs / fulcrum / LN nodes.
What this skill does
# Bitcoin Core Indexes Three optional indexes (in addition to the always-on UTXO set): ## txindex ```ini txindex=1 ``` Maps every txid to its block / position. Enables: - `getrawtransaction <txid>` for **any** historical tx (without txindex, only mempool + recent blocks since restart). Cost: - Disk: ~80 GB. - IBD time: +20-50% if enabled from start. - Rebuild from scratch on a synced node: hours, not days. When to enable: - Block explorers / public APIs. - Forensic / compliance tools. - Apps that need to look up arbitrary historical txs. When to skip: - Pruned nodes (cannot combine). - Node that only serves recent activity (mempool + last few blocks). ## blockfilterindex (BIP157/158) ```ini blockfilterindex=1 peerblockfilters=1 # serve filters to peers ``` Maintains compact block filters per block. Enables: - `getblockfilter <blockhash>` RPC. - Serving filters to BIP157 clients (Neutrino in LDK / btcwallet). - Used by Electrs for fast scan operations. Cost: - Disk: ~6 GB total. - IBD impact: +5-10%. When to enable: - Running Electrs / Fulcrum / similar indexers (they need it). - Lightning node using LDK / Neutrino backend. - Provides scan service to lightweight clients. ## coinstatsindex ```ini coinstatsindex=1 ``` Maintains rolling stats for `gettxoutsetinfo` (UTXO set value, count, hash) without a full scan. Cost: - Disk: ~1 GB. - IBD impact: +2-5%. When to enable: - Frequent calls to `gettxoutsetinfo` (without it, the call takes minutes and locks the wallet). Without it, `gettxoutsetinfo` still works but does a full scan on-demand → slow. ## Combining All three can be enabled together. Pruning prevents only `txindex`. Typical configurations: | Use case | txindex | blockfilterindex | coinstatsindex | prune | |----------|---------|------------------|----------------|-------| | Personal wallet | no | no | no | optional | | LN node (LDK) | no | **yes** | optional | no | | LN node (LND/CLN) | no | optional | optional | no | | Electrs/Fulcrum host | no | **yes** | optional | no | | Block explorer | **yes** | yes | yes | no | | Forensic / API | **yes** | optional | yes | no | | Lightweight personal | no | no | no | **yes (550-15000)** | ## Rebuilding Adding `txindex=1` to existing node: ```bash # Stop node bitcoin-cli stop # Edit conf, add txindex=1 # Restart; node rebuilds index bitcoind -daemon # Watch tail -f ~/.bitcoin/debug.log ``` Output: ``` 2025-... reindex-chainstate already=true txindex=true blockfilterindex=true coinstatsindex=true 2025-... Building txindex ... (hours later) ... 2025-... txindex is enabled ``` To force rebuild from scratch: `-reindex` (full reindex, days) or `-reindex-chainstate` (UTXO + indexes only, hours). ## Index storage - `<datadir>/indexes/txindex/` — LevelDB. - `<datadir>/indexes/blockfilter/basic/` — filter files. - `<datadir>/indexes/coinstats/` — LevelDB. ## Common bugs - Adding `txindex=1` to a pruned node → bitcoind exits. - Removing `txindex` from conf → bitcoind warns but continues with index "stuck"; manually delete `indexes/txindex/` to free disk. - Electrs/Fulcrum not connecting → check `peerblockfilters=1` and `blockfilterindex=1` are both set. ## See also - [operations/SKILL.md](../operations/SKILL.md) - [rpc/SKILL.md](../rpc/SKILL.md) - [../../infrastructure/electrs/SKILL.md](../../infrastructure/electrs/SKILL.md) - [../../infrastructure/fulcrum/SKILL.md](../../infrastructure/fulcrum/SKILL.md)
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.