The Solidity compiler stores the hash of contract metadata in the bytecode of each deployed contract. This metadata could be used to improve the confirmation dialog to display the natspec description, decode the function call arguments and display a link to the source code.
Details: https://chriseth.github.io/notes/talks/trust_gap_meetup

cc @frankiebee @rekmarks
0xD4D14e59F6a681dFe5a2E89e04ed7CcB1BBBd6c5
@chriseth 馃憢
Sorry for radio silence on my part regarding this, but I still think this is a fantastic feature. I lost my notes from when we talked at Devcon, but how can we move forward with this?
I'm currently implementing a proof-of-concept source code and metadata repository here: https://github.com/ethereum/source-verify/
Until this is done, I fear you cannot do much, unless you want to help out with that as well :)
We can of course also implement this in parallel, which would make it happen soon, but would also require a bit more coordination. If you want, we can schedule a call next week. Please contact me at [email protected]
Adding Christian's talk here, which may have enough info to extract this info?:
https://www.youtube.com/watch?v=_73OrDbpxoY
Adding @edisinovcic here who is working on the repository.
Let me know if I can help or answer questions that you may have.
Just I or both of us (@chriseth) can jump on a call with you and help you with this upgrade. :)
Joining your sync or something else.
Documentation is a bit scarce in this stage but we are actively working on it.
Trying to push this a bit forward: wonder if this could be possible with snaps (e.g. starting based on https://github.com/MetaMask/snaps-cli/tree/master/examples/recipient-address-auditor) - first just checking if the address is verified. As far as I see currently there is no way to augment the UI more as we would need here.
What is the state of snaps btw? Is there a RoadMap to launching them?