dm3 protocol

Open your wallet, pick a contact, and send a message that follows you across dapps. With dm3, you set up once and chat anywhere that speaks the standard. On first use, you generate or import messaging keys, choose where metadata lives (local-first, ENS text records, or IPFS), and pick relays for delivery. Add contacts by ENS name or address, preview verified profiles, and back up your keys to hardware or social recovery. Compose direct messages or start a thread, attach files, set an expiry, and request read receipts. If you switch apps or devices, your identity and conversation state sync through the protocol, not a single vendor.

Use it to run day-to-day work. DAO contributors spin up token-restricted rooms tied to a multisig, share proposal drafts, and schedule reminders that ping members when a vote opens. Creators broadcast updates to holders and accept subscriber DMs without doxxing an email. Support teams wire wallet chat into their sites, triage requests to agents, and hand off to bots that check on-chain status before replying. For planning and writing, threads hold outlines, code snippets, and task lists; mentions and reactions keep momentum without dragging people into meetings.

Developers can add dm3 in a sprint. Install the SDK, initialize it with a wallet provider, register a profile, and open a session. Send a message with a single call, passing content type (text, markdown, file) and delivery options. Plug in a storage adapter and a relay list; subscribe to incoming traffic via events or webhooks. Verify signatures to prove authorship, and expose capabilities so other apps can route messages to you. For mobile, tie notifications to WalletConnect or native push. Add spam controls with allowlists, stamps, or small fees, and use rate limits per identity.

Security and control are built into the flow. Messages are end‑to‑end protected with keys you own; intermediaries can relay but not read. There is no mandatory hub: pick multiple relays for redundancy and failover. Rotate keys when devices change, set recovery guardians, and export history if you migrate clients. Hashes and optional attestations let you prove a message existed without revealing its content. Presence is opt‑in, and delivery metadata can be minimized for sensitive teams. Because addressing is chain-agnostic, one handle can reach contacts on different networks, keeping your communications portable as your stack evolves.