design
design copied to clipboard
aragon
Agent app
Forum thread with spec and user stories: https://forum.aragon.org/t/actor-app-arbitrary-actions-from-daos.
The Transfer tab is missing but it could be the same panel from the Finance app without the reference field (actually the reference field could be added if we want to).
Some quick wireframes with the idea I have in mind:
This view shows the actions the app has performed to external contracts, and the change in assets if the action resulted in the actor app gaining or losing tokens:
This view would show all the asset transfers of the actor app, that either happen as the result of an action or direct deposit/withdrawals:
The panel for submitting a new action:
As I mention in the image, we may not know what the ABI for the contract is and we may have to ask the user for the ABI (a long JSON array) of the contract or for them to input the function signature they want to call (e.g. transfer(address to, uint256 amount) this is not strictly the signature but it is better as it has the param names).
I wonder if there is value in the distinction (and seperation in the UI) of Actions and Assets. It seems like you show asset transfers in the Actions list anyways.
There are actions that cause transfers so there is some duplication there, but actions sometimes don't perform a transfer, and transfers can have no action associated with them (basic deposit/withdrawal)
Forgot to link this here:
Invision prototype and discussion
https://forum.aragon.org/t/agent-app-ui-ideas/582/2
