Dmail has rolled out Auto-Forwarding 2.0, an update designed to route messages across several widely used platforms while maintaining the identity and privacy principles tied to decentralised communication.
The new feature allows messages received through Dmail to be forwarded automatically to services such as Telegram, MetaMask and Gmail. The aim is simple. Users receive notifications wherever they already spend time, rather than switching between different applications or inboxes. According to the project, the forwarding happens instantly once the feature is activated.
Dmail describes the upgrade as part of a wider effort to address fragmentation in online communication. Web3 users often juggle multiple channels including messaging apps, wallet notifications and traditional email. Keeping track of updates across these platforms can be difficult, especially when projects and communities rely on different systems to reach users.
The company argues that a unified notification flow reduces the risk of missed updates. With Auto-Forwarding 2.0, messages can appear simultaneously in a user’s preferred channels while remaining tied to their decentralised identity.
From a practical standpoint, the setup is designed to be quick. Dmail says users can enable the feature through its notification interface and choose the channels where messages should appear. Once configured, new notifications are delivered across those platforms automatically.
The update reflects a broader trend in the Web3 sector. Communication tools built around blockchain identities have been attempting to bridge the gap between decentralised services and familiar Web2 platforms. Many users continue to rely on tools like Telegram groups or email for everyday communication, which means Web3 services often need to meet them where they already are.
Auto-forwarding systems are not new in digital communication. Automation tools and integrations have long been used to send alerts between apps such as Gmail and Telegram, often through third-party services or custom bots. What Dmail is attempting, however, is to place that functionality inside a decentralised messaging environment tied to a blockchain identity.
Dmail’s positioning centres on ownership of data and identity. The platform promotes the idea that users should maintain control over their inbox and communication history rather than relying entirely on centralised providers. Within that framework, forwarding messages to external platforms does not transfer control of the underlying identity, according to the project.
The concept is part of a broader push among Web3 communication platforms to challenge the idea that messages must live inside a single service. Instead of forcing users to stay within a dedicated app, projects are experimenting with tools that distribute notifications across multiple channels.
Dmail suggests this approach helps reduce dependence on individual platforms. If one channel becomes unavailable or restricted, notifications can still reach users through other connected services.
Still, the approach also raises familiar questions about privacy and security when messages interact with centralised platforms. Telegram and Gmail operate under their own data policies, which means information forwarded to those services becomes subject to their respective systems. For users focused on decentralisation, that trade-off may remain a consideration.
For now, Dmail’s update reflects an effort to balance convenience with the ethos of decentralised identity. By connecting wallet alerts, email and messaging apps, the company is attempting to streamline how Web3 notifications reach users while keeping the underlying account anchored to a blockchain identity.
The company says the feature can be activated within seconds through its notification settings page. Users choose the platforms they want connected, and future messages appear across those channels automatically.
Whether such tools become widely adopted will depend on how users weigh convenience against control. Many in the Web3 community value sovereignty over data and identity, yet everyday communication habits often remain tied to familiar services like Telegram or email.
Auto-Forwarding 2.0 sits squarely between those two worlds, offering a way to keep decentralised messaging connected to the platforms people already use.
Dear Reader,
Ledger Life is an independent platform dedicated to covering the Internet Computer (ICP) ecosystem and beyond. We focus on real stories, builder updates, project launches, and the quiet innovations that often get missed.
We’re not backed by sponsors. We rely on readers like you.
If you find value in what we publish—whether it’s deep dives into dApps, explainers on decentralised tech, or just keeping track of what’s moving in Web3—please consider making a donation. It helps us cover costs, stay consistent, and remain truly independent.
Your support goes a long way.
🧠 ICP Principal: ins6i-d53ug-zxmgh-qvum3-r3pvl-ufcvu-bdyon-ovzdy-d26k3-lgq2v-3qe
🧾 ICP Address: f8deb966878f8b83204b251d5d799e0345ea72b8e62e8cf9da8d8830e1b3b05f
Every contribution helps keep the lights on, the stories flowing, and the crypto clutter out.
Thank you for reading, sharing, and being part of this experiment in decentralised media.
—Team Ledger Life
Community Discussion