full_scan over RPC ignores --scan-stop-gap: restored wallet silently misses funds at external index >= 25
Los mantenedores suelen responder en 3 días
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 50/100
Línea de trabajo
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.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
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
- Lenguaje dominante
- Rust
- Estrellas
- 142
- Forks
- 99
- Merge medio
- 4 d 1 h
- PR fusionados (30 d)
- 3
Preparar el entorno
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de bitcoindevkit/bdk-cli
-
enhancement
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
bitcoindevkit/bdk-cli#332 · 2 comentarios ·
Los mantenedores suelen responder en 3 días
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
bitcoindevkit/bdk-cli#330 ·
Los mantenedores suelen responder en 3 días
-
Crate chacha20 0.10.1 is yankedAbierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
bitcoindevkit/bdk-cli#318 ·
Los mantenedores suelen responder en 3 días
-
Enforce Core-compatible OP_RETURN / datacarrier and standard tx-size limits in create_txPosiblemente ocupada @tvpeter la tomó hace 2 días. Abiertoenhancement
bitcoindevkit/bdk-cli#339 · 1 asignado ·
Los mantenedores suelen responder en 3 días
-
Dificultad 4/5 3-5 días Aptitud para principiantes 48/100
bitcoindevkit/bdk-cli#338 ·
Los mantenedores suelen responder en 3 días
Todos los issues de bitcoindevkit/bdk-cli
Issues similares
-
area: dogs area: lookout bug security
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
Los mantenedores suelen responder en 1 día
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 92/100
Los mantenedores suelen responder en 2 días
-
documentation
Dificultad 2/5 1-3 horas Aptitud para principiantes 84/100
OpenDevicePartnership/ina4230#31 ·
Los mantenedores suelen responder en 1 día
-
area:breg criticality:p3 documentation triage:needs-implementation
Dificultad 1/5 Menos de una hora Aptitud para principiantes 86/100
registrystack/registry-stack#1713 ·
Los mantenedores suelen responder en 1 día
-
Rename CLAUDE.md to AGENTS.mdAbierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
posit-dev/ggsql#565 · 1 reacción ·
Los mantenedores suelen responder en 1 día