π¨ $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.
@sloger88 No, he wasn't buying more $DERO. He was selling his 1M dev fund to pay for all expenses, exchange listings, marketing, dev bounties... (as said by foundation)
He ended up with more DERO because he exploited similar bug back on Atlantis.
Read whole https://t.co/N5Bo8nty6i page.
π¨ $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.
@pssstmifren @illyrian_bloody@TheConnectoor@Pinkman_Zano Wrong. But feel free to provide your own proof for this TX then.
And then explain how those 2.2M $DERO left that otherwise empty wallet π
@illyrian_bloody@TheConnectoor@Pinkman_Zano You have it backwards. First was analysis and deanon of whole network -> that exposed the INFLATION EXPLOIT -> which required full Explorer to provide transparency. Without it you would have nothing.
If I knew this before, I wouldn't spent a minute on this project.
@pssstmifren @illyrian_bloody@TheConnectoor@Pinkman_Zano To make a deroproof, you must have right amount... Hmm. So what are you complaining about now, if the amount must be right?
The amount was -220000000181. Make a peace with reality.
@illyrian_bloody@TheConnectoor@Pinkman_Zano I suspect civilware fucked something up regarding compatibility with old TX proofs when they implemented their workaround for privacy fix.
Use original explorer by Captain to see how it should work properly, since the TX happened with original code too.
@illyrian_bloody@TheConnectoor@Pinkman_Zano Read the code and understand how the proofs and CBOR work, if you want to know what is wrong with your apparently modified version of the explorer.
There is no problem with official explorer on chakipu's server.
@illyrian_bloody@TheConnectoor@Pinkman_Zano If I had access to the inflation exploit, why wouldn't I "accumulate" Dero just by printing more of it from the thin air? While silently dumping it on market.
If you are just trolling, you can get right out of here.
@illyrian_bloody@TheConnectoor@Pinkman_Zano Because Derolytics Explorer provides proofs for all deanonymized TXs.
Also, if I was the exploiter then why the fuck would I warn everyone about it?
@whoopdeedoodero@chakipu Privacy bug allows us to deanonymize the TXs and find the shared key which was used to encrypt the payload. With that knowledge we can also generate the proof (which we also show on explorer).
Chakipu is lying here. All our proofs are correct and calculated in the same way.
@newworldbitcoin Isn't >$8M good reward for a few months (or year) of work? With a way to repeat it in a few years again.
He wasn't that greedy. So he let that 3M in his wallets just be there (which also provides plausible deniability), generating as much as he needed using the exploit instead.
@newworldbitcoin Exactly - real scammer would be greed AF. He wouldn't stop at 2.1M. He wouldn't be careful not to destroy whole project by dumping it all at once.
Captain likely planned to be away for few years, enjoying this money, and then get back with some new update as if nothing happened.
@joschobam You think it was some random attacker who decided to spend 2 years slowly liquidating the 2.2M coins to not drop $DERO price too much because he cared about the project?
Why would he stop at 2.2M? Why not 10M?
And why it coincides with Captain silently abandoning whole project?
Of course, you are free to think it wasn't the Captain who did it.
But that doesn't change the fact that $DERO is vulnerable to inflation exploit, which cannot even be detected anymore thanks to recent privacy fix.
This makes all coins worthless. Or as we say:
DERO is DEAD β οΈ
This all points to Captain being the perpetrator.
He already had automation in place for handling the swap. After unusually short swap period was over, he just modified his bot for this operation.
No random attacker would go through this long planning and extraction process.