News for hackers. Stuff that matters.
Re:Critical Update on DAO Vulnerability by jchrisa on Friday June 17, 2016 @09:25AM (#11922481)
Maybe someone can write an insurance contract that future DAO authors can hire, as an alternative to interventions. It would have to be bug free.
Re:Critical Update on DAO Vulnerability by rspeer on Friday June 17, 2016 @02:18PM (#11924454)
Step 1: Write an insurance contract against the malicious use of Ethereum

Step 2: Find someone foolish enough to accept the other side of the insurance contract, in a world where "insurance fraud" is no excuse

Step 3: Use Ethereum maliciously, stealing your own Ether under another identity

Step 4: Collect insurance

Step 5: Profit (in Ether)

Step 6: Good luck turning your Ether into actual money when people figure out how broken everything about it is

Re:Critical Update on DAO Vulnerability by genmon on Friday June 17, 2016 @01:43PM (#11924195)
This is a smart response. The insurance company could also review the contract code in order to provide cover -- this would give investors extra confidence.
Re:Critical Update on DAO Vulnerability by vkou on Friday June 17, 2016 @02:26PM (#11924515)
Suppose that I want to make a medical device, and I want to get liability insurance for when a bug in its code administers a lethal dose of radiation to a patient.

Is there any extant insurance company that would want to review my code in exchange for a lower premium?

If not, why would one be willing to do this for a flash-in-the-pan cryptocurrency, but not a useful, real-world device?

Re:Critical Update on DAO Vulnerability by rabidferret on Saturday June 18, 2016 @01:14PM (#11929515)
For an insurance policy like that, they wouldn't offer any policy without auditing the device, including the code.
Re:Critical Update on DAO Vulnerability by will_brown on Friday June 17, 2016 @05:16PM (#11925608)
Re:Critical Update on DAO Vulnerability by ricksplat on Friday June 17, 2016 @11:36AM (#11923251)
Sounds like kernel space code.