News for hackers. Stuff that matters.
Re:Deconstructing the DAO Attack: A Brief Code Tour by tmalsburg2 on Saturday June 18, 2016 @10:32AM (#11928771)
One solution might be to design a safe language that compiles to the the language used in Ethereum. Not sure if possible within the given constraints.
Re:Deconstructing the DAO Attack: A Brief Code Tour by krapp on Saturday June 18, 2016 @10:43AM (#11928823)
Wouldn't it be better to just rewrite everything in that safe language and abandon whatever Ethereum is written in?
Re:Deconstructing the DAO Attack: A Brief Code Tour by tmalsburg2 on Saturday June 18, 2016 @10:51AM (#11928855)
Sure, but many people are so deeply invested in Etherum that I doubt that it's going to happen. But perhaps there will be a competing system.
Re:Deconstructing the DAO Attack: A Brief Code Tour by jacquesm on Saturday June 18, 2016 @11:37AM (#11929048)
The only person who is currently really deeply invested is the hacker. The rest, not so much.
Re:Deconstructing the DAO Attack: A Brief Code Tour by wildlogic on Saturday June 18, 2016 @12:09PM (#11929182)
Hah.
Re:Deconstructing the DAO Attack: A Brief Code Tour by eudox on Saturday June 18, 2016 @10:36AM (#11928790)
The problem then becomes ensuring that only code compiled from that language can run.
Re:Deconstructing the DAO Attack: A Brief Code Tour by tmalsburg2 on Saturday June 18, 2016 @10:38AM (#11928802)
Just let people use whatever they want. Those who write unsafe contracts will get bitten but that's ok.
Re:Deconstructing the DAO Attack: A Brief Code Tour by dangero on Saturday June 18, 2016 @11:16AM (#11928962)
Seems like this option is now invalid since the devs have now shown their unwillingness to let their pet contracts 'get bitten'.
Re:Deconstructing the DAO Attack: A Brief Code Tour by Atwood on Saturday June 18, 2016 @11:18AM (#11928973)
ПРЕДУПРЕЖДЕНИЕ! ^objects in mirror are larger than they appear.