Derolytics (@Derolytics) profile picture

This is the end. DERO is DEAD. https://teapawt.net/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.
24
23
18
132
38,650
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
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
The second #DERO exploiter used public txs, so we know exactly how much he created. He did it in 4 separate rounds, each from a different starting wallet: Round 1: 2.38M Round 2: 3.17M Round 3: 8.18M Round 4: 10.23M Total created: almost 24M $DERO
1
2
715
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
2
4
10
3,042
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
Max supply was supposed to be 21M, but in reality it is now something between 40M and lets say 256M. It's impossible to know.
1
2
182
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
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
You don't need to explain to me how Dero works. We've spent probably hundreds of hours looking into all the on-chain data. Meanwhile you haven't even read the full evidence we provided. Your ignorance towards the real evidence shows you're not here in good faith.
1
51
Wrong. Already addressed that here: teapawt.net/Derolytics/status/2088…
Replying to @crazytown_1
Well, someone did it. Evidence is not in the proof strings at all - their unreliability is completely separate issue. Evidence is in the 781 transactions and 242 unique exchange accounts the 2.2M $DERO was laundered through. That's undisputable fact. teapawt.net/Derolytics/status/2088…
1
114
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
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
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
Replying to @AhMEdV_A
Attackers created dozen millions, maybe hundred millions, if not even billions $DERO. Cut your losses and move on. I already warned you 2 years ago when we found evidence of the first inflation exploit. Now the situation is 100x worse and you're still not listening.
1
2
334
Replying to @AhMEdV_A
I said "no". Meaning your number is wrong.
1
407
Replying to @AhMEdV_A
No. And no one will ever know what is the total inflated supply. Inflation transactions from first attacker cannot be deanonymized. Only the second attacker was clueless enough to use the old wallet with broken privacy.
1
128
Replying to @AhMEdV_A
It's over bro. Wake up. It's first item on this list of duplicate transactions. github.com/DEROFDN/derohe/bl…
1
203
Replying to @AhMEdV_A
TX hash: ab1da121afe17852ee24f19b836e602d3389b569048838223acd754247d7ff91 Proof: deroproof1qytw4qhkjddgazz0cmjx80grtggqywhyklrp3rfk4fegnmhcuxqyxqdzvfyyskpqzxc9ygawacskx6rzzgajn92hq9rhxw2mt7fc8zr6y0p9j07ax73ky4j4rvqqqqrhxshm2yq30qzwp Suit yourself.
2
1
183