Timeline for How to know contract functionality given only bytcode and address
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 23, 2022 at 2:36 | vote | accept | bioround | ||
| Apr 22, 2022 at 14:17 | comment | added | stam_a | ...As I understand it, the idea is that if you want other accounts to interact with your smart contract, you are strongly incentivized to share the source code in a standardized (i.e. human-friendly) form on the internet. It doesn’t matter if its through centralized or decentralized means since everyone can always check that it compiles to exactly what’s on the chain. This process is still completely trustless even though it's not directly written into the protocol. | |
| Apr 22, 2022 at 14:13 | comment | added | stam_a | I believe the ethereum protocol doesn’t not comment on this topic. That is not to say that the core contributors weren’t aware of it, as they definitely were. It simply wasn’t a design constraint of the protocol to provide a way for humans to understand the functionality of each smart contract. Although it doesn’t seem difficult to build a solution to this problem directly into the protocol, it wouldn’t be practical or necessary... | |
| Apr 22, 2022 at 0:32 | comment | added | bioround | Makes sense. If this is the case, how can anyone trust the behavior of smart contracts in a purely decentralized world? It seems the only way to trust a smart contract would be to obtain the source code and verify an exact bytecode match oneself. | |
| Apr 15, 2022 at 17:25 | review | Late answers | |||
| Apr 21, 2022 at 3:45 | |||||
| Apr 15, 2022 at 17:09 | history | edited | stam_a | CC BY-SA 4.0 |
deleted 133 characters in body
|
| S Apr 15, 2022 at 17:04 | review | First answers | |||
| Apr 20, 2022 at 9:16 | |||||
| S Apr 15, 2022 at 17:04 | history | answered | stam_a | CC BY-SA 4.0 |