Nov 19, 2018

It has something to do with config. But if bitcoind has not activated segwit I don’t think it should be relaying segwit txs.

Indeed, something weird is going on there. Anyhow, I'm probably going to need segwit activated in the near future, so it's best for me to leave it on and just figure out what's going wrong between libbitcoin-server and bitcoind. Any idea where my configs could be broken? My libbitcoin-server configuration is basically 1:1 with the one on the wiki.

Also tested with bitcoind v0.14.2 and v0.15.1 (user lastcanal reported that these versions worked correctly in https://github.com/libbitcoin/libbitcoin-server/issues/404) and the result was the same - libbitcoin-server starts rejecting all blocks after 431.

Dunno, but the config issue could be internal (not exposed to the config file) in v3. See chain_state constants.

Are you referring to the ones in include/bitcoin/bitcoin/constants.hpp? The bip9 checkpoints? The block hash and height seem correctly set to the genesis block 🤔

Thanks a million!

No, thank you! You should create a github incident so I can link the patch back to you.

Assuming it works 🙂

Will do!

Hmm, that didn’t seem to fix it. Getting the same errors at the same block heights 😕

Oh, nevermind. Had the easy_blocks setting enabled 😄

Looks like it’s working! Thanks again 👍

Great, thanks for the confirmation.