This tweet did not age well. The guy who wrote this? His buggy code was committed into Mirror Protocol in June 2021, creating a hole that allowed an attacker to drain $88m from users just a few months later. https://github.com/Mirror-Protocol/mirror-contracts/commit/56c79bafa7b2f7693653d5144e2e3aab93673695#diff-61e7453301fdb7fea66099c942a799658950c63013da0257f88b9541d30a877fR182 …https://twitter.com/csanti_95/status/1492130389254893574 …
-
-
Oh not saying it’s not ‘his fault’ - or anyone’s. But feels a bit more witch-hunty than needed. The fault falls on TfL and their processes as a whole. Doesn’t require tagging an old tweet. It’s not like this tweet is some kind of hubris like the Do ones.
-
It sounds like an inexperienced dev being excited about their work and to look out. Pretty sure 99% of people would post something similar. Idk, just seems unnecessary to me?
- Show replies
New conversation -
-
-
@hackenclub@buda_kyiv@cer_live How can audits be standardized to avoid this kind of behavior? Token standards exist, so what about smart contract coding standards somehow to enable automated auditing. Sounds impossible when writing it, but something is deffo needed


-
This is crucial question for the industry. We have analyzed which authority can be the standard issuer and conclusion is http://caia.org we launched the work in this direction. It will take around 1 year
- Show replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
