Author

Topic: [testnet] Are there some block propagation or segmentation issues on testnet? (Read 420 times)

newbie
Activity: 13
Merit: 1
Ok, figured it out.
The segwit parts of my blocks were wrong, so most nodes would reject them.

However, there seem to be some old nodes that accept erroneous blocks like that (being unaware of these parts thanks to backwards compatibility), including that block explorer, but they don't propagate into the more up-to-date part of the network.
That's where the impression of segmentation came from.

I eventually stumbled onto a node that gave me a proper reject message (bad-witness-nonce-size), and it all clarified from there.
newbie
Activity: 13
Merit: 1
I've been trying to mine the Bitcoin testnet (for fun/education) with some obsolete HW, and after about 6 mined block the picture is always the same: The block is accepted and propagated by the nodes i can reach, show up on https://testnet.blockexplorer.com/blocks , but never show up on https://www.blocktrail.com/tBTC

Some time later, new blocks appear at the same height on then blocktrail side, and eventually my block gets orphaned.
Thing is, it's never even in the orphaned list on blocktrail, which makes me wonder if there is some propagation issues.

The blocks from the blocktrail side make it to blockexplorer side, but any block i submit on the blockexplorer never makes it to the blocktrail side.

I've tried to gather getaddr replies from many nodes, and then connected to about 50 live nodes out of the list, all of which would receive the block i mined.
However, it still won't show up in any shape or form on blocktrail side.

I'm confused about what is going on over there.
Jump to: