Next.IDBangkok Identity Meetup
Next.ID hosted a panel discussion in Bangkok on 4th January 2023 where Web3 & identity thought leaders gathered to exchange ideas and discuss the concept behind Decentralized Identities (DID).Speaker InfoHannah Shen, Head of Growth @ Next.IDMax, CEO @ Port3Vincent, Partner @ AC CapitalKai, DID BuilderModerator: Yisi Liu, Initiator @ Next.IDYou may watch the full recording on YouTube: youtu.be/hdcOIXtUVEo?t=1373Concept and framing of the term “Decentralized Identity (DID)”. Why does it matter?...
Next.IDNext.ID Co-Hosted Web3 Social House at ETHDenver 2023
Imagine a week-long gathering that brings together brilliant minds from all over the world to create, innovate, and share ideas about the future of Web3. That’s what happened during ETHDenver’s BUIDL week in February 2023.Next.ID had the pleasure of participating in ETHDenver’s BUIDL week, where we co-hosted the Web3 Social House event alongside other innovative projects, to name a few: Mask Network, ChainBase, Firefly, and Collab.Land. Web3 Social House provided a platform for developers, en...
Your reliable DID infrastructure layer for all social dApps to build upon. We connect your Web2 & Web3 identities.
Next.IDBangkok Identity Meetup
Next.ID hosted a panel discussion in Bangkok on 4th January 2023 where Web3 & identity thought leaders gathered to exchange ideas and discuss the concept behind Decentralized Identities (DID).Speaker InfoHannah Shen, Head of Growth @ Next.IDMax, CEO @ Port3Vincent, Partner @ AC CapitalKai, DID BuilderModerator: Yisi Liu, Initiator @ Next.IDYou may watch the full recording on YouTube: youtu.be/hdcOIXtUVEo?t=1373Concept and framing of the term “Decentralized Identity (DID)”. Why does it matter?...
Next.IDNext.ID Co-Hosted Web3 Social House at ETHDenver 2023
Imagine a week-long gathering that brings together brilliant minds from all over the world to create, innovate, and share ideas about the future of Web3. That’s what happened during ETHDenver’s BUIDL week in February 2023.Next.ID had the pleasure of participating in ETHDenver’s BUIDL week, where we co-hosted the Web3 Social House event alongside other innovative projects, to name a few: Mask Network, ChainBase, Firefly, and Collab.Land. Web3 Social House provided a platform for developers, en...
Your reliable DID infrastructure layer for all social dApps to build upon. We connect your Web2 & Web3 identities.
Share Dialog
Share Dialog
Subscribe to Next.ID
Subscribe to Next.ID
<100 subscribers
<100 subscribers
How it works and how to contribute
NextID, as a decentralized identity service, aggregates the digital identities of web2 and web3 applications into an Avatar.
ProofService uses cryptographic public-private key pairs to verify and authenticate the user’s Avatar across their Web2 and Web3 accounts. Subsequently, allowing the user’s Avatar to establish a trusted and verifiable connection with the respective Web2/Web3 platforms.
To start off, the user signs the Avatar with his private key and publicly posts the signature on the platform that needs to be connected. This is called “Proof Post”.
The user will be required to send the “Proof Post” link back to ProofService, where the content of the link (Platform account, Wallet ID, Signature) is collected and verified. If the verification is successful, the connection is properly established.
These platform-bound identities (Avatars) are stored in a blockchain-like structure called ProofChain. Each Avatar is aggregated onto ProofChain and all data storage and modification of the ProofChain is recorded on Arweave. This ensures that all data is open, transparent, and publicly verifiable.
For more details, please refer to this documentation: https://docs.next.id/getting-started/quick-start
The example in the above documentation uses Twitter as an example, showing the process of generating an Avatar which consists of a public and private key pair, using an elliptic curve. After which, you will be required to generate a “Proof Post”, post it on Twitter, send the URL of the Twitter post to Proof Service, and finally successfully bind your Avatar to your Twitter account. This pretty much sums up the layman step-by-step process of binding your Avatar to your Twitter account.
How it works and how to contribute
NextID, as a decentralized identity service, aggregates the digital identities of web2 and web3 applications into an Avatar.
ProofService uses cryptographic public-private key pairs to verify and authenticate the user’s Avatar across their Web2 and Web3 accounts. Subsequently, allowing the user’s Avatar to establish a trusted and verifiable connection with the respective Web2/Web3 platforms.
To start off, the user signs the Avatar with his private key and publicly posts the signature on the platform that needs to be connected. This is called “Proof Post”.
The user will be required to send the “Proof Post” link back to ProofService, where the content of the link (Platform account, Wallet ID, Signature) is collected and verified. If the verification is successful, the connection is properly established.
These platform-bound identities (Avatars) are stored in a blockchain-like structure called ProofChain. Each Avatar is aggregated onto ProofChain and all data storage and modification of the ProofChain is recorded on Arweave. This ensures that all data is open, transparent, and publicly verifiable.
For more details, please refer to this documentation: https://docs.next.id/getting-started/quick-start
The example in the above documentation uses Twitter as an example, showing the process of generating an Avatar which consists of a public and private key pair, using an elliptic curve. After which, you will be required to generate a “Proof Post”, post it on Twitter, send the URL of the Twitter post to Proof Service, and finally successfully bind your Avatar to your Twitter account. This pretty much sums up the layman step-by-step process of binding your Avatar to your Twitter account.
As an open-source project, we welcome all interested developers to contribute and build with us. All of our existing supported platforms for ProofService can be found at https://github.com/NextDotID/proof_server#readme
If you wish to get involved with Next.ID, a great way would be to help integrate ProofService with more platforms. We are ecstatic to see developers who are already trying this.
To start off, you may select from the list of platforms as shown in our planned roadmap and work on them. Of course, platforms that are not listed are also welcomed. In order to know if the selected platform is able to access ProofService, we would have to consider:
The user is able to post on the platform (content is not limited to text, but can be in any form, e.g., images, audio, video), through which the Avatar private key signature is posted.
The post has to be public to allow verification.
Open an Issue
In ProofService’s code repository, create a new Issue, eg: [Feature] support XXX platform
Clarify and elaborate on how the above 2 criteria for accessing the platform are met. Any uncertainty can be addressed in the Issue so other developers are able to chime in to help and discuss. Once the idea is deemed feasible, you may start on the development phase.
2. Coding
In the structure of the code, there is a validator folder with access implementations for each platform
You may refer to template implementations for other platforms and implement the corresponding GeneratePostPayload(), GenerateSignPayload(), Validate() methods. Proceed to add the new platforms to: https://github.com/NextDotID/proof_server/blob/ develop/types/platform.go
The corresponding step-by-step test procedure can be found in our documentation: https://docs.next.id/getting-started/quick-start
3. Merge Request
Do a merge request upon the completion of the new platform implementation
Our core contributors will verify and comment on the written code to confirm the feasibility of the implementation and perform the corresponding merge operation
NextID is a community-led project and we encourage open-source contributors and enthusiasts to participate and build with us. ProofService is merely one of the many services you may work on.
Interested? You may join us on our biweekly calls to get project updates, ask questions, and partake in discussions.
As an open-source project, we welcome all interested developers to contribute and build with us. All of our existing supported platforms for ProofService can be found at https://github.com/NextDotID/proof_server#readme
If you wish to get involved with Next.ID, a great way would be to help integrate ProofService with more platforms. We are ecstatic to see developers who are already trying this.
To start off, you may select from the list of platforms as shown in our planned roadmap and work on them. Of course, platforms that are not listed are also welcomed. In order to know if the selected platform is able to access ProofService, we would have to consider:
The user is able to post on the platform (content is not limited to text, but can be in any form, e.g., images, audio, video), through which the Avatar private key signature is posted.
The post has to be public to allow verification.
Open an Issue
In ProofService’s code repository, create a new Issue, eg: [Feature] support XXX platform
Clarify and elaborate on how the above 2 criteria for accessing the platform are met. Any uncertainty can be addressed in the Issue so other developers are able to chime in to help and discuss. Once the idea is deemed feasible, you may start on the development phase.
2. Coding
In the structure of the code, there is a validator folder with access implementations for each platform
You may refer to template implementations for other platforms and implement the corresponding GeneratePostPayload(), GenerateSignPayload(), Validate() methods. Proceed to add the new platforms to: https://github.com/NextDotID/proof_server/blob/ develop/types/platform.go
The corresponding step-by-step test procedure can be found in our documentation: https://docs.next.id/getting-started/quick-start
3. Merge Request
Do a merge request upon the completion of the new platform implementation
Our core contributors will verify and comment on the written code to confirm the feasibility of the implementation and perform the corresponding merge operation
NextID is a community-led project and we encourage open-source contributors and enthusiasts to participate and build with us. ProofService is merely one of the many services you may work on.
Interested? You may join us on our biweekly calls to get project updates, ask questions, and partake in discussions.
No activity yet