Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Show the parameters for Agent Executions #1511

Open
MicahZoltu opened this issue Jul 31, 2020 · 0 comments
Open

Show the parameters for Agent Executions #1511

MicahZoltu opened this issue Jul 31, 2020 · 0 comments

Comments

@MicahZoltu
Copy link

Is your feature request related to a problem? Please describe.
When I submit a vote for my DAO to vote on, there is no easy way for them to validate that it is what I say it is. My DAO has mildly technically advanced users and I can give them a script to help validate the execution parameters match what they should, but at the moment they can't actually see or even find the vote details reasonably.

Describe the solution you'd like
When I submit an Agent execution/action for vote, the vote panel should include the contract being called, the function being called on that contract, and the parameters passed to that function. Ideally it would present them in a decoded form, but just making them available at all would be a huge step up from the current system.

Describe alternatives you've considered
The current work around (which is terrible) is to tell voters to go find the transaction on EtherScan and look at the transaction input, then compare the bytes at the end with the expected bytes of the function being called. This barely works for a highly technical audience, and it doesn't work at all for a non-technical audience without a huge amount of training and practice.

Additional context
To make this feature most reasonable, the canonical function signature should be included with the Agent execution transaction so it can be retrieved by future clients without having to resort to looking up function signatures in a database. A next-best option would be to have the UI lookup the signature in a database like 4byte.directory, though this is problematic for functions selectors that have multiple matching signatures.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant