Next.ID will be hosting a panel with Collab.Land, Ceramic, Spruce, and Disco, discussing Web3 social apps, DIDs, security, data, and the state of smart contract wallets. There will be product presentations and educational sessions on building with Next.ID and other open social protocols as well.

Located in downtown Denver, Web3 Social House is just steps away from major hotels. Enjoy a comfortable and well-equipped space with excellent Wi-Fi, power outlets, and workstations, along with complimentary snacks and drinks. Network, relax, and connect with attendees from various Web3 social projects and open protocols.

Check out Next.ID’s past achievements and goals for 2023:

https://mirror.xyz/nextdotid.eth/UVJz8OnMRIQhX6fqVioSrC_zEzDcASnYis-Xm472T-I

Sneak peek of the 2-day event rundown (more details to be updated):

Next.ID’s official developer-facing debut with the ETHDenver community

• Variety of workshops showcasing Next.ID

• Developer Q&A hours

• Opportunity to meet and chat with Next.ID founders, core developers, and Dev-Rel folks

Chainbase workshop

• How to use Chainbase’s Data Cloud API to generate an account-based DeFi portfolio overview

Web3 Users’ Security Afternoon: A sub-event hosted by GoPlus

• Different dimensions to protect Web3 user security

• Decentralized security data framework for Web3

• Event Registration

**DID Panel: Collab.Land, Spruce, Ceramic, Disco.xyz, Next.ID **

**Impact Panel — With Scott Moore (Gitcoin) and Suji Yan (Mask Network) **

Web3 Wallet Panel

Web3 Mass Adoption Panel — Web3 growth & playbook

Happy Hour Networking Night — Chill music and abundant drinks

Community Members — Lens, Farcaster, RSS3, Gitcoin, and more

Lists of Participants & Sponsors

Web3 Social House Co-hosts:

• Mask Network (@realMaskNetwork): Your Portal to the new, open internet

• Next.ID (@NextDotID): Your reliable DID infrastructure layer for all social dApps to build upon. We connect your Web2 & Web3 identities.

• Chainbase (@ChainbaseHQ): Chainbase is a leading web3 data infrastructure that provides datasets accessed with APIs and lets you build custom data pipelines.

• Collab.land (@Collab_Land_): Collab.Land is an automated community management tool that curates membership based on token ownership.

Web3 Social House Sponsors:

• KNN3 (@Knn3Network): One-stop Web3 User-centric DataFi solution for dApps and smart contracts

• GoPlus (@GoplusSecurity): Security Infrastructure Builder For Web3 By providing Open, Permissionless, User-Driven Security Services

• MirrorWorld (@joinmirrorworld): A content matrix that aggregates all the Blockchain-based games in the Mirror World Ecosystem

• Quest3 (@Quest3_xyz): Marketing Tool Collection for Sustainable Web3 Project Growth

Web3 Social House Community Sponsors:

• Gitcoin (@gitcoin): The community of builders, creators, and protocols at the center of open web ecosystems

• Lens Protocol (@LensProtocol): A permissionless, composable, & decentralized social graph that makes building a Web3 social platform easy

• RSS3 (@rss3_): Information dissemination of the Open Web

• Ceramic (@ceramicnetwork): Decentralized data network for building Web3 applications with composable data

Web3 Social House Strategic Support:

• SevenX Ventures (@SevenXVentures): Providing relentless support, from marketing to fundraising, from tokenomic design to resource integration, for projects and helping entrepreneurs succeed

• DWF Labs (@DwfLabs): the global digital asset market maker

Join us from February 28th to March 1st and be a part of Web3 Social House!

Registration is free — get your spot today: https://lu.ma/yawp7vd8

Here’s a look back at 2022 and what’s in store for Next.ID in 2022.

Our Team

The Next.ID team is globally distributed and remote-first, with members mainly in the US and Asia. Rather than having a physical office, we gather in different locations whenever possible for team events and workshops. If you need to reach out, we are active on Twitter, Telegram, and Discord.

How Developers Use Next.ID Today

Next.ID is a decentralized identity aggregation protocol that integrates all Web2 and Web3 digital identities, offering a verifiable identity database for open-source developers and projects to innovate and build dApps on.

4 Main Services For Developers

ProofService — Ensure data integrity with cryptography

ProofChain follows a blockchain-like model to retain data integrity, using cryptography and the private-public key pairing system. Only users with the right private keys can add to the data in each “block”.

ProofService and every change in its history are fully visible on Arweave, true to the Next.ID community’s commitment to complete transparency for its protocols.

KVService — Organize and make sense of the data provided by users

As users and protocols read and write data using Next.ID, KVService sets up a framework to organize the information neatly. This enables smoother frontend usage of Next.ID, as well as allowing developers a clearer understanding of how Next.ID can be utilized.

RelationService — Enable comprehensive identity queries and social use cases

RelationService takes all Web2 and Web3 IDs and aggregates them into a database. Having Next.ID as the ID layer, social dApps may use this database to perform internal functions. As more projects onboard with Next.ID, more data points are collected and the limit to the database is boundless. Developers can access the RelationService server here.

AuthService — Self-hosted service that provides authentication and authorization for web apps and dApps

Social dApps may use Next.ID’s AuthService for ID authentication. Think of it as the Web3 version of “Sign-in with Google/Twitter”.

Integrated with Web2 and Web3 platforms

Community Engagement Efforts

Over the past few months, there has been a myriad of different marketing and community engagement efforts dished out by the Next.ID core community. Ranging from Twitter Spaces, Discord AMAs, and Hackathons, to IRL panel discussions. Here are some of the key highlights:

• DID Summer #1: Being Human in Web3 — We hosted our 1st Twitter Space and invited renowned DID projects and Web3 builders such as Collab.land, Ceramic, KNN3, .bit, and Unipass. The topic of discussion was the importance and use cases of DIDs.

• Hacktoberfest 2022 — We participated in Hacktoberfest, an open-source event where developers were rewarded for contributing to Next.ID’s repository.

• Ethereum Foundation Devcon 2022 — We participated in a panel discussion in Devcon, Bogota, which was geared toward Ethereum and Web3 builders. The keynote dialogue was themed around AI games, gaming identity, personal data ownership, and how to collaborate with local communities in South America.

• Social Hour Hackathon — We organized a virtual hackathon in conjunction with Gitcoin to encourage open-source developers to get remunerated as crack their brains and problem-solve.

• Bangkok Identity Meetup — We hosted a panel discussion in Bangkok where Web3 & identity thought leaders gathered to exchange ideas and discuss the concept behind DIDs. We had guest speakers who are DID enthusiasts, along with representatives from Port3 Network and AC Capital. Great way to connect with fellow Web3 builders in the budding city.

• Gitcoin Educational Bounty — We decided to engage our community members by getting them to channel their creative juices and partake in content creation for Next.ID. We had a fun time reviewing the video and article submissions and were blown away by the effort that was put in. Definitely looking forward to organizing similar events in the future!

Content

Apart from being hyper-focused on building the best-in-line DID protocol, we also place a strong emphasis on educating the general public on the concept of DIDs. Even if you are a Web3 native like us, there are constantly new ideas to be learned as boundaries are being challenged every single day. You may refer to some of our thought pieces below:

• Why We Need To Own Our Digital Identities In A Decentralized World

• Digital Identity: What It Is, What It Solves & What Lies Ahead

• How Digital Identity Evolved Over The Years — Web1, Web2, & Web3

• Is a DID a wallet? Let’s debunk myths about identities in Web3

Partnerships

Since Next.ID is a DID infrastructure layer, our key metric of impact is to get dApps to entrust us with their backend identity management and social graph integrations. Next.ID will provide these dApps with our comprehensive social graphs and best-in-class user authentication so that they can have ease of mind and focus on building their product.

Here are a few success stories:

• DID partner of choice with Mask Network and Firefly

• Alpha Test Partner with SwapChat, KNN3, .bit, and RSS3

• Next.ID’s identity graph service supports 0xScope and Web3.bio

Outlook For 2023

Let’s take a look at what Next.ID envisions achieving in 2023. The main gist would be to reduce and consolidate the existing 4 main services into 3 — ProofService, RelationService, and CoreService. Below is the list of plans moving forward.

Proof Service — Smoother DID Verification & Management

Relation Service takes all Web2 and Web3 IDs and aggregates them into a database. Having Next.ID as the DID layer, social dApps may use this database to perform internal functions. As more projects onboard with Next.ID, more data points are collected and the potential of the database are limitless. In 2023, Next.ID would like to:

1. Include more data sources from Web3 and Web2 platforms

2. Ensure 100% credibility of data sources

3. Improve graph algorithms by Heterogeneous graph mining, Weighted node score, etc.

4. Develop a dune-like open dashboard for backend access

5. Optimize graph database for better performance

Core Service — Self-hosted Tech Stack To Expand DID Use Cases

You are in for a treat as Next.ID is looking to launch a new module named Core Service soon! As you may already know, Next.ID uses Arweave as a 3rd party decentralized data storage solution. Moving forward, we would like to allow our end users to self-host their DID and network of data so as to minimize external risks and regain absolute control over their own database. Keep your eyes peeled as we will release more updates soon.

Closing

We’re growing! Our core team has evolved in a major way and we’re gearing up for a big run in the new year. In addition to our current core contributors, we’ve also been actively onboarding talents across the different functions of the team.

We look forward to branding Next.ID as the leading DID infrastructure and key opinion project by building out benchmark use cases, content reservoirs, and leading industry discussions.

Also, the team is laying the groundwork for Next.ID to eventually operate as an open-source community governed as a DAO. We call for more builders to join our mission of making decentralized identity the gateway to interconnected and fair cyberspace.

Intrigued? Find out more at docs.next.id or reach out to us at developer@next.id. Follow us on Twitter: @NextDotID

Let’s talk about digital identities.

Before we begin, credit where it’s due: to Mark Zuckerberg, thanks for bringing metaverses into the mainstream consciousness. And while he has his own vision of what the metaverse is, we’re here to present a different vision. A metaverse not of digital dragons and spaceships, but of digital identities, social value, and how real people relate to each other online.

We’ve started trusting pseudonymous identities

Even now, with Web3 in its infancy, there are completely pseudonymous identities that most of us would trust: Punk6529 and Tetranode are just 2 OGs in the crypto space. They are accorded respect by the community for both the length of time they’ve been around, as well as the value of their opinions.

Who are they really? What do they do in their free time? Do they collect stamps or baseball cards? Do they play football or longboard? For that matter, what about Satoshi? Does it matter?

The point is not that we should trust pseudonymous people. The point is that when people consistently show us who they are, we should take note. We cannot just trust anyone, but we can trust their track records and repeated patterns. And yes, when these are verifiable via cryptographic signatures, we can trust even pseudonymous individuals.

The importance of this cannot be overstated. As blockchain technology continues to innovate, more people each day are starting to realize that living online is not a meme. And if we’re able to live online, we also need a foundational framework for understanding who we are.

Growing into our digital identities

Our offline selves have undergone an evolution and will continue to undergo changes.

When we are born, our identity is singularly our parents’ children. This identity evolves as we age, as we start exploring the world and what it has to offer. We take on other identities, some primary (aka more important) like being best friends, as well as secondary (aka less important), like students. As we grow further, we take on even more responsibilities while shedding older ones.

This evolution from a single-faceted to a multi-dimensional identity is limited in a Web2 world because we cannot truly own our identities — different corporations own different facets of our history. Thankfully, with the catalyst that is blockchain technology, cryptographic signatures are emerging as the cement that connects the building blocks that are our identities across multiple platforms.

For Web3 to properly take off, we need to first own our digital identities. Today, we have the technology, we have the skills, and we have the desire to make the change.

There are 2 parts to this letter:

1. Defining the issues around Digital Identities

2. How we will solve these problems

Digital Identities and their issues today

The problems with Digital Identity today are clear: who we are online, along with our data and history, are at the mercy of corporations in Web2. Our identities and who we are, are being auctioned off to the highest bidder. Data leaks are kept secret until companies are forced to admit it, and all our hard work can be negated with one internal policy change made to please policymakers.

The promise of the Internet was supposed to be a new dawn for mankind, opening new frontiers for self-expression. This promise is what we are reclaiming through digital self-sovereign identity, starting with these 3 issues.

1. Current digital identities are non-sovereign, stored in centralized servers

Autonomy is the primary priority for a true Digital Identity — and it is at risk as long as we keep them in centralized servers. Blockchain technology gives us the first credible opportunity since the invention of the Internet to move away from Big Tech’s centralized servers and reclaim our sovereignty.

Consider the possibilities once we create digital incarnations of ourselves. We’ll have interoperable avatars with full control over our data flow and income from digital sources. Today’s Web2 users face arbitrary gatekeeping at multiple stages. For example, your work on Quora, Zhihu, and similar platforms are stored centrally, meaning a portion of your life work could disappear through no decision of your own. And even if we assume the benevolence of these services, the probability of them being hacked is non-zero.

2. Current digital identities are superficial because they are single-faceted

As Shakespeare said, all the world’s a stage, and each of us has many parts to play.

One less-talked-about facet of Digital Identity is the ability to synthesize multiple parts of our lives. As we grow into our digital identities, there has to be a publicly verifiable history of who we are and what we’ve done — as decided to be disclosed by the user. Given how nascent Web3 still is, the first iteration of such a project should include Web2 as well as Web3 platforms, if only to provide users with a more complete history.

As the digital landscape develops over the next decade, we may see purely Digital Identities emerge, which is a cause for excitement. This would enable anyone from anywhere to create value for the community, make a name for themselves, and make an honest living, purely online.

With a truly Digital-only Identity, you can truly be yourself as a Web3 user. We can build reputations for pseudonymous creators. Whether you prefer to be doxxed, anonymous, or pseudonymous, cryptographic identity is the pathway that allows for a choice to happen. Who knows, Generation Alpha may be the first generation to live their entire lives on-chain, within a bustling economy of decentralized dApps and networks.

3. There is no true individual ownership in the current digital economy

As a direct response to the “real world” economy, where barriers to entry are gatekept by institutional actors, independent digital economies must be created — economies that evaluate parties on merit. For this to happen, we require a better identity system.

The current Web2 model for the creator economy is heavily centralized. Platforms like YouTube and WordPress have an array of options to ensure creators toe the line: they can hard ban (de-platform) or soft ban (shadowban) the creators, and there’s no avenue for recourse except to launch an appeal. This, plus the fact that the creators don’t own the communities they build, makes us think that there has to be a better way to approach the creator economy.

Thankfully, the stars are aligning for this to change. A mere 2 years ago, we had no proof of concept for a decentralized creator economy. Now, with the success of Mirror.xyz, we have at least one blueprint for digital creators to build projects and monetize them in a trustless way — articles, NFTs, and digital assets can be built completely on-chain, with data stored in a decentralized way.

This innovation by Mirror.xyz means that users can now create content in a trustless way, with nothing but a wallet. Because of this, creators, who have been beholden to centralized platforms in the past, are now able to truly own their content, its distribution, and the profits that arise from them.

This opens the door to a user-governed Universal Reputation System, where pseudonymous and/or anonymous creators are judged purely on the quality of their content, free to build and own communities. Digital identities are key to this happening, because like in real life, you only truly own something you buy, not something you rent. Digital assets stored on third-party servers are just that — rented goods.

In the future, if you want to bring followers from a decentralized version of Twitter to a decentralized version of Facebook, it will be frictionless. Everything you do will accrue value to your credibility across all platforms, and across all chains.

How we’re solving the Digital Identity problem

We are working on an open-sourced identity protocol that is the answer to the 3 issues highlighted above: Next.ID.

While it is still in the works, here is how we aim to address the issues in broad strokes:

1. Next.ID will create a completely digital you that exists everywhere you go

One of the primary functions of Next.ID is to be a one-stop platform for users’ Web2 and Web3 identities. This means that it will be as frictionless for users to connect their Facebook as their Metamask account to Next.ID, creating a “galaxy” that houses all an individual’s authenticated and verified Digital Identities.

The user will be in full control of this identity, using it across multiple platforms, while always retaining full control of their privacy and data. Next.ID will also introduce a universal standard for basic identity items, building a uniform platform for future developers to build protocols on, and increasing interoperability across multiple projects.

Phase 1 of Next.ID protocol: Establishing verifiable proofs among a user’s different digital identities

2. Next.ID uses cryptographic authentication to “complete” your digital personhood

While blockchain technology is hogging the spotlight, Next.ID uses a simpler and more robust technology as a basis: cryptography. The use of the private/public key pair to verify and authenticate identities allows for a seamless experience while maintaining the highest level of security.

Verifying then linking accounts to Next.ID confirms that the user has access to the accounts while allowing the account’s activity to stay off-chain. This is important because it maintains the user’s privacy even as it confirms their identity. Think of it as confirming that you work at a company without the details of what you did available on a publicly-searchable database.

Next.ID will then use our proprietary Proofchain, developed in-house, to enable everyday users to verify user’s identities. While on-chain sleuthing would have enabled the technically-minded among us to do this, Proofchain simplifies the process, democratizing on-chain analysis.

3. Next.ID will only build with partners who empower your ownership

The goals Next.ID intends to achieve are lofty and will only be possible with a whole-of-ecosystem push. As such, we will achieve our goals on 2 levels: a primary open-sourced foundational protocol designed in-house to ensure a consistent foundation, and secondary projects built by partner projects who share the same values. As Web3 builders know, the difference between Web2 and Web3 is that the former encourages competition while the latter incentivizes cooperation. It is this ethos that we hope to harness, such that everyone takes ownership and moves together towards a brighter future.

As Next.ID is hyperfocused on Digital Identity, we recognize that there are areas we will lack expertise in. It is in these areas that we will work with projects who have a similar vision. For example, we recognize that Digital Identity in and of itself will not be useful. It is because of this that we intend to work with Social Graph protocols to close the circle and achieve a network effect.

As we continue to map out the pathway that adds the most value to the ecosystem, we will continue to iterate according to sentiment and user feedback, always recognizing that the best projects require the best possible minds working together.

Next.ID: Towards a future that is owned, not rented

We want a future that is collectively owned, not one that is rented by nameless and faceless corporations that have no regard for users. This is the promise that self-sovereign identities powered by cryptographic signatures can give us, and it’s one that Next.ID intends to bring to the masses.

We’re living in a quickly-developing world, and it is anyone’s guess where the next project that will revolutionize the world will come from; 12-year-olds are capable of developing projects, and it won’t matter if they’re based in Asia, Africa, or America. It is within this context that Next.ID’s vision is important, because now more than ever, we need to break away from the Internet landlords that are Meta, Twitter, and other corporations.

I hope you join us* as we progressively reveal and flesh out what Next.ID can do it over the next few months.

Thank you from the Next.ID team.

*We’re currently in alpha testing and welcome trailblazers to join us for early-stage development. If what you’ve read interests you, reach out and say hello, bonjour, or 你好 on Twitter at @NextDotID. For more specific queries, you can also reach out to @YisiLiu (Lead Developer) and @hannah_h2s (Partnerships), and @sohchris (Community).

Speaker Info

• Hannah Shen, Head of Growth @ Next.ID

• Max, CEO @ Port3

• Vincent, Partner @ AC Capital

• Kai, DID Builder

• Moderator: Yisi Liu, Initiator @ Next.ID

You may watch the full recording on YouTube: youtu.be/hdcOIXtUVEo?t=1373

Concept and framing of the term “Decentralized Identity (DID)”. Why does it matter? (37:00 Yisi)

38:21 Kai: Digital identity should not be directly linked to your digital assets, bank statements, NFTs held, etc. There should be an intermediate layer that protects user privacy while providing information necessary for apps to function properly. DID is an umbrella term that encapsulates projects and services such as ENS, privacy-preserving protocols, ZK solutions, etc.

40:13 Vincent: When we think about DID, we first ask ourselves,” Why decentralizing matters?” If we look at Web2 account systems, they are all generated in a centralized manner, in a centralized server. If the entity so wishes to ban your account, it can easily be done so. However, with DIDs, we will be able to generate accounts/wallets locally and you have control over what you own.

Secondly, DID enables interoperability of your account/wallet. With a single wallet address, the user will be able to interact with multiple protocols and Web3 services, without any boundaries. Unlike that of Web2 whereby user accounts are bound specifically to a particular website/server. (e.g. Google accounts can only be accessed with Google services).

43:30 Max: In the Web3 world, DID allows for universal accessibility of your digital identity. Say, for example, you have been active on Facebook for a long time. Your connections, posts, likes, and comments on Facebook will remain solely on Facebook’s server and it cannot be seen and accessible on other platforms. If you do wish to build your brand on another platform like Twitter, you have to start from scratch. However, the concept of DIDs will allow you to bring your digital identity and footprint across other platforms.

46:07 Hannah: The concept of DID is the same as Self-Sovereign Identity (SSI). At its core, users have control over their private keys and public addresses and be able to verify/attest credentials among themselves, without involving a 3rd party.

From the value protection side in the future, when users access services and authentication through DID/SSI, it will give users freedom and safety.

From the value creation side, there could be reputation scoring built using DID methods.

The idea of SSI has been around for more than a decade. However, Web3 has provided the technology to utilize this idea. Right now there are many wallet addresses on different blockchains that contains different on-chain behaviors across different ecosystems. Web3 DID is an idea that connects the on-chain world with the off-chain world and that is what Next.ID has been working on it actively.

How do we strike a balance between the online freedom of users and user privacy/security? (49:30 Yisi)

50:25 Vincent: We are unable to enforce this idea because users simply do not care. People do not mind trading their online information for user convenience. Especially so for the majority of people who have other priorities in life and need to make a living. Their personal private information is deemed to be not important and they do not mind giving it up, as long as they can get things done as quickly as possible.

The way to get mass adoption for DIDs would be to get role models in the space and eventually make it into a social norm for the rest of the people to follow.

54:50 Max: What Port3Network does is that we request users to provide their cross-platform identity. It is done by providing incentives to users from other projects.

59:38 Hannah: While we have all the privacy-protecting benefits of DID, it comes with an entry barrier for many users. We builders constantly need to think about educating end-users and how to get them to care.

In terms of getting end-users to enjoy the freedom of their ownership through DID technology, there are 2 parts.

1. How DID can be a better service for builders and developers to get onboard. E.g. DID login authentication is used as an alternative or additional option to sign in on their server, be it a decentralized or centralized server. It provides a gateway for users to learn about what DID and it allows them to set up DID while using their services. In order to achieve this, we need consensus from Web3 applications to adopt it as the default ID management/login solution.

2. In terms of finding the needs of end-users on the application side, like what Max mentioned, would be to encourage users to verify themselves through DID which could bring benefits such as better reputation building and credit scoring, without relying on 3rd parties. This form of verification is done so through gamification of on-chain actions. This will greatly incentivize end-users to adopt and care about DID, not solely on the moral high ground of “protecting user privacy” point-of-view, but it actually brings real benefits. For application layer builders, This is something that application layer builders can think about, find out the true needs of cyber citizens which are not being fulfilled on centralized platforms today.

Do you think users need to be educated about the concept of DIDs? (1:08:40 Yisi)

1:09:00 Hannah: Users do not need to know the ins and outs. It depends on the targeted users. To target early adopters, we will need to get them to understand why DID in general is necessary. Whereas for mass adoption, the level of understanding may be weaker. However, the bare minimum is for users to know what a private key is, similar to the understanding of how you manage your current accounts.

1:09:40 Max: “When you fly on a plane, do you think a user needs to know the aerodynamics of how the plane works?” Users do not need to understand the concept of DID. Instead, it is important for users to know how will DID benefit them in delivering the service that is needed, which is not attainable with other identity services.

Main Takeaway

1. Is Decentralized Identity (DID) the right framing? Why it matters? DID is the response to the centralized account system and the privacy in Web2. We’ve seen movements on self-sovereign identities and DID long before Web3 but the growing crypto adoption makes blockchain-based identifiers more relevant, giving rise to Web3 DIDs and hybrid IDs.

2. We should first think about what kind of applications and developers could benefit from DID versus traditional web2 id system or wallet-first solution and find the utility and motivation for users to own DIDs.

3. End-users should at least know how to manage their DIDs similar to remembering their password but we don’t need everyone to agree with the technical and philosophical reasoning around decentralized identities and related technology.

Project Info:

• Next.ID is the world’s first Decentralized-Identity-as-a-Service (DIaaS) protocol

• Port3 is a one-stop platform to create, utilize and evolve your Web3 identity.

• AC Capital is an investment firm focusing on Blockchain and Fin-tech, committed to discovering unicorns and boosting their development.

For anyone who is interested in Next.ID and DIDs in general, please do follow Next.ID’s official Twitter account @NextDotID and join our Telegram and Discord groups. We will be hosting more similar events and will continue to invite more industry leaders and emerging Web3 builders to talk with us.

Next.ID is a decentralized identity protocol that integrates Web2 and Web3 identities, offering a comprehensive and verifiable identity management and database for open-source developers and projects to innovate and build dApps on. Next.ID offers Decentralized-Identity-as-a-Service (DIaaS).

As the world’s first DIaaS, Next.ID creates an identity infrastructure that securely aggregates and authenticates users’ identities into a Decentralized Identifier (DID) called Avatar, making it the primary touch point for interfacing with any app or dApp.

Next.ID’s identity Avatars exist independently from Web2 and Web3, using a blockchain-like model to retain data integrity. This allows Next.ID to connect to all Web2 and Web3 platforms, aggregating all identities in a fully-agnostic way, unifying them into one single DID.

Next.ID is looking for experienced developers who want to build on Next.ID as a public good, to create a framework that empowers users, and to create a digital society that stands apart from traditional constraints.

About 0xScope

0xScope is the first Web3 Knowledge Graph Protocol. It solves the problem that Web3 data analyzes addresses instead of real users by establishing a new identity standard — — the new Scope Entity from the data layer. And it unifies the standards of different types of Web2 data and Web3 data by utilizing its knowledge graphing capability, which greatly reduces the difficulty of data acquisition and improves data penetration ability.

0xScope has built a robust and growing database. As of now, we have identified over 84 million entities, and fully analyzed over 640 thousand tokens, 11 thousand protocols, and 51 million smart contracts. At the same time, we have more than 1.4 million identity labels, over 5 million behavior labels, over 17M risky address labels, and more than 31M exchange deposit and withdrawal address labels.

To this date, 0xScope has launched Watchers, a B2B data service and a developer platform, providing entity-based transaction tracking, risk scoring, and portrait identification capabilities, which can be integrated into partners’ businesses in a variety of flexible ways through APIs, data collaboration, custom data analysis reports, etc.

(We are actively seeking cooperation with the Web3 pioneer team to build a new data standard layer and elevate the quality of the Web3 product experience and security standards to the same level as Web2.）

Core collaboration scope between 0xScope & Next.ID

Next.ID’s RelationService — 1 of 4 existing services that enable comprehensive identity queries and social use cases, and powers 0xScope’s knowledge graph protocol.

RelationService is an aggregation of existing DIDs, identity graph queries, and IDs bound to and in parallel to Next.ID. It opens up a range of possibilities for integration with external protocols and creates greater Web3 native social use cases. Developers can access the prototype of the RelationService server here.

The search bar on 0xScope’s platform leverages Next. ID’s RelationService to populate data for each searched address. 0xScope has an algorithm to calculate an entity’s risk score/credit score. With Next.ID’s RelationService, more social identity data of each address will be aggregated into 0xScope’s API, further enhancing the entire database. 0xScope will also use the Next.ID’s database to backtest the data algorithm’s accuracy and to improve its relationship graph.

How will this partnership benefit 0xScope users?

Next.ID authenticates and aggregates identities from Web2 and Web3 applications using secured cryptographic methods to give users a self-sovereign digital identity.

0xScope takes the aggregated data and elevates its value by bringing in the element of risk analysis — Know Your Entity (KYE) — a comprehensive risk control service that allows the exploration of the complex relationship between multiple addresses. The protocol incorporates various machine learning algorithms to provide real-time analysis, signals, and reports for the platform user. 0xScope’s integration with Next.ID will allow 0xScope to provide a more accurate analysis of different customers.

With 0xScope, you can instantly get all related addresses by simply searching for one address. 0xScope is necessary to locate, classify, and examine the connections between addresses inside a network. Next.ID allows users to associate wallet addresses with social profiles while protecting and verifying addresses with users having full data ownership. This collaboration will enhance 0xScope’s platform user experience and further explore improvements in identity and knowledge graphs.

Links for Next.ID

Official Website: https://next.id/

Twitter: https://twitter.com/NextDotID

Telegram: https://t.me/NextDotIDofficial

Medium: https://medium.com/@Next.ID

Docs: https://docs.next.id/

Notion: https://www.notion.so/nextid/Next-ID-Home-0fb4ba9200d6458ab6c4fa81778f6a7b

YouTube: https://www.youtube.com/channel/UC17C9xWKp0h_pZhfxbNtHsg

Discord: https://discord.com/invite/PhRCmFCskY

Links for 0xScope Logo: https://docs.watchers.pro/marketing-material

Website: https://0xscope.com/

Linktree: https://linktr.ee/scopeprotocol

0xScope Website: https://0xscope.com/

0xScope Developer Center: https://developer.0xscope.com/

Twitter：https://twitter.com/ScopeProtocol

Learn more: https://medium.com/@0xscope_labs

The Next.ID community would like to encourage active discussion through the following series of articles:

1. What feature or system of DID do users benefit most from?

2. What are the user migration costs for moving from Web2 to Web3?

3. What can DIDs offer to users in Web3 that is unachievable in Web2?

Is MetaMask a form of DID?

MetaMask’s current monthly active users (MAU) are approximated to be > 30 million. With this large user base, many projects naturally would want to create an identity layer through MetaMask. However, given that MetaMask is merely a wallet with no DID applications, this idea would not work.

Metamask is an EOA-like (Externally Owned Address) wallet. One of the biggest problems surrounding the use of such wallets is the risk of users losing all of their digital assets if their private key or seed phrase gets lost or compromised.

As long as MetaMask fails to solve this pain point, Web3 adoption would still be a huge curveball.

Let’s take a step back and take a look at some of the immediate problems of Web3 identities.

1. Web3 needs to find a solution for wallet recovery

• Using a simple analogy here. Each individual has a name and unique ID number (or driver’s license or passport) in Web2 analogous to the public and private keys of Web3 respectively.

• If a Web2 user loses his ID card, by the analogy of private keys, he will still be able to apply for a new ID card through one of the centralized certification bodies (i.e. national public security authorities) and his corresponding assets will not be lost.

• Web3 also needs to do the same. How can the user regain control of his account through a decentralized authentication network, even after the loss of the private key? If there is a method to do so, Web2 to Web3 migration will be much easier.

2. Seed phrases are cumbersome in Web3

• As we all know, whenever we create a brand new wallet on different dApps and platforms, we would be given different recovery phrases to jot down. We are told to not lose them as it will risk losing all assets in that wallet.

• With so many wallet addresses, private keys, and seed phrases to remember, it surely is a very unpleasant user experience.

• There needs to be a decentralized Web3 version of 1Password or LastPass to aid users in better wallet management.

So what’s the problem? Let’s go back to the Web2 world and think about it.

A wallet like MetaMask is essentially like a bank account, which is used to conduct financial transactions. We can only open a new bank account using a unique ID like an ID number (or driver’s license or passport). However, if one takes a Citibank account and requests withdrawals at Standard Chartered, it would simply not work.

This is because the user “identity” and “bank account” are not the same thing.

Recently, the Ethereum community passed the proposal of EIP-2938 — using “Account Abstraction” for the development of smart contract wallets. Another popular DID product, UniPass, also takes a similar approach.

We are seeing more proponents of decoupling the “identity” (public-private key pair) from the “bank account” (abstracted account, wallet address) and building a completely new mechanism. Below are some potential solutions to the aforementioned idea.

Generating a new private key for the one that was previously lost. Some potential methods may include:

1. Social recovery — A way to guarantee wallet ownership through high-quality on-chain interaction with friends and connections who are able to justify on your behalf.

2. Backup questions — A series of private and security questions can be used to assist in recovering the private key of the wallet. For example, what was the name of my childhood pet, who was my high school English teacher, etc.

The management of all related Account Abstraction (Web2 IDs and Web3 Abstracted Accounts) can be directly bound and collected into a digital identity (public-private key pair). This is what we call “Avatar” in Next.ID. As shown in the diagram below.

So far, we have touched on the foundational layer of defining DIDs with a “public-private key pair”. In the aspect of DID private key management, we would need the help of the greater Web3 community to explore together the use of social recovery and personal privacy quizzes to lower the barrier to user adoption.

Have we truly considered the proper use of DID before?

Back in Aug 2022, the regulatory sanctions of Tornado Cash (TC) brought upon by the U.S OFAC had caused much fear and uncertainty amongst many Web3 practitioners. Wallet addresses that interacted with TC had been frozen. Even wallet addresses that did not specifically use TC but unknowingly had crypto transferred over to them from another wallet address that used TC, had their wallets frozen. This incident made people question if Web3 is truly resistant to censorship.

At the same time, many DID projects in the market are nonchalant with their services. They are blatantly disregarding the potential risks of leaking personal information, rushing to ship imperfect products for the sake of chasing the hype, and putting no long-term progressional thoughts into it. Given that Web3 privacy protection technology (e.g ZK proofs) has not yet fully matured, we should not expose ourselves to such flaws, putting ourselves in danger of getting another regulatory sanction. If another incident were to arise from exposing the flaws of DID in a regulatory manner, it could get rather embarrassing.

Are DID projects overly focused on external clients and neglecting the needs of users?

From the user’s point of view, the overall implementation of a DID system should go beyond the foundational layer of defining DID identity as the public-private key pair, as discussed earlier.

• In order to properly integrate DIDs, it needs to achieve the same level of interoperability and user-friendliness, similar to Web2 counterparts like OpenID/OAuth. It needs to be as simple as possible whereby only a few clicks are needed to complete logins.

• Also, all Web2 (e.g. Twitter and Instagram) and Web3 accounts (e.g. Abstracted Accounts and Smart Contract Wallets) should be aggregated under the premise of protecting user privacy. If the user chooses to be anonymous/pseudonymous on their Web2 accounts, there should not be any way to reveal his identity. Ultimately, they can only be traced to an online virtual identity — a string of alphanumeric characters.

What kind of Web3 “one-click login” do users need?

In the Web2 era of apps, every user is familiar with using the one-click log-in. Easy to use and no more annoying passwords.

Advantages

• Password required for the first registration.

• Subsequent logins can always use Google, Facebook, Email, etc.

Disadvantages

• Users do not have ownership of their own data and they are putting their private info at risk by giving full control of it to the platforms.

• Users are bombarded with all kinds of forced advertising as most platforms heavily rely on advertisements to generate revenue and sell user info to these advertisers

With the help of Web3, the issue of data sovereignty can be solved. However, the user experience of dApps in Web3 is not user-friendly and still remains to be improved. It needs to achieve somewhat the same level as the experience we have on Web2 apps if we ever want to talk about user adoption.

Potential improvements in Web3 user experience

AuthService — The Next.ID community has come up with a new idea to improve the UX in Web3 social account interactions. It is designed with the following flow.

Flowchart for Next.ID’s AuthService

1. Users can leverage Next.ID’s AuthService SDK for dApp account authorization operations. The data sources are bound to Next.ID’s in-house ProofService.

2. The authorization operation is verified by a VPS (Virtual Private Server) deployed by the user.

3. Upon successful authorization, the user will specify the “scope” to reveal private info related to the user account.

The key 1st step is to use Next.ID when logging into the dApp.

The next step would be to access the authorized account’s data (Wallet ID, Twitter Authentication, etc.). (Step 3 as shown in the main diagram)

Finally, the data of the account gets released (Steps 5 & 6 as shown in the main diagram)

In the subsequent articles, we will dive deeper into the topics related to “privacy” and “security”, and also further explain the VPS (Virtual Private Server) idea behind AuthService.

Thank you for reading and feel free to comment and reblog — the Next.ID open source community warmly invites you to join us in promoting the DID ecosystem.

[1] W3C’s definition of DID is “Decentralized Identifier”. In the Web3 social space, “Decentralized Identity” is used instead for better commercial and product context.

Official Site：https://next.id/

Twitter: @nextdotid

Github：https://github.com/nextdotid

Discord: https://bit.ly/NextID_Discord_Official

Biweekly Community Call Recording：

YouTube (EN): https://www.youtube.com/channel/UC17C9xWKp0h_pZhfxbNtHsg

Bilibili (CH): https://space.bilibili.com/1004643496

Next.ID is one of the main sponsors of this Social Hour Hackathon. We used this AMA opportunity to address any possible queries that participants might have with regard to approaching the bounties. With these rewards, we hope to be able to attract and incentivize developers who wish to explore building with us.

Gloria from Gitcoin shared with the audience what it is like to join a Hackathon. Participants can either team up or go solo. You may find video recordings of past workshops Gitcoin has held on its YouTube channel to get a better foothold. To follow Next.ID’s future developments, you may join our Telegram or Discord as we exchange ideas amongst our developers and other community members.

The reason why we encourage developers to participate in hackathons is because it gives good exposure to industry needs and it is a tremendous boost to their portfolio.

Between the period of 28 Oct to 15 Nov (12 AM UTC+0), there will be 3 bounties with a grand total prize of 6000 USD to be claimed:

1. Headless Browser For Fetching Proof Post

2. Help Us Expand The `Relation_server` Social Graph With More Data Sources

3. Support More Platforms On `Proof_server`

If you would like a walk-through and find out more about the bounties and what Next.ID is up to, feel free to watch the AMA recording:

Ever since Elon Musk took over Twitter in Oct 2022 with intentions of tackling the existing problems of censorship, bot infestation, content moderation, etc., it gave rise to the possibility of using Web3 to solve some of these issues. The idea of protocol decentralization and the need to use DIDs to power our identities have certainly been accelerated. We at Next.ID believe that now is the perfect time to bring more awareness to the public about the future of Web3 social, along with use cases of DIDs.

In the current state of social media, we do not truly own the data on these Web2 platforms, resulting in potential mishandling of our private data as platforms are known to sell our personal data to 3rd-party companies. These Web2 social media giants do not want their users to know how their data is being used.

Right now, the idea of Web3 is to shift away from the absolute powers of these conglomerates and build toward a decentralized model of social media. In this newly envisioned version of Web3 social media, users will have greater ownership of all online activities and identities. He/she can decide what info to share, and how much they want to share.

We are gradually seeing more projects sharing the same vision and building on DIDs. It is surely challenging to decentralize our social identities and platform as the technology is still very nascent. Next.ID is evangelizing its DID-aggregating service by reaching out and collaborating with social media dApps, providing them with decentralized identities and social layer graphs. We intend to help dApps lower onboarding friction, eliminate phishing, enhance identity integrity, and enrich social connections.

People are re-evaluating the use of existing Web2 social apps and they have been trying to find alternatives these days. They are now more aware of the importance of data ownership and self-sovereign identities. Early builders and developers are playing the visionary role in making all of the aforementioned ideas a reality.

For the uninitiated, you may listen to the recording as our speakers exchanged some brief explanations of the technicalities and terminologies.

Next.ID is not building just another Web3 protocol. We’re building to facilitate a paradigm shift in an identity infrastructure.

If you are excited about Next.ID and the identity space in general, come forth and join our tribe in helping to build the new foundational layer of the new open internet. Do follow us on Twitter and Discord as we will be hosting many more similar events to chat with leading Web3 industry practitioners and builders.

Speakers:

Hannah Shen, Head of Global Growth at Next.ID

Wei Duan, OSS Community Manager at Next.ID

Gloria, Hackathon and Event Team Member at Gitcoin

Official Site: https://next.id/

Twitter: @nextdotid

GitHub: https://github.com/nextdotid

Discord: https://bit.ly/NextID_Discord_Official

For WeChat Users: add up BinaryHB to join our official group

Bi-weekly Community Call Recordings：

Bilibili: https://space.bilibili.com/1004643496

YouTube: https://www.youtube.com/channel/UC17C9xWKp0h_pZhfxbNtHsg

Next.ID 社区希望通过系列文章邀请大家讨论：

1. 用户到底需要什么样的 DID，或者说什么样的 DID 体系;

2. Web2 的用户迁往 Web3 面临着什么样的迁移成本;

3. Web3 DID 能给用户带来什么在 Web2 中无法获得的东西。

MetaMask 钱包是 DID？

据不完全披露，钱包领头羊 MetaMask 目前的月活用户数，起码是 3 千万以上的级别。这导致了大部分的 dApp，很自然的希望通过 MetaMask 来做身份层。而这个想法显然有非常多的挑战，毕竟 MetaMask 只是想做一个钱包而已。

先不论 MetaMask 有没有动机和动力，愿意维护这样海量级别的公共 API 来给 dApp 调用。一个始终绕不过去的，横亘在用户面前的大难题是：作为 EOA 类（externally owned address，外部所有者账户）钱包，只要我的私钥或者助记词丢失，我将丢失我对应账户里的所有资产。

只要 MetaMask 类的钱包无法解决这个巨大痛点，Web2 用户很难突然有勇气跳入 Web3 的兔子洞。

那 Web2 的用户目前是什么样的体验呢？

如果我们做一个简单比喻，把 Web2 里的姓名和身份证号（或者驾照、护照）这样的唯一 ID，分别对应于 Web3 的公钥地址和私钥。

可以发现，第一个问题：一个 Web2 用户即使丢失了身份证，即类比于私钥，Ta 依然可以通过中心化的认证机构之一国家公安机关，来重新申请一个身份证。Ta 的对应资产不会丢失。

以此类推，Web3 同样需要做到：私钥丢失后，我能不能通过去中心化的认证网络，通过什么样的方式来恢复对这个账户的控制呢？如果这个目标达成，在这一点上，Web2 用户迁移 Web3 的成本为零。

那么第二个问题：我有 MetaMask 钱包，我有币安等各类交易所的钱包，我还有各种 dApp 服务给我默认生成的钱包。这么多私钥，这么多助记词，我们是不是要等 Web3 重造一个去中心化版本的 1Password 或者 LastPass 来进行托管呢？用户成本大大增加，要去添加、管理所有的可能未来长到没有尽头的账户列表。简直要命。

所以问题出在哪里呢？让我们一起回到 Web2 世界想一想，就清楚了。

MetaMask 这样的钱包，本质上是一个银行户头，就好像我们在中国工商银行、花旗银行等等的账户，从而可以进行金融交易。我们只能使用身份证号（或者驾照、护照）这样的唯一 ID，去开一个新的银行开户。那如果我们持有中国工商银行的户头，去中国建设银行要求开户，可想而知一定会被工作人员请出去。

因为“身份”与“银行户头”，并不能直接画上等号。

并不止 Next.ID 社区持有这个观点，很多社区和 DID 产品也都这样认为，比如以太坊社区通过提案 EIP-2938，正式提出抽象账户（abstracted account），以此开发智能合约钱包。另一个很受欢迎的 DID 新产品 UniPass 也是采取类似思路。

也就是说，通过身份（公私钥对）与银行户头（抽象账户，钱包地址）的解耦，尝试建立一些全新的机制，我们得到前述难题的解法：

1. 私钥丢失不代表资产丢失，我可以用新的私钥去绑定已经丢失私钥的资产。

   1. 方式一，社交恢复（social recovery），通过过去已建立联系、链上留下高质量互动记录的好朋友们，给你进行担保的方式；

   2. 方式二，可以使用一系列等价于私钥级别的隐私安全问题，来辅助恢复账号。比如我小时候的宠物叫什么名字/我高中的英文老师是谁等等；

2. 所有相关抽象账户（Web2 IDs、Web3 抽象账户）的管理，可以直接绑定、收归到某一个数字身份（公私钥对）进行管理，在 Next.ID 里我们称之为数字化身 Avatar。神作电影《阿凡达》记得吧？半身不遂的人类 Jake 通过神经连接，控制着一个纳美星男性健全的身躯。是不是很像我们未来控制一个元宇宙里的数字化身？如示意图：

好的，到这里为止，我们算是把「定义 DID 身份的最底层是公私钥对」这一层说了个大概。当然了，作为 DID 的私钥管理问题，仍然有待整个 Web3 社区一起去探索，在未来通过社交恢复以及等同于密钥等级的个人隐私问答等等方案，一起来降低使用门槛。

我们有没有从第一性原理出发考虑 DID？

前一阵，Tornado Cash 所带来的监管风暴，让很多 Web3 从业者感到后怕。直接查封地址，甚至还会连带封杀所有与之有过交易记录的地址，这种“满门抄斩株连九族”的做法令人不禁对 Web3 的抗审查性产生怀疑，信仰动摇。

与此同时，市面上很多 DID 项目做的就是粗暴的聚合服务，也不管是否链上链下账户，会不会有泄漏个人信息的风险，统统放到一起。那是不是等于说，在 zero knowledage proof（零知识证明）等隐私保护技术尚未完全成熟的今天，我们直接把自己拱手交出，好让监管部门一网打尽？

颇为尴尬。

有没有可能 DID 项目都太照顾项目方需求、反而忽视了用户的真正需求？

如果从用户角度出发，一个 DID 系统整体的落地方案，不仅包含前一小节我们谈到的「定义 DID 身份的最底层是公私钥对」，还至少包括往上的两个层面：

• 第二层面，在这套方案中，随意一个 DID 身份能够安全地满足，所有前来访问需要授权信息的 dApps 的并发调用流量，同时提供媲美 Web2 的 OpenID/OAuth 一样的丝滑体验，用户操作”傻瓜“式简单，点一两下，一键完成登录；

• 第三层面，与该 DID 身份所绑定的所有 Web2 账户如 Twitter（当然，你的 Twitter 也必须是主动地去隐私化，无真名无真人头像等，比如著名 NFT OG 6529，即使出席大会也从不露真容）、Web3 抽象账户如智能合约钱包，都可以在保护用户隐私的前提下，被聚合到一起。即使被“人肉”，用户在真实世界里具体是“谁”也无从得知，最终也只能追查到一个线上的虚拟身份、一串数字罢了。

用户需要的 Web3 “一键登录”会是什么样？

Web2 时代的 App，每一个用户都熟练使用一键登录。使用体验方便，且不用再输入恼人的密码。

对用户来说，登录 App 的好处：

• 第一次注册时需要密码；

• 后续可以永远使用 QQ、WeChat、支付宝登录。

同时对用户的坏处是：

• 数据主权，不在自己手上。使用平台（QQ、WeChat、支付宝）提供的账户体系；

• 被动接受各类基于隐私信息的广告，用户自己没得选。

Web3 的账号，尽管可以帮忙把数据主权拿出来，但绕不过去的问题是：账户授权和使用，能像 Web2 的一键登录那么流畅吗？

Next.ID 社区提出了 AuthService 这样的思路，试图来解决这个工程问题。它的设计流程如下：

1. 用户使用 Next.ID 的 AuthService SDK，进行 dApp 的账户授权操作，数据来源子用户绑定到 ProofService 的数据；

2. 授权操作通过用户自行部署的 VPS（Virtual Private Server，虚拟私人服务器）来验签；

3. 成功通过后，用户指定可以具体的 scope 开放出用户账号的相关隐私信息。

其中关键的第一步，登录 dApp 时使用 Next.ID：

第三步，授权时开放哪个账号的数据：

最后第五/六步，开放账号的哪些数据出去：

以上是本期文章的所有内容，在后续的文章，我们将继续就「隐私」和「安全」的相关话题展开讨论，也将就 AuthService 背后的 VPS（Virtual Private Server，虚拟私人服务器）思路进一步进行说明。

感谢你的阅读，欢迎评论和转发。开源社区 Next.ID 也诚挚邀请你的加入，一起推进 DID 生态的落地。

官网：https://next.id/

开源代码：https://github.com/nextdotid

Discord: https://bit.ly/NextID_Discord_Official

添加社区经理微信：BinaryHB

社区双周会录制：

• 中文 B 站：https://space.bilibili.com/1004643496

• 英文 YouTube: https://www.youtube.com/channel/UC17C9xWKp0h_pZhfxbNtHsg

WAMO Summer Dali Web3 Fest DID Camp is one of the decentralized themed camps of the Dali Web3 Fest. Next.ID, UniPass, MetaID, and KNN3 co-hosted a round-table talk both online and offline. During the talk, the projects focused on building Web3 decentralized identities (DIDs) gathered and took a deep dive into the application level, imagination room, and the current problems in the DID build-out phase.

Here are the key takeaways from the round-table talk.

1. Why do we need DIDs? What are the biggest problems with the current ID system? Are DIDs solving the problems?

• DIDs provide users with the ability to prove their identities online without dependence on a third party. They are the foundation for the entire Web3 self-sovereign narrative. Only through DIDs can users fully own their identities.

• Problems with the current ID system:

  • User data is stored on the respective servers of the different applications

  • Due to the lack of trust among these applications, the data stored is much fragmented, causing data silos in Web2.

  • Users can not fully own their data and are dependent on the mercy of these application providers.

• Blockchain-based DIDs solve the existing problems in the ways of

  • Both user information and their data are stored on-chain, making it nearly impossible to tamper and stay permanently on-chain.

  • Thanks to blockchain’s trustless and transparent nature, data generated by DID-based Web3 applications no longer belong to any business entities, and is interconnected and interoperable, fully owned by users themselves.

  • Historical changes will be made by DIDs. Web3 without DID might be a false assumption.

2. What are the typical solutions for DID? Their pros and cons?

• DID, as well as Web3, is in the early stage. Different projects have their own understandings of DID, which does lead to differentiated focuses. Their visions might be identical, but the roadmap will not be the same. Which is the correct way is still under observation.

• The one and only criterion to decide whether a solution is successful is ultimately the number of satisfied users. The DID narrative has a strong network effect which will eventually benefit all projects on the same track.

• Typical solutions:

  • Smart contracts

  • EOAs (externally owned accounts)

  • UTXO model

  • Domain names

  • To-Cs

• UTXO model and its pros and cons:

  • Easier to make data fully on-chain.

  • Larger user capacity.

  • Lower transaction fees.

  • Costs: there are fewer developers and users on UTXO, which makes it more difficult to start.

3. What are the prerequisites for DID to become mainstream? What is its biggest value proposition? What are the biggest blockers for now?

• Having enough use cases is key. Lowering the entry bar and better user experience will also be vital.

• Values provided by DID-based Web3 applications are relatively intangible to users.

  • It is until there are more Web3 applications in the market and more interoperable data coming into being can users better understand the values of DID.

  • This process is not short-termed, meaning the growth of decentralized identities will be a hard one but also will be exponential in later stages.

• The biggest blocker at present is the lack of infrastructure.

• Gas fees remain an obstacle for DID to achieve mass adoption for the high costs and the difficulty to obtain it. To solve this:

  • Make gas fees lower.

  • Onboard users with fiat on-ramps on gas fees.

4. Wallets, e.g. MetaMask, have become a common user identity layer for Web3 services. Are wallets equivalent to DIDs?

• Wallet and DID are two different applications at the fundamental key pair management level.

  • MetaMask, for example, is built for financial purposes without optimizations in the DID use cases. While DID is more focused on identifying data.

  • Wallets don’t provide users with enough rights to manage their permissions.

  • DID solutions, on the contrary, lower the entry bar and provide users with a more flexible account permission management. Data is not interconnected and interoperable among different wallets, and a user’s identity is not unified cross-chain. MetaMask for now wouldn’t be enough to be an ideal DID-compatible wallet. We need better wallets for this.

5. What’s the relation between DID and social graphs? How do we build our own DIDs and reputation system in the Web3 era? Can the reputation system replace the voting power of tokens in DAO governance? How to build a non-tokenized social network?

• If DID-based Web3 projects go mainstream, because the data is linked, a user will only have one social graph on-chain then. This is a brand new experience for users and users will start to be careful with what they do on-chain as reputation will be an essential part of users’ identity assets.

• There is a large possibility that the reputation system can replace the voting power of tokens in DAO.

  • Tokens only mean how much a user has invested, which doesn’t fit certain monetary scenarios, such as profit allocations.

  • DIDs are more quantified metrics to identify DAO participants.

6. How to balance user privacy and data transparency since DID emphasizes openness?

• Privacy is always key in Web3 and is also an important standard to measure a DID solution/protocol.

• A good DID solution should be one that cares about privacy protections but doesn’t encourage anonymity.

  • An anonymous society isn’t necessarily a perfect society. Introductions of technologies such as ZKP (zero-knowledge poof) are good ways to protect users’ privacy.

  • After DID becomes popular, it should be less advantageous to speak and socialize anonymously. In the foreseeable future, there might be less anonymity.

7. How are SBT (soul-bound tokens) manifested in DID?

• SBT is a sub-DID to some extent, or we can say a good DID solution itself is an SBT.

8. Relations between DID, NFT, DAO, and DeSoc.

• Most of the current NFTs, DAOs, and DeSoc lack DIDs as their foundation, which will be hard for them to popularize.

  • Only with DIDs can Web3 applications and NFTs, etc. be connected in the data layer.

  • The network effect of such data connectivity will have a crushing advantage over applications that don’t have DIDs.

9. From DID to an immortal Metaverse

• DID is the foundation for Web3 and Metaverse.

• An immortal Metaverse is upon us:

  • Combined with AI and DID, it’s highly probable that our minds live eternally in the Metaverse.

  • The future Web3 and Metaverse, based on DID, is a tamper-proof digitalized virtual space that is not controlled by any business entities. As all our online activities become visible on-chain through DIDs, all our on-chain behaviors and our minds can be stored permanently on-chain.

  • When most of our daily lives happen in the Metaverse or in the digitalized world, all this data can be moved on-chain. AI can then simulate our behaviors, our languages, and our minds through machine learning. 4). Immortality is realized when even our close friends and family members cannot tell the difference between AI and us.

Highlights from KNN3

With the rapid growth of Web3 and everyone's concerned about their privacy, DIDs as the carriers for the digital world have come to the spotlight today.

Currently, KNN3 Network as an aggregator of relational data has integrated with different DID protocols such as Next.ID and .bit.

The presence of DIDs allows for a better container for building the reputation system and social graphs. Web2 and Web3 are more relevant to each other thanks to it. A user’s on-chain activities and reputation no longer point to a single wallet but to a more figurative actor.

As DID protocol and the application of ZK continue to take shape, privacy will be greatly enhanced on the basis of users fully owning their data. We expect DIDs to take a bigger role in Web3 social in the future.

Highlights from Next.ID

DIDs are equivalent to ID cards and passports in Web2. Whether we can build a distributed and secure DID system following the Web3 paradigm will be the first step of dApp construction.

At present, EOA (externally owned account) wallets such as MetaMask are still the mainstream for users to use Web3 services for identity authorizations. Meanwhile, some services such as Web3Auth which builds identity authorization in the Web2 manner don’t serve the purpose of self-sovereign identities and full data ownership.

Next.ID wants to allow users to completely have control over their own data through VPS (virtual private server).

Project Info

UniPass: UniPass is a multi-chain unified crypto identity and your universal passport to the crypto world and the metaverse.

• Official site: https://wallet.unipass.id/

• Open-source link: https://v1.tryunipass.com/login

MetaID: MetaID is a Decentralized Identity (DID) sub-protocol of Metanet, the next generation of the Internet.

• Official site: https://www.metaid.io/

KNN3 Network: KNN3 Network is a Web3 Relationship Aggregator on multi-chain to empower Web3 social discovery & user enabling.

• Official site: https://www.knn3.xyz/

Next.ID: Next.ID, the world’s first protocol offering Decentralized-Identity-as-a-Service (DIaaS) is moving into beta testing. It is a decentralized identity aggregation protocol that integrates all Web2 and Web3 digital identities, offering a comprehensive and verifiable identity database for open-source developers and projects to innovate and build dApps on.

• Official site: https://next.id/

• Open-source link: https://github.com/nextdotid

• Discord: https://bit.ly/NextID_Discord_Official

• For WeChat users: BinaryHB

• Bi-weekly community calls：

  • Bilibili: https://space.bilibili.com/1004643496

  • YouTube: https://www.youtube.com/channel/UC17C9xWKp0h_pZhfxbNtHsg

About WAMO Summer Dali Web3 Fest

WAMO Summer Dali Web3 Fest is a two-day camp in the picturesque province of Yunnan, joined by a group of decentralized and DAO communities. The fest brings together tech talents, entrepreneurs, incubators, projects, and DAO practitioners to connect people to build a better Web3.

节目中，嘉宾们共同探讨、分享了：对于 DID（去中心化身份，decentralized identity）以及 SBT（灵魂绑定通证，soul-bound token）的理解、它们之间的关系，已经看到哪些在赛道上构建比较实际的案例或者认可的方向，DID 与 SBT 落地过程中碰到的难题等。

在哔哩哔哩上收听回放：https://www.bilibili.com/video/BV1WW4y1B7U4

目前你对 DID 是怎么理解的？DID 已有应用场景有哪些？是否已有成熟 App 可以使用、体验？

LXDAO Bruce：DID 首先是 ID，ID 在现实世界可以类比：身份证、学生证等，虚拟世界有推特、微博账号等。DID 则是去中心化的 ID，没有签发、管理的机构，不会有被删除、封号的风险。现实中最接近的是护照，对个人身份进行证明，有一个统一的认可标准。

DID 其实已经有很多应用了。聚焦到以太坊上，以太坊上的 DID 可以认为就是地址。在 ENS 上可以绑定邮箱、地址等，如不考虑其它公链，我认为在以太坊上钱包就是一个 DID。在以太坊基金会上，他们也是这么介绍的。

HashKey Capital JZ：DID 直到最近一年才慢慢起来，早期大家觉得是很好的概念，但没有落地场景。去年以太坊域名火热了一把之后，大家觉得 DID 会产生一些价值并逐渐注重人们身份的价值。每个人身份不同的体现可以透过代币、机制体现出来。

现今 Web3 用户量仍较小，对于确定一个身份是真正的人还是机器人（bot），是很有用的。如何把价值确定下来，有可能通过 DID、SBT 实现，只是暂时没有确定的方向。

不能被删号的场景，互联网从第一天开始，如果用户选择自建网站，已经可以免去审查（censorship）。因为用户体验，Web2 放弃了这个做法。在 DID 的世界里，我们如何可以放弃建立在一个大的平台上搭建而是完全自主？（王建硕）

LXDAO Bruce：不被删号只是 DID 的一个特性，假设定义全网是以太坊的话，DID 是全网唯一的、通用的、用户可以完全掌控的 ID。用户可以通过 DID 连接到很多支持它的产品，这些数据只要在链上，都属于用户，不会被删除，或未被授权去产生交互，这是与传统账号最大的区别。传统账号许多平台之间还没有实现互通。

对 DID 的定义是什么？现在看到 3 种定义，一是 W3C 提出的 decentralized identifier（去中心化身份标识符），二是 decentralized infrastructure（去中心化基础设施），三是纯数学上的 ID，只需私钥就能生成公钥，不需任何软件和提前告知。（王建硕）

Next.ID 段少：我认可 Bruce 提到的护照，DID 抽象理解是一个串，背后身份本身涉及到两个问题：1. 这个串由谁定义；2. 拿到串之后的交互过程。

回到 Web2，类似护照之类的证件是由国家颁发的，用户可以使用这个“串”证明身份，资产不跟用户名字绑定，资产是跟身份证号绑定，只有通过身份证号才能拿到资产，对资产进行确权。粗暴地理解，资产的确权来自身份证号（或者说私钥），对外界来说是用户的名字。在链上或者以太坊上就是用户的地址。W3C 提到的标准是一个大一统的标准，Next.ID 天然兼容 W3C。

目前以太坊上的钱包，从目前跟大家讨论得出，钱包并不等同于 DID。钱包只是早期出现的产品形态，大家把它当成某种 DID 授权身份。现实世界中，用户的身份证丢了，资产不会随之消失，中心化的认证机构依然存在。在 Web3，当把公私钥的身份直接等同于金融账户时，如果私钥丢了，资产就没了。对 Web3 用户来说风险很大，以太坊社区已经认识到这个问题，他们正在发展智能合约钱包，对账户进行抽象，将身份层与金融层区分，即便资产丢失，仍能通过 social recovery（社交恢复）或者通过个人持有的一些秘密（等同于私钥），比如一些身份认证问题，来恢复账号的控制权，实现用新的私钥来控制资产，以便解决这个问题。目前 DID 等同钱包的认知是业界发展遗留下来的问题。

你对 SBT 是怎么理解的？SBT 是概念还是已经落地了？SBT 跟 DID 是互相可替代的吗？

HashKey Capital JZ：SBT 算作 DID 的一种，DID 是一个更大的集合，SBT 相对细分。一个人可能有很多 DID，但根据现有设计，一个人只能有一个 SBT，人的很多特性能够通过不同 DID 活动在 SBT 上体现。由于涉及用户隐私，用户不一定会选择持有 SBT。

SBT 研究员 夏禾：关于 SBT 提案较多，约 6–7 个，暂没有一个是通过共识的。SBT 本身名称可帮助我们更好理解，针对链上的傀儡账户与真实账户，能更好分辨账户真实性。

两个特征帮助 SBT 弥补区块链之前空白，一是它是由任何主体发起的，第二是它不可转让和交易。给了用户一个通道能把主观和感性的判断带到链上，而不是链上冰冷数字、交互记录。链上的数据是客观，链下的数据相对主观。针对“女巫攻击”，很多项目在用 Web2 的方式，比如填表格、进 Discord 验证身份等，而有了 SBT，可以帮助更好地筛选优质用户。

LXDAO Bruce：SBT 在未来会很重要，它能真正塑造身份画像。token（通证）可以类比现实世界的资产，一个人可以拿着一台车宣称这是自己的资产，SBT 可以证明用户的忠诚性，比如用户积极参与该车品牌的活动，具备凭证，这些信息是不可转让的，塑造了用户忠诚用户的画像。随之产生的应用比不可少，需要通过用户画像来了解一个人的身份，便于应用到面试等场景。

SBT 用什么的方式来确认一个人只能有一个账号？如何与 soul（灵魂）一一对应？（王建硕）

SBT 研究员 夏禾：SBT 没有实现一一对应。需要一套新的 SBT 标准，实现原生的、不可转让的。

理论上，当 SBT 的数据源都来自链上时，链上数据公开、透明、不可篡改，让我们可以完成清晰的判定账号之间的相似度，评分链上行为的真实性。

LXDAO Bruce：SBT 是 Vitalik 今年 1 月份左右发表博客提到，来自于他玩魔兽争霸的灵感。游戏中的道具非常稀有，需要绑定到魔兽争霸账号，在游戏体系内不可交易、转让。今年 5 月份他与微软研究员合作产出了 SBT 论文，描述、定义相对清晰。论文中对于 SBT 定义，没有提到 DID 概念，SBT 概念上对应 soul。灵魂类比现实世界的一个人，一个人的表现来自于过去的经历。可以用学位证、驾照类比 SBT，此类文件规定规则是只能有一个，有法律等的保障。SBT 本身价值来自不可转让、不可买卖。

Next.ID 段少：Next.ID 项目的定义里，DID 等同于公私钥对，公私钥对就是身份。SBT 相当于把和公私钥绑定的行为形成一个映射关系。只要最终判定映射关系，即可限定不可转让。用户可以生成多个身份，每个身份都是一个公私钥对。任一公私钥对都可以绑定 SBT，可以定义为一个灵魂。

魔兽世界里，一个玩家可以创建多个游戏角色，这个角色可以等同于链里面的一个 DID，只有完成特定任务玩家才能获取某个灵魂代币，即是通过 SBT 区分一个人是一个 trader（交易者） 还是 一个 builder（建造者）。Next.ID 认同的观点是一个 DID 可以有多个 soul，多个数字化身，每个数字化身绑上 SBT 后，即跟某个角色绑在一起。

如何杜绝作假？不杜绝。养大批量的账号的成本很高，不需要特别杜绝。

王建硕：理解了。其实 soul-bound token 更像 ID-bound token 或者 public-key bound token。跟灵魂、肉身、谁在使用没关系，它唯一绑定的是 ID，token 一旦发到 ID 上，就不可改变了。

DID 和 SBT 落地的过程中，遇到什么难题？你们在尝试用什么思路解决？

LXDAO Bruce：我们在做 Marry3，是帮助用户在 Web3 结婚的产品。已经有 56 对伴侣在上面结婚了。结婚证二者都有，是 SBT 且不可转让，也可以申请离婚，离婚后证书就会断掉。遇到的挑战是来自人们的质疑：比如如何跟链下的结婚证绑定在一起、怎么证明二者的结婚关系。我们不关心这个问题、也不关心背后是谁，更关注链上的两个地址，在虚拟世界中是我们所认为的灵魂。后期会新做项目来举办婚礼，吸引用户的朋友见证婚礼的举行，通过语音宣誓，见证人的公信力越高，越证明了这个 SBT 的价值，因为小号无法邀请到公信度高的人。不是所有人都能申请到一些东西、成本也有区别，维护 SBT 成本越大、SBT 价值越高。

我们在做的 LXDAO 也希望能招募一些优质的社区成员，会有审核机制，需要提交申请、面试，确认参加者之前没有参与过，具备一定技能、技术，之后才会颁发 SBT，给 SBT 赋予了价值，证明成员的 builder 身份。

灵魂与人的绑定，目前观察到两个产品，一个是 Binance 发的 BAB，Binance 可以中心化地管理用户的 KYC，能够获取用户信息，通过绑定到钱包地址，能知道该地址对应的账号，证明用户真人的属性。第二个是 BrightID，通过 Zoom 会议，绑定用户的人脸与地址，很多项目会使用 BrightID 的验证作为审核用户条件。

SBT 研究员 夏禾：SBT 没有通用标准，暂时还处于社交、社会概念之下，社交需要人的互动，Web3 用户基数还较小，一是需要在技术上有共识，二是需要更多用户。

王建硕：后期可以想象专门做指纹的哈希等方式，把人的肉身与链上的 ID 绑定，一旦这个关系建立，链上的事情解决起来会更轻松。现在遇到的问题是链上与链下的割裂，割裂的解决方案还非常有限。

对 DID、SBT 生态的寄语？如何让 Web3 对这两个领域产生重视、吸引更多的成员进来一起共建？

王建硕：期待概念清楚后，SBT 与 DID 能解决更多事。

SBT 研究员 夏禾：希望更多 builder 加入进来，或者有一些“毁灭性”事件让人们意识到 SBT 必须接入。

LXDAO Bruce：希望有更加实用的产品。现在协议过于底层，希望有更多应用，不管符合标准，先让大家看明白、理解。吸引用户上应该顺其自然，Vitalik 博客上已经告知了我们哪些地方可以深挖，LXDAO 已经在尝试构建。SBT 之类概念对于普通用户没有感知，除非能在日常中使用，才会有普及度。

Next.ID 段少：Next.ID 在探索 AuthService 以及 OpenID，关注身份如何与其它 dApp 交互，探索如何验证，欢迎大家有兴趣一起 build。希望 AuthService 能媲美 Web2 体验，或者接近持平，用户的迁移自然而然就会发生。

SBT 研究员 夏禾：希望更多 builder 加入进来，或者有一些“毁灭性”事件让人们意识到 SBT 必须接入。

LXDAO Bruce：希望有更加实用的产品。现在协议过于底层，希望有更多应用，不管符合标准，先让大家看明白、理解。吸引用户上应该顺其自然，Vitalik 博客上已经告知了我们哪些地方可以深挖，LXDAO 已经在尝试构建。SBT 之类概念对于普通用户没有感知，除非能在日常中使用，才会有普及度。

Next.ID 段少：Next.ID 在探索 AuthService 以及 OpenID，关注身份如何与其它 dApp 交互，探索如何验证，欢迎大家有兴趣一起 build。希望 AuthService 能媲美 Web2 体验，或者接近持平，用户的迁移自然而然就会发生。

嘉宾/项目信息

王建硕：百姓网创始人、CEO，@jianshuo

HashKey Capital：HashKey Capital（@HashKey_Capital）是一家专注投资区块链技术和数字资产的机构资产管理公司。

夏禾：Crypto/SBT 研究员，关注 ZK（zero-knowledge）、L2（layer 2）、SBT、database，以及 account abstraction 等领域，@0x30cF

LXDAO：LXDAO 是一个以研发为重点的Web3 DAO，聚集建造者，以可持续的方式建设和维护Web3 项目，官网地址：https://lxdao.io。

Web3Go Labs：Web3GO Labs 是一个专注 Web3 的创新实验室。第一阶段，将在实验室中搭建一个专注 Web3 的孵化器，全力支持全球 Web3 华人创业者。

Next.ID：Next.ID 是世界上第一个为去中心化身份提供服务的协议（DIaaS），即将开启公开测试。它是一个去中心化的身份聚合协议，整合了所有 Web2 和 Web3 的数字身份，为开源开发者和项目提供全面的、可验证的身份数据库，以便于创新和开发 dApps。

作为世界上第一个为去中心化身份提供服务的协议（Decentralized-Identity-As-A-Service, DIaaS），Next.ID 创建了一个身份基础设施，将用户的身份安全地聚合到 Avatars（即基于密码学生成的用户数字化身）。在 Web3 生态中，Next.ID 会成为各类去中心化社交协议和 dApp 的身份聚合关口。

官网：https://next.id/

开源代码：https://github.com/nextdotid

Discord: https://bit.ly/NextID_Discord_Official

社区双周会录制：

中文 B 站：https://space.bilibili.com/1004643496

英文 YouTube: https://www.youtube.com/channel/UC17C9xWKp0h_pZhfxbNtHsg

大理瓦猫之夏 DID 主题营地圆桌论坛是大理 Web3 街会分布式主题营地之一，由 Next.ID、UniPass、MetaID、KNN3 共同承办的一场线上、线下圆桌讨论，重点讨论了去中心化身份（dencentralized identities, DIDs）的构建、应用场景，以及想象空间。

以下为 DID 主题营地圆桌论坛精彩对话摘取。

1. 为什么我们需要 DID？目前的 ID 体系存在的最大的问题是什么？DID 会如何解决这些问题？

UniPass CEO 知县：DID 给用户提供了不依赖第三方也能够在网络世界证明自己身份的能力，它是整个 Web3 主权叙事的基础，可以说用户只有通过 DID 才能变成身份持有人。

MetaID 冯新宇：现在的 ID 体系主要问题是：用户数据都存在应用方各自的服务器里，由于各个应用方之间缺少信任机制，导致了数据割裂，形成了现在 Web2 世界的数据孤岛、数据不属于用户、用户围着应用转等局面。

而基于区块链技术的 DID 就可以很好解决这些问题。由于用户信息以及和用户关联的应用数据都存在链上，数据不可篡改近乎永久保存。同时也利用了区块链的无需信任和开放溯源的机制，基于 DID 的 Web3 应用可以做到数据不属于商业实体、应用之间数据可互联、互通，实现数据真正归用户所有。

DID 所带来的影响将是历史性的，没有 DID 的 Web3 也是一个伪命题，可以说未来 Web3 世界的基石一定是 DID。

2. DID 目前有哪一些常见的方案？各自的优势、劣势是什么？

MetaID 冯新宇：DID 和 Web3 一样处于早期阶段，各个团队对 DID 的理解也不太一样，确实导致了各个团队的 DID 方案的切入点和侧重点不一样。

有的方案基于智能合约，有的方案基于 EOA，有的则基于 UTXO 模型自定义一套数据格式。有的则从别名系统入手，有的从打造 C 端应用作为切入点。

可能大家最终的愿景都类似，但选择的切入点不一样可能导致发展路线的巨大差异，哪个路线更好可能有待观察。但有一个不变的评判标准的就是：哪个方案最早取得最多数用户的满意，这个方案就更大概率取得成功。因为 DID 方案很明显是一个网络效应很强的赛道，最终的结果大概率是赢家通吃。

MetaID 方案就是选择了基于 UTXO 模型的 DID 方案，从 C 端的 SocialFi 应用作为切入点，我们之所以选择 UTXO 模型而不是更多区块链开发者所喜欢的 EOA 或智能合约方向，是经过深思熟虑和反复测试的。

好处主要有三点：1. 更容易实现数据全上链；2. 更可能承载大量用户；3. 手续费非常便宜。这样更可能推动 Web3 应用的普及。代价就是 UTXO 路线上的开发者和币圈用户相对较少，起步可能更艰难点。不过好在我们经历了两年的发展，以有累积有 14 万用户和 20 多个应用了。

3. DID 走向大众和广泛应用的条件是什么？它对普通用户最大的价值体现是什么？离落地的愿景还有多远？现在最大的阻碍是什么？

UniPass CEO 知县：最重要的是要有足够吸引人的场景，其次是要大大降低用户使用 DID 的成本，提升用户体验。目前最大的阻碍是基础设施不足，场景介入难度比较大。

MetaID 冯新宇：我们认为，DID 要大规模普及首先要解决使用 Web3 应用的 gas 费问题。Gas 的获得方法现在大家都知道，对普通用户来说是挺曲折的过程，而且大部分的 gas 费也不低。

因此 DID 普及优先要满足两点：1. 要让 gas 费足够低；2. 让用户可以法币支付 gas 费，但又不能触碰到 gas（即不能反向兑换）。我们 MetaID 相关的 gas 费足够低，并且我们最近半年也花了很大力气在用户无需拥有 gas 即可使用 Web3 的功能模块上。法币用户现在也可以很简单进入了。

基于 DID 的 Web3 应用能给用户带来很多好处，但很多好处其实是用户短期内感知不到的。比如：数据真正归属于用户，数据不可篡改，数据永久保存等，这些其实用户并不太关心。因此给用户带来的直观好处我觉得需要等大量的 Web3 应用出现，Web3 应用的相互可组合性以及数据互联、互通，打破信息孤岛后，才能彻底体现出来。这个过程不是一个短期的时间，这意味着 DID 是一个道阻且长的赛道，但也是一个后期爆发力很强的赛道。

4. 以 MetaMask 为首的钱包，已经大面积成为 Web3 服务通用的用户身份层。这能称之为 DID 吗？它有什么问题？

UniPass CEO 知县：我认为钱包和 DID 是两个不同的场景，是底层的密钥管理能力在不同业务方向上的应用。

目前的 MetaMask 产品导向还是钱包场景，没有对 DID 场景做专门的优化，比如：降低用户进入的门槛以达成更大规模的用户量，以及提供权限管理能力让用户账户的安全性和稳定性更强。相比之下 UniPass 在 DID 场景下可以提供更低的进入和使用门槛，更灵活的账户权限控制等对 DID 场景的支持。

MetaID 冯新宇：这看怎么定义 DID 了。MetaMask 暂时实现不了数据互联、互通，跨链层面也不能统一身份。而且 MetaMask 早期定位只是一个钱包，钱包解决的问题是“钱”的身份问题。DID 更多的是解决“数据”的身份问题，需要有一个为 DID 很好适配的钱包。我们也在往这个方向努力，但 MetaMask 显然暂时还不满足 DID 钱包要求。

5. DID 与社交图谱的关系？Web3 时代如何构建自己的 DID 以及声誉系统呢？声誉体系可否替代 token 在 DAO 中代表投票权重？非货币化的社会关系网络如何搭建？这又是否会成为新的空想社会主义呢？

MetaID 冯新宇：如果基于 DID 的 Web3 应用普及的话，由于数据互联、互通，那么用户在链上就只有一个社交图谱了，这可能是一个全新的体验。比如一个新的社交应用上线后，举例抖音刚开始的时候，用户之前的微信、微博所累积的声誉、关系就可以无缝切换过去。用户将开始极度注重自己的行为。

因为有了 DID 后，用户在网上就和其他用户形成了一个可持续重复的长期博弈过程。声誉就是每个用户身份最重要的资产。

声誉体系代替 token 作为一个权重，在很多场景是可行的。token 只是代表你投入金钱的多少，这在一些以分配利益和金钱的场下是合适的，比如公司的分红等。但很多场景用 token 来划分是不合适的。比如一个作者组成的 DAO，凭什么让大户来做决策？这样的场景显然是根据声誉做权重会更合适。

其实自古以来，在乡里部落里，都是由德高望重的长老来掌握大的投票权重的，而 DID 就可以用一个量化的指标来定义什么是德高望重。

6. DID 强调数据互联、互通，数据有所归属，如何在这个背景下平衡好用户数据的隐私、公开和匿名的关系？

MetaID 冯新宇：隐私是 Web3 应用中很重要的一个环节，也是衡量 DID 方案好坏的一个重要标准。一个好的 DID 方案我认为应该是注重隐私保护而不鼓励匿名的。

因为匿名将不会带来更美好的社会。MetaID 方案在隐私保护中做了很多工作，比如我们最新的方案还引入了零知识证明，还有我们创立了 MetaAccess 的方案，应用能否访问用户的数据还需经过用户授权。但由于整体数据都是在 MetaID 的树状结构呈现，因此难以做到完全匿名。而且我们认为在 DID 普及后，匿名发言和社交将不会有任何优势。

我认为在未来 Web3 世界中，匿名的情况将会更少出现。

7. DID 中的 SBT（soul-bound tokens，灵魂绑定通证）会以什么形式体现？

MetaID 冯新宇：其实某种意义上 SBT 就是一个次级 DID，或一个好的 DID 方案本身就是一个 SBT。

8. DID 与 NFT，DAO，DeSoc 之间的关系？

MetaID 冯新宇：DID 与 NFT，DAO，DeSoc 之间的关系 DID 是一切功能性 NFT、一切实用性 DAO 和 DeSoc 的基础。现在大部分的 NFT、DAO 和 DeSoc 都缺少 DID 作为基础，这是不可能实现真正普及的。原因很简单，具有了 DID后，这些不同的 Web3 应用、NFT 等才可以在数据层面连成一片，这样数据联通所带来的网络效应将会对没有 DID 的孤立应用会形成碾压性的优势。

9. 从 DID 到元宇宙虚拟永生蓝图

MetaID 冯新宇：我认为，DID 是未来 Web3 和元宇宙的基础，没有 DID 的 Web3 和元宇宙都是伪命题。

基于 DID，配合上 AI 技术的发展，我们确实有可能在未来元宇宙数字世界中达到意识永生。因为基于 DID 的 Web3 或元宇宙可以让我们未来生活在一个不可篡改的，不受任何一个商业实体控制的数字化虚拟空间里。当我们一切上网互动、一切的现实行动等数据都通过 DID 上传到链上，我们就能永久保存我们所有的行动和思想。

当我们日常生活大部分都在元宇宙或数字化世界中时，我们所有生活全部均数据上链，AI 便可以通过机器学习来模拟我们的行为、语言、性能以及思想。日后 AI 程序所模拟出我们的思想和言语到连最亲密的亲人好友都分辨不出来时，这时某种意义上就实现“永生”了。

KNN3 胜阳

DID 作为数字孪生的载体，在 Web3 迅速成长和大家对隐私关注的今天，成为热门的话题。目前 KNN3 Network 作为关系数据的聚合器也集成了不同的 DIDs，比如 Next.ID 和 .bit 等。

相较与目前 MetaMask 为首的钱包用户身份层，DID 的存在使得在构建声誉系统和社交图谱时有了更佳的容器，使得链上的行为和声誉不再指向单一的钱包地址，而是具像化背后的操作者，使 Web2 及 Web3 不再是孤立的世界。

随着 DID 协议的不断完善和 ZK（zero-knowledge，零知识）的应用，DID 在数据属于用户的基础上，隐私性也会大大提升，未来我们期待 DID 在非货币化投票和社交网络中发挥更大的作用。

Next.ID 社区经理 段少

作为和 Web2 世界里身份证、护照一样分量的系统，是否能循着 Web3 范式打造出这样一个分布式的、安全的 DID，是 dApp 构建的第一步。

眼下，以 MetaMask 为首的 EOA 类型钱包，基本成为了目前 Web3 服务中需要使用“身份”授权时的主流。同时，一些继续按照 Web2 中心化的方式构建身份授权的服务，如 Web3Auth，并没有解决用户对自己数据宣示主权的根本目的。

Next.ID 希望通过 VPS（virtual private server，虚拟专属主机）的方式，让用户对自己的数据拥有完全的决定权。

项目方产品、开源地址

UniPass

简介：UniPass Wallet 是一个支持邮件社交恢复的智能合约钱包解决方案。通过 UniPass Wallet，开发者可以提供免私钥的、免手续费的用户体验，从而快速地吸引海量的 Web2 用户。

UniPass Wallet 支持任意代币支付手续费，可兼容所有主流 EVM 链，并将覆盖网页版、移动端、浏览器插件全平台，支持多种调用方式。UniPass Wallet 兼容最新的 ERC-4337 账户抽象协议，是领先的智能合约钱包解决方案。

官网：https://wallet.unipass.id/ 开源地址：https://v1.tryunipass.com/login

MetaID

简介：MetaID 是一个经历了两年考验的开源开放分布式 ID 协议，获得了剑桥大学区块链大赛“Phoenix Challenge”第二名。基于 MetaID 可实现用户只需要一个私钥就可以使用所 MetaID 应用，应用之间互联互通打破信息孤岛，应用数据可根据协议相互组合等特点。

现在已有超过20款基于 MetaID 的 Web3 应用，共有 14 万用户。这些应用涵盖 SocialFi，NFT，游戏等领域。下一步 MetaID 还可支持跨链适用于 UTXO 模型同构链，实现 UTXO 区块链之间的数据联通。

官网：https://www.metaid.io/

KNN3

简介：KNN3 是一个用于探索 Web3 关系数据的图形数据解决方案，与 TheGraph 等许多Web3 数据解决方案类似，KNN3 提供 GraphQL API 供 Web3 开发者使用。

官网：https://www.knn3.xyz/

Next.ID

简介：Next.ID 是世界上第一个为去中心化身份提供服务的协议（DIaaS），即将开启公开测试。它是一个去中心化的身份聚合协议，整合了所有 Web2 和 Web3 的数字身份，为开源开发者和项目提供全面的、可验证的身份数据库，以便于创新和开发 dApps。

作为世界上第一个为去中心化身份提供服务的协议（Decentralized-Identity-As-A-Service, DIaaS），Next.ID 创建了一个身份基础设施，将用户的身份安全地聚合到 Avatars（即基于密码学生成的用户数字化身）。在 Web3 生态中，Next.ID 会成为各类去中心化社交协议和 dApp 的身份聚合关口。

官网：https://next.id/

开源代码：https://github.com/nextdotid

Discord: https://bit.ly/NextID_Discord_Official

添加社区经理微信：BinaryHB

社区双周会录制：

• 中文 B 站：https://space.bilibili.com/1004643496

• 英文 YouTube: https://www.youtube.com/channel/UC17C9xWKp0h_pZhfxbNtHsg

关于大理 Web3 街会

大理 Web3 街（gāi）会「瓦猫之夏」是一次由一群去中心化的、DAO 的参与者组成的 Web3 社交大会，是大理社区与 Web3 文化的展示，也将顶尖的技术人才、创业者、孵化器和项目方团队以及 DAO 的践行者聚集在一起，彼此深度对话、相互联系和共同创造。

The internet was born in 1989, thanks to the legendary Tim Berners-Lee. It looked like this:

According to Insider, this is what the first-ever website looked like in 1992.

Today, the internet looks different. For one, there are colors. Even the most basic of websites feature more HTML code than the first-ever website created. For another, hundreds of thousands of people are learning, exploring, and growing the entire ecosystem.

How did we get here? What is here? And where do we go from here? To properly understand this, we need to dive into what digital identities are and how they shape the worldviews we have of the internet.

What is a digital identity?

In a nutshell, our digital identities are how we understand our relationships to the internet.

Take, for example, your passport. As long as you hold it, you have a claim over your birth name and birth date. We can call this your physical identity. As long as you hold your passport, you have rights in your home country that tourists don’t.

Similarly, your Digital Identity gives you rights online, depending on how you use it. We’ll delve into them later, but it’s important to recognize that whenever you do anything online with your digital identity, you will knowingly leave “footprints” behind in the form of posts you create, but also unknowingly leave “footprints” behind in the form of cookies and metadata.

Now that we have a high-level understanding of Digital Identity, let’s go back in history and take a chronological look at how it has evolved over time.

Digital Identity in Web1 (the “Read-Only” phase) from a user’s perspective

Scroll up and look at the first picture in this article again. Text and hyperlinks. Those were what made up the majority of Web1, which is why it was known as the read-only phase of the internet. Pictures came later, and when Dr. Fun, one of the first webcomic platforms, was published, it was heralded as “a major breakthrough for the Web” by the National Center for Supercomputing Applications.

Where did Digital Identity come into play against such a landscape? This is a bit of a trick question as Digital Identities were not accessible to the masses. The level of interactivity was so limited that you couldn’t even enter your email address to get sent updates from your favorite creators — the functionality hadn’t been invented yet.

What does this mean for users?

In Web1, we were all limited citizens — perhaps even ghosts — who were only allowed to interact with basic text and hyperlinks that site owners have put out. We were spectators who did not feel any sense of ownership over anything seen online, and this is part of the reason using the internet in those days was so transitory. It was purely window shopping, nothing else.

Digital Identity in Web2 (the “Read-Write” phase) from a user’s perspective

Then things started to change. The infrastructure got better, more people started recognizing the value of the internet, and the invention of a new beast — social media — started a complete revolution.

With this heightened interest in the internet, major giants started appearing. You may have heard of some of them: Facebook, Google, YouTube, Twitter, and Neopets just to name a few. Interactivity was key to getting users on their platforms, as the more we could play games, watch videos, or talk to friends, the more of our time we were spending on these platforms, and the more advertising dollars they got.

This is where Digital Identity really started to form: you needed a form of identification for interactions online to be meaningful. It was a win-win solution: you were able to interact with others online and companies were able to get feedback on what you wanted to do online.

Phase 1: Siloed identities

• Username + password logins

• Email addresses

• Mobile phone numbers

A virtual pets website, Neopets, has used siloed identities since its launch in 1999.

The initial stages were pretty much a free-for-all among digital companies. As they were figuring out how to engage with users, they started creating the very first forms of “digital identity”.

Think of these “digital identities” as membership cards — they were recognized by the card issuers but nowhere else, essentially making them siloed. Siloed identities are still common today. Most websites that enable signups or subscriptions allow you to create a new login which you can then use to interact with the website.

Phase 2: Federalised identities (via the OpenID standard)

• One-tap logins across multiple platforms

• E.g. Sign in with Facebook/Gmail

Spotify allows logins via federalized identities.

Not all internet-native companies are created equal. With the incredible growth of tech giants like Facebook and Google, we soon saw attempts at creating federalized identities. Federalized identities are created via the OpenID standard, which enables you to provide your details to one provider, who is then authorized to share this with other websites you visit. The OpenID standard has been adopted mainly by the bigger tech companies who are aiming to integrate users into a larger ecosystem of apps.

Note: OpenID is an open-sourced standard created in 2005. Since then, there have been over 1 billion OpenID-enabled accounts, with over 50,000 websites accepting them.

At first glance, federalized identities are a win-win-win solution for users, the tech giants, and the platforms that integrate the federalized identities. After all, this system leads to a much quicker signup process for users, tech giants increase the scope of their data collection with minimal work, and the platforms gain access to a wider range of users.

However, if we looked deeper into how it’s set up, we’ll soon notice a few issues with digital identity in Web2, all inherent to the fact that we’re using third-party platforms:

• Censorship may occur at any time

• Our data is being sold without consent

• Data breaches may occur

• We don’t own our identities

This is not meant as a criticism of Web2, it is showing that there can and will always be improvements to be made.

What does this mean for users?

Web2 so far has shown us a glimpse of what is possible with Digital Identity. It was the first time “normal” people from one corner of the world could interact with friends from the opposite corner in split seconds. Social media itself has been a beast of revolution, upending how we interact with friends and even strangers.

While Web2 users are happy with their experience so far, this will only continue for as long as tech giants and the platforms they use act in a benevolent way. In essence, on Web2, We are children, able to make some choices but the moment our parents (i.e. tech companies) get upset, we have no choice but to obey them. This happens most obviously in cases of censorship and data privacy.

This brings us to…

Decentralized Identities (the “Read-Write-Own” phase) from a user’s perspective

Now we’re on the cutting edge of technology. The path forward is always being paved, and for all the good that Web2 has brought us as digital citizens, it’s time to stop renting digital space and become homeowners for ourselves. After all, if the Web1 to Web2 revolution brought such drastic changes, imagine what the Web2 to Web3 revolution will bring.

Web3 differs from Web1 and Web2 because it operates primarily on blockchain technology. Being on-chain provides new advantages such as everyone being able to own part of it, allowing projects to be community-owned (i.e. decentralized).

Decentralized Identities are digital identities that are generated by a completely neutral protocol, generated from pure math. Put simply, imagine if a large corporation like Google or Facebook were issuing identities, except for decentralized identities, the “issuer” is Math. This completely eliminates the possibility of the issuer selling your data or spying on you without consent.

What does this mean for users?

While Decentralized Identities are not yet in mainstream use, it effectively demonstrates how Web2 Digital identities’ main weaknesses can be nullified: take decision-making power away from the identity issuer and they won’t be able to sell or use your data without your consent.

The driving motivation for Decentralized Identities is for users to own their own identities and not rely on centralized third parties for verification. This is a huge step. We are now adults, having graduated from “renting” space from tech giants and able to interact directly with protocols with self-owned identities.

Why we need to understand Decentralized Identities

Decentralized identities are important because of the growth of social protocols. Many such protocols are decentralized and permissionless, so if the decentralized identity is integrated into these social protocols, you’ll 1) own your identity and 2) have an uncensorable platform.

Now, imagine you have an ID/passport/driver’s license. Every time someone else uses it, they need to crack an unbreakable (cryptographic) code. Only you, who can prove your identity, get free access to it. This future is made possible by the cryptographic technology that enables Web3, and may well be a cornerstone of decentralized identities.

Because the decentralized identity space is still evolving, there are competing ways of determining identity:

• Verified Credentials

• Holding a “badge” or a “Verified Credential” in your account could verify that you’re a member of a community

• Soulbound NFTs

• Same as Verified Credentials, except Soulbound NFTs cannot be transferred and are permanently associated with your wallet

• Referral networks (like Proof-of-Humanity)

• Using word-of-mouth to create a community of verified accounts. Proof-of-Humanity does this by requiring existing community members to refer their friends to the network

Where Next.ID fits in this Digital Identity landscape

Now that we’ve covered most of what you need to know about Digital Identity, let’s take a look at where Next.ID fits in. Next.ID is the world’s first Decentralized-Identity-As-A-Service (DIaaS) protocol, with the goal of creating a home for all digital identities, ultimately integrating digital identities from both Web2 and Web3.

With a community-centric approach and the ultimate goal of decentralization, the founding members of Next.ID has laid the groundwork for its success by pioneering 3 pieces of technology: ProofService, KVService, and RelationService.

Together, these 3 technical breakthroughs create the foundation for Next.ID.

• ProofService uses a blockchain-like model to store data and retain data integrity using cryptography, ensuring that only users with the correct private keys can make changes to their identity.

• KVService’s full name is Key Value Service. It’s a framework to store key information, facilitating developers in creating new use cases.

• RelationService aggregates existing IDs, ID queries, and IDs bound to and in parallel to Next.ID, opening up possibilities for integration with external projects and creating more native social use cases

The Next.ID strategy is simple: we want to build a public good that benefits every user of the internet, from Web2 to Web3, and anything that comes after.

We want to build an ecosystem that wins and helps other projects win. Our long-term goal, as you can see from the roadmap below, is to eventually build a framework for normal everyday users to self-host their data, creating a properly-decentralized world with all the liberties it promises.

Next.ID roadmap

If you’re interested in building with us, check out docs.next.id or reach out to us at developer@next.id. Follow us on Twitter: @NextDotID.

Next.ID hosted DID Summer Episode 2 on 2 Aug 2022 with Web3 developer communities & builders from Minority Programmers, Her DAO, 0xCorgis, and Developer DAO. In line with the vision of building Next.ID into a DAO, the core team organized this AMA to create awareness and reach out to potential developers and community members.

Next.ID comprises of 3 main services:

1. ProofService

2. KVService

3. RelationService

The session started with a product demo illustrating the back-end mechanics followed by an in-depth explanation of each individual service. Other developer communities were invited to familiarize themselves with Next.ID’s vision, so as to allow for open-source building and collaborations.

You can watch the full episode on YouTube: https://youtu.be/sVVXA5gxHzM

Key Takeaways:

• In existing identity systems, users do not fully own their digital identities. Web2 social media companies have control over our online data and privacy. Our accounts and content can easily be censored or deleted by these companies. Next.ID aims to solve this issue by returning ownership of digital identities back to users.

• Next.ID’s ProofService, KVService, and RelationService are in-house developed identity management services that allow users to aggregate identities across Web2 and Web3 via Avatars. Developers are free to brainstorm and leverage Next.ID’s back-end API/protocol to build their front-end applications.

• Next.ID is exploring ways to incentivize community members to get involved in the development of its DAO. We want to find a solution to provide the best user experience without compromising user privacy.

• ProofService is the core DID management service that aggregates all identities across Web2 and Web3.

• KVService allows users to store data off-chain on Arweave, without sacrificing the user’s ownership of the data. Cryptography and public-private key pairs are used to validate the data and only the user gets to modify it.

• RelationService builds a robust connection tree between the network of identities. It contains upstream data collected from third parties which are then combined to build a more comprehensive identity database. Examples of on-chain Web3 protocols include RSS3, CyberConnect, and LensProtocol. Examples of off-chain Web2 parties include Keybase and ProofService.

• Common misconception from Q&A: Next.ID DID aggregation does not happen on the blockchain. Instead, it uses ProofChain which is a model that builds trustless authentication.

For anyone who is interested in future Twitter Spaces & Discord AMAs, please follow Next.ID @nextdotid. We will be hosting more similar events and will continue to invite more industry leaders and emerging Web3 builders to talk with us.

Speaker Info:

• Minority Programmers

• Her DAO

• 0xCorgi

• Developer DAO

• Product Demo: Wei Duan, Community Manager at Next.ID

• AMA Respondents: Yisi Liu & Nyk Ma, Core Engineers at Next.ID

• Host: Hannah Shen, Head of Global Growth at Next.ID

Project Info:

• Minority Programmers is a global network of developers unified to spread STEM education & build socially impactful dApps

• Her DAO is a women-led developer DAO championing innovation, diversity, and women-led ventures

• 0xCorgis is a developer advocate who aims to make code cute and informative

• Developer DAO is a community of people who are interested in participating, learning, and contributing to the future of Web3.

• Next.ID is the world’s first Decentralized-Identity-as-a-Service (DIaaS) protocol

DID Summer is a Twitter Space series by Next.ID where Web3 projects and builders gather and exchange ideas on building cutting-edge decentralized identity infrastructure and applications.

____

Timestamps:

00:00 Welcome and intro

2:08 Product demo introduction

4:20 ProofService step-by-step

11:07 Community Governance

12:41 Quick summary of demo

13:51 Round-table discussion

16:33 Vision and progress for Next.ID

23:50 Her DAO’s thoughts on the Web3 DID space

26:02 0xCorgi’s take on open-source identity management

27:52 What is DIaaS (Decentralized-Identity-as-a-Service)?

33:10 Mission and plans for the respective guest communities

38:10 How can community members participate in Next.ID’s development as a DAO?

44:00 Explanation of ProofService, KVService, RelationService

55:00 Q&A

For anyone who is interested in future Twitter Spaces & Discord AMAs, please follow Next.ID on Twitter at @nextdotid. We will be hosting more events and continue to invite more industry leaders and emerging Web3 builders to share their thoughts.

如果 Web3、区块链技术有共同为人们所诟病之处，便是数据难理解。有时，开发者提到关于 Etherscan 或其他区块浏览器的新想法时，会比较晦涩难懂，这也是令新加入 Web3 的人产生困惑的主要原因。

Web3 发展得越快，人们对数据产生的途径了解的需求越大。

KNN3 基于此应运而生，其以图谱或图片的表达形式，对链上关系作简洁呈现。虽然 KNN3 是偏后端的协议，但它能帮助开发者在更简单、更易懂的界面上做开发，有效降低了面向消费者的 dApps 开发的技术门槛。KNN3 的目标是实现完全由社区主导，促使更多应用在链上进行数据合作。

KNN3 与 Next.ID 合作案例分析

KNN3 是一个社交图谱协议。当用户在区块链上交互留下记录时，KNN3 会聚合这些记录来说明用户之间的联系，将这些联系通过关系节点来展示、呈现。这些都是 100% 在链上可验证的。

Next.ID 则是去中心化的身份服务协议（DIaaS），聚合 Web2 和 Web3 的数字身份，支持用户创建无需许可的 DID（decentralized identifier，去中心化身份），即 Avatars（数字化身）。

KNN3 无需任何许可即可接入 Next.ID，引入 Avatars，从而给 KNN3 的社交图谱增添新功能：

• 数据的组成现在可以以身份先行；

• Avatars 提供链下身份数据，帮助 KNN3 建立更全面的用户账户资料。

身份先行的数据

KNN3 以中立的方式聚合数据，赋能社交 dApps 和 AI 分析。而 Next.ID 则提供看待数据的主观视角，聚焦身份关系的梳理。

KNN3 和 Next.ID 的合作，可给 KNN3 现有的技术成就增添新维度，开启社交图谱和社交网络的新范式。

跨越 Web2 和 Web3 的全面数据

一方面，KNN3 专注聚合区块链数据，另一方面，Next.ID 通过提供、补充 Web2 数据的访问来弥补盲点。如果用户将其 Avatars 与 Web2 账户（如 Twitter 和 Discord）相关联，KNN3 就能访问这些关联关系，给用户提供更全面的社交图谱。

有了这些社交图谱，开发者和用户都能更顺畅地体验 Web3，感受全新的使用场景，如社交关系对应或朋友推荐，也能够体验一个更为可靠的声誉系统。

社区贡献者推特：@zengjiajun、@sohchris。

Next.ID hosted DID Summer Episode 1 on 20 July 2022 with Decentralised Digital Identity (DID) Web3 builders — KNN3, Collab.land, Ceramic, .bit and Unipass. Representing various types of DIDs with different use cases, they set aside some time to discuss the importance and use cases of DIDs.

They shared diverse perspectives on DIDs, such as how ownership of identities can enable greater use cases. Use cases include proving one’s humanity beyond wallet addresses and this could even bring about real-world use cases beyond Web3. These builders also shared their project’s roadmaps and their thoughts on DID’s future outlook.

You can watch the full episode on YouTube: https://youtu.be/tE1cw6HXJTQ

Key Takeaways:

• In current identity systems, we, as users, do not own our identity. However, this has enabled third parties like Web2 social media companies to remove our content and even our accounts.

• Decentralized Digital Identities (DIDs) are important as they give us ownership over our identities and thus our voice in the world. Ownership enables us to:

  1. Own and claim credentials

  2. Build our financial and social reputation

  3. Build our relationships and connections with others

  4. Blend our IRL and digital identities

• DIDs are bringing ownership of individual identities via private wallets and NFTs. More forms of identification may be expected to emerge as projects find more ways to decide what constitutes the user’s DID.

• DIDs enable us to identify ourselves beyond our wallet addresses, proving our identities in a more holistic and colorful manner. This includes:

  1. Aggregation of our Web2 & Web3 identities

  2. Contextualization of our social connections with others

  3. Verifiable credentials that build our social and financial reputation

• DIDs prove our individuality — DIDs use proofs such as verifiable credentials to validate identities. Using DID protocols, we are able to validate IDs, eliminate bots and enable different types of governance.

• As we build the identity infrastructure for dApps, we can expect future use cases such as:

  1. Alternative governance and voting models

  2. Integration of SBTs and DIDs to create a trustless mechanism in Web3 social

  3. Greater coordination of Web3 social activities

For anyone who is interested in future Twitter Spaces, please follow Next.ID @nextdotid. We will be hosting more events of this kind, and continue to invite more industry leaders and emerging Web3 builders to talk with us.

Speaker Info:

• Yisi Liu, Founder & CTO of Next.ID

• Thomas Yu, Co-founder of KNN3

• James Young, CEO of Collab.Land

• Lauren Feld, Head of Growth at Ceramic

• Vicky, Director of Global Market at .bit

• Iris, Head of Business Development and Strategy at Unipass

• Host: Hannah Shen, Head of Global Growth at Next.ID

Project Info:

• KNN3 is a Web3 relationship aggregator on multiple blockchains

• Collab.land leverages the power of identity through cryptocurrency to create a social space unique to a specific network of humans.

• Ceramic is a decentralized data network that brings unlimited data composability to Web3 applications.

• .bit are Web 3.0 identities for you and your community

• Unipass is a universal passport to the metaverse

• Next.ID is the world’s first Decentralized-Identity-as-a-Service (DIaaS) protocol

DID Summer is a Twitter Space series by Next.ID where Web3 projects and builders gather and exchange ideas on building cutting-edge decentralized identity infrastructure and applications.

If Web3 and blockchain technology have a common criticism, it is that data is extremely hard to make sense of. It sometimes feels as though developers speak a completely different language as they discuss their findings on Etherscan or any other block explorer, and this is a major cause of friction for newcomers into the Web3 space.

After all, the quicker Web3 grows, the greater the need for avenues of understanding the data that comes out of it.

Enter KNN3. KNN3 is a direct result of this environment, providing simple-to-understand explanations of on-chain relationships in graphic/pictorial form. Although it is primarily a backend protocol, KNN3’s existence enables and facilitates generations of developers to build on an easy-to-translate interface, effectively lowering the barrier of entry to build consumer-facing dApps.

Ultimately, KNN3 aims to be completely community-driven, in order to unlock greater applications of on-chain data collaboration.

How KNN3 works with Next.ID: A case study

KNN3 is a social graph protocol. This means that as users generate footprints on blockchains, KNN3 aggregates these to interpret the connections among users, converting them into relational connectors. All 100% verifiable on-chain.

Next.ID, on the other hand, is a Decentralized-Identity-as-a-Service (DIaaS) protocol that aggregates digital identities across Web2 and Web3, allowing users to create permissionless DID (decentralized identifiers) called Avatars.

With the permissionless integration of Next.ID and the introduction of Next.ID’s Avatars, KNN3’s graphs are given brand new life:

• there is now an identity-first component to the data

• Avatars provide off-chain identity data for more comprehensive profiles

Identity-first data

KNN3 aggregates data in a neutral manner, allowing for the eventual empowerment of social dApps and AI analytics. Next.ID provides a subjective perspective of the data, with a focus on streamlining identity.

This allows for work done with KNN3 to take on a completely new dimension, using the synergy between KNN3 and Next.ID to create new forms of social graphs and networks.

Comprehensive data across Web2 and Web3

As KNN3 is focused on aggregating blockchain data, Next.ID covers one blindspot by providing access to Web2 data as well. If users’ Avatars are connected to their Web2 accounts like Twitter and Discord, KNN3 will now have access to these connections, allowing it a much more comprehensive view of the social graph.

Based on the Avatars’ associations of users’ Web2 (Twitter) and Web3 (blockchain wallets) accounts on Next.ID, KNN3 can now provide users with social graphs mapped across Web2 and Web3. With these graphs, developers, and users will have a more streamlined experience of Web3, as well as access to previously unheard of usage scenarios like social relationship discovery/recommendation and a robust reputation system.

Contributed by: @zengjiajun and @sohchris

We identify in many ways: our races, our nationalities, our genders, and our favorite sports teams. Being able to articulate our identities helps us create 1) a sense of self, complete with goals and hopes, and 2) a sense of community, where we co-exist with like-minded people.

As technology advances, we find new ways to self-identify.

Take for example the NFT boom in 2021. It allowed entire clusters of people to identify as all sorts of cartoon animals and even aliens online. While we’re not going to get into how NFTs work, suffice to say that groups of people who had NFTs from the same collections found commonality with each other, strengthening their bonds.

The evolution of Digital Identity

Over time, as our digital identities evolve to be more similar to our real-life ones, it is important to discuss — beyond NFTs — how identity may evolve on digital platforms.

Digital identity has evolved over the past two decades and it consists of 3 phases:

Current

If you’re above 25, there’s a chance you’ve had experience with the first 2 phases.

★ Siloed Identity — Users create an account for every platform used, managing multiple usernames and passwords for each site.

Eg Neopets, Hotmail

★ Federated Identity — Users create an account with centralized providers that give them access to multiple sites, trusting the providers with their data.

Eg Google, Apple ID

Future

We are now at the cusp of an identity revolution, with the introduction of a new form of digital identity: the DID.

★ Decentralized Identity (DID) — Users create and own an account that has access to multiple sites, maintaining full ownership of all data.

Eg Next.ID

The current problems with Digital Identity

Having a Digital Identity on the internet today means having to deal with a few recurring issues, some technical and some behavioral. We’ll delve into them in this section.

• Censorship and sale of data without consent

Centralized organizations currently dominate the internet. Personal data is commercialized and placed into the hands of third parties who can do anything they want with it. This leads directly to the first problem: the censorship and sale of user data.

We use the internet to catch up with close ones, for work, and to stay up to date with current affairs. How we do this is by signing up with centralized services, clicking through their indecipherable terms and conditions, then “renting” their bandwidth to interact with others online.

It is “normal” at this stage to consent to giving our data away without a second thought, giving tech titans like Google and Facebook a final say over our digital footprints. As a result, our data is sold to third parties, any statements we make can be censored without cause, and our online profiles can disappear overnight.

• Identity Ownership and Privacy

How would you feel if someone could walk into your home at any time of the day, peer over your shoulder as you do your daily activities, then broadcast this information to anyone they wanted to?

That’s effectively what centralized platforms can do today, given how intrusive their terms and conditions are. Your private messages with a lover? It belongs to them. That post you wrote that unexpectedly went viral? It belongs to them. How often do you log in and at what times? Even this data, which you may not be privy to, belongs to them.

The relationship is extremely one-directional — they see and hear all we do. And in extreme cases, they’ve reportedly even used this data to shape political opinions at the behest of politicians — even during election seasons.

• Data security

Having user digital identities and data stored in centralized servers is a ticking time bomb. We’ve seen this in multiple hacks across the years, ranging from the probable to the improbable. Banks have been hacked. Tech giants have been hacked. Even government institutions have been hacked.

User data is quite possibly the single most valuable commodity in the world today. With the right amount of data, analysts can predict and possibly even initiate global and local trends. And yet, when centralized platforms succumb to hacks, there’s little they do other than apologize and — if we’re lucky — get a small slap on the wrists by relevant government regulators.

How does Web3 solve Web2’s Digital Identity Problems?

Not all hope is lost. In recent years, breakthroughs have been made in blockchain technology. The issues above are fixable using blockchain, cryptography, and decentralized networks. Here’s how:

• Blockchains allow all users to own — not rent — their space

In Web3, Digital Identities are created and stored on blockchains. Blockchains are decentralized networks maintained by multiple validator nodes (i.e. computers) that run 24/7. While platforms in Web2 run and maintain their networks, blockchains operate on a different incentive structure.

When blockchain users interact with the chain or any decentralized apps (dApps) that are built on-chain, they’re not required to “sign up”. They simply generate a private wallet using cryptography*, allowing the user and only the user access to the account. Using this account, users have permissionless access and are able to interact with anyone or any dApp they want to. This means that there’s no centralized entity that can censor your data, just as no centralized entity that can sell your data.

It is a new paradigm of freedom online.

*It sounds difficult, but dApps like MetaMask and WalletConnect simplify it for beginners.

• Identity ownership given back to users

Having our Digital Identities stored on blockchains means that all our activities cannot be tampered with. When an interaction is performed by a user, we know for a fact that the user was the one who did it.

The moment you have an on-chain wallet, your identity is sovereign. This means you control everything that you do — 100%. You cannot be compelled to perform a transaction you don’t want to and there are no mechanics in place that allows a third party to force you to do anything against your will. This means that even in the extreme case of having the world’s governments and tech giants wanting you to do something, you still hold the ability to say no.

There are downsides to this though. For one, you assume full responsibility for everything you do. This means you’ll have to keep your keyphrase (and password) secure because the moment a third party gets their hands on it, your identity is compromised.

Having our Digital Identities stored on blockchains means that all our activities cannot be tampered with. When an interaction is performed by a user, we know for a fact that the user was the one who did it.

The moment you have an on-chain wallet, your identity is sovereign. This means you control everything that you do — 100%. You cannot be compelled to perform a transaction you don’t want to and there are no mechanics in place that allows a third party to force you to do anything against your will. This means that even in the extreme case of having the world’s governments and tech giants wanting you to do something, you still hold the ability to say no.

There are downsides to this though. For one, you assume full responsibility for everything you do. This means you’ll have to keep your keyphrase (and password) secure because the moment a third party gets their hands on it, your identity is compromised.

• Decentralized nodes are almost impossible to hack

With multiple nodes running the blockchains, any malicious actor who wants to “hack” the system needs to take over >50% of the nodes. The difficulty of this varies from chain to chain, as some blockchains have hundreds of nodes, while others have fewer. Still, this is much harder than simply looking for a vulnerability in one centralized system.

Because of this, there is a drastically less likelihood of external hacks that lead to data compromise. Plus, blockchains are secured by the highest possible level of security: cryptographic signatures.

Key DID Players

• Next.ID

Next.ID is the world’s 1st DIaaS (Decentralized Identity As A Service) that connects and aggregates Web2 and Web3 accounts and addresses, allowing users to connect their Facebook and Twitter accounts to their Ethereum and SwapChat accounts.

• Lens Protocol

Lens Protocol is an infrastructure layer that uses social graphs to connect users — think of Twitter on Web3. Built by Aave, one of the OG DeFi teams, it builds out one possible way Web3 social can take shape, using NFTs as a base.

• Proof of Humanity

Proof of Humanity is a social identity verification system for users on Ethereum. It aims to solve one of the biggest problems plaguing the internet ever: bots. It does this by creating a verified network of human beings, using referrals and video proof to establish their credibility.

Further Digital Identity readings and viewings

• Self-Sovereign Identity: The Ultimate Beginner’s Guide!

• A brief history of SSI: Where does it come from? A timeline.

• Your Web3 Identity

• Can web 3.0 solve the problems of web 2.0?

• 
  

Next.ID 是世界上第一个为去中心化身份提供服务的协议（DIaaS），即将开启公开测试。它是一个去中心化的身份聚合协议，整合了所有 Web2 和 Web3 的数字身份，为开源开发者和项目提供全面的、可验证的身份数据库，以便于创新和开发 dApps。

作为世界上第一个为去中心化身份提供服务的协议（Decentralized-Identity-As-A-Service, DIaaS），Next.ID 创建了一个身份基础设施，将用户的身份安全地聚合到 Avatars（即基于密码学生成的用户数字化身）。在 Web3 生态中，Next.ID 会成为各类去中心化社交协议和 dApp 的身份聚合关口。

Next.ID 的 Avatars 独立于 Web2 和 Web3 而存在，使用类区块链的模式来保持数据的完整性。因此，Next.ID 可以连接所有 Web2 和 Web3 平台/协议，以一种独立于平台和公链生态的方式聚合所有的身份，将它们整合为单一的、去中心化的身份（DID）。

欢迎来到数字身份的未来。

为 Web3 建造者提供体验最顺畅的 DID 聚合器

• 作为一个去中心化身份系统，只有在优先考虑身份安全和数据隐私的架构上，才能最好地服务开发者。

• 一个通用的数字身份管理系统必须整合各大公链上的身份数据以及 Web2 和 Web3 各平台/协议的身份，这样身份数据才会有用和有意义。

Next.ID 了解到多种身份识别方法的优势， 这些识别方法包括可验证凭证（Verifiable Credentials）和灵魂令牌（Soulbound Tokens），通过为身份识别创建合理的底层 “Layer 0” 将它们聚合起来，确保不同的身份识别系统之间始终具有互操作性，并由一个统一的标准来数据结构化使用。

Next.ID 是无需信任的（trustless），我们欢迎所有的开发者在 GitHub 上审核流程和代码。如果你有志于建造赋予用户身份数据主权的 Web3 应用和协议，欢迎加入我们的开源社区。

Next.ID 如何建立一个身份基础设施？

• 正如人在现实中在不同环境中可以展现不同人格，Next.ID 让用户可以创建多个数字化身 Avatars，在 Web2 和 Web3 平台上进行互用。

• 也正如人自我认知、归属社会群体（如年龄、种族、国籍），Next.ID 建立了一个允许用户进行自我身份构筑的框架。

虽然在一个框架内运作的 Avatars 听起来可能像是一个国家身份系统，相较于有社会安全号码和第三方监管的传统身份管理，有几个关键的区别将 Next.ID 与之区分开来，使得用户真正拥有和管理自己跨平台的身份关系。

Avatars 是：

• 基于加密密钥对构建的，具有防篡改和不可破解性；

• 在非强制使用基础上使用的，这意味着用户可以根据自己的需求创建任何数量的 Avatars；

• 可在任何支持与 Next.ID 整合的平台上使用和操作的。

简而言之，Next.ID 的目的是帮助更多的用户实现在数字世界的自治和建立数字世界中的声誉。

更好了解为什么 Next.ID 对互联网的下一步发展至关重要，请阅读《为什么我们需要在一个去中心化的世界中拥有我们的数字身份》。

基于 Next.ID 丰富的应用场景

SwapChat X Next.ID

任何开发者都可以体验 Next.ID 的功能。SwapChat 是 Next.ID 的 内测阶段的合作伙伴之一。它是一个帮助用户跨平台（目前支持 Opensea 及 Twitter）与买家和卖家聊天的 dApp。

通过与 Next.ID 这样的 DIaaS 协议集成，Swapchat 的用户现在能够通过他们在 OpenSea 上的 Avatars 与买家和卖家谈判价格，从而实现更有效的价格发现。用户还可以使用 Avatars 查找对方的 Twitter 和 Discord。Next.ID 的多平台身份架构赋能了 SwapChat 跨平台社交的应用场景。

使用 Next.ID 的协议和 dApps 名单每周都在增加。以下是其中的一部分：

1. Mask Network — 连接 Web2 和 Web3 的社交协议网络

2. KNN3 — 用于 Web3 关系数据探索的社交图谱数据解决方案

3. RSS3 — 内容推送协议，支持聚合 Web2 和 Web3 的内容

4. SwapChat/Web3MQ — 跨平台的聊天协议，允许用户在 Opensea 和 Twitter 上发送信息和群聊，实现社交 NFT 交易

5. Web3.bio — Web3 身份前端账户页面

6. .bit — Web3 数据容器和命名服务，帮助用户连接 ENS 和其他身份服务

注：Next.ID 正在积极发展其开发者和合作伙伴生态系统。如需合作，请联系：developer@next.id。欢迎参考 Next.ID 开发者文档：docs.next.id。

为 Next.ID 提供支持的技术突破

ProofService（验证服务）- 用密码学确保数据的完整性

ProofChain（验证链）通过密码学和私对公密钥配对系统，采用类区块链的模式来保持数据的完整性，从而保证只有拥有正确私钥的用户才能在每个“区块”中添加数据。

ProofService（验证服务）及其每个历史变化都在 Arweave 上完全可见，这也与 Next.ID 社区对其协议保持完全透明的承诺一致。

KVService（KV服务）- 帮助组织用户数据并使之趋于合理化

当用户和协议使用 Next.ID 读写数据时，KVService（KV服务）设置了一个框架来清晰地组织信息，使 Next.ID 的前端使用更加顺畅，同时也让开发者更清楚地了解如何使用 Next.ID。

RelationService（关系服务）- 实现全面的身份查询和社交用例

RelationService（关系服务）是现有的 IDs、ID 查询以及与 Next.ID 绑定、并行的 ID 的聚合，为与外部协议的集成开辟了一系列可能性，并创造了更大的 Web3 原生社交用例的可能性。开发者可以点此访问了解 RelationService（关系服务）服务器原型。

与 Next.ID 一起建造：解决 Web3 的身份危机问题

如果你在熊市读到这篇文章，我们有一个建议：与我们一起做可持续的创新。

随着用户对数字经济愈加熟悉，DIaaS 将成为 Web3 未来发展背后的基石。虽然最近的牛市为我们提供了全新、创新的流动性挖矿叙事，但它缺乏可持续性。一个具有真正数字所有权的、可持续的未来正是 Next.ID 正在全力建造的。

Next.ID 正在召集愿意将 Next.ID 作为一项公众事业来发展的、有经验的开发者，来创造一个赋权用户的框架，并创建一个不受限于传统的数字社会。

路线图

阶段1（即日起至 2022 年 12 月）

1. 集成更多的 Web2 平台，首先会集成：Discord、Medium 和 TikTok。

2. 推出面向用户的示例 dApp 协议 (Web3.bio)，展示 Next.ID 的全套功能。

3. 扩大我们的关系服务数据库，从其他 DID 服务和数据库中聚合更多可验证的连接，使搜索查询更加高效和可信。

4. 为 Next.ID 作为一个开源社区运作奠定基础，使其成为一个去中心化自治组织（DAO）。 阶段2（2023 年）

阶段2（2023 年）

1. 建立开发者生态系统，鼓励开发者在 Next.ID 社区构思和创建项目。

2. 与社区共同开发项目。

3. 扩大 Next.ID 在社交媒体、游戏、安全和资产管理方面的采用和应用率。 阶段X（未来可期）

阶段X（未来可期）

1. 建立针对去中心化的个人对个人 (P2P) 节点的框架，帮助用户实现自我托管数据。

2. 发展为一个成熟的 DAO，让社区决定未来的路线图。

需要了解更多？请查阅我们的开发者文档：docs.next.id 或与我们联系：developer@next.id。欢迎关注我们的推特：@nextdotid。

Trading on OpenSea is pretty much a straightforward affair. Open a tab, browse the collections you want, find sellers with art that speaks to you, place a bid, and voila, you may be the owner of a super-rare punk.

What if this experience could be improved? Swapchat’s new partnership with Next.ID solves exactly this.

What are Swapchat and Next.ID?

Swapchat is a decentralized cross-platform messaging app that aims to increase communication across Web3 communities, reducing the crypto community’s reliance on centralized platforms like Twitter and Discord and addressing the lack of interactive functions on Opensea. Users can send direct messages as well as form community group chats around NFT collections using Swapchat’s Chrome plugin.

Complementing Swapchat is Next.ID, a Universal Identity System. Next.ID is a protocol that enables users to crystallize and solidify their online identities across Web2 and Web3, consolidating and authenticating identities from social media platforms (eg Facebook and Instagram) to blockchain wallets (eg Metamask). Next.ID builds the basis for a comprehensive user-owned digital identity social graph, enabling us to grow our networks beyond isolated accounts.

OpenSea 🤝 Swapchat 🤝Next.ID

When you see what Swapchat has built on OpenSea, your first thought will be “OpenSea should have built this long ago!” By allowing conversations between buyers and sellers, a natural conclusion will be a greater price discovery mechanism via negotiations. Buyers will be able to offer NFTs, tokens, and any combination of both for sellers to consider, and sellers will have a different avenue to better articulate price demands.

Because Swapchat works cross-platform, users can easily get notifications for updates on Opensea from their Twitter interface and vice versa. Plus, users can also use Swapchat as an initial starting point before moving to trusted third-party protocols like Sudoswap for OTC NFT transfers — without extra fees.

How Swapchat x Next.ID can revolutionize Web3 communities

Next.ID’s universal identity system opens new pathways to building a community. For example, users who connect their Twitters to Metamask via Next.ID are able to follow each other and continue their conversations there.

Buyers and sellers of gaming NFTs can discuss strategies and potential combinations that will give them an edge over others, and GameFi projects benefit from greater liquidity and communication among players.

Newly-launched projects can also encourage greater conversations within their communities in a trustless way, using Swapchat as a tool to drive hype and conversations about roadmaps.

Next.ID, the world’s first protocol offering Decentralized-Identity-as-a-Service (DIaaS)

is moving into beta testing. It is a decentralized identity aggregation protocol that integrates all Web2 and Web3 digital identities, offering a comprehensive and verifiable identity database for open-source developers and projects to innovate and build dApps on.

As the world’s first DIaaS, Next.ID creates an identity infrastructure that securely aggregates users’ identities into Avatars, making it the primary touch point for interfacing with any app or dApp.

Next.ID’s Avatars exist independently from Web2 and Web3, using a blockchain-like model to retain data integrity. This allows Next.ID to connect to all Web2 and Web3 platforms, aggregating all identities in a fully-agnostic way, unifying them into one single decentralized identifier (DID).

Welcome to the future of Digital Identity.

The most seamless DID aggregator for Web3 builders

• The ideal DIaaS System must be built with an architecture that prioritizes identity safety and data privacy

• A universal Digital Identity management system must consolidate identifiers across chains and platforms in both Web2 & Web3 so identity data can be useful and meaningful

Next.ID recognizes the strengths of multiple approaches to identity (including Verifiable Credentials and Soulbound Tokens) and combines them by creating a sensible “Layer 0” for identities, ensuring that there will always be interoperability between different identity systems, held together by one unifying standard.

It is trustless, and we welcome all developers to audit the code on Github. If you like what you see, come build with the community.

How does Next.ID build an identity infrastructure?

• Just as people are infinitely dynamic, Next.ID allows users to create Avatars that are infinitely interoperable across both Web2 and Web3 platforms.

• Just as people recognize social groupings (e.g. age, race, nationality), Next.ID builds a framework that allows self-identification.

While Avatars who operate within a framework may sound like a national identity system, complete with social security numbers and Big Brother’s watchful eyes, there are a few key differences that show how Next.ID empowers users to own their identities and is not enslaved by them.

Avatars are

• Cryptographic key pairs, making them tamper-proof and unhackable

• Used on an opt-in basis, meaning you can create as many or as few of them as you want

• Usable and operationable across any platform that supports integration with Next.ID

In short, it is designed to on-board as many users as possible, helping them to create digital autonomy and credibility.

To understand why Next.ID is vital for the next evolution of the internet, please read Why We Need To Own Our Digital Identities In A Decentralized World.

SwapChat integrates Next.ID

Next.ID’s capabilities can today be experienced by anyone. SwapChat, a Next.ID alpha test partner, is an instant messaging dApp across all Web3 pages that allows users to chat with buyers and sellers on OpenSea.

By integrating a DIaaS like Next.ID, SwapChat users now are able to negotiate prices with buyers and sellers via their Avatars on OpenSea, allowing for more efficient price discovery. Users can also use Avatars to discover communities via Twitter and Discord, leveraging SwapChat’s integration of multiple social platforms.

The list of protocols and dApps using Next.ID is growing weekly. Here are just some of them:

1. Mask Network — Permissionless platform that bridges Web2 users to Web3

2. KNN3 — Social graph data solution for Web3 relational data exploration

3. RSS3 — Content syndication protocol that allows aggregation of Web2 and Web3 content

4. SwapChat/Web3MQ — Cross-platform chat protocols that allow users to send messages and group chats on OpenSea and Twitter to realize social NFT trading

5. Web3.bio — Frontend profile page for Web3 identities

6. .bit — Web3 data container and naming service that enables users to link ENS and other identity services

Note: Next.ID is actively looking to grow its developer and partner ecosystem. Please reach out to us at developer@next.id.

Technical breakthroughs that power Next.ID

ProofService — Ensure data integrity with cryptography

ProofChain follows a blockchain-like model to retain data integrity, using cryptography and the private-public key pairing system. This ensures that only users with the right private keys will be able to add to the data in each “block”.

ProofService and every change in its history are fully visible on Arweave, true to the Next.ID community’s commitment to full transparency for its protocols.

KVService — Organize and make sense of the data provided by users

As users and protocols read and write data using Next.ID, KVService sets up a framework to organize the information neatly. This enables smoother frontend usage of Next.ID, as well as allows developers a clearer understanding of how Next.ID can be utilized.

RelationService — Enable comprehensive identity queries and social use cases

RelationService is an aggregation of existing IDs, ID queries, and IDs bound to and in parallel to Next.ID, opening up a range of possibilities for integration with external protocols and creating greater Web3 native social use cases. Developers can access the prototype of RelationService server here.

Build with Next.ID: Solve the Identity Crisis in Web3

If you’re reading this even in the bear market, we have a proposal for you: build something that lasts.

Digital-Identity-as-a-Service will be the cornerstone on which Web3 will be built, as users get increasingly familiar with a digital economy. While the most recent bull run provided us with completely new and innovative liquidity mining primitives, it lacked sustainability. A sustainable future with true digital ownership is exactly what Next.ID is building.

Next.ID is looking for experienced developers who want to build on Next.ID as a public good, to create a framework that empowers users, and to create a digital society that stands apart from traditional constraints.

Roadmap

Phase 1 (Now-Dec 2022)

1. Integrate more Web2 platforms, starting with: Discord, Medium, and TikTok

2. Debut a user-facing demo dApp (Web3.bio) that showcases the full suite of Next.ID’s capabilities

3. Enlarge our RelationService database to aggregate more verifiable connections from other DID services and databases, making search queries more efficient and trustworthy.

4. Lay the groundwork for Next.ID to operate as an open-source community governed as a Decentralized Autonomous Organization (DAO).

Phase 2 (2023 and beyond)

1. Build out the developer ecosystem, encouraging developers to ideate and execute projects in the Next.ID community

2. Co-develop projects with the community

3. Expand Next.ID adoption and applications in social media, gaming, security, and asset management

Phase X (TBD)

1. Build the framework for decentralized P2P nodes to enable users to self-host their data

2. Develop into a full-fledged DAO, allowing the community to decide a future roadmap.

Intrigued? Find out more at docs.next.id or reach out to us at developer@next.id. Follow us on Twitter: @NextDotID