2

Newb question. I have just started running btcsuite/btcd. After spending a couple days initializing the blockchain it no longer appears to be writing new blocks. btcctl getblockcount reports 828835 which today (2024-02-05) is about 36 hours behind.

The logs seem to show valid activity

2024-02-05 21:16:48.101 [INF] SYNC: New valid peer 209.222.252.235:30340 (inbound) (/Bitcoin ABC:0.14.6(EB8.0)/)
2024-02-05 21:16:50.996 [INF] SYNC: Lost peer 207.154.205.24:57960 (inbound)
2024-02-05 21:16:50.996 [INF] SYNC: Syncing to block height 829096 from peer 69.4.94.226:8333
2024-02-05 21:16:51.769 [INF] SYNC: Rejected block 0000000000000000000202b00ad6c08ae74632e1355c7919e1b0ef34d6c93361 from 69.4.94.226:8333 (outbound): previous block 00000000000000000002af7f6d56ec5a25f7e8f6772b1c5e0ed6c74af94b7e87 is known to be invalid
2024-02-05 21:16:51.832 [INF] CHAN: Adding orphan block 000000000000000000024ef5fe9fa06e137c4194468485e053b5cbbf54adaec8 with parent 00000000000000000000e0fd16374c0b72e7827b1625bb3f5d4476bf8caafcda

Checking the database file directory reveals the issue as well:

root@meta-01:/data/btcd-data/data/mainnet/blocks_ffldb# ls -lt  | head
total 533918380
drwxr-xr-x 2 root root   1892352 Feb  5 13:18 metadata
-rw-r--r-- 1 root root 285130543 Feb  3 21:41 000001019.fdb
-rw-r--r-- 1 root root 536651991 Feb  3 21:38 000001018.fdb
-rw-r--r-- 1 root root 536626098 Feb  3 21:33 000001017.fdb

Anyone know what might be causing this? Is my server off on some dead-end fork? Can I roll the chain back to the "last good block?"

2
  • 1
    Are you running a pruned btcd node? I reported a similar problem with my pruned (monitoring) node in github.com/btcsuite/btcd/issues/2121
    – 0xb10c
    Feb 16 at 13:37
  • Nope. This happens immediately after a full IBD.
    – r1ky
    Feb 28 at 17:00

1 Answer 1

0
2024-02-05 21:16:51.769 [INF] SYNC: Rejected block 0000000000000000000202b00ad6c08ae74632e1355c7919e1b0ef34d6c93361 from 69.4.94.226:8333 (outbound): previous block 00000000000000000002af7f6d56ec5a25f7e8f6772b1c5e0ed6c74af94b7e87 is known to be invalid

Looks like the software you use incorrectly implements the Bitcoin consensus rules: it treated block 00000000000000000002af7f6d56ec5a25f7e8f6772b1c5e0ed6c74af94b7e87 as invalid although it's perfectly valid.

Alternative Bitcoin clients have tried, and failed, to correctly re-implement Bitcoin consensus rules since its inception. I'd recommend using Bitcoin Core instead.

5
  • Surprisingly forkmonitor didn't detect this: forkmonitor.info/nodes/btc. Feb 6 at 15:39
  • Maybe just a hardware failure. @r1ky what are you running this node on? Feb 6 at 15:57
  • Thanks for your reply sir. I'm running btcd in a Docker container running alpine:3.16. I'm a bit of a Go nerd so had an initial interest in running btcd since at least I have some hope of understanding the code. I've restarted from scratch and will resist restarting the server as I did in my first kick at the can. Will see if I get stuck on the same block and report back...
    – r1ky
    Feb 7 at 4:24
  • I've now tried both v0.23.3 and v0.24.0. Both exhibit the same behavior. After about 36h of IBD I catch up to the head of chain. And then syncing just stops and block count freezes. As I mentioned earlier - the logs show the same issue: ``` 2024-02-10 16:45:43.516 [INF] SYNC: Rejected block 00000000000000000003b3480ed47cd0d435069efcc1eccdbcd84629a9e912ae from 47.63.181.85:8333 (outbound): previous block 00000000000000000001a9931d3181dcad10319187e0b668fc2db0f8dff656c9 is known to be invalid ```
    – r1ky
    Feb 10 at 16:51
  • Weird. I see you've commented on an issue at BTCD. Feel free to edit my answer or add another answer once you've gotten an answer from them. (For the lurkers: github.com/btcsuite/btcd/issues/2090). Feb 11 at 15:27

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.