Skip to content

Remove direct bitcoind dependency, sync via electrum/esplora indexer#126

Open
bitwalt wants to merge 1 commit into
RGB-Tools:masterfrom
bitwalt:bitcoind-removal-indexer
Open

Remove direct bitcoind dependency, sync via electrum/esplora indexer#126
bitwalt wants to merge 1 commit into
RGB-Tools:masterfrom
bitwalt:bitcoind-removal-indexer

Conversation

@bitwalt
Copy link
Copy Markdown
Contributor

@bitwalt bitwalt commented May 1, 2026

Implements #125.

Routes block + transaction sync through the configured indexer (electrum or esplora) via lightning-transaction-sync, dropping lightning-block-sync (RPC mode) and removing the four bitcoind_rpc_* fields from the unlock/init API, OpenAPI spec, README and Dockerfile. Async gossip verification, fee estimation, broadcast and UTXO lookup all go through the indexer client.

Sync block/tx state via the configured indexer (electrum or esplora)
through lightning-transaction-sync, dropping the lightning-block-sync
RPC client and removing the bitcoind RPC fields from the unlock API,
OpenAPI spec, README and Dockerfile. Async gossip verification is
preserved on top of the new indexer client.

Also stabilises two integration-test flakes that surface in long
sequential runs: swap_roundtrip_multihop_asset_asset waits for all
four channels to be usable before maker_init (both swap legs route
over distinct RGB-asset channels), and upload_asset_media::fail
tolerates the connection-reset that RequestBodyLimitLayer can produce
mid-stream instead of a 413 response.
@bitwalt bitwalt force-pushed the bitcoind-removal-indexer branch from 0e5ad71 to 9500239 Compare May 4, 2026 11:41
@bitwalt bitwalt marked this pull request as ready for review May 4, 2026 15:04
Copy link
Copy Markdown
Member

@zoedberg zoedberg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please check my comment #125 (comment), I explained why we should not replace the block-sync with the transaction-sync but add it instead as an alternative sync mode. Please update this PR accordingly

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants