<p>Because nobody has implemented a feature to deal with this rare situation. There is nothing fundamentally hard about it; it just doesn't exist.</p>

CC BY-SA 4.0
2024-05-18T21:13:43.770Z
Actually, according to [this](https://bitcoin.stackexchange.com/a/74614/4334), there is [PR#10794](https://github.com/bitcoin/bitcoin/pull/10794) (or the more recent RPC command [`getblockfrompeer`](https://bitcoincore.org/en/doc/27.0.0/rpc/blockchain/getblockfrompeer/), [#20295](https://github.com/bitcoin/bitcoin/pull/20295)), which does somewhat what I'm looking for.
Geremia
CC BY-SA 4.0
2024-05-18T20:50:36.383Z
2024-05-18T20:50:36.383Z
Pieter Wuille
<p>If I have corrupt or missing blocks but good a chainstate, why do I need to re-download entire chain? Why doesn't it just re-download the needed blocks?</p>

<bitcoin-core><synchronization><pruning><reindex>
If I have corrupt/missing blocks but good a chainstate, why do I need to re-download entire chain?
Geremia
# If I have corrupt/missing blocks but good a chainstate, why do I need to re-download entire chain?

(Asked by: username_0 on 2024-05-18)

If I have corrupt or missing blocks but good a chainstate, why do I need to re-download entire chain? Why doesn't it just re-download the needed blocks?

**Tags:** bitcoin-core, synchronization, pruning, reindex


---

## 1 answers

### Answer by username_1 on 2024-05-18. Score: 2

Because nobody has implemented a feature to deal with this rare situation. There is nothing fundamentally hard about it; it just doesn't exist.

> **Comments:**
> **username_0**: Actually, according to [this](https://bitcoin.stackexchange.com/a/74614/4334), there is [PR#10794](https://github.com/bitcoin/bitcoin/pull/10794) (or the more recent RPC command [`getblockfrompeer`](https://bitcoincore.org/en/doc/27.0.0/rpc/blockchain/getblockfrompeer/), [#20295](https://github.com/bitcoin/bitcoin/pull/20295)), which does somewhat what I'm looking for.  

---

