-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Aragon Vote Rewards JSON #3
Comments
Issue Status: 1. Open 2. Started 3. Submitted 4. Done This issue now has a funding of 2500.0 USDC (2500000000000000.0 USD @ $1.0/USDC) attached to it.
|
Could you define "Rewards JSON" please? Thanks! |
@blockchain-nz it should be an extra json property in the already existing connect-voting |
Issue Status: 1. Open 2. Started 3. Submitted 4. Done Workers have applied to start work. These users each claimed they can complete the work by 2 days, 7 hours from now. 1) pmlambert has applied to start work (Funders only: approve worker | reject worker). DAO Global Hackathon Contribution Learn more on the Gitcoin Issue Details page. |
Hi. |
Hello @DeepDAO2 and @githubdoramon! I just posted a PR addressing this issue. |
@DeepDAO2 @githubdoramon https://thegraph.com/hosted-service/subgraph/pmlambert/aragon-voting?selected=playground It has queries directly for script executions and rewards for all votes, or listing them by vote. |
Issue Status: 1. Open 2. Started 3. Submitted 4. Done Work for 2500.0 USDC (2500.00 USD @ $1.0/USDC) has been submitted by:
|
Rewards Object
The current version of Aragon Connect doesn't specify the proposal rewards in a detailed format that can be parsed by code. For this bounty please create a vote_rewards JSON, as specified in the technical requirements below.
Technical Requirements
The Rewards JSON will include the specifics of each token, and token value requested as part of the Vote.
For example if the person creating the Vote requests 1000 ANT and 500 USDC. The Rewards JSON object will specify each token's address, symbol, and monetary value.
If the Vote is for the execution of code and not directly a monetary reward, the Rewards JSON would specify the contract address, and function name.
If the Vote doesn't directly ask for a monetary reward, or the execution of code, the Rewards object will be null.
A fully realized submission will apply for all existing, and future Votes on Aragon V1. A minimal implementation will include only rewards on future Votes.
Submission
Provide a PR on the Connect Github with the fix.
Judging Criteria
The judges are members of the DeepDAO and Aragon technical teams.
DeepDAO
Website
Discord
Twitter
The text was updated successfully, but these errors were encountered: