Derolytics (@Derolytics) profile picture

This is the end. DERO is DEAD. https://nitter.gq/t.co/NsRBaBenv8

Joined August 2024
Photo by Derolytics (@Derolytics)Photo by Derolytics (@Derolytics)Photo by Derolytics (@Derolytics)Photo by Derolytics (@Derolytics)Photo by Derolytics (@Derolytics)Photo by Derolytics (@Derolytics)Photo by Derolytics (@Derolytics)Photo by Derolytics (@Derolytics)Photo by Derolytics (@Derolytics)Photo by Derolytics (@Derolytics)
🚨 $8.3M CRYPTO HEIST EXPOSED 🚨 Evidence suggests Captain executed a sophisticated inflation exploit, creating 2,200,000 $DERO from nothing! Then systematically sold it over 2 years (Oct 2022-July 2024) while abandoning project entirely. This is the end. #DERO IS DEAD.
23
23
18
132
38,636
My last #DERO post ever, a final conclusion on the exploit: First attacker used private txs, so the inflated amount is unknown. But it's clear he did it 14x, up to 2^14 = 16,384x his balance. If he started with 64k $DERO (under $4000 then), he would create over 1 BILLION DERO!
6
3
4
10
3,041
A chain meant to have a max supply of 21M now has between 45 million and 1 billion $DERO in circulation. Possibly more. What a shitshow. Goodbye, #DERO cult. You won't be missed.
1
4
520
Addendum: Here are all relevant transactions as supporting data. Note that the value each deanonymized round ends at is sent to the final wallet, so you need to multiply that value by 2 to get the real final amount.
1
235
No $DERO was burned this way. Dozen millions of coins from recent inflation exploit are still present. Notice this transaction has type "NORMAL", not "BURN". Someone simply put number into a field that is normally unused. #DERO code is full of missing checks and bugs like that.
So 5M $DERO were burned from what we can see on this txid? explorer.dero-node.net/tx/80… How bad is the situation? What does this shit show even mean? Fascinating how hard this coin is fudded. $DERO #DERO
1
1
4
1,528
UPDATE: We've been told this is incorrect and the 5M $DERO in this payload were really burned, even though the transaction itself is not of type BURN_TX. I don't understand why would anyone write code that allows normal transfer to also burn coins, but here we are. DERO is DERO.
89
UPDATE: We've been told this is incorrect and the 5M $DERO in this payload were really burned, even though the transaction itself is not of type BURN_TX. I don't understand why would anyone write code that allows normal transfer to also burn coins, but here we are. DERO is DERO.
No $DERO was burned this way. Dozen millions of coins from recent inflation exploit are still present. Notice this transaction has type "NORMAL", not "BURN". Someone simply put number into a field that is normally unused. #DERO code is full of missing checks and bugs like that.
1
1
5
743
This is embarrassing 😳 but I think you deserve to know... Member of #DERO Foundation is downplaying the inflation exploit while SELLING HIS OWN $DERO like a champ! 😎 This is @notoriousjoshyb - still using old wallet. Did no one tell him whole chain was deanonymized before? 🐛
4
2
4
2,091
Apparently @elkryptoid was accused by an exchange of dumping millions - but his transactions can't be deanonymized, so we can't verify or disprove that on-chain. That's all for today 🍿
1
329
If I printed millions of $DERO (which I didn't), why would I keep warning you about it? Real attacker wants the price UP while quietly dumping on exchanges. Exactly what Captain did in 2022-24. So ask yourself: who's the one telling you everything's fine and to keep buying?
But now he was able to exploit a BUG and print enough coin to cause a major shock to confidence in the $Dero project. He succeeded in undermining the project, diminishing its importance, and diverting attention from it—all because of the captain and his escape.
3
1
2
1,038
The people who hate @Derolytics for uncovering the truth are the ones trying to take advantage of you. They need you to buy, so they can sell. They need you to be their exit liquidity. That's all you ever were to them.
2
179
"pull the chain please" 😀🍿 This wallet is possibly owned by attacker of the recent inflation exploit. 3 weeks ago he created this wallet and bought $DERO on Mindmesh Swap - just to register this username 15 days later.
1
3
660
Derolytics retweeted
What's your guess on the current $DERO supply?
2
2
2
640
Food for thought: If #DERO had never tried to be a privacy chain, it would never have suffered these inflation exploits (one in 2022, another in 2026). Or at least it wouldn't be in this fucked up state where you can no longer know what the real supply of $DERO actually is.
3
4
1,371
What's your guess on the current $DERO supply?
2
2
2
640
What do you #DERO cult members say now? Attacker casually minted 1.2M $DERO and sent it to exchange. It's still just a FUD, right? Good price to buy, right?
When $DERO devs found and fixed this double-spend exploit, they set hard-fork v3 to activate 7 days later, giving people time to upgrade their nodes. But by announcing it publicly, they tipped off a completely new attacker, who exploited it successfully shortly after!
1
1
3
8
3,330
When $DERO devs found and fixed this double-spend exploit, they set hard-fork v3 to activate 7 days later, giving people time to upgrade their nodes. But by announcing it publicly, they tipped off a completely new attacker, who exploited it successfully shortly after!
2
2
1
10
2,126
Instead of quickly reverting the chain to neutralize the double spends and limit the damage, they decided to leave the transactions and the newly minted coins on-chain. And on top of that, they effectively helped new attackers mint even more coins before HF3 activated! #DERO
1
2
533
Interestingly, this new attacker was pretty careless and used an old wallet with the privacy bug. This confirms there were at least two different attackers, but it also allows us to deanonymize some of these $DERO double-spend transactions. Anyone else having déjà vu?
2
2
489
Feels like I'm having déjà vu (or $DERO vu?) 😂 ⚠️ What we just found is probably worse than anything we've seen so far! ⚠️ How do #DERO devs always fuck this up so bad?
1
1
1
5
947