Smart contracts on the blockchain are compiled. Is there any system in place to verify all the public dapp contracts do what they propose to be doing?
i.e. this could be done by compiling open-source contracts and verifying contract hash signatures, or in the case of closed-source but public d-apps, potentially decompiling compiled byte code and verifying code paths/function calls, although this is much murkier territory.
See for example https://etherscan.io/address/0xf97e0a5b616dffc913e72455fde9ea8bbe946a2b#code which is the CryptoKitties "gene combination" algorithm. Whilst the rest of CryptoKitties is open-source, this particular code module is closed-source. It has however been reverse engineered - here's a blog post about it, https://firstname.lastname@example.org/cryptokitties-mixgenes-function-69207883fc80. Whilst this is a small code function, there appears to be the possibility that a dapp could launch, proposing and appearing at first glance to be open-source, but in fact containing a hidden time-bomb, e.g. to transfer the balance of Ether to a bad actor's account on a hardcoded future date.
Do we need some framework or service was set up by which all published smart contract code can be validated to some degree?