Privacy shouldn’t be something developers have to add after an application or asset has already been built. It has to be built in. That’s the maxim with which Beldex has built its network, products, and infrastructure.
With the launch of Confidential Assets, also known as Privacy Tokens, on the Beldex testnet, we are taking another step toward making privacy part of the infrastructure itself.
Privacy Tokens enable developers and projects to issue their own privacy-preserving tokens directly on the Beldex network, with transaction confidentiality built into the asset layer from the beginning.
The implementation is being introduced through the Proto testnet hard fork at testnet block height 4,242,200.
Developers can now begin deploying and testing Privacy Tokens on the Beldex testnet at testnet.beldex.dev. Similarly, they can obtain the testnet BDX from faucet.beldex.dev.
What Are Privacy Tokens?
Most blockchain assets operate on transparent networks where transaction activity can be publicly inspected. Even when an application adds privacy features at another layer, the underlying asset and its transaction history may remain completely visible.
Privacy Tokens take an entirely different approach.
They are assets issued directly on the Beldex network that inherit transaction-level privacy from the network. At launch, Privacy Tokens use Beldex's UTXO-based architecture, extending the privacy model already used for BDX to independently issued assets.
This means projects can create tokens where sensitive transaction information, including sender and recipient details, transferred amounts, and balances, is protected from public visibility.
Instead of building a token first and finding a way to make it private later, developers can start with privacy at the asset layer.
As Beldex Chairman Afanddy Bin Hushni explains:
“Privacy Tokens lets developers build an entire application economy where privacy is the starting point. It isn’t just another token standard. Whether it’s a private DeFi protocol, a confidential rewards system, or a new dApp entirely that no one has previously imagined, these assets all inherit the same cryptographic guarantees that protect every BDX transaction on our network.”
From a Privacy Ecosystem to Privacy Infrastructure
Beldex has spent years building applications around private digital interactions.
Today, the ecosystem includes BChat for private messaging, BelNet for decentralized network routing, the Beldex Browser for private web access, the Beldex Wallet, and BNS for decentralized blockchain-based names.
Privacy Tokens expand what can be built on top of this existing infrastructure.
Instead of Beldex being the only team building privacy-focused applications within the ecosystem, developers can begin creating their own applications and asset economies on the network.
A project could issue a Privacy Token and use it as the native asset of a privacy-focused application. Depending on the application, the token could support private payments, rewards, access mechanisms, community utilities, or entirely new use cases.
The important distinction is that privacy does not need to be recreated separately by every project. It begins at the network and asset layers itself.
The Developer Stack Behind Privacy Tokens
Launching a token standard alone is not enough. Developers also need practical tools that allow applications and users to interact with those assets.
Alongside Privacy Tokens, Beldex is introducing the infrastructure required to start building web-based applications around them.
Beldex Extension Wallet
The Beldex Extension Wallet provides a browser-based interface through which users can create and manage their Beldex wallets and interact with supported applications.
For developers, it creates the connection between a web application and the user's wallet.
Web3JS SDK
The Beldex Web3JS SDK gives developers the tools required to integrate Beldex functionality into web applications.
Together, the Extension Wallet and Web3JS SDK allow applications to connect to wallets, retrieve relevant wallet information, initiate supported transactions, and integrate Privacy Tokens into application workflows while preserving the underlying privacy model.
With these components available alongside Privacy Tokens, developers now have the beginnings of a complete stack for building privacy-first applications on Beldex:
Privacy Tokens → Extension Wallet → Web3JS SDK → Privacy-first dApps
What Can Developers Build?
Privacy Tokens are the underlying infrastructure rather than a single predetermined use case.
They could support applications such as private payment systems, private swap platforms, confidential rewards programs, privacy-focused DeFi applications, decentralized platforms, membership or access systems, and other applications where publicly exposing users' financial activity would be undesirable.
And because Privacy Tokens are issued on Beldex, developers do not need to create an entirely new privacy blockchain simply to launch a private asset.
They can build on an existing Layer 1 designed around transaction privacy.
Why Start With UTXO?
Privacy Tokens have initially launched using Beldex's UTXO-based architecture.
This allows the first version of the standard to build directly on the privacy architecture already used by the Beldex network instead of attempting to retrofit privacy onto a transparent account-based environment.
But UTXO-based Privacy Tokens are only the first stage.
Beldex is also developing account-based addresses and a planned EVM-compatible sidechain.
Once these components are introduced, the goal is to provide a path for projects that begin with UTXO-based Privacy Tokens to move / bridge into an EVM-compatible environment while retaining privacy-oriented capabilities.
The approach is deliberate:
Privacy first. EVM compatibility second.
So, instead of beginning with a transparent architecture and adding privacy afterward, Beldex is building outward from its existing privacy foundation.
Building an Open Privacy Economy
Privacy Tokens represent a broader change in how Beldex is evolving.
Beldex began by building its own privacy-focused ecosystem. The next phase is about giving developers the infrastructure to build their own products, applications, and economies on top of it.
Privacy Tokens provide the asset layer.
The Extension Wallet provides the user interface.
The Web3JS SDK provides the developer interface.
Together, they move Beldex closer to becoming an open infrastructure layer for applications where privacy is a default property rather than an optional feature.
And this is only the testnet stage.
Developers can now begin deploying Privacy Tokens, testing integrations, experimenting with applications, and providing feedback ahead of the planned mainnet rollout. They can also start applying for grants at beldex.io/grants.
Start Building on the Beldex Testnet
The Proto testnet hard fork introduces Privacy Tokens at block height 4,242,200.
Developers can explore the Beldex testnet at: testnet.beldex.dev
The Beldex Extension Wallet and Web3JS SDK provide the supporting tools for developers looking to begin integrating Beldex into web applications.
For Beldex, this launch marks an important transition: from building privacy applications ourselves to providing the infrastructure for others to build the next generation of them.
Privacy Tokens are now live on testnet. It's time to build privacy into the asset itself.
Listen
back to blog