The attack is still on.

Nobody is celebrating Bitcoin Independence Day today, huh? Understandable, but sad. If I was a state attacker, that’s probably what I’d do to destroy moral. 🤔

👀

THEY KNEW!!!

You should all thank Peter RekTodd.

Do not sell your CC to this a-hole or anyone else. Or throw it away. It might be the only way to prove you held your coins in a law-suit.

btw these two losers don’t deserve to be in this picture or the article since they were against BIP-148. Remember, to convince you that BIP-110 has failed, they need to erase/change the history. Doing a good job so far.

Happy Bitcoin Independence Day! Do you even know what we celebrate today as a community? Do you care? Anyway, you may find this article enlightening and worthy of preserving in case the history revisionists try to bury it: https://braiins.com/blog/3-year-anniversary-bip148-uasf

Do you know who else was lazy? And arrogant when presented with criticism? Nvk and his CC crew. Do you even have a CC? If yes, then I admire your stone cold attitude. If not, you’re just a troll and a waste of time. Or an idiot.

🤷‍♂️

Ocean mined block 110 themselves. That’s poetic! 😆

Some even speculated that the bug was introduced when they close sourced the firmware after Foundation guys forked it off.

You’re all watching the wrong NGU.

FFS

The attacker used RBF to steal the coins from CC users who were trying to move them off to a different address. I think a total of 34 bitcoin were stolen this way. So far. CC users are in a very bad place right now. They can’t export the bad seeds on another device. And they are at risk to move their UTXOs to another seed/device bc the attacker can intercept them with RBF while awaiting confirmation on chain.

Good question.

TL;dr:

Don’t know, will try to find

Sending you some funds, brb, stay safe

TL;DR: Peter RekTodd created both the problem and the solution. 1) technical advisor for CC since 2014 2) pushed for full RBF since 2013, now enabled by default on all nodes (users’ and miners’) 3) enabled (probably unwillingly) the full RBF attack exploited by the CC hacker and philosophically justified the solution for it (outbound services like Slipstream) 4) even if you disable RBF manually you’re still vulnerable to the attack because the whole network enforces it by default We should have ousted this FED at least 10 years ago! This human trash should be handcuffed along with NVK if you ask me.