connect
connect copied to clipboard
aragon
(Aragon 1) Seamlessly integrate DAO functionality into web and node.js apps.
Quoting Brett: > And perhaps list which features they use in a table so someone can have a quick look to see which one is relevant? And myself: > We...
### Description Support transaction paths as mentioned in the [Agreement spec](https://www.notion.so/aragon/Agreement-v1-Architecture-1cf240b8791841189225318b7f3532f5#c7bebfe21c6840dcbc90009410fff25f). On a conceptual level, the current transaction pathing algorithm should be able to find transaction paths with a disputable...
The current Connect API logic only calculates the shortest Forwarding Path. But in many cases, we may want more flexibility to allow: - [ ] Calculate all existing Forwarding Paths...
This issue goes further into the details of what it takes to create a Forwarding Path description. The logic that we currently support was migrated from `aragon.js` and it's not...
This issue is to discuss and outline the scope of changes we may need to do to allow the app connector to add more details when sending transactions. - E.g....
Try to answer the question: What is the content of Repo? It is quite common. We should include new method `repoByName` that handle and parse a query in the lines...
Radspec descriptions are usually very _organization-specific_ (contextual to each individual organization). This would require https://github.com/aragon/radspec/issues/88, but we should expose a way for Connect users to declare any additional radspec descriptions...
Subgraphs in voting and tokens are using a slightly more sophisticated data source system which hasn't been applied in the main subgraph. E.g. compare manifest/templates in `connect-thegraph` and `connect-thegraph-tokens`. While...
I think this is non-trivial for Connect, because it requires app-level information (and even then it may be difficult due to the lack of explicit information in events or other...
See discussion https://github.com/aragon/connect/pull/165#discussion_r464553015