Guides
Nine explainers on how DChat actually works, sitting between the short answers in the FAQ and the parameter-level detail in the cryptographic specification. Written for people, accurate for engineers, and explicit about the limits.
How DChat is put together
Three layers: a chain that carries identity, a relay network that carries ciphertext, and clients that hold every key.
Read the guide →Your identity is a key pair
BIP-39, the derivation path, the dc1 address, and what owning your own identity means.
Read the guide →How a message travels
From keystroke to delivery: ECDH, HKDF, ChaCha20-Poly1305, the envelope, the pool, the flood, the ticks.
Read the guide →Groups
The N-sender-keys model, off-chain membership, and how key rotation protects a group.
Read the guide →Voice and video
Peer-to-peer one-to-one calls, and the media server that makes group calls possible.
Read the guide →Files, photos and IPFS
Encrypt, sign, upload. Why the content hash is public and the content is not.
Read the guide →Our security model
How DChat protects your messages, your keys and your account.
Read the guide →Nodes, staking and rewards
Service-node economics, uptime proofs, slashing, and the client-reward module in real numbers.
Read the guide →Building on DChat
What the SDK covers and how to build on the DChat network.
Read the guide →Building something on DChat?
Enterprise teams get white-label apps, dedicated infrastructure and source-level engagement with the core team.