3 ms·
A thing that you could do for smart contracts is have formal-methods analyzers that check properties that you care about in the contract. The analyzer can say,
by schoen 10y ago
A thing that you could do for smart contracts is have formal-methods analyzers that check properties that you care about in the contract. The analyzer can say, of a particular contract, "good", "bad", or "don't know". Then you can avoid (or even somehow ban?) contracts that get "bad" or "don't know".
Or, you could simplify things by having "bad" and "don't know" be in the same bucket! You could call it "can't be proven safe". Because of the halting problem issue, some safe contracts will always end up "can't be proven safe", but if the analyzer is good enough to allow for quite a lot of flexibility in the contracts, you can say that writing something that can't be proven safe is the contract author's fault or responsibility.
Then you can say that you will only use contracts that can be proven safe. There's no contradiction between this and Turing completeness or the halting problem, and there's no inherent reason to think that these contracts will be rare or hard to find. You do have to be careful about what particular properties you're checking for in your definition of "safety", though!