@fridgebuzz.eth
There was discussion on X today about the “punk heist”, and this post brought up a good point about crypto’s exclusionary nature. (You need dev expertise to properly participate).
Which gives me an idea: what if contracts were treated like REST APIs? That is, documented in a machine-readable way (like OpenAPI specs).
Then users could access dashboards showing all the contracts they’ve interacted with (filtering required, obv), notify them of significant events (like the “shotgun” call in this punk heist), and give them a user-friendly UI with which to interact with the contracts in turn (in this case, to reject the shotgun proposal).
It’s not enough that Etherscan etc effectively let you call contract functions. Even for a dev, doing that’s pretty scary, and in this story, a small mistake caused unintended consequences. I think we can do better. What do you think?
https://x.com/pablorfraile/status/1834203109117014482?s=46&t=65SFOvn3rO_M3KVdAeCY4g