r/btc•
timepad

To the black-hats: your attack has failed, but thank you. Thank you for proving that BCH is worth attacking. Thank you for making BCH stronger and more anti-fragile.

I appears that some entity with malevolent intent exploited a mempool-validation bug present in ABC at the exact time of the scheduled hard-fork. The intent of this attack is clear: cause maximum damage to BCH, and attempt to discredit all hard-forks by making it look like hard-forks cause chaos.

It's worth re-iterating: the exploit had nothing to do with the hard-fork. The attackers simply sat on an old vulnerability for months, waiting to exploit it at the same time as the hard-fork.

This exploit required expertise to discover. Whoever was behind this attack is either a security researcher themselves, or they've hired security researchers. This type of expertise isn't cheap.

Regardless of how well-funded this attack was, it has proven to be an abysmal failure. Within hours, miners have patched their nodes, and the network is operating normally again. In the end, BCH is now only stronger.

Posted May 15, 2019, 4:18 PM UTC

14541
Rikreadit•

What doesn't kill you makes you stronger. Bitcoin (=BCH) survived everything.

29
meta96•

Best dev.

7
MobTwo•

Regardless of how well-funded this attack was, it has proven to be an abysmal failure. Within hours, miners have patched their nodes, and the network is operating normally again. In the end, BCH is now only stronger.

Bitcoin Cash winning again, where's egon when you need his presence, lol.

25
effgee•

Is he on vacation? Haven't seen his posts for 2 days or so..

1
libertarian0x0•

"It's worth re-iterating: the exploit had nothing to do with the hard-fork."

Don't worry, maximalist will sell this as a forking failure.

20
[deleted]•

[deleted]

17
unitedstatian•

"It's worth re-iterating: the exploit had nothing to do with the hard-fork."

It's a punishment for daring to HF. Thou shalt not HF was the message of Blockstream and Coingeek.

7
spukkin•

worth noting that some SV miner was mining BCH for weeks leading up to just before the upgrade, possibly to dump just at the time of the upgrade.

9
[deleted]•

Which has yet to happen BTW, but note the artificial spike in SV even though there is virtually no organic trading volume

17
Ant-n•

Which has yet to happen BTW, but note the artificial spike in SV even though there is virtually no organic trading volume

Intersting, attack + BSV pump at the same time, suggest the attack came from SV.

Well thanks guy for your effort!

All you proved is BCH dev are very professional and reactive!

8
bUbUsHeD•

If you look at the volume around ~400 USD, somebody has set up a sell wall and dumped a fuckton of coins - half that volume pushed the price from 160 USD to 360 USD, which would put us somewhere at 900 USD now.

2
phillipsjk•

BEEPBOOP**

PARSE FAILURE.

3
unitedstatian•

When they move to economic grounds you know BCH isn't compromised.

2
horsebadlydrawn•

Yep, they showed their cards. Honestly I expected something better from them.

So I guess I'm pleasantly surprised.

4
RecalescenceCoins•

Honey badger doesn't something something...

2
pinkwar•

Why are empty blocks still being mined?

1
[deleted]•

[deleted]

1
steelballs009•

The attack could have just started

-15
timepadOP•

The last 5 blocks all have plenty of transactions in them, so it looks like the mempool-validation exploit has been fixed by most miners.

16
[deleted]•

There's probably going to be a dump in price when the SV crew unload a bunch of freshly mined coins to pump SV, but it won't be sustained nearly like the November 2018 dump was

7
Liiivet•

Sounds like someone's short.

1
[deleted]•

I don't short BCH, just calling it like I see it

3
Ant-n•

Say the new account with 5 comment history:)

Good luck with your effort!

3
PaidSockPuppetRedditor for less than 60 days•

I guess this is going to be the new narrative. Always projecting the blame outwards. So let's roll with that assumption; that it was an outside job. What does that say about the QA setup of BCH, that someone else knows the code better than the actual devs?

-30
spukkin•

btc chain has had some pretty serious bugs, including one that was discovered and then responsibly disclosed by a bch dev. i think that ultimately reflects favorably on bch dev community. also, btc next block tx fee: $4.21/ bch next block tx fee $0.0019 .

19
PaidSockPuppetRedditor for less than 60 days•

Sure, bugs happen, but like I said, since the narrative is to blame someone else for exploiting a bug. Maybe it's more productive to look at how to improve and learn from it.

-14
spukkin•

agreed. perhaps a more equal distribution of alternate node implementations run by miners would help. maybe big miners and pools would have incentive to run a diverse selection of node software if they knew it would harden the network against such attacks and protect the value of their holdings.

10
PaidSockPuppetRedditor for less than 60 days•

maybe big miners and pools would have incentive to run a diverse selection of node software if they knew it would harden the network against such attacks and protect the value of their holdings.

Very good point.

-3†
Ant-n•

Sure, bugs happen, but like I said, since the narrative is to blame someone else for exploiting a bug.

?

Obviously the bug was exploited by someone else than the ABC dev?

What wrong in saying that?

5
PaidSockPuppetRedditor for less than 60 days•

Exploited, or just encountered during normal operation?

1
Liiivet•

No bug ever existed in code before this moment, right?

Loser.

13
PaidSockPuppetRedditor for less than 60 days•

Whaaaat? Do you know what a non-sequitur is? See your reply.

-9
HoolanderRedditor for less than 60 days•

Do you know what an asswipe is? Look in the mirror for further details.

2
redmoonrisesRedditor for less than 60 days•

I take a big PaidSockPuppet every morning

1
PaidSockPuppetRedditor for less than 60 days•

All you got is ad-homs. Tell your parents I said "Hi".

1
mtrycz•

One thing is having a (fairly innocuous) bug in one implementation.

Another is an exploit attack right at the time of the protocol hard fork.

3