👨‍💻 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:

• Issue a GM Credential from a button click, after wallet is connected
• Issue a Contribution Credential after submitting a form/airtable, after wallet is connected.
• Issue a DarkModePref for selecting Dark/Light mode in an app, after wallet is connected.
• Issue a GM credential to any recipient using a form for the wallet address

Encourage all ideas and creativity! You can use something like web3.js, or the WAGMI frontend library to grab the address.

Example Javascript Request:

var myHeaders = new Headers();
myHeaders.append("Content-Type", "application/json");
myHeaders.append("Authorization", "Bearer <redacted>");

var raw = JSON.stringify({
  "schemaUrl": "https://raw.githubusercontent.com/discoxyz/disco-schemas/main/json/GMCredential/1-0-0.json",
  "subjectData": {},
  "recipientDID": "did:ethr:0xE6FF2d91f6EeEe8BDA4bCc562d63c431496FCf2A"
});

var requestOptions = {
  method: 'POST',
  headers: myHeaders,
  body: raw,
  redirect: 'follow'
};

fetch("http://api.disco.xyz/v1/credential/", requestOptions)
  .then(response => response.text())
  .then(result => console.log(result))
  .catch(error => console.log('error', error));

disco-access-controls

Potential File Structure

integrations/disco
├─ actions/
│  ├─ get-credentials-from-did.ts
│  ├─ get-profile-from-address-simple.ts
│  ├─ get-profile-from-address.ts
├─ components/
│  ├─ disco-profile-basic.tsx
│  ├─ disco-profile-credentials.tsx
├─ handlers/ NEW FOLDER
│  ├─ use-verifiable-credentials-access-controls-route.ts
│  ├─ use-verifiable-credentials-access-controls-page.ts
├─ hooks/
│  ├─ use-disco-get-credentials-from-did.ts
│  ├─ use-disco-get-profile-from-address.ts
│  ├─ use-disco-get-profile-from-did.ts
├─ routes/
│  ├─ route-credentials-from-did.ts
│  ├─ route-disco-profile-from-address.ts
│  ├─ route-disco-profile-from-did.ts
├─ disco-client.ts
├─ README.md

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.

👨‍💻 User Story

As a developer I want to protect pages and api routes using decentralized identity and verifiable credentials.

More specifically I want to use Disco's API services as the access controls systems for protecting my applications resources.

Have question?

Join the ⚡️TurboETH Discord channel

💰 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 create page and api handlers to enable access controls using decentralized identity and verifiable credentials.

Required Functionality:

1. Server Side Rendered (SSR) page gating using Official Disconaut Credential
2. API gating using Official Disconaut Credential

How It Could Work:

1. The handlers use the disco-client to request user's public verifiable credentials.
2. If the authenticated account has an "Official Disconaut Verifiable Credential"

Developer Tasks:

• Create Route handler - useVerifiableCredentialsAccessControlsRoute(...args)
• Create Page handler - useVerifiableCredentialsAccessControlsPage(...args)

The handlers should be similar to the lib/server.ts methods that wrap withIronSessionApiRoute and withIronSessionSsr so authenticated user sessions can be accessed.

import { withIronSessionApiRoute, withIronSessionSsr } from 'iron-session/next'

import { NextApiHandler } from 'next'

import { SERVER_SESSION_SETTINGS } from './session'

export function withSessionRoute(handler: NextApiHandler) {
  return withIronSessionApiRoute(handler, SERVER_SESSION_SETTINGS)
}

export function withSessionPage(handler: any) {
  return withIronSessionSsr(handler, SERVER_SESSION_SETTINGS)
}

Potential File Structure

integrations/disco
├─ actions/
│  ├─ get-credentials-from-did.ts
│  ├─ get-profile-from-address-simple.ts
│  ├─ get-profile-from-address.ts
├─ components/
│  ├─ disco-profile-basic.tsx
│  ├─ disco-profile-credentials.tsx
├─ handlers/ NEW FOLDER
│  ├─ use-verifiable-credentials-access-controls-route.ts
│  ├─ use-verifiable-credentials-access-controls-page.ts
├─ hooks/
│  ├─ use-disco-get-credentials-from-did.ts
│  ├─ use-disco-get-profile-from-address.ts
│  ├─ use-disco-get-profile-from-did.ts
├─ routes/
│  ├─ route-credentials-from-did.ts
│  ├─ route-disco-profile-from-address.ts
│  ├─ route-disco-profile-from-did.ts
├─ disco-client.ts
├─ README.md

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.

Resources

• 🪩 Disco
  • Information - https://disco.xyz/
  • Documentation - https://docs.disco.xyz/
• ⚡️ TurboETH
  • Documentation - http://docs.turboeth.xyz