Fully validated AssumeUTXO starts revalidating after restart #32029
Description
After fully validating the recent update to AssumeUTXO until 880k in the background:
2025-03-08T09:58:19Z UpdateTip: new best=00000000000000000001b5d3d95fe8153004c0a8e4f5fbd08e4fead4298897ff height=886840 version=0x246ea000 log2_work=95.483816 tx=1163409635 date='2025-03-08T09:58:50Z' progress=1.000000 cache=136.3MiB(966526txo)
2025-03-08T10:00:03Z [background validation] UpdateTip: new best=0000000000000000000159629ce4f039b1ec8287b2942acd13b1bde150343c2c height=878000 version=0x20306000 log2_work=95.369968 tx=1140089747 date='2025-01-05T22:13:51Z' progress=0.969631 cache=4287.4MiB(28845142txo)
2025-03-08T10:01:05Z New block-relay-only v2 peer connected: version: 70016, blocks=886840, peer=179
2025-03-08T10:13:17Z New block-relay-only v1 peer connected: version: 70016, blocks=886840, peer=180
2025-03-08T10:13:25Z [background validation] UpdateTip: new best=000000000000000000010b17283c3c400507969a9c2afd1dcf2082ec5cca2880 height=880000 version=0x268be000 log2_work=95.396383 tx=1145604538 date='2025-01-20T01:42:23Z' progress=0.976559 cache=5145.5MiB(35241631txo)
2025-03-08T10:13:25Z [warning] Flushing large (5 GiB) UTXO set to disk, it may take several minutes
2025-03-08T10:17:26Z [snapshot] computing UTXO stats for background chainstate to validate snapshot - this could take a few minutes
*2025-03-08T10:32:23Z [snapshot] snapshot beginning at 000000000000000000010b17283c3c400507969a9c2afd1dcf2082ec5cca2880 has been fully validated*
2025-03-08T10:32:23Z [snapshot] allocating all cache to the snapshot chainstate
2025-03-08T10:32:23Z Opening LevelDB in ~/bitcoin/chainstate_snapshot
2025-03-08T10:32:23Z Opened LevelDB successfully
2025-03-08T10:32:23Z Using obfuscation key for ~/bitcoin/chainstate_snapshot: 67720f7b17c65cc7
2025-03-08T10:32:23Z [Chainstate [snapshot] @ height 886840 (00000000000000000001b5d3d95fe8153004c0a8e4f5fbd08e4fead4298897ff)] resized coinsdb cache to 8.0 MiB
2025-03-08T10:32:23Z [Chainstate [snapshot] @ height 886840 (00000000000000000001b5d3d95fe8153004c0a8e4f5fbd08e4fead4298897ff)] resized coinstip cache to 9990.0 MiB
2025-03-08T10:32:23Z [snapshot] re-enabling NODE_NETWORK services
2025-03-08T10:32:23Z [snapshot] restarting indexes
2025-03-08T10:32:23Z Flushed fee estimates to fee_estimates.dat.
2025-03-08T10:32:23Z Saw new header hash=000000000000000000012962b376caa8878516abce31ca476e569e70fb7fb964 height=886841
[...]
2025-03-08T10:49:53Z UpdateTip: new best=0000000000000000000069aed813954edef3972f9c8ee36632f3113a72dad42b height=886849 version=0x20400000 log2_work=95.483928 tx=1163418786 date='2025-03-08T10:49:44Z' progress=1.000000 cache=140.5MiB(1002553txo)
2025-03-08T10:50:10Z tor: Thread interrupt
2025-03-08T10:50:10Z torcontrol thread exit
2025-03-08T10:50:10Z addcon thread exit
2025-03-08T10:50:10Z opencon thread exit
2025-03-08T10:50:10Z Shutdown: In progress...
2025-03-08T10:50:11Z net thread exit
2025-03-08T10:50:11Z msghand thread exit
2025-03-08T10:50:11Z DumpAnchors: Flush 2 outbound block-relay-only peer addresses to anchors.dat started
2025-03-08T10:50:11Z DumpAnchors: Flush 2 outbound block-relay-only peer addresses to anchors.dat completed (0.00s)
2025-03-08T10:50:11Z scheduler thread exit
2025-03-08T10:50:11Z Writing 2481 mempool transactions to file...
2025-03-08T10:50:12Z Writing 0 unbroadcast transactions to file.
2025-03-08T10:50:12Z Dumped mempool: 0.003s to copy, 0.890s to dump, 37229324 bytes dumped to file
2025-03-08T10:50:12Z Flushed fee estimates to fee_estimates.dat.
2025-03-08T10:50:16Z Shutdown: doneWhen I restart the node, it seems to retrigger the snapshot validation:
[...]
2025-03-10T23:07:38Z init message: Loading block index…
2025-03-10T23:07:38Z Assuming ancestors of block 00000000000000000001b658dd1120e82e66d2790811f89ede9742ada3ed6d77 have valid signatures.
2025-03-10T23:07:38Z Setting nMinimumChainWork=0000000000000000000000000000000000000000b1f3b93b65b16d035a82be84
2025-03-10T23:07:38Z [snapshot] detected active snapshot chainstate (~/bitcoin/chainstate_snapshot) - loading
2025-03-10T23:07:38Z [snapshot] switching active chainstate to Chainstate [snapshot] @ height -1 (null)
2025-03-10T23:07:47Z [snapshot] set m_chain_tx_count=1145604538 for 000000000000000000010b17283c3c400507969a9c2afd1dcf2082ec5cca2880
2025-03-10T23:07:53Z LoadBlockIndexDB: last block file = 4817
2025-03-10T23:07:53Z LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=53, size=92824607, heights=879796...879999, time=2025-01-18...2025-01-20)
2025-03-10T23:07:53Z Checking all blk files are present...
2025-03-10T23:08:00Z Initializing chainstate Chainstate [ibd] @ height -1 (null)
2025-03-10T23:08:00Z Opening LevelDB in ~/bitcoin/chainstate
2025-03-10T23:08:00Z Opened LevelDB successfully
2025-03-10T23:08:00Z Using obfuscation key for ~/bitcoin/chainstate: ab3f38a96955367d
2025-03-10T23:08:00Z Loaded best chain: hashBestChain=000000000000000000010b17283c3c400507969a9c2afd1dcf2082ec5cca2880 height=880000 date=2025-01-20T01:42:23Z progress=0.983528
2025-03-10T23:08:00Z Initializing chainstate Chainstate [snapshot] @ height -1 (null)
2025-03-10T23:08:00Z Opening LevelDB in ~/bitcoin/chainstate_snapshot
2025-03-10T23:08:00Z Opened LevelDB successfully
2025-03-10T23:08:00Z Using obfuscation key for ~/bitcoin/chainstate_snapshot: 67720f7b17c65cc7
2025-03-10T23:08:00Z Loaded best chain: hashBestChain=0000000000000000000069aed813954edef3972f9c8ee36632f3113a72dad42b height=886849 date=2025-03-08T10:49:44Z progress=0.999139
2025-03-10T23:08:00Z Opening LevelDB in ~/bitcoin/chainstate
2025-03-10T23:08:00Z Opened LevelDB successfully
2025-03-10T23:08:00Z Using obfuscation key for ~/bitcoin/chainstate: ab3f38a96955367d
2025-03-10T23:08:00Z [Chainstate [ibd] @ height 880000 (000000000000000000010b17283c3c400507969a9c2afd1dcf2082ec5cca2880)] resized coinsdb cache to 0.4 MiB
2025-03-10T23:08:00Z [Chainstate [ibd] @ height 880000 (000000000000000000010b17283c3c400507969a9c2afd1dcf2082ec5cca2880)] resized coinstip cache to 22.0 MiB
2025-03-10T23:08:00Z Opening LevelDB in ~/bitcoin/chainstate_snapshot
2025-03-10T23:08:00Z Opened LevelDB successfully
2025-03-10T23:08:00Z Using obfuscation key for ~/bitcoin/chainstate_snapshot: 67720f7b17c65cc7
2025-03-10T23:08:00Z [Chainstate [snapshot] @ height 886849 (0000000000000000000069aed813954edef3972f9c8ee36632f3113a72dad42b)] resized coinsdb cache to 7.6 MiB
2025-03-10T23:08:00Z [Chainstate [snapshot] @ height 886849 (0000000000000000000069aed813954edef3972f9c8ee36632f3113a72dad42b)] resized coinstip cache to 418.0 MiB
*2025-03-10T23:08:00Z [snapshot] computing UTXO stats for background chainstate to validate snapshot - this could take a few minutes*
[cancelled revalidation]
2025-03-10T23:08:08Z [error] UTXO snapshot failed to validate. Restart to resume normal initial block download, or try loading a different snapshot.
2025-03-10T23:08:08Z Shutdown: In progress...
2025-03-10T23:08:08Z scheduler thread exit
2025-03-10T23:08:08Z Flushed fee estimates to fee_estimates.dat.
Error: UTXO snapshot failed to validate. Restart to resume normal initial block download, or try loading a different snapshot.
2025-03-10T23:08:08Z Shutdown: done
Process finished with exit code 1This seems like an error, after fully validating it I would expect all traces of AssumeUTXO seeding to be gone.