Español

Open-Source Decentralized Platform

Community-driven tools for decentralized identity based on W3C standards. DIDs, Verifiable Credentials, IPv6-first peer-to-peer mesh, and DIDComm v2 for decentralized messaging — no central authority required.

Self-Sovereign Identity

Create and control your own DIDs and Verifiable Credentials. Your identity lives on your device — no platform can revoke it.

IPv6-first P2P mesh

Nodes discover each other with libp2p and keep the DID document registry in sync with no central server. IPv6 is the default for peer addressing and reachability; IPv4 remains as a compatibility path for legacy networks, not the long-term design center.

Built on W3C Standards

Implements DID Core, VC Data Model 2.0, and Data Integrity. Interoperable by design.

DIDComm v2

Standard protocol for encrypted, decentralized messaging between DIDs — exchange messages, credentials, and proofs without a central message broker.

How it works, in plain words Diagram: two personal apps exchanging secure messages; each app can ask any of several network helpers spread near the user, in their region, and worldwide; helpers stay in sync with each other. Shared, always-in-sync network Near you In your region Worldwide H H H H H H H Store info · relay messages Encrypted, end-to-end messages Your app Sends & receives securely Your app Sends & receives securely Ask any one — same trusted answer
Centralized Server down — everyone offline
1 2 3 Single server Down
Decentralized Some nodes down — network still up
1 2 3

Why a decentralized platform

Decentralized identity spreads trust across peers and standards — not a single company or server.

Always-on availability

Centralized services go down whenever their servers do. Here there is no single point of failure: as long as any node in the network is up — in your area, your region, or the world — the service keeps running.

Control & censorship resistance

Self-sovereign identifiers and credentials stay with the holder. Your digital identity is not the same as a revocable account on one provider.

Interoperability

W3C DIDs and Verifiable Credentials let other systems verify and exchange data without proprietary, closed APIs.

IPv6 over IPv4 by design

A decentralized mesh needs truly reachable peers. The stack treats IPv6 as the primary path for libp2p multiaddrs and discovery, cutting through NAT pain at global scale. IPv4 is still supported, but the architecture assumes IPv4 as a legacy fallback—not the end state of the network.

Sovereignty & deployment

Run your own node, choose your infrastructure, and align with internal policy or jurisdiction — without mandatory reliance on our cloud.

Transparency & trust

Open-source code and public standards mean behavior can be reviewed and audited instead of taken on faith alone.

Platform Modules

Four community-built components that work together as a decentralized network.

Daemon

Network node with gRPC and REST, libp2p peer discovery, and DID document replication. Exposes and prefers IPv6 listeners and announced addresses; IPv4 is available where the environment still requires it.

Rust · tonic · libp2p · axum

Wallet

Mobile-first identity wallet for holders. Create DIDs, store credentials, biometric auth, cloud backup, and QR exchange.

Tauri v2 · React · TypeScript

Desktop

Graphical app to manage and run the daemon — same scope as the CLI, with a desktop UI. Monitor the network, peers, storage, and node configuration.

Tauri v2 · React · TypeScript

CLI

Terminal interface to the daemon. Full TUI with network overview, peer management, storage, and logs.

Rust · ratatui · crossterm

Community-Driven, Open Standards

Built in the open by contributors around the world. No vendor lock-in, no paid dependencies. Run your own node, audit every line of code, and help shape the future of decentralized identity.