5 ms·
Yes, you shouldn't change the terms of a contract after the fact, so you only need to think of all possible use cases of the smart contract in advance, test for
by briatx 8y ago
Yes, you shouldn't change the terms of a contract after the fact, so you only need to think of all possible use cases of the smart contract in advance, test for all edge cases, and then write flawless code in a minefield infested language like Solidity (a feat that its own creator couldn't accomplish).
Since this isn't very likely, it strongly implies the smart contract model isn't a good one for writing software.
- davidgerard 8y agoWe previously learnt this with database triggers and stored procedures, where pretty much everyone with experience says "DON'T DO THIS!" It turns out commingling your program with your data is an obfuscation, debugging and maintenance nightmare, and you should almost always keep the program manipulating your data separate from the data. And that's before the ridiculous idea of making the program super-hard or even impossible to fix bugs in.
- earlz 8y agoDon't forget, you also need to make sure your code will never break [1] by an Ethereum blockchain upgrade or security fix too. [1]: https://www.reddit.com/r/ethereum/comments/57ork1/ive_made_a_list_of_contracts_which_will_be_100/ https://www.reddit.com/r/ethereum/comments/57ork1/ive_made_a...