logoETHGlobal Paris

Next.ID & Mask Network



Dear Builders,

Mask Network brings privacy and benefits from Web3 to social media like Facebook & Twitter - with an open-sourced browser extension. Next.ID was initiated by the core team responsible for the development of Mask Network last year.

Next ID is an open-source protocol designed for developers to create and manage identities. The Next ID protocol acts as a secure conduit connecting various web2 and web3 identifiers, such as wallets, Twitter profiles, ENS names, Lens profiles, and more.

When a person's different identifiers are linked together, they form an identity graph, creating powerful, portable, and self-sovereign digital identities. We refer to these identities, digital representations of self, as avatars at Next ID.

You can find more information on our official site: https://Next.ID

Our GitHub page: https://github.com/NextDotID

We are here to help you overcome any challenges:

Join our Community Telegram Group for quick assistance: https://t.me/NextDotIDofficial

For any questions, feel free to send an email to developer@next.id

On this occasion, we have prepared a bounty of 10000 USD for you to explore and build upon. We look forward to seeing your innovative contributions!


1. Main Bounty: Total of 9,400 USD

Best Use of RelationService - Develop the Next-Gen Application with a Portable Universal Profile

Prize Pool

1st prize (max 1): $3k USD

2nd prize (max 2): $2k USD

3rd prize (max 3): $800 USD


Utilize the RelationService API (https://docs.next.id/relation-service/rs-graphql) to develop a use case that addresses market needs.

Strive to be as innovative as possible.

Recommended Use Cases (but not limited to):

Cross-Platform Profile Search and Recommendations

Get an understanding of what this involves and why it's useful by visiting web3.bio first.

For instance, consider linking a Twitter account with Mastodon using a DID.

Sybil Attack Resistance by Wallet History Verification

For instance, in a significant airdrop event, bot accounts controlled by a small group of people need to be filtered out, ensuring that each user claiming the airdrop is a legitimate individual user.

DAO (Decentralized Autonomous Organizations) Tooling

For instance, a DAO member's credentials can be made portable across different blockchain ecosystems.

For instance, when a new member joins, their existing social credentials can be immediately displayed, and different access levels can be provided based on their existing profile data.

Growth and Personalization

For instance, utilize a universal profile(Similar to this one: https://web3.bio/vitalik.eth) to identify potential user personas. Track social identities using wallet addresses and use this information to create look-alike audiences.

For instance, use a universal profile(Similar to this one: https://web3.bio/vitalik.eth) to solve the cold-start problem for apps. Allow users to invite their connections on Web2 by examining the wallet addresses they interact with.

Acceptance Criteria

Proof of Work: Submit either an open-source project published on GitHub for the judges to review, or if its business value necessitates confidentiality, share a private project repo address with us.

Relevance: Your use case should be pertinent and demonstrate a practical application of the RelationService feature within the DID protocol.

Protocol Compliance: Your use case must fully adhere to the DID protocol's specifications and accurately implement the RelationService feature.

Security: Your use case must prioritize data privacy and security. It should not introduce any security vulnerabilities.

Innovation: Creative or innovative applications of the RelationService feature are highly valued, even though not strictly required.

License Compliance: All submissions must be in accordance with the licensing terms of the open-source project.

2. Side Bounty: 600 USD

ProofService: Continue validation API


ProofService is a zero-trust identity relationship creation/query protocol. We have a reference implementation called proof_server.

The binding relationship between a web2 identity and ProofService's web3 identity (named Avatar) is done through cryptography signing and "Proof Post" mechanism.

Currently, if a user encounters a problem (e.g., client crashed / closed) submitting their proof post to the NextID server after posting it on target platform, NextID's process doesn’t allow the user to continue the process from this proof post with zero additional info.

We would like to add an API to allow users to restart the verification process from an existing proof post, without other info fetched from POST /v1/proof/payload.

From now, all info needed for restart validation procedure is included in the proof post itself (incl. signature, UUID, created_at timestamp, previous proof’s signature).

You need to create an API except only the proof post’s location, and recover the “site” only from proof post’s content, then continue validation and saving procedure just like a normal one.

Acceptance Criteria

An API (named by you), request with proof post’s location, platform and identity, response like POST /v1/proof .

Modify type IValidator interface , add a new function: Continue() (err error) for your core logic.

You can always use your own code structure design if you feel something is wrong.

Only one platform implemented is OK. Starting with validator/twitter is recommended.

Write test for your Continue() function and API.

Winner setting

Will accept only 1 winner, judged by code quality and function completeness

The sole winner will be rewarded with 600 USD


This workshop is happening in-person
Take Reputation Anywhere with DIDs and Universal Profiles
Time: 04:00 PM CEST – Jul 21, 2023
Location: Workshop Room 2

Getting Started