connect
connect copied to clipboard
aragon
(Aragon 1) Seamlessly integrate DAO functionality into web and node.js apps.
Currently we only use the `appId` in each app subgraph to determine a contract template. However, an app instance may actually go through multiple versions (e.g. as they did when...
The boilerplate should help a new developer to bootstrap: 1. A simple Aragon Connect custom front-end 2. Have `use-wallet` configured 3. Have GitHub pages already set up for easy deployments
Atm, our subgraphs need to use as script that reads an env variable with the access token. This shouldn't be necessary when `graph auth` is fixed. Submitted an issue in...
This is an advance provider that: >It uses a quorum and connects to multiple Providers as backends, each configured with a priority and a weight. Ethers API documentation: [FallbackProvider](https://docs.ethers.io/v5/api/providers/other/#FallbackProvider)
I think it could be nice to consider the `master` branch stable, and automate the build + version bump + npm publication using GitHub Actions. We could: - Have a...
The current utilities list are: https://github.com/aragon/connect/blob/master/packages/connect-core/src/utils/index.ts
Like the signing panel we have on the client, this would allow app authors to provide to their users an easy way to pick a transaction path.