Post
Topic
Board Speculation
Re: Wall Observer BTC/USD - Bitcoin price movement tracking & discussion
by
allstolennnnn
on 01/08/2017, 21:13:30 UTC


faulty code




so what do people make of this?

{
"height" : 478559,
"hash" : "000000000000000000651ef99cb9fcbe0dadde1d424bd9f15ff20136191a5eec",
},
{
"height" : 478559,
"hash" : "00000000000000000019f112ec0a9982926f1258cdcc558dd7c3b7e5dc7fa148",
},


https://blockchair.com/bitcoin-cash/block/000000000000000000651ef99cb9fcbe0dadde1d424bd9f15ff20136191a5eec

https://tradeblock.com/bitcoin/block/478559
Hmm funny I did some experiments with that Bitcoin Clash Daemon but it seems the oversize Block doesn't get accepted on the abc daemon as well...

2017-08-01 18:29:27 ERROR: TestBlockValidity: Consensus::CheckBlock: bad-txns-oversize, Coinbase check failed (txid 1f5132b4722a9dec48092f6b9490594df3676cd0c6322f6ceb0c1812cbb851b2)  (code 16)


Who's coding that thing ? Roger himself ? Smiley
Saw this on another thread:


Quote
Quote
BCH Mempool is 1.6Mbytes, so it's over the 1M threshold to trigger the fork when the block is found.

THE FUN PART:

Bcc forked at wrong block. No full mempool.
That means their code is faulty and will continue to fork
 or they did some offline trick to make "orphan" to continue their own chain.

Trick or fail, that can be only solved after their first block.




Is that true?