3 ms·
Hm that seems to defeat the whole purpose of transparency and trustlessness? What is the point of a contract whose contents I can't read? Who would "sign" (inte
by kkjjkgjjgg 5y ago
Hm that seems to defeat the whole purpose of transparency and trustlessness? What is the point of a contract whose contents I can't read? Who would "sign" (interact with) such a thing?
But others said the same, so it may be true. Perhaps for saving storage/bandwidth, and you can simply verify that it is the contract corresponding to some source code that has been published elsewhere?
- pests 5y agoEh, they exist. Not many people even know how to check the source or even if it's been verified. Saving bandwidth is definitely a reason. The EVM call to create the contract charges a gas fee per byte. Currently etherscan and other chain explorer sites will recompile your provided source (and compiler options) and ensure your deployed bytecode matches their results. If so they publicly provide the source and a nice verification checkbox. Some also give you (the public) tools to make read/write API calls to the contract directly by introspecting the API.
- pests 5y agoMost projects do opt in to transparency by verifying the source. Its up to you who you support.