
Beldex (BDX) is a privacy coin that runs its own chain, forked from the Monero codebase. Transactions are confidential by default. A layer of staked master nodes secures the network and also carries an encrypted messenger, a mixnet and an on-chain naming system, and BDX pays for transactions and for the collateral those nodes lock.
Beldex's own chain says 9,939,527,993 BDX exist. The aggregators that price it publish 7,870,587,552. We went looking for what the missing 2,068,940,441 tokens are, across the chain, the block explorer, a 41-page whitepaper and 37 pages of documentation. The design intent is stated in all of them. The number is stated in none of them. At the Tuesday 8 September 2026 close that gap prices at $158.6 million.
|
Metric
|
Details
|
|
Token name
|
Beldex
|
|
Ticker
|
BDX
|
|
Blockchain
|
Beldex, its own CryptoNote chain forked from Monero
|
|
Consensus
|
Proof of stake, one block every 30 seconds
|
|
Decimals
|
9 atomic places, not the 12 used by the Monero codebase it forked
|
|
Total ever emitted
|
9,951,366,263.900 BDX at block 5,735,724
|
|
Burned
|
11,838,270.716 BDX at the same block
|
|
Chain supply, emission minus burn
|
9,939,527,993.184 BDX
|
|
Supply published by aggregators
|
7,870,587,552 BDX
|
|
Difference
|
2,068,940,441 BDX, 20.79% of everything ever emitted
|
|
Master node collateral
|
10,000 BDX, time-locked
|
|
Network state at that block
|
daemon 7.0.2, hard fork 21, 5,911,309 transactions, 6,593 registered names
|
|
Core narrative
|
Confidential payments plus a staked service layer
|
|
Primary risks
|
Two supply definitions that differ by a fifth, thin turnover, documentation that lags the chain
|
|
On Phemex
|
No BDX spot pair and no BDX perpetual contract
|
What Is Beldex
Beldex is a fork of Monero's code that kept the parts making Monero private. Ring signatures hide which input was spent, stealth addresses hide who received it, and amounts are concealed. There's no setting to switch any of it off, so every transaction looks the same from outside.
What Beldex added on top is a paid service layer. Operators lock 10,000 BDX to run a master node, and those nodes carry more than blocks. They route traffic through a mixnet, back an encrypted messenger, and hold a naming system mapping readable names to addresses. At the block we read, 6,593 names had been registered.
The chain is proof of stake and produces a block every 30 seconds. The whitepaper splits each reward ten percent to the block builder and ninety percent to the master node next in line, with operators pushed to the back of the queue once paid. Think of it as a rota rather than a lottery.
Why Beldex Has Two Different Circulating Supplies
The chain's figure isn't an estimate. The explorer's supply call returns three fields, and the one labelled circulating_supply is total emission minus everything burned. We read 9,951,366,263.900 emitted and 11,838,270.716 burned at block 5,735,724, and the difference lands on 9,939,527,993.184 to the ninth decimal. It's subtraction, not a model.
That matters because the label invites you to read it as a float estimate, the way a company reports shares outstanding after buybacks. It's a count of every coin the chain has ever paid out and not destroyed.
The aggregators publish 7,870,587,552. The difference is 2,068,940,441 BDX, or 20.79 percent of everything ever emitted.
|
Supply definition
|
Tokens
|
Market value at $0.076653503
|
|
Chain, emission minus burn, block 5,735,724
|
9,939,527,993.18
|
$761,899,643
|
|
Published circulating supply
|
7,870,587,552
|
$603,308,110
|
|
Difference
|
2,068,940,441
|
$158,591,533
|
The feeds agree on the exclusion far more closely than they agree on the price. One aggregator's own total-supply field carries 9,939,527,316, the chain number. Divide the other's printed capitalisation by its printed price and you get 7,870,527,472, within about 60,000 tokens of the first. Two sources half a percent apart on price land within 0.0008 percent of each other on how much supply to leave out.
So somebody decided what to exclude, and both feeds took the same decision. We couldn't find who, or what.
Where we looked
The whitepaper runs 41 pages and uses the phrase "circulating supply" exactly once, arguing that locking coins raises the cost of a Sybil attack. No figure. The documentation set is 37 pages, and the word "supply" appears five times across all of it, one of those being advice about a stable power supply for your server. The overview page states the intent plainly, that Beldex "encourages the active suppression of the circulating supply", then points at its own emissions-curve page for the mechanism. That page says nothing about an emissions curve.
The explorer's public interface has no endpoint for a master node count. We probed four spellings and got four not-found responses.
We're not going to tell you what the 2.07 billion is, because we couldn't establish it and neither, apparently, has anyone else. The silence is the finding.
What Beldex Master Nodes Actually Run
The obvious explanation for a large excluded balance is staking, so we tested it first. An operator time-locks 10,000 BDX and registers, and the network holds that collateral for at least thirty days. Request it back and it stays locked a further fifteen days, still earning. Go offline too long and the node is deregistered, with the collateral held thirty days as a penalty.
Divide the gap by the collateral and you need roughly 206,894 master nodes to account for it. That is the arithmetic, and it's why we stopped treating staking as the answer. We couldn't retrieve a node count from the public explorer, so the defensible claim is narrow. Collateral at the documented rate would need a node population nobody has published.
The same page carries a second wrinkle. One paragraph validates collateral against a decreasing collateralisation requirement, implying the amount falls over time. The next says it's constant.
As for what the nodes do, the documentation details one function. A privacy chain of this design forces light wallets to download blocks and scan them locally, which is expensive for whoever hosts the public node and leaks your IP address to them. Beldex makes every master node serve that role. It's a real problem, and a smaller claim than most readers expect from a staking layer.
How Thin Is the BDX Tape
Two feeds priced the Tuesday 8 September 2026 close at $0.076653503 and $0.076277, a spread of 0.494 percent. Wide enough to notice, narrow enough to trust. We used the higher figure and showed both.
Turnover is where BDX differs from the tokens it gets grouped with. Against the dated volume for the session ending at that close, it turned over 1.45 percent of its published capitalisation, or 1.15 percent on the chain supply. At the same timestamp, dogwifhat turned over 14.05 percent. BDX is the larger asset by value and changes hands at roughly a tenth the rate.
Imagine two shops holding identical stock, where one sells through it ten times faster. The slow one isn't cheaper or safer. Any order of size has further to travel before it finds the other side, and a position you can open comfortably isn't always one you can close.
Beldex has no spot pair and no perpetual contract on Phemex. Confidential-asset exposure through a listed derivative runs through other assets.
What Moves the BDX Price
The privacy bid
Zcash closed the 8 September session 41.97 percent above its own 200-day average, the most extended reading among the 57 spot pairs on our board carrying a full 200-session history. That's a statement about those 57 pairs and nothing wider. Our work on Zcash's drawdown and its risk-adjusted score covers what extension like that has cost holders, and the changes inside Zcash's development team explain part of why the name is bid.
Which supply number a feed adopts
If an aggregator switched to the chain figure, BDX's published capitalisation would rise by $158.6 million with no trade behind it. Screeners, index rules and portfolio filters key off that number, so a definitional change moves where an asset appears without anyone buying.
Collateral entering and leaving
Every registration locks 10,000 BDX for at least thirty days, and every release carries a fifteen-day tail. Against a tape this thin, node flows are a supply variable, not a footnote.
The dated macro calendar
Producer price data lands Thursday 10 September at 12:30 UTC and consumer price data Friday 11 September at the same hour. The Federal Reserve meets 15 and 16 September with projections. Thin books move most on those prints.
What Are the Risks
The supply you are quoted may not be the supply that exists
Every ratio built on circulating supply changes by a fifth depending on which definition your data source picked. Neither number is wrong. They answer different questions, and almost nothing displaying them says which one you're reading.
A wrapped contract is not the chain
A token named BELDEX with the ticker BDX and nine decimals exists on BNB Chain at address 0x9d10a1ec41fe7878429bb457e31f9b050d38c633. It reports a total supply of 4,335,728.69 tokens, 0.04 percent of the chain's supply and 0.21 percent of the gap, so it explains nothing. It's also an upgradeable proxy, confirmed on two independent BNB Chain nodes, so what it reports can be replaced without the Beldex chain changing.
The paperwork lags the chain
The whitepaper states the block reward as a constant 6.5 BDX. The block we read paid 6.25, and eleven consecutive blocks moved the emission total by exactly 6.25 each. The chain is authoritative and the document is stale, which tells you how much weight the rest of the published tokenomics can carry.
You cannot count the nodes
The public explorer exposes emission, network state and individual blocks, but no node count. If the staking layer is the argument for holding BDX, you can't size it from primary data.
The tape is thin
At roughly 1.45 percent daily turnover, exit liquidity is the binding constraint, not entry. Privacy assets also carry listing risk other categories don't, and a delisting on a thin name compounds quickly.
A near-identical ticker
A separate asset trades under the ticker BDXN, and it is not Beldex. Confirm the chain and the full name before acting on any figure, the same way you'd check the privacy layer and the reorg that hit Litecoin before assuming an optional privacy feature behaves like a mandatory one.
Frequently Asked Questions
How many BDX are there? The chain reports 9,939,527,993.184 at block 5,735,724, after 11,838,270.716 burned. Aggregators publish 7,870,587,552 as circulating.
Why do different sites show different Beldex market caps? They multiply the same price by different supply figures. At the Tuesday 8 September 2026 close the two definitions differ by $158.6 million.
Is Beldex a fork of Monero? Yes. It keeps the CryptoNote design, with ring signatures and stealth addresses, but runs proof of stake, adds a collateralised master node layer, and uses nine decimal places rather than twelve.
What is BelNet? It's the mixnet Beldex master nodes carry, routing traffic through multiple hops so no single node sees both ends of a connection.
Final Thoughts
Beldex is a working privacy chain whose service layer is real and smaller than the marketing suggests. The interesting part isn't the technology. It's that the most basic fact about the token, how much of it counts, has two answers 2,068,940,441 apart, and no primary document reconciles them.
We looked in the chain, the explorer, the whitepaper and the documentation. The intent to lock supply is written in three of those places. The quantity is written in none. If you hold BDX, that isn't a detail you can delegate to a screener, because the screener has already chosen for you and hasn't said which one.
Disclaimer: This article is for informational purposes only and is not financial advice. Cryptocurrency trading involves substantial risk. Always do your own research before making investment decisions.






