Nov 16, 2018

Hi again guys, I’m having more block rejection issues on regtest. libbitcoin-server stops publishing blocks/transactions after it gets a block that it rejects with Rejected block [block hash] from [127.0.0.1:28333] transaction inputs or outputs empty I had to fetch the block using bitcoin-cli, since v3 of libbitcoin-explorer doesn’t have the fetch-block command. After this block gets rejected by libbitcoin-server, it gets stuck in an Ask [127.0.0.1:28333] for headers after [block hash] loop. This happens every night, while my regtest is running (I have a script that generates transactions and auto-mines blocks using bitcoind RPCs). From what I’ve seen, this always happens at a different block height (always below 500). Is this another segwit issue? Does bitcoind switch some bip on after a certain block height or # of transactions? Has anyone encountered this before?