BChat: A Decentralized Privacy Messenger Built on the Beldex Network

End-to-end encryption is now standard on popular messaging platforms like WhatsApp, Signal, iMessage, and Telegram in its opt-in secret chats. But encryption only protects the content of a message. The metadata, which reveals who messaged whom, when, how often, from which IP address, and on which device, often remains exposed and, in some cases, is more revealing than the message itself.

That gap is what BChat, a decentralized privacy messaging app built on the Beldex masternode network, aims to close. Instead of routing messages through corporate servers tied to phone numbers and device IDs, BChat onion-routes them through a peer-to-peer network of 2,680 masternodes, with no phone number, email, or personal identifier required to sign up.

BChat is part of Beldex's broader push to build a privacy layer for the internet, a stack that also includes the BelNet decentralized VPN, the Beldex Browser, and the Beldex Name Service (BNS) for human-readable identities.

Why Metadata Matters

The case for metadata-resistant messaging is compelling. Privacy is moving from cypherpunk wishlist to baseline expectation across the crypto ecosystem, with Ethereum, Circle, JPMorgan, and other industry players integrating zero-knowledge and fully homomorphic encryption primitives.

Centralized messengers retain logs that, even when end-to-end encrypted, expose who you talk to and how often. Phone numbers serve as persistent identifiers linking a chat account to a real-world identity, payment record, and location. Federal subpoenas, data brokers, and platform breaches have all produced metadata leaks in recent years. For journalists, traders, activists, and anyone holding self-custodied assets, metadata is a meaningful attack surface.

What Is the BChat Privacy Messenger?

BChat is an open-source private messaging app available for Android, iOS, Windows, macOS, and Linux. It is built to protect user privacy by removing phone number requirements and minimizing metadata collection.

Messages are routed through a decentralized network, enhancing privacy and giving users complete control over their communications online.

Three pillars define its architecture:

• Decentralized routing: Each message takes at least three hops through the masternode network. No single node sees both the sender and the recipient. This is the same routing principle that underpins private transactions, applied to messaging rather than the transfer of value.
• No personal identifiers: Account creation generates a 24-word recovery phrase, a 64-character BChat ID (your public key), and a Beldex wallet address. There is no phone number, no email, and no centralized account database. If you lose the seed phrase, the account is gone.
• Encrypted at rest and in transit: Messages use the TextSecure protocol, the same cryptography that powers Signal. Messages are stored locally on your device in encrypted form. When a recipient is offline, messages are held temporarily by a swarm of masternodes in encrypted form, then delivered when the recipient comes back online.
• Open source and metadata-free: The codebase is publicly available for independent security audits, increasing transparency and helping detect potential backdoors, while the app is designed to operate without collecting or retaining user metadata.

How BChat Compares

BChat is structurally different from the mainstream incumbents, since Signal still requires a phone number, Telegram only encrypts opt-in secret chats and stores messages on its own servers, and WhatsApp ties accounts to a phone number under a single corporate jurisdiction.

However, since a 64-character public key is unwieldy, BNS lets users map a human-readable .bdx name (yourname.bdx) to their BChat ID, Beldex wallet, and BelNet domain. The same .bdx name can host a private web app on BelNet accessible through the Beldex Browser, giving users a portable identity across the Beldex stack.

Strengths:

• Permissionless onboarding with no phone number, email, or KYC.
• The TextSecure encryption protocol is audited and battle-tested.
• The 2,680-strong masternode network provides meaningful routing diversity, with each message taking three or more hops.
• Default end-to-end encryption applies to both DMs and groups.

Limitations:

• The user experience is improving, with user-friendly features being regularly shipped, but it still lags Signal and Telegram, particularly in onboarding.
• Voice and video calls are peer-to-peer encrypted but not yet onion-routed.
• Network effects are limited so far.

The target audience is users whose threat model includes metadata exposure, such as journalists protecting sources, remote teams coordinating sensitive work, traders managing OTC flows, and DAOs coordinating governance.

Getting Started

Setup takes just a few minutes.

• Get BChat from the Play Store,App Store, or as a desktop client for Windows, macOS, or Linux.
• Open the app, tap "Create Account," and the app generates a 24-word seed phrase, a BChat ID, and a Beldex wallet address. Write the seed down on paper. Do not store it digitally. Set a display name, and you are in.
• Share your BChat ID through any other encrypted channel (or share your .bdx BNS name if registered). If you’ve got your friend’s BChat ID, then tap the new chat icon, paste the contact's BChat ID, and start messaging.
• Use the chat window like any other messenger. Encrypted text, images, files, voice notes, and videos.

Secret groups of up to 105 members work out of the box. Social groups (unlimited members) require a server and are intended for communities; however, setting it up requires a fair bit of technical knowledge.

Bottom Line

The Web3 industry has spent most of its energy on the value layer, building permissionless rails for money, while the communication layer has lagged. But the same primitives that make decentralized finance work, namely cryptographic identity, peer-to-peer routing, and economically secured node networks, can be applied to messaging.

BChat exemplifies that thesis. The architecture is sound, the encryption is well-known, and the integration with BNS provides users with a portable identity that works across messaging, browsing, and payments without revealing a phone number or email address. Meanwhile, the broader Beldex stack offers a model for what a privacy-first communication layer for Web3 might look like.