Summary of the problem you're solving, the impact and the approach to building a solution
0xbc4fb635636b81e60a4e356c4dceb53cac507d0300000084be038478000000000000000000000000c08fbc829a879470c15916aad14e85905e6ab90100000000000000000000000059a15718992a42082ab2306bc6cbd662958a178c2309a8cbbd5c3f18649f3b7ac47a0e7b99756c2ac146dda1ffc80d3f80827be6000000000000000000000000fbd0b2726070a9d6aff6d7216c9e9340eae68b2a
➡️
An app will be built to load a verified smart contract from any supported network. The app will allow to include a description for each smart contract function adding a fixed collateral for each.
To include a new function on the registry a cooldown period should elapse without being challenged. If the new entry is challenge will be raised to an arbitrator to resolve the dispute (e.g. Celeste).
At any point an entry could be challenged. If the dispute rule in favor of the challenger the entry will be removed from the registry.
Data fetching and user facing tooling will be created so developers can integrate descriptions and read from the registry.
Summary of what users are trying to accomplish.
Smart contract users want more contextual information when interacting with complex protocols.
DAOs want to describe votes that does complex actions.
Summary of the high level pains.
Lack of a standarized way to verify smart contract logicTransaction call data is crypted information for most usersDAOs need a transparent way to inform about vote actionsUser story format: As a user persona, I want goal so that some reason.