Beldex is a privacy chain where BDX is both “gas” and node collateral

Beldex is positioning itself as a confidentiality-first stack: private transactions on its base chain, plus privacy-oriented apps like BChat and BelNet that lean on an incentivized node layer. The project describes itself as built on the CryptoNote protocol, using techniques like ring signatures and one-time stealth addresses to keep transaction details private. For a comparison point, our Oasis tokenomics review covers a different privacy-oriented design.

That “incentivized node layer” is not window dressing. Beldex runs Master Nodes (the docs use “Master Node” terminology) where operators time-lock BDX as collateral and, in return, receive a share of block rewards, as outlined in the Master Node overview. The minimum collateral requirement is 10,000 BDX.

So BDX ends up wearing three hats in practice:

1) Network asset: it is minted via block rewards under PoS.

2) Security collateral: it is locked to stand up Master Nodes, with explicit lock and unlock frictions.

3) Fee / utility token: it pays network fees. Some fees are explicitly burned (more on that later), and BNS domains are purchased with BDX and burned out of supply.

Supply: no hard cap, emissions matter, and “static supply” narratives break fast

Supply metrics currently display Beldex with a max supply of ∞ (uncapped), not a fixed ceiling. That single line changes how you should read everything else. You are not valuing a capped commodity. You are valuing a live emission system with burns and scheduled treasury releases.

As of March 5, 2026, CoinGecko shows:

Circulating supply: 7,605,973,430 BDX.

Total supply: 9,936,271,967 BDX.

On the protocol side, Beldex states it transitioned to Proof of Stake on December 10, 2021 via the Bucephalus hardfork. In the protocol whitepaper, Beldex states block rewards increased to 10 BDX per block after Bucephalus, with 62.5% allocated to masternode block producers and 37.5% allocated to governance, and it reiterates a 30-second block time.

The project’s own AMA recap (hosted on the Beldex blog) gives a concrete emission arithmetic consistent with the 30-second block time: about 2,880 blocks per day and 28,800 BDX minted per day at 10 BDX per block.

One nuance you should not ignore: the documentation is internally inconsistent on reward splits. The whitepaper’s Bucephalus section describes 62.5%/37.5% (implying 6.25/3.75 BDX per block). The AMA recap states 6.25 to the validator and 3.25 to governance (which sums to 9.5, not 10). And elsewhere in the same whitepaper there is a “block reward is 6.5 BDX” statement that conflicts with the Bucephalus section.

From a market microstructure angle, that inconsistency is not academic. Yield expectations anchor staking demand. Staking demand anchors lockup. Lockup anchors float. Float sets the marginal price response to flows. When reward math is fuzzy in public docs, modelability drops and the market is more exposed to “surprise repricing” around upgrades.

Allocations and unlocks: the quarterly release calendar is the liquidity schedule

Beldex’s clearest tokenomics disclosure is not a fancy chart. It is the project’s repeated “scheduled release” communications and a 2022 tokenomics update that explicitly frames a large chunk of supply as allocated into purpose-specific wallets.

In its tokenomics update, Beldex states that the “total supply” (explicitly excluding validator-minted rewards after PoS went live on December 10, 2021) was classified into categories and placed into multisig wallets, and it states the total supply (in that sense) is 9.9 billion BDX.

Those allocations (as presented by Beldex as of October 1, 2022) are:

This is where the microstructure lens bites. A “vesting schedule” is not just investor relations. It is a recurring liquidity event. If those wallets are large relative to organic spot depth, they can create predictable sell-side pulses even if the project acts in good faith.

Beldex’s more recent scheduled release posts make this quarterly cadence explicit and publish wallet addresses and view keys for verification. On March 31, 2025, Beldex states 130,680,000 BDX was released from the Ecosystem Development Wallet and that total Q1 2025 releases were 229,680,000 BDX.

That same update reports remaining balances after the releases, including 2,261,160,000 BDX remaining in the Ecosystem wallet and 66,000,000 BDX remaining in the Team wallet at the time of writing.

On September 30, 2025, Beldex states another 130,680,000 BDX was released from the Ecosystem Development Wallet, leaving 1,999,800,000 BDX remaining in that wallet.

Two practical observations:

First: the scheduled release posts contain date inconsistencies in their own narrative text. For example, the March 31, 2025 post says “the thirteenth scheduled release of BDX took place on March 31, 2024” while also stating “On March 31, 2025” releases occurred. That is not fatal, but it does reduce confidence in “clean calendar” modeling unless you cross-check on-chain movements.

Second: aggregator “tokenomics” panels that show “unlocked” vs “locked” amounts can be useful context, but they are not the same thing as a primary disclosure. When a third-party breakdown disagrees with the project’s wallet-based reporting, I would treat the project’s own wallet disclosures as the anchor and use aggregators as a consistency check, not the source of truth.

Fees, burns, and fiscal flows: Beldex burns at the margin, mints by default

BDX has two broad supply directions happening at once. If you want a non-privacy reference for how burn narratives can (or can’t) offset issuance, compare this to our CAKE tokenomics review.

Emission: new BDX minted via block rewards under PoS.

Burn: BDX removed from circulation via specific fee-burning mechanics tied to network usage and BNS adoption, as described in the project’s burning mechanisms write-up.

Beldex describes “Flash transactions” as an instant-transaction layer, and the whitepaper states flash instant transactions were launched with “a network confirmation of 2 nodes.” For burns, Beldex states that the Flash transaction fee is automatically burned on-chain by being sent to a wallet whose seed phrase is unknown.

The burn rate here is structurally constrained because the project also states the fee is “considerably low,” meaning only a small portion of circulating supply is removed via flash fee burn unless transaction volume is very large.

On fee levels, the Beldex explorer UI publishes fee parameters including a base fee and a higher “flash fee.” For example, one explorer snapshot displays: base fee 0.0001 BDX/output + 0.006666 BDX/kB and flash fee 0.0003 BDX/output + 0.019998 BDX/kB. Those numbers matter because they bound burn per transaction. If fees are tiny, burns are tiny, unless usage is enormous.

The more interesting burn rail is BNS (Beldex Name Service). Beldex introduced BNS and a BNS fee-burning mechanism as part of the Bern hardfork (live at block height 2,986,890, per the announcement). Beldex states that BNS transaction fees are removed or destroyed, reducing circulating supply as adoption increases.

The burning mechanisms post provides explicit BNS pricing, which is helpful because you can actually model it. Subscription fees are stated as: 650 BDX for 1 year, 1000 BDX for 2 years, 2000 BDX for 5 years, and 4000 BDX for 10 years, and a flat 50 BDX transfer fee.

Mechanically, this is good design for narrative stability. Burns scale with ecosystem usage, not with price. But it also creates a clean trade-off:

If BNS adoption is modest, burns are background noise versus emissions and quarterly releases. You will still experience dilution and liquidity shocks.

If BNS adoption is strong, burns can become a meaningful sink that partially offsets issuance and release-driven float expansion.

Governance and parameter control: “governance rewards” exist, but governance is not well-specified

Beldex’s protocol-level economics explicitly carve out a “governance” share of rewards after Bucephalus. The whitepaper says 37.5% of the new block rewards are allocated to governance.

Developer documentation shows this governance reward is not necessarily paid out in every block output. It states that “batching of Governance rewards was introduced” and that the governance reward is paid every GOVERNANCE_REWARD_INTERVAL blocks.

What is missing in public materials is the thing markets usually need most: who controls governance reward flows and by what process. The docs and whitepaper talk about quorums that validate blocks, and the Master Node docs mention voting in the context of “swarm voting” for Master Node operations. But that is operational voting, not treasury governance in the tokenholder sense.

The closest statement to decision-making process I found is in the Changelly AMA recap, which says Beldex “will take into account the community vote / validator response when introducing a hardfork.”

So the practical governance picture, as an analyst, looks like this:

Protocol governance: partially mechanized via PoS quorums and a governance reward emission stream.

Treasury governance: largely centralized around designated wallets whose releases are announced by the team.

This structure can work. It can also produce sharp repricings when parameters change, because decision rights are not legible on-chain the way they are in typical token-vote DAOs.

Microstructure: collateral lockups compress float, unlock queues and scheduled releases expand it

The BDX market is shaped by two opposing liquidity forces that both have teeth:

Float suppression via staking: Master Node operators lock BDX to become eligible for rewards. The docs say Master Nodes become eligible when the owner locks the required amount “for 30 days” and submits a registration transaction. The whitepaper also describes time-locking collateral for 86,400 blocks, which is consistent with a 30-second block time equating to ~30 days.

Float expansion via unlock mechanics: when contributors request an unlock, the staking requirement page states funds “will stay locked for an additional 15 days” while still receiving rewards. The Master Node full guide reiterates that unlocking schedules node expiry and that deregistration can extend lock time to 30 days via blacklisting.

That delayed-unlock design tends to reduce “instant unstake bank runs,” which is good. It also creates a visible exit queue. If demand deteriorates, you can get a slow-motion supply overhang: first in “unlock requested” state, then arriving on exchanges later.

Reward distribution mechanics also influence sell pressure. Beldex’s Master Node RPC guide describes rewards as being sent to service nodes that “have been waiting longest since their last reward,” then pushed to the back of the queue. Queue-based payout smooths rewards across operators. It does not remove sell pressure. It just spreads it.

The other major liquidity engine is treasury flow. The tokenomics update and scheduled releases make clear that large balances sit in designated wallets and are released on a schedule. This is the closest thing Beldex has to a traditional unlock calendar, and it is the calendar I would monitor first.

If you are trying to do a serious supply model or risk review, it is worth being explicit about what you can and cannot see. Beldex is a privacy chain. Rich list style analysis is constrained. The project partially compensates by publishing addresses and view keys for certain designated wallets in scheduled release posts. That helps, but it is still not the same as fully transparent on-chain balance visibility across the whole ecosystem.

Risk analysis

Dominant risk: liquidity shocks from concentrated wallet supply meeting thin spot depth.

The structural issue is concentration. Beldex itself framed its post-PoS “non-emission” supply as 9.9 billion BDX allocated across purpose wallets and circulation. Even after years of releases, CoinGecko still shows a large gap between circulating supply (7,605,973,430 BDX) and total supply (9,936,271,967 BDX) as of March 5, 2026. Some of that gap is normal for any chain with treasuries and locked balances. The risk is how that gap gets converted into tradeable float.

Beldex’s own communications highlight recurring release events. On March 31, 2025, Beldex reported 229,680,000 BDX released in Q1 2025 across wallets. On September 30, 2025, it reported another 130,680,000 BDX released from the ecosystem wallet.

Those are not trivial amounts in isolation. The question is always microstructural: what is the ratio of “newly sellable supply” to “real bid depth,” not to market cap. If releases are spent into operations, listings, market-making, or ecosystem incentives, some portion will hit exchange order books. If order books are shallow, price impact rises quickly. If liquidity is deep, the same flows are absorbed with less volatility. The token design does not guarantee either outcome. It sets the conditions for predictable flow windows.

Burn mechanisms help, but they are not an automatic offset. Flash fee burn is explicitly described as small because fees are low. BNS burns can be larger per action (hundreds or thousands of BDX per registration term), but only if BNS adoption is real and sustained. Meanwhile, baseline emissions are always on. The whitepaper describes 10 BDX per block after Bucephalus, and max supply is explicitly marked as uncapped.

In other words, Beldex’s narrative stability depends on a balance between (a) emissions, (b) burns, (c) staking lockup levels, and (d) treasury release throughput. The design is workable, but the equilibrium is not guaranteed. It has to be maintained through usage and through disciplined treasury operations.

From a risk management standpoint, I would treat quarterly releases as “scheduled liquidity events” even if the project frames them as operations funding. Markets trade flows. Intention is secondary.

Top 3 risks

  1. Treasury release shock. Trigger: large quarterly (or ad hoc) releases from designated wallets, or large transfers out of those wallets. Mechanism: step-change in sellable float overwhelms spot depth, causing slippage and cascades as bids pull. Who bears it: spot holders, LPs, and leveraged traders; second-order impact on stakers if price decline reduces staking participation. Measurable indicators: published scheduled release amounts, remaining wallet balances, exchange net inflows around release windows, and discrete jumps in circulating supply metrics.
  2. Parameter uncertainty and upgrade repricing. Trigger: hardforks or code-level changes that alter reward splits, collateral requirements, or governance reward batching. Mechanism: expected staking yield reprices quickly, changing lockup incentives and inducing node churn; unlock queues can translate into delayed sell pressure. Who bears it: Master Node operators, delegated contributors, and spot holders exposed to volatility. Measurable indicators: hardfork announcements, doc updates, changes in explorer “Hard fork” version display, and shifts in staking/unlock behavior.
  3. Usage shortfall (burns stay small). Trigger: BNS and flash usage does not scale, or user demand shifts away from Beldex apps. Mechanism: burns fail to offset ongoing emissions and treasury releases, so net float expands and the market needs persistent new bid to sustain price. Who bears it: long-only holders and ecosystem participants paid in BDX. Measurable indicators: BNS registration and renewal activity, burn totals over time, and transaction/burn fee volumes relative to the known emission pace.

If you are building internal monitoring around BDX, treat this like a flow-driven asset. Track the release cadence, not just the “total supply” headline. Track staking lock/unlock behavior as a leading indicator for future spot supply, and archive your own research reports around each release window to keep comparisons consistent over time.

If you need a structured framework for this kind of flow-first review, this is the type of work that falls under tokenomics services. The only way it’s useful is if you tie every narrative claim back to an observable supply or liquidity mechanism.

For definitions and common modeling questions, start with our tokenomics FAQ.



This article is part of our Tokenomics Deep Dive series.