Rebuilds local block/index state from available block data according to the node's implementation.
Wallet rescan and blockchain reindex address different layers and should not be conflated.
Actual corruption recovery requires controlled failure experiments on a disposable node and exact release.
| Area | Finding | Status |
|---|---|---|
| Reindex concept | Reindex is a local reconstruction operation based on available blockchain data; it should not be described as a universal database repair mechanism. | Architecture |
| Chain validation | Recovered blocks still have to satisfy the node's consensus validation rules. | Consensus boundary |
| UTXO rebuild | Rebuilding spendable state is distinct from rebuilding a block index. | Architecture |
| Wallet rescan | A wallet rescan is a wallet-layer operation and is separate from chainstate recovery. | Architecture |
| VTA command behavior | Exact reindex/recovery flags and their historical behavior require a release-pinned VTA Core source/manual check. | Needs source pin |
| Crash recovery | No controlled interruption during block/UTXO updates was performed. | Not measured |
| Database corruption | No deliberate corruption test or low-level database repair was performed. | Not measured |
| Reference-node comparison | A proper recovery test should compare tip, block metadata and selected UTXO state against a clean reference node. | Test method |
1. Use a disposable VTA Core node. 2. Preserve a clean reference copy. 3. Record tip, block index and wallet state. 4. Stop the node cleanly. 5. Create a controlled damaged-copy scenario. 6. Test reindex/recovery on the copy only. 7. Verify chain tip and block metadata. 8. Verify UTXO state against the clean reference. 9. Test wallet rescan separately. 10. Record runtime, errors and recovered state. 11. Repeat with a simulated interrupted shutdown. 12. Do not use the experiment on the only production wallet/data copy.
wallet.dat and private-key material offline and backed up before any destructive experiment.