Is there an existing issue for this?
- I have searched the existing issues
Current behaviour
running 30.1 and just noticed the entire blockchain on ssd went from having the entire 800gb+ synced to only having 6 .dat files after recently updating. bitcoin.conf has not had any prune setting configured.
excerpts of note from debug log
2026-01-05T03:13:12Z Prune configured to target 953 MiB on disk for block and undo files. 2026-01-05T03:13:18Z Loading block index db: last block file = 5324 2026-01-05T03:13:18Z Loading block index db: last block file info: CBlockFileInfo(blocks=89, size=132165834, heights=930862…930950, time=2026-01-04…2026-01-05) 2026-01-05T03:13:18Z Checking all blk files are present… 2026-01-05T03:13:18Z Loading block index db: Block files have previously been pruned 2026-01-05T03:13:20Z Initializing chainstate Chainstate [ibd] @ height -1 (null)
2026-01-05T03:13:21Z Block index and chainstate loaded 2026-01-05T03:13:21Z init message: Pruning blockstore… 2026-01-05T03:13:21Z block tree size = 930952 2026-01-05T03:13:21Z nBestHeight = 930950
unusual outputs after connecting another instance of bitcoin gui on another local network computer and directly connecting via 192.168.1.210:8333 which i did use a prune setting on bitcoin.conf as i just wanted to sync the wallet. i first noticed the oddity as it wouldnt sync and did not label the full node it was connecting to as a full relay
2026-01-05T03:48:30Z [ipc:info] {bitcoin-node-9205/b-capnp-loop-9209} IPC server destroy N2mp11ProxyServerIN3ipc5capnp8messages13BlockTemplateEEE 2026-01-05T03:48:30Z [ipc:info] {bitcoin-node-9205/b-capnp-loop-9209} IPC server destroy N2mp11ProxyServerIN3ipc5capnp8messages13BlockTemplateEEE 2026-01-05T03:48:30Z [ipc:info] {bitcoin-node-9205/b-capnp-loop-9209} IPC server destroy N2mp11ProxyServerIN3ipc5capnp8messages13BlockTemplateEEE 2026-01-05T03:48:30Z [ipc:info] {bitcoin-node-9205/b-capnp-loop-9209} IPC server destroy N2mp11ProxyServerIN3ipc5capnp8messages13BlockTemplateEEE
i am running a stratum 2 protocol mining pool so could possibly be coming from that but it is operating without any errors.
Expected behaviour
to not prune the blockchain
Steps to reproduce
not sure
Relevant log output
No response
How did you obtain Bitcoin Core
Pre-built binaries
What version of Bitcoin Core are you using?
30.1
Operating system and version
arm linux
Machine specifications
radxa rock 5b+ armbian debian 13
edit- found issue, i opened the gui and entered a prune value. after immediately closing it added the value to the settings.json file and pruned the blockchain after running the daemon via command line. that setting value should not easily prune the blockchain without confirmation. should be more steps in place to prevent that from happening.