-
Notifications
You must be signed in to change notification settings - Fork 6
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
Bounty: Use Programmatic Issuance to issue a Verifiable Credential via Disco API - USDC $400 #5
Comments
Hi @ericc572 I am interested |
@visitskyworld feel free to fork this repo, then tag this issue and send it to us in the #dev-lounge channel in Discord! here's an invite: https://discord.gg/sRVntFGf |
Is anyone still working on this issue? @visitskyworld @ericc572 |
The issue was already assigned I think @SouravInsights |
Assigned to you or somebody else? |
somebody else |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
π¨βπ» User Story
As a developer I want to issue a Disco credential via the Disco API, based on some event, or button-click.
π° Bounty Reward
The bounty reward is $400 USDC, 50 OP tokens and a TurboETH DevPass digital collectible.
Sponsored by Disco and District Labs.
𧱠Project
Using the Disco API, issue a credential to an ETH address using the following endpoint:
POST https://api.disco.xyz/v1/credential
List of schemas can be found here: http://github.com/discoxyz/disco-schemas
Example Ideas:
Encourage all ideas and creativity! You can use something like web3.js, or the WAGMI frontend library to grab the address.
Example Javascript Request:
disco-access-controls
Potential File Structure
Notice
The final integration may not resemble the proposed integration - that's O.K - a natural part of software development.
During development you might discover an original hypothesis doesn't make sense. No problem. Make a comment and clearly explain why a new approach is better than old one. Get rewarded for thinking out of the box.
The final bounty reward can be increased to match new bounty tasks.
The text was updated successfully, but these errors were encountered: