1/ After looking deeper into this issue, there is *enormous cause for concern* as the entity in question on the Bitcoin Cash blockchain essentially has full control over the chain at this point in time. (thread)
2/ Skipping to the chase here, the address in question can be found here (Blockchair) = blockchair.com/bitcoin-cash/a… 
3/ For $BTC / $BCH , there is no 'attribution' in block headers.
We can make a very educated guess about who mined a given block from:
A) Address receiving 'coinbase' transaction [block reward]
and/or
B) Mining pools that sign blocks
We can make a very educated guess about who mined a given block from:
A) Address receiving 'coinbase' transaction [block reward]
and/or
B) Mining pools that sign blocks
4/ With the address in question that we're looking at (blockchair.com/bitcoin-cash/a…) , it has been the recipient of countless coinbase rewards, so its more than reasonable to suggest that whatever entity/entities its attached to = connected/working in unison
5/ Here's a quick look at some of the most recent TXs going into this wallet address (all transactions are coinbase rewards; 12.5 $BCH)
6/ What's concerning is not just the fact that this address is *dominating* in terms of % of blocks found/won, it is also finding blocks at an absurd rate.
Between 11 a.m. - 1 p.m. UTC today, this entity found 24 (TWENTY FOUR) blocks. That's absurd.
Between 11 a.m. - 1 p.m. UTC today, this entity found 24 (TWENTY FOUR) blocks. That's absurd.
6a/ $BCH has a different retargeting algorithm than $BTC (diff formula), but they are both still designed to manufacture adjusting difficulties that target a consistent 10-minute block time.
Thus, on average, there should be 6 blocks/hour found.
Thus, on average, there should be 6 blocks/hour found.
6b/ However, with this entity finding *24 blocks* in a 2-hour time span, it is not only beating out the entire network, its pretty much 'broken' the retargeting algorithm for $BCH. This is not good.
Attached is the documentation on diff retarg. for $BCH
github.com/bitcoincashorg…
Attached is the documentation on diff retarg. for $BCH
github.com/bitcoincashorg…
7/ Checking coin.dance, we can see that this entity (going as 'unknown' since they aren't signing any blocks) has won the last 8/14 blocks.
Between this entity & BTC.top, no one else has won a block on the protocol (besides BTCC) since block 606283
Between this entity & BTC.top, no one else has won a block on the protocol (besides BTCC) since block 606283
7a/ Perhaps the bigger issue here though is that on $BCH, block height 606283 occurred at 3:12 p.m (EST; GMT-4), which was an hour ago (to the minute).
Right now, $BCH is at block height 606304. So 21 blocks have been found in an hour.
Again, there's only supposed to be SIX.
Right now, $BCH is at block height 606304. So 21 blocks have been found in an hour.
Again, there's only supposed to be SIX.
8/ Spoke w Amaury Sechet & other devs in the $BCH ecosystem.
They are aware of the problem.
There's nothing that they can realistically do about the situation since its out of their hands.
They are aware of the problem.
There's nothing that they can realistically do about the situation since its out of their hands.
9/ It is strongly recommended that users *avoid transacting on or with $BCH at any and all costs* until this issue is resolved.
