3 ms·
Essentially this is the equivalent of a dev mistakely using an eval in the wrong place in a nodejs code. But all these articles are making it sound like the Eth
by heliumcraft 10y ago
Essentially this is the equivalent of a dev mistakely using an eval in the wrong place in a nodejs code. But all these articles are making it sound like the Ethereum team created the DAO and this issues affect Ethrereum as whole, which just isn't true.
- tremon 10y agoThe way I see it (continuing the simile): if you're writing something as critical as monetary transactions, everywhere is the wrong place to use eval in nodejs code. And when you're writing a dedicated language for monetary transactions, including eval in your API is just as wrong. The last part is why this issue affects all of ETH. Solidify is a new language, specifically designed for Ethereum. If the response to contract issues like this is "but that's a known failure mode, don't do that", then that signals a problem with the language, not just the contract code.
- stcredzero 10y agoIf the response to contract issues like this is "but that's a known failure mode, don't do that", then that signals a problem with the language, not just the contract code. It also signals a problem with the culture, with respect to the perceived amount of rigor required by the problem domain.