The problem Dexmail solves

Web3 has solved payments and ownership with wallets, but communication is still dependent on Web2 platforms like Gmail, Discord, and Twitter. This creates several problems:
Projects cannot reliably communicate with their users.
Important alerts (security warnings, liquidations, governance updates) are often missed.
Users rely on centralized platforms that can censor, filter, or lose messages.
There is no native communication layer tied to wallet identity.
DexMail solves this by turning a wallet address into a secure inbox.
With DexMail, users can send and receive encrypted messages directly linked to their wallet. Instead of needing a traditional email address, the wallet itself becomes the communication identity.
This enables several powerful use cases:
Protocol alerts – DeFi platforms can send liquidation warnings or security notifications directly to wallets.
DAO communication – Governance updates and voting reminders can reach verified members.
NFT communities – Projects can message holders without relying on social media platforms.
Wallet-to-wallet messaging – Users can securely communicate using only wallet identities.
DexMail creates a decentralized, censorship-resistant communication layer for Web3, allowing users and applications to interact without relying on traditional email infrastructure.

Challenges I ran into

One of the biggest challenges was designing a system that balances onchain verification with scalable messaging.
Storing messages fully onchain is expensive and impractical, but keeping everything offchain removes the trust and verification benefits of blockchain. The challenge was finding the right architecture that preserves decentralization while remaining efficient.
To solve this, DexMail uses a hybrid approach:
Onchain smart contracts handle identity registration, sender verification, and message routing references.
Encrypted message content is stored offchain to keep costs low and improve performance.
Another challenge was designing the system so that wallets could act as inbox identities without requiring complex onboarding. The goal was to make the experience feel as simple as traditional email while maintaining Web3 security principles.
This required carefully designing wallet authentication, encryption flows, and message verification so users can interact with DexMail seamlessly while keeping full ownership of their communication identity.