Closed wain1 closed 5 months ago
2024-04-19 01:19:23.651 [INF] CHAN: Adding orphan block 0000000000000000000222ec7fc8e0c1416f585de8032125f2c90027da5b632c with parent 00000000000000000000f76969754849032684136a89c15d70317dbe40dc752e 2024-04-19 01:19:26.373 [INF] SYNC: Rejected block 000000000000000000003be2016de9a4d591307534b208326f1a06d208942c52 from 120.79.71.72:8333 (outbound): previous block 000000000000000000003e52a967334cbd9becc911620af4b64dcbcb141b1c4d is known to be invalid
Which version are you on? Can you give further logs for when this started to happen?
We've fixed this issue in the latest rc tag: https://github.com/btcsuite/btcd/issues/2090
Which version are you on? Can you give further logs for when this started to happen?
We've fixed this issue in the latest rc tag: #2090
btcd version 0.24.0-beta
What should I do now?
Sir,I should have a synchronization problem after this block: 000000000000000000005bd85abbabf227d2632a7c9f1ea663c1b5c0e06f2522
Looks like the re-org issue we fixed (image above is from https://fork.observer/), you'll need to resync the chain for now. We're looking into some RPCs to help out the older nodes that had this issue.
The block has been synchronized to the latest height, but when using rpc to query the block height and hash, a block from 12 hours ago is returned. What is the problem? My system is win11, and the configuration file only adds nodes. , no other operations are performed