Hacker News Reader

You will have to define "safe", but in general things like infinite loops are effectively bound by the amount of gas provided. Mistakes are still expensive, and it is easy to get the code wrong (the DAO hack and quadrigacx screw up this week are obvious examples), but the network itself is fairly stable, which is priority number one.

View on HN

Is there an analysis/post-mortem on the QuadrigaCX snafu anywhere? I would be very interested in reading a detailed account of exactly what went wrong.

Here's their comment:

https://www.reddit.com/r/ethereum/comments/6ettq5/statement_...

Also, it's normal practice for a contract to throw an exception if ETH is sent to any function that doesn't know how to deal with it. This includes the "fallback function," which is what runs if no other function in the contract is called. With recent versions of Solidity, this throw is built in, unless you mark a function "payable." But they were using an older contract, and there was no protection built into their fallback, and that's what made them vulnerable to this issue in the first place.

Reply on news.ycombinator.com