Interaction

• [ ] What's the pattern we are going to offer to the users to install some disputable apps?

  Facu: I think we should have an installation guide explaining how to install the Delay app or the Disputable Voting app (experimental) using the installer tool from 1Hive or aragon CLI.

• [ ] Do we need to enforce some particular structure for the Agreement content or are we fine with a simple IPFS link?

• [ ] Should challengers use the staking pool to deposit their collateral and/or receive rewards?

• [ ] Should we allow addresses other than the submitters to create a dispute? Brett: Especially in the case of the long-lived Registry app, it is a large responsibility if the submitter account always has to be responsive to a challenge

• [ ] Notifications (email / etc)

  • What do we want to support? Should we re-use the existing client notification service?

Design

• [ ] How will we display token balance oracles?

  Brett: I think this should be a separate step we consider later, for adding better ACLOracle support into the client

• [ ] Should we have a banner to announce the agreement app in the client?

• [x] Do we need to handle multi-action transaction paths?

  Given the current designs (2020-07-01), we will be able to describe these in the modal

Frontend

• [ ] What would be the simplest way to show agreements text diffs?
• [ ] How will version history work? Perhaps just viewing the content diff?
• [ ] Show Agreements in App Center?
• [ ] Show Agreements in Permissions?

Implementation unclear:

• [ ] Designs for Signing Modal include "more advanced" details for forwarding paths (better descriptions, more details about durations, etc.)—we will need more metadata published with the disputable app
• [ ] "Draft" feature may be very difficult to implement