Roadmap

Read it like a conversation

Every roadmap is a list of promises. Ours is a thread, and the delivery ticks are the status, exactly as they work inside the app.

Two blue ticks · shipped Two grey ticks · building One tick · queued
Privacy & protocol

Sealed sender

An ephemeral key, generated fresh for every message and tied to nothing, wraps the whole envelope. A relay forwards your message without ever learning which account sent it.

Shipped

End-to-end encryption

Direct messages, group messages and one-to-one calls sealed on your device with ChaCha20-Poly1305 before they go anywhere.

Shipped

No identity to collect

No phone number. No email. No password. Your account is a key pair, and your address book never leaves your phone.

Shipped

Automatic key rotation

Chat keys roll over every 10,000 messages or 30 days, so no single key ever covers your whole history.

Shipped

Group membership off the ledger

Never written to the chain, so no permanent public record exists of who belongs to which group.

Shipped

Encrypted multi-device sync

Conversations, contacts and keys move between your own devices without any server holding a readable copy. Rolling out across the last of the clients.

Shipped

Unlinkable routing tags

The conversation identifier becomes a rotating tag that changes every message and cannot be linked to the one before it.

Queued

Optional private routing

Onion routing as a per-conversation switch, so you trade speed for network-level anonymity only where it matters.

Queued

Independent security audit

Our full cryptographic specification is already published. External review is next, and we publish the result either way.

Queued
The app

Group video calls

Up to 25 people, from a group or straight from a contact picker.

Shipped

Voice and video calls

One to one, device to device, with no server in the media path.

Shipped

Screen sharing

Share your screen inside a call.

Shipped

Push notifications

Messages wake the app even after it has been closed.

Shipped

Animated stickers

A full animated sticker engine, with packs and reactions.

Shipped

Live location

Share where you are in real time, for a window you choose.

Shipped

Payments in the conversation

Send value inside a chat as a payment bubble, not in a separate app.

Shipped

Web and desktop

The full client in a browser and on Windows, macOS and Linux.

Shipped

Four languages

English, Arabic, French and Spanish, with full right-to-left layout.

Shipped

Android 7 and up

Runs on phones going back to Android 7, so nobody is shut out by an older handset.

Shipped

Channels

Broadcast to an audience that follows you, one to many, with the same encryption and still no phone number behind the account.

Building

Video stickers

Higher fidelity animated stickers with modern video compression.

Building

iOS release

The same client, on the App Store.

Queued
Network & economy

Staked relay nodes

Operators stake to run a node, prove uptime to a rotating quorum, and get paid per epoch.

Shipped

Message mining

Ordinary users earn for messaging activity, gated behind proof of humanity so the pool pays real people.

Shipped

Non-custodial wallet

Built into the app, secured by the same device-held keys. Nobody else can freeze or move your funds.

Shipped

Live block explorer

Every block, transaction and node registration, publicly viewable.

Shipped

Desktop relay nodes

Run a relay from an ordinary computer and earn for carrying traffic, instead of needing a server.

Queued

Cross-chain transfers

Move assets between the DChat chain and the wider ecosystem, from the wallet already in your pocket.

Queued
DChat is typing...

Not promises yet, just things we keep coming back to: A public feed where creators post and get paid directly, and Games you play inside a chat, with the wallet already there.

Service nodes, not servers

This gets misread constantly, so plainly: DChat is not a company running its servers in several data centres. That is a distributed system, and it still has one operator, one owner, and one entity that can be compelled or shut down.

A DChat relay is a service node. It registers itself on a public blockchain, bonds stake to take part, and proves its uptime to a rotating quorum of other nodes seeded by the block hash, so no node can choose its own verifiers. Registration, stake, rewards and slashing are public on-chain records you can read in the block explorer yourself. Who belongs to the network is decided by stake and protocol rules, not by anyone's deployment list.

Want something moved up the thread? Tell us

Most of this thread is already in your hands

No phone number, no email, no password. Free on Android, web and desktop.