Next.ID primary sources
Reviewed: 2026-05-10 UTC
Core project framing
- https://next.id/
- Official site; best concise product framing for Avatars, Proof Service, KV Service, Relation Service, Web3.bio, and the Universal Profile SDK.
- https://docs.next.id/
- Documentation entrypoint; useful for the broad framing of sovereign identity graphs and how Next.ID connects wallets, social accounts, and downstream profile products.
Proof-chain identity binding
- https://docs.next.id/core-concepts/proof-service/ps-intro
- Most important single-page source for the mechanism. It explains Avatar-to-identity binding, signed payloads, public proof posts, the
Proof/ProofChainmodel, and Arweave publication.
- Most important single-page source for the mechanism. It explains Avatar-to-identity binding, signed payloads, public proof posts, the
- https://github.com/NextDotID/proof_server
- Official implementation-facing repo page; useful for supported platform proof methods and the explicit explanation that each identity has a public proof chain.
User-signed portable metadata
- https://docs.next.id/core-concepts/proof-service/ks-intro
- Best source on the KV Service as a portable metadata layer. Especially useful for namespace design, RFC 7396 patch semantics, and the app-specific-namespace model.
Graph indexing and profile serving
- https://github.com/NextDotID/relation_server
- Best concise source on RelationService. Reveals that the project treats identity aggregation like a search engine and explicitly mentions a PageRank-like
soul ranksystem.
- Best concise source on RelationService. Reveals that the project treats identity aggregation like a search engine and explicitly mentions a PageRank-like
- https://docs.next.id/getting-started/importing-universal-profiles
- Short but useful explanation that Web3.bio APIs expose Universal Profiles across ENS, Lens, Farcaster,
.bit, and Next.ID.
- Short but useful explanation that Web3.bio APIs expose Universal Profiles across ENS, Lens, Farcaster,
- https://api.web3.bio/
- Primary developer-facing API surface for downstream profile synthesis; especially useful for seeing how Next.ID-style identity graphs become unified profile outputs rather than just proof records.
- https://web3.bio/
- End-user product surface powered by the same graph and profile stack.
Governance / roadmap direction
- https://docs.next.id/roadmap
- Useful because it makes the stack expansion explicit: more platform integrations, larger relation databases, self-hosting plans, DAO ambitions, auth service, and universal-profile tooling.
Main takeaways from this pass
- Next.ID’s distinctive mechanism is the split between public proof-chain binding, portable user-signed metadata, relation aggregation, and downstream profile APIs.
- The
Avataris the real identity root; individual platform proofs are append-only-ish links around that root rather than standalone credentials. - Arweave publication improves verifiability, but hosted proof, relation, and profile services still matter, so indexing and API policy remain important control surfaces.
- RelationService is analytically important because it shifts the stack from merely verifying links to ranking, searching, and synthesizing cross-platform identity graphs.
- Web3.bio shows how identity infrastructure becomes application middleware: profile rendering, discovery, and onboarding sit downstream from the proof layer.