Skip to main content

Beldex

Beldex (BDX) — a reference card for a crypto project: what the product does and how verifiable the project’s key claims are; also — alignment with the Decentralized AI thesis (DecAI Fit).

Beldex — a privacy‑oriented L1 (based on the ideas of Monero/CryptoNote), which the whitepaper describes as an ecosystem for confidential transactions and communications (blockchain + services). No AI component is claimed in Tier‑1 sources; the term “confidential computation” refers to privacy/cryptography, not to ML/AI.

Disclaimer

Important: this page is a reference overview of the project. Within DecAIHub, we separately record a verification based on open sources within the AI thesis (what is real AI/onchain/why a token, and which sources this is based on).
This is not financial advice and not a recommendation to buy/sell/hold any asset. We do not assess price, returns, or entry/exit timing.
Conclusions are based on publicly available materials found as of the verification date. The absence of confirmation does not imply the absence of the technology.

TL;DR (for readers who are not into AI)

  • What it is: a privacy blockchain and a set of services (wallet/messenger/browser/VPN, as described in the whitepaper) for confidential transactions and communications.
  • Who it’s for: users who need privacy, and masternode operators/network validators.
  • Why onchain/token: onchain is the core of the product (confidential transactions + consensus); the BDX token is the native asset for fees, economic incentives (including masternode collateral) and the operation of the network.

How it works (very briefly)

  1. The user does: sends/receives transactions or uses the ecosystem services.
  2. The system does: applies cryptographic privacy mechanisms (ring signatures, stealth addresses, RingCT) and confirms blocks via a PoS model with masternodes (per the whitepaper).
  3. The user gets: confidential transactions/operations and the ecosystem services.
  4. Where the blockchain is: Beldex’s own L1 network (native coin BDX, the explorer is listed in links_*).
  5. Token role: fees/payments on the network + incentives/collateralization for masternodes (staking requirement).

Quick links: AI thesis fit

Project passport

Field Value
Project name Beldex
Also known as (aliases) BDX, Beldex Coin
Logo (logo) ../assets/beldex_logo.jpg
Token symbol (ticker) BDX
Category Infra
Primary chain (chain) Beldex
Type Appchain
Network status mainnet
Consensus (consensus) PoS (Beldex; masternodes + quorum)
Launch date (launch_date) —
Project status (status) active
Token (standard) native
Token contract native (no contract)
Token model (token_type) utility (payments + staking)
Max supply —
Issuance inflationary + burn (Flash fees)
Tokenomics (tokenomics, brief) PoS block rewards; masternode collateral 10000 BDX; Flash fee burning
Governance —
Admins/keys —
Audit —
Bug bounty —
Team (team) —
Funding (investors/funding) —
AI component (ai_component) —
Use‑case (use_case) confidential transactions/communications
DecAI Fit — AI thesis fit 0/6 — no AI reality and no AI intent (ai_score=0)
DecAI Fit component summary 0 / 3 / 2 / 2
Last verified 2026-02-10

General project overview

According to the whitepaper, Beldex describes itself as a PoS coin and an ecosystem for private transactions/messaging/online activity. The document lists cryptographic privacy mechanisms (RingCT, stealth addresses, ring signatures), as well as a network of masternodes as the validating/infrastructure layer.

Features/modules

  • Confidential transactions: ring signatures / RingCT / stealth addresses mechanisms (as in the CryptoNote/Monero approach).
  • PoS + masternodes: masternodes as block proposers/validators; a PoS quorum model (producer + 11 validators; 7/11 attest).
  • Flash: layer‑2 “instant transactions” involving masternodes, where the network fee from Flash transactions is burned (per the whitepaper).

Typical scenarios

  • Scenario 1: a user transfers BDX → the network ensures the privacy of the transaction parameters → the transaction is included in a block.
  • Scenario 2: an operator launches a masternode → locks collateral (10000 BDX) → receives a share of the rewards for participating in consensus/quorums.

Getting started (wallet/network)

  • What you need: a Beldex wallet/network client; for infrastructure — the masternode requirements/guide (see docs).
  • Network/chain: Beldex mainnet.
  • Fees: network fees; for Flash — a higher fee as described, part of which is burned.

Architecture/tech (non‑AI)

  • Components: the L1 blockchain + masternodes + ecosystem services (messenger/browser/VPN/wallet, per the whitepaper).
  • Participant roles: users, masternode operators, quorum validators.
  • Where logic runs: privacy and transaction validation — at the network protocol level; auxiliary ecosystem services — on top of the network.

Token/economics (expanded, no forecasts)

  • Fees and incentives: PoS block production with rewards; the whitepaper specifies the distribution of block rewards (example: 6.5 BDX, 10% node reward, 90% masternode reward).
  • Masternode collateral: a staking requirement of 10000 BDX (described as necessary for a masternode).
  • Burn mechanics: the fee from Flash transactions is burned (description in the whitepaper).

Governance

The whitepaper mentions the distribution of part of the rewards “to governance”, but the specific mechanism (DAO/voting/procedures) is not specified in the Tier‑1 sources above — which is why — is left in the passport.

Security and incidents

  • Audits: no public reports were found in the listed Tier‑1 links.
  • Security advisories: the security section on GitHub is listed.
  • Bug bounty: not found in Tier‑1 sources.

Project status and timeline

  • Current status: mainnet.
  • Key milestones: the transition to PoS (Bucephalus hardfork) is described in the whitepaper (Dec 10, 2021).

Ecosystem/integrations

  • Docs: GitBook docs.
  • Code: the GitHub organization Beldex‑Coin.

AI component of the project

  • What is real AI here? The Tier‑1 sources (whitepaper/docs) contain no claims about ML/AI models/agents/inference; the focus is privacy and network services.
  • What is truly onchain? All the logic of private transactions and consensus is implemented in Beldex’s own L1 network.
  • Why is a token needed? BDX is the base asset of the network: fees/payments + incentives and collateral for masternodes.
  • Red flags (based on the information found): substituting “confidential computation” for “AI computing”; what to double‑check: the current issuance/burn parameters and the actual governance mechanism (if claimed outside the whitepaper).

DecAI Fit component summary

  • DecAI Fit: 0/6 — no AI reality and no AI intent (ai_score=0)
Component Level Score
AI reality absent 0
Onchain necessity high 3
Token necessity medium 2
Evidence Tier‑1 present 2
Details

AI reality

AI_0 — AI intent (Tier‑1 roadmap) (1/0)

  • AI_0 (decision): 0
  • Claim (one line): There is no Tier‑1 statement/roadmap about AI.
  • Evidence: Tier‑1 — https://www.beldex.io/whitepaper.pdf
  • Why sufficient / why not (one line): the whitepaper describes privacy/consensus/services, but not AI.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 0
  • Claim (one line): No AI functionality is described.
  • Evidence: Tier‑1 — https://www.beldex.io/whitepaper.pdf
  • Why sufficient / why not (one line): there is no description of AI models/algorithms.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 0
  • Claim (one line): There is no Tier‑1 demo of an AI component.
  • Evidence: Tier‑1 — https://docs.beldex.io/
  • Why sufficient / why not (one line): the docs are devoted to wallets/masternodes/BelNet, without AI.
  • Conflict note (if any): —

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0
  • Metrics: —
  • Context (version/date/how measured): —
  • Evidence: Tier‑1 — https://www.beldex.io/whitepaper.pdf
  • Why sufficient / why not (one line): there are no AI metrics.
  • Conflict note (if any): —

AI_4 — tech description/architecture/versions (1/0)

  • AI_4 (decision): 0
  • Claim (one line): there is no technical description of AI models/architecture.
  • Evidence: Tier‑1 — https://www.beldex.io/whitepaper.pdf
  • Why sufficient / why not (one line): an AI component is absent in Tier‑1.
  • Conflict note (if any): —

Onchain necessity

OC_1 — contracts/addresses/chain (1/0)

  • OC_1 (decision): 1
  • Chain: Beldex mainnet
  • Addresses/identifiers: native coin BDX; the public network explorer
  • Evidence: Tier‑1 — https://explorer.beldex.io/
  • Why sufficient / why not (one line): the network and its state are observable via the official explorer.
  • Conflict note (if any): —

OC_2 — onchain beyond just a token (1/0)

  • OC_2 (decision): 1
  • What useful logic is onchain: private transactions (RingCT, etc.) and the PoS quorum consensus.
  • Evidence: Tier‑1 — https://www.beldex.io/whitepaper.pdf
  • Why sufficient / why not (one line): the whitepaper describes the protocol mechanics of privacy and PoS.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 1
  • “Replace the blockchain” test: replacing it with a centralized server removes the key property — trustless private transactions and consensus without a trusted operator.
  • Evidence: Tier‑1 — https://www.beldex.io/whitepaper.pdf
  • Why sufficient / why not (one line): the core of the product is a blockchain protocol of privacy/consensus.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): the token/coin BDX exists as the native asset of the network.
  • Evidence: Tier‑1 — https://www.beldex.io/whitepaper.pdf
  • Why sufficient / why not (one line): the whitepaper describes BDX as the protocol’s coin and the reward economy.
  • Conflict note (if any): —

TK_1..TK_4 (1/0)

TK_1 — payment for the service (1/0)

  • TK_1 (decision): 1
  • Claim (one line): network fees and Flash fees exist; the Flash fee is described as burned.
  • Evidence: Tier‑1 — https://www.beldex.io/whitepaper.pdf
  • Why sufficient / why not (one line): the document describes the fee model and the burn for Flash fees.
  • Conflict note (if any): —

TK_2 — incentives/collateral/penalties (1/0)

  • TK_2 (decision): 1
  • Claim (one line): a masternode requires collateral of 10000 BDX; rewards are distributed among nodes/masternodes.
  • Evidence: Tier‑1 — https://www.beldex.io/whitepaper.pdf
  • Why sufficient / why not (one line): the whitepaper describes the collateral and the reward mechanics.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 0
  • Claim (one line): the Tier‑1 sources contain no explicit description of a token‑based governance process.
  • Evidence: Tier‑1 — https://www.beldex.io/whitepaper.pdf
  • Why sufficient / why not (one line): “governance” is mentioned as a direction/reward allocator, without a specification of mechanisms.
  • Conflict note (if any): —

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 0
  • Claim (one line): the replaceability of BDX is not claimed and contradicts its role as the network’s native coin.
  • Evidence: Tier‑1 — https://www.beldex.io/whitepaper.pdf
  • Why sufficient / why not (one line): BDX is the base asset of the L1, not designed as a replaceable “app token”.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://www.beldex.io/whitepaper.pdf Beldex as a PoS coin with masternodes; privacy mechanics (RingCT/stealth/ring signatures); Flash and the burning of Flash fees; collateral of 10000 BDX
Tier‑1 https://docs.beldex.io/ the official docs of the project/ecosystem
Tier‑1 https://explorer.beldex.io/ observability of the network (explorer)
Tier‑1 https://github.com/Beldex-Coin/beldex/releases releases/history of code changes

No comments to display

Back to top