dm3 protocol

Open your wallet, pick who you want to reach, and send a message that only the intended recipient can read. That’s the everyday flow with dm3 as your messaging rail. Start by linking your wallet and publishing your public messaging key. Choose where messages live (your own node or a decentralized backend) and set rules for who can contact you. You can message an address, an ENS name, or a DID without worrying about which chain they use. Your inbox supports block/allow lists, delivery acknowledgments, and export for backup. Rotate keys when you change devices, and keep threads intact across browsers and mobile clients.

Building in a dApp takes a few steps. Install the SDK, configure identity resolution (addresses, ENS, or CAIP identifiers), and select a transport and storage option. Drop a chat widget into your marketplace so buyers and sellers can negotiate privately, or embed a support panel that authenticates users by signature instead of passwords. Trigger programmatic messages when on-chain events fire—listings created, bids matched, or vault thresholds crossed. For code workflows, generate a scoped sender, sign the payload, attach optional metadata (like order IDs), and dispatch through a relayer your users trust. Add rate limits and an allowlist to stop spam, and expose webhooks so back-office tools can log conversations without seeing plaintext.

For DAOs and token-gated communities, define channels that unlock based on roles, token balances, or verified credentials. Spin up a proposal thread where authors, reviewers, and signers coordinate without leaking strategy. Require signatures for critical updates and publish message hashes on-chain if you want an immutable audit that proves who said what—without revealing the content. When incidents hit, shift to a private room for core contributors, push high-priority notices to all signers, and archive the timeline after resolution. Moderators can mute bad actors at the protocol level, and communities can move between clients because the identity and history are portable.

Operate across ecosystems without extra accounts. dm3 routes by wallet identity so you can ping collaborators whether they live on Ethereum, L2s, or sidechains. If your users still need email or chat-app notifications, add a consented bridge that forwards only headers or redacted content until they unlock with their key. Automate daily ops with bots: send price alarms, verify deposits before releasing goods, or remind multisig members to sign. If you need more control, run a self-hosted relayer close to your users for lower latency and custom policies. Back up keys, set recovery delegates, and export message archives when teams rotate. With these workflows, dm3 becomes the secure, private-by-default backbone for communication in your web3 apps and organizations.