With the SDK team of Aragon One we have been working on a new initiative in the last couple of weeks. We went through the process of discovery, initiative formation, and experimentation. Now we have a better understanding of the current problem, user personas, and pain points we are dealing with.
The next step is to scope and start shaping the new tool. Before continue we want to gather feedback from the community and potential users about the direction we are going and to validate if our assumptions are correct.
You can follow the current development efforts in this Github repo: aragon/plumbery
We put our thoughts in the following Notion document: Toolkit API design
The document has comments allowed to have an open discussion, your feedback is really important to shape the future of this new tooling.
If you can’t go through the whole document following is a summary.
Aragon is seeing a level of experimentation that the Aragon Client has not been able to fully address. Developers want to create their own front-end interfaces, access to the organization data (permissions, apps), and handlers for organizations’ logic (transaction path, radspec, evmscripts). This document aims to explain the motivations for these use cases, and the design of a node SDK to address the existing limitations. On top of the node SDK we will create a React hooks API
Note both Toolkit and Plumbery are codenames until we decided on a naming convention. Suggestions are welcome