News for hackers. Stuff that matters.
Re:Deconstructing the DAO Attack: A Brief Code Tour by revelation on Saturday June 18, 2016 @08:55AM (#11928375)
What a shitshow. These people don't need "advanced static analysis tools" [1], they need a big old bag of clue.

1: Developers, cryptographers and computer scientists should note that any high-level tools (including IDEs, formal verification, debuggers, symbolic execution) that make it easy to write safe smart contracts on Ethereum are prime candidates for DevGrants, Blockchain Labs grants and String’s autonomous finance grants.

Re:Deconstructing the DAO Attack: A Brief Code Tour by ethbro on Saturday June 18, 2016 @10:37AM (#11928795)
OpenSSL had some code cruft too, and god knows that didn't stop it from being deployed in production. People use code because it works, not code that's perfect.
Re:Deconstructing the DAO Attack: A Brief Code Tour by kartickv on Saturday June 18, 2016 @11:22PM (#11931662)
That's not good enough for software that's meant to be money. Besides, OpenSSL has the excuse of being old. Why would you design a new system to be crufty from day one?
Re:Deconstructing the DAO Attack: A Brief Code Tour by ethbro on Sunday June 19, 2016 @09:08AM (#11932833)
I wouldn't design any system to be crufty or have bugs. I was just pointing out that it happens. And honestly probably gives us a lot cooler stuff than were software production restricted to developers who were certified to produce best practices code.

I feel like without weird blood we'd only ever get enterprise-approved spreadsheet software.

PS: Caveat. Personally, of course I'd never use stuff like that for mission critical deployments until it's been battle tested.