Programming for smart contract execution... What could go wrong?
Inverse Finance has top programming talent creating smart contracts to get rid of the human element to have 'perfect' contract execution so as to "....eliminate human error or manipulation of investor funds by placing decision-making power into the hands of an automated system and a crowdsourced process."
I have in my career designed hardware: motherboards, graphics cards, add on accelerators, SBC, and I have also programmed.. primitive operating systems.. programs...
I can tell you that I have never had a hardware bug or software bug. In telling you this I would be LYING... I have yet to see perfect hardware or code. There are ALWAYS ways that it can be AB/used to make things happen that one did not anticipate...
The more complex.. the more esoteric the potential problems.
We see that on CPU's with side channel attacks... CPU's designed by teams far more intelligent then myself...
It is only the arrogance of untested youth that can think something would be perfect and unbreakable.......
In the days when most programmers have no clue as to what is really going on in the 'machine', and they use high level foundations or classes/libraries..... they think it shall be perfect.
This smart contract concept is lovely.. but it gives me the willies... and makes me worry.. as the more complex the system... the harder it is to anticipate all the different AB/use cases. Sometimes a human is good as they can stop something that looks out of the ordinary....
I am truly worried about the future.. where young inexperienced programmers think the world can easily be replicated using logic... What about a bit error induced by a solar flare on the hardware? How do they manage a hardware error during the smart contract execution? ARRG ... enough for now... I feel old. I am old. Too old..