full_scan over RPC ignores --scan-stop-gap: restored wallet silently misses funds at external index >= 25
Maintainer antworten meist innerhalb von 3 Tagen
Dieses Issue hat noch niemand übernommen.
Bewertung
- Schwierigkeit
- 4/5
- Geschätzter Aufwand
- 3-5 Tage
- Anfängerfreundlichkeit
- 50/100
Rechercherichtung
Read src/handlers/online.rs, especially the RPC branch after the Electrum and Esplora handling, and compare how stop_gap is consumed by each backend. Run the linked regtest reproduction to confirm the external-index failure and inspect the wallet lookahead context described in the issue. Done means RPC scans no longer silently miss these funds, or clearly warn and document the limitation.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Beschreibung
Environment: bdk-cli 4.0.0 from crates.io (tag v4.0.0, git 5b3cb00, built with --features rpc), bdk_wallet 3.2.0, bdk_chain 0.23.3, bdk_bitcoind_rpc 0.22.0, Bitcoin Core v31.1.0, regtest, macOS arm64
What happens
Restoring a wpkh() descriptor exported from Bitcoin Core and running full_scan with --client-type rpc does not find funds received at external index 25 or higher when no lower index has been used. The command exits with status 0, prints "Full scan completed successfully." and reports a zero balance. Passing --scan-stop-gap 100 does not change the result, even though full_scan --help documents that flag without noting that it has no effect with --client-type rpc.
| Funded external index (only) | Core getbalance |
bdk-cli balance |
|---|---|---|
| 24 | 1.00000000 | 100000000 sat |
| 25 | 1.00000000 | 0 |
| 30 | 1.00000000 | 0 |
30 with --scan-stop-gap 100 |
1.00000000 | 0 |
bdk-cli's own event output shows the chain was fully walked in every case ("Chain tip advanced from height 0 to …"), but a "Transaction … confirmed" event appears only for index 24.
Expected behavior
Either the funds are found when --scan-stop-gap is raised (as the help text suggests), or the CLI warns that the flag has no effect with --client-type rpc.
Why (from reading the v4.0.0 source)
In src/handlers/online.rs, stop_gap is passed to the Electrum (L123) and Esplora (L134) clients, but the RPC branch (L141+) walks blocks with Emitter and never reads it. Detection then depends on the keychain lookahead (DEFAULT_LOOKAHEAD = 25 in bdk_chain 0.23.3). bdk_wallet already exposes a lookahead() parameter for this, but bdk-cli does not use or expose it.
Related library-level context: bitcoindevkit/bdk_wallet#83, where it was noted that lookahead and stop_gap "should be fixed together". This report is about the CLI surface: the flag is accepted but has no effect with RPC, and there is no way to raise the lookahead from the CLI.
Why it matters
Bitcoin Core wallets pre-derive 1000 keys by default (DEFAULT_KEYPOOL_SIZE), so funds past index 24 are plausible. A user restoring such a backup with bdk-cli over RPC sees a successful scan and a zero balance.
Possible fixes (maintainers' call)
- Pass
--scan-stop-gapthrough as the wallet lookahead for block-based backends, or add a--lookaheadoption. - Warn or error when
--scan-stop-gapis passed with--client-type rpc. - Document the behavior.
Reproduction: self-contained regtest script and logs: https://gist.github.com/devdavidejesus/25b34cb7d2735f04791800c12b21d59d
- Vorherrschende Sprache
- Rust
- Sterne
- 142
- Forks
- 99
- Ø Merge
- 5 T. 21 Std.
- Gemergte PRs (30 T.)
- 4
Entwicklungsumgebung
Erste Schritte
- Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
- Forken Sie das Repository und arbeiten Sie in einem Branch.
- Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.
Mehr aus bitcoindevkit/bdk-cli
-
enhancement
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 72/100
bitcoindevkit/bdk-cli#332 · 2 Kommentare ·
Maintainer antworten meist innerhalb von 3 Tagen
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 65/100
bitcoindevkit/bdk-cli#330 ·
Maintainer antworten meist innerhalb von 3 Tagen
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 76/100
bitcoindevkit/bdk-cli#318 ·
Maintainer antworten meist innerhalb von 3 Tagen
-
Enforce Core-compatible OP_RETURN / datacarrier and standard tx-size limits in create_txEvtl. vergeben @tvpeter hat das vor 3 Tagen übernommen. Offenenhancement
bitcoindevkit/bdk-cli#339 · 1 zugewiesene Person ·
Maintainer antworten meist innerhalb von 3 Tagen
-
Schwierigkeit 4/5 3-5 Tage Anfängerfreundlichkeit 48/100
bitcoindevkit/bdk-cli#338 ·
Maintainer antworten meist innerhalb von 3 Tagen
Alle Issues in bitcoindevkit/bdk-cli
Ähnliche Issues
-
type/bug
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 68/100
stackabletech/kafka-operator#1033 · 1 Kommentar ·
Maintainer antworten meist innerhalb von 1 Tag
-
bug good first issue needs testing
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 84/100
Maintainer antworten meist innerhalb von 1 Tag
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 68/100
Maintainer antworten meist innerhalb von 3 Tagen
-
docs: release notes v3.7.0–v3.8.0 footer links to README/CHANGELOG are broken after docs reorgOffen
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 90/100
farion1231/cc-switch#7744 · 1 Kommentar ·
Maintainer antworten meist innerhalb von 1 Tag
-
datafusion
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 76/100
apache/iceberg-rust#3297 ·
Maintainer antworten meist innerhalb von 1 Tag