bitcoin: corrupted data

Is there an existing issue for this?

  • I have searched the existing issues

Current behaviour

The only peer (via connect=IP in bitcoin.conf) is another local node running aba504759caa version and that node has 94 other peers at the moment so I guess there is no problem there.

I do not know if it is related, but since I run aba504759caa (the testnet4 commit) also for mainnet, here is link to testnet4: https://github.com/bitcoin/bitcoin/pull/29775

Expected behaviour

Synchronization of all the blocks with the P2P Bitcoin network.

Steps to reproduce

Figuring that out. It all worked well for weeks with no change.

Relevant log output

2024-07-11T06:06:42Z UpdateTip: new best=000000000000000000036686ffd324b99fa90f190f48c7372e14738bda739383 height=851624 version=0x2462e000 log2_work=95.031625 tx=1038976733 date='2024-07-11T02:42:12Z' progress=0.999922 cache=17.2MiB(151149txo)
2024-07-11T06:06:42Z Leaving InitialBlockDownload (latching to false)
2024-07-11T06:06:42Z initload thread exit
2024-07-11T06:06:42Z Warning: not punishing manually connected peer 0!

How did you obtain Bitcoin Core

Compiled from source

What version of Bitcoin Core are you using?

v27.1.0 from bitcoincore.org

Operating system and version

Pop!_OS 22.04 LTS

Machine specifications

Linux x86_64

$ free -h
               total        used        free      shared  buff/cache   available
Mem:           7.6Gi       1.7Gi       461Mi       359Mi       5.5Gi       5.1Gi
Swap:          7.6Gi       985Mi       6.7Gi

Swap is zram

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Comments: 16 (5 by maintainers)

Most upvoted comments

You’ll have to enable at least the net debug log category to get some more details on the type of misbehaviour. (C.f. PeerManagerImpl::Misbehaving)