Between foundry, ant pool, and those hashing on behalf of ant pool, lets assume they control 60-70% of the hash rate; they could exclude valid blocks from other miners and simply build on their last block in perpetuity.

The nodes would recognize the longest chain as the longest chain with the most work and the nodes would accept that chain as valid.

We assume the network would respond by moving hash, but it hasn't done so yet.

In short, I am not trying to make a technical argument. I'm simply identifying an issue that bothers me and hoping node runners and bitcoiners like yourself help to protect bitcoin.

Reply to this note

Please Login to reply.

Discussion

why haven't they switched their hash? because there is no problem... When one becomes apparent, switching pools is easy. And I do mine. With braiins pool. I also wrote a BIP, contributed to ecash and lightning.

I got you bro. We all want the same thing.

Thanks ocean. Thanks for building. For now, it’s just an “optics” problem. But fixing the issue now would be ideal. Fighting off a 60-70% attack in real time is not a road I want to go down.

An example from my area of expertise: It’s best to deal with your cardiovascular health with diet, exercise, meditation, proper sleep…

than to wait until you are actively have the heart attack.

Even if you survive the heart attack, the damage is done and the heart is never the same.