Skip to main content

MBD Financials

MBD Financials — 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).

MBD Financials — an AI/Other project on Ethereum, token (symbol: MBD).

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: an ecosystem that combines DeFi products, a marketplace, game scenarios and an RWA direction (per the whitepaper and the website).
  • Who it’s for: Web3 users who need a set of products (DeFi/marketplace/game) around RWA scenarios.
  • Why onchain/token: onchain is used for the token and the RWA/NFT logic (per the whitepaper); the token is claimed as a utility token for fees/access and parts of the ecosystem.
  • What you can actually touch (Tier‑1): the DeFi interface https://hybridex.app/ (other product URLs are also listed on the website).

How it works (very briefly)

  1. The user does: uses one of the product modules (DeFi platform/marketplace/game mode).
  2. The system does: carries out operations with tokens/NFTs/RWA objects and the related onchain logic.
  3. The user gets: the result of the action (swap/trade/issuance/exchange/game reward) within the product.
  4. Where the blockchain is: the token and smart contracts (including the RWA/NFT layer) run onchain (claimed: Ethereum).
  5. Token role (if any): the whitepaper describes utilities: fees, discount tiers, game utility, participation in governance (as a whitepaper claim).

Quick links: AI thesis fit

Project passport

Field Value
Project name MBD Financials
Also known as (aliases) Metaverse Business District, MBD
Logo (logo) —
Token symbol (ticker) MBD
Category AI/Other | DeFi
Primary chain (chain) Ethereum
Type EVM
Network status mainnet
Consensus (consensus) PoS (Ethereum)
Launch date (launch_date) —
Project status (status) active
Token (standard) ERC-20
Token contract 0xaAf449Bf8A33a32575C31BA8CBb90612Dd95aCFa
Token model (token_type) utility (fees + discounts + game + governance)
Max supply 40000000000 (per the whitepaper)
Issuance —
Tokenomics (tokenomics, brief) utility: marketplace fees, discount tiers, game utility, governance (per the whitepaper)
Governance —
Admins/keys —
Audit yes
Bug bounty —
Team (team) —
Funding (investors/funding) —
AI component (ai_component) AI assistants/search/recommendations
Use‑case (use_case) RWA marketplace + DeFi + game
DecAI Fit — AI thesis fit 5/6 — high alignment with the Decentralized AI thesis
DecAI Fit component summary ai_score 3 / onchain_score 2 / token_score 2 / evidence_score 3
Last verified 2026-02-11

General project overview

MBD Financials publishes a whitepaper describing an ecosystem of three main “pillars”: Marketplace (including gold‑backed NFTs), 360 DeFi platform and the Golddigers game. It also claims AI integration into various parts of the product (for example, an AI shopping assistant and the simplification of user decisions), as well as an onchain layer on Ethereum (token, smart contracts and RWA/NFT logic).

Features/modules

  • DeFi module (claimed): swaps/routing/financial features within the ecosystem.
  • Marketplace (claimed): trading of NFT/RWA objects; the whitepaper describes a gold‑backed NFT vault.
  • Game module (claimed): a Tap2Earn/PvP game tied to RWA NFTs.
  • AI layer (claimed): an AI assistant for discovery/explanations/navigation and “AI‑enhanced shopping”.

Typical scenarios

  • Scenario 1: the user opens the DeFi interface → performs a swap/operation → receives the result onchain.
  • Scenario 2: the user uses the marketplace → buys/sells NFT/RWA objects → receives onchain artifacts.
  • Scenario 3: the user plays Golddigers → receives “shards/rewards” → converts them into NFT objects (per the description in the whitepaper/website).

Getting started (wallet/network)

  • What you need: access to one of the product URLs (for example, https://hybridex.app/); an EVM wallet for operations on Ethereum.
  • Network/chain: Ethereum (whitepaper and token contract).
  • Fees: Ethereum fees for transactions; fees inside the products require separate verification.

Architecture/tech (non‑AI)

  • Components (per the whitepaper): ERC‑20 token, NFT/RWA contracts (gold vault), DeFi layer, oracle components for prices/metadata, game mechanics.
  • Participant roles: users, operators/admins (per the description of security roles in the whitepaper), external providers (vault/oracle — as claimed).
  • Where logic runs: the token and key smart contracts — onchain (Ethereum); AI assistants and parts of the UX — offchain.
  • Dependencies: oracle sources, web application infrastructure, storage/validation providers for RWA (per the description).

Token/economics (expanded, no forecasts)

  • Token utility (Tier‑1, whitepaper): marketplace fees, discount tiers, game utility; governance and future staking/rewards are also mentioned.
  • Protocol necessity drivers: the token is described as the connecting element of the ecosystem (fees/discounts/game/treasury routing).
  • Who pays fees: users during transactions on Ethereum.
  • Where fees go: network fees — to Ethereum validators; the distribution of fees inside the product requires separate verification.
  • Issuance/burn: the whitepaper states a total supply of 40,000,000,000 MBD; other parameters require separate verification.
  • Incentive mechanisms: staking/rewards are listed as future; details not verified.
  • Distribution/vesting: not established per Tier‑1.
  • Treasury: treasury routing is mentioned; control details require verification.

Governance

  • Who makes decisions: not established per Tier‑1.
  • How protocol parameters change: not established per Tier‑1.
  • Where decisions are discussed/made: the project’s public channels (links in links_*); a formal governance process (DAO/snapshot) is not confirmed.
  • Keys/multisig: not established per Tier‑1.

Security and incidents

  • Audits: the website lists CertiK and Paladin as auditors (external audit pages).
  • Bug bounty: not found per Tier‑1.
  • Incidents: no public postmortems were found per Tier‑1.
  • Threat model (what to double‑check): exactly which contracts are covered by the audits; admin roles/keys (the whitepaper has roles); the security of the oracle layer; the legal/compliance parts of RWA.

Project status and timeline

  • Current status: active (the website and product URLs are available; the token contract exists onchain).
  • Key releases/milestones: not established per Tier‑1.
  • Roadmap: https://docs.mbdfinancials.com/

Ecosystem/integrations

  • Integrations: EVM wallets and Ethereum infrastructure; the ecosystem’s product web modules (for example, https://hybridex.app/).
  • Partners: not established per Tier‑1.
  • Where it’s actually used: per Tier‑1, the public entry points (website/DeFi interface) are confirmed; usage metrics require separate verification.

AI component of the project

  • What is real AI here? the whitepaper claims AI assistants (shopping assistant, AI‑enhanced shopping) and the use of AI to simplify user actions/decisions.
  • What is truly onchain? the token and RWA/NFT contracts on Ethereum; the whitepaper describes the vault architecture and security controls.
  • Why is a token needed? the whitepaper describes the token’s utility (fees/discount tiers/game utility) and additional functions (governance/future staking).
  • Red flags (what to double‑check): which AI modules are actually available to the user now; which contracts/addresses are deployed and where their list is; what CertiK/Paladin covered; which roles/keys have the right to pause/mint/admin actions.

DecAI Fit component summary

  • DecAI Fit: 5/6 — high alignment with the Decentralized AI thesis
Component Level Score
AI reality high 3
Onchain necessity medium 2
Token necessity low 2
Evidence Tier‑1 present 3
Details

AI reality

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

  • AI_0 (decision): 0
  • Claim (one line): The AI component is described as part of the product (assistant/AI integration), so AI_0 is not used as “intent only”.
  • Evidence: Tier‑1 — https://mbdfinancials.com/whitepaper
  • Why sufficient / why not (one line): there are descriptions of AI modules in the whitepaper.
  • Conflict note: —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 1
  • Claim (one line): The AI assistant is used for discovery/explanations/navigation and “AI‑enhanced shopping” (as described in the whitepaper).
  • Evidence: Tier‑1 — https://mbdfinancials.com/whitepaper
  • Why sufficient / why not (one line): the whitepaper describes the functions of the AI assistant and the areas of application.
  • Conflict note: —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 1
  • Claim (one line): the ecosystem’s product URLs are available (for example, the Hybridex DeFi interface).
  • Evidence: Tier‑1 — https://mbdfinancials.com
  • Why sufficient / why not (one line): the official website has direct links to the products (Launch DeFi/Marketplace/Game).
  • Conflict note: —

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0
  • Metrics: —
  • Context (version/date/how measured): —
  • Evidence: Tier‑1 — https://mbdfinancials.com/whitepaper
  • Why sufficient / why not (one line): AI quality metrics/benchmarks are not provided in the whitepaper.
  • Conflict note: —

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

  • AI_4 (decision): 1
  • Claim (one line): the whitepaper contains sections on the technical architecture of the RWA layer and mentions AI components.
  • Evidence: Tier‑1 — https://mbdfinancials.com/whitepaper
  • Why sufficient / why not (one line): there are technical details on the components (contracts/roles/oracles) and descriptions of the AI modules.
  • Conflict note: —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: Ethereum
  • Addresses/identifiers: ERC‑20 0xaAf449Bf8A33a32575C31BA8CBb90612Dd95aCFa
  • Evidence: Tier‑1 — https://mbdfinancials.com/whitepaper ; https://etherscan.io/token/0xaAf449Bf8A33a32575C31BA8CBb90612Dd95aCFa
  • Why sufficient / why not (one line): the whitepaper states the network/address of the token, and the explorer provides the onchain artifact.
  • Conflict note: —

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

  • OC_2 (decision): 1
  • What useful logic is onchain: RWA/NFT vault logic and DeFi operations/swaps/settlement support (per the whitepaper).
  • Evidence: Tier‑1 — https://mbdfinancials.com/whitepaper
  • Why sufficient / why not (one line): the whitepaper describes the GoldVault architecture, the roles of the contracts and onchain swapping.
  • Conflict note: —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: no explicit Tier‑1 justification of onchain criticality (in terms of trustless properties) was found.
  • Evidence: Tier‑1 — https://mbdfinancials.com/whitepaper
  • Why sufficient / why not (one line): onchain components are described, but without a formal test of “without the blockchain the product breaks down”.
  • Conflict note: —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): the project has a token, MBD (ERC‑20).
  • Evidence: Tier‑1 — https://mbdfinancials.com/whitepaper ; https://etherscan.io/token/0xaAf449Bf8A33a32575C31BA8CBb90612Dd95aCFa
  • Why sufficient / why not (one line): the whitepaper records the network/address of the token, and the explorer provides the onchain artifact at the address.
  • Conflict note: —

TK_1..TK_4 (1/0)

TK_1 — payment for the service (1/0)

  • TK_1 (decision): 1
  • Claim (one line): the whitepaper states “Marketplace fees” and the token’s utility in the ecosystem.
  • Evidence: Tier‑1 — https://mbdfinancials.com/whitepaper
  • Why sufficient / why not (one line): this is a direct Tier‑1 description of the token’s utility.
  • Conflict note: —

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

  • TK_2 (decision): 0
  • Claim (one line): the whitepaper mentions “future staking and rewards”, but as an operating protocol mechanism this is not confirmed per Tier‑1.
  • Evidence: Tier‑1 — https://mbdfinancials.com/whitepaper
  • Why sufficient / why not (one line): future plans are insufficient for a 1 without artifacts/conditions and a current implementation.
  • Conflict note: —

TK_3 — governance (1/0)

  • TK_3 (decision): 1
  • Claim (one line): the whitepaper states “governance participation” as part of the token’s utility.
  • Evidence: Tier‑1 — https://mbdfinancials.com/whitepaper
  • Why sufficient / why not (one line): this is a Tier‑1 description of the token’s role in governance (as a claimed function).
  • Conflict note: —

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 0
  • Claim (one line): the replaceability of the token is not established: some functions are claimed to be tied to the token (fees/discounts/governance), but the protocol details are not verified.
  • Evidence: Tier‑1 — https://mbdfinancials.com/whitepaper
  • Why sufficient / why not (one line): without a formal specification and a current implementation, “replaceable/irreplaceable” cannot be strictly proven.
  • Conflict note: —

Evidence (table)

Tier Source What it proves
Tier‑1 https://mbdfinancials.com/whitepaper Tier‑1 whitepaper: AI modules, RWA/NFT architecture, tokenomics/utility, network/address of the token
Tier‑1 https://mbdfinancials.com Tier‑1 website: direct links to the products (DeFi/Marketplace/Game) and audit claims
Tier‑1 https://hybridex.app demo/entry point into the DeFi module (app)
Tier‑1 https://etherscan.io/token/0xaAf449Bf8A33a32575C31BA8CBb90612Dd95aCFa onchain fact: the MBD token contract
Tier‑1 https://skynet.certik.com/projects/mbd-financials Audit/verification of the MBD Financials project (security artifact, auditor page).
Tier‑1 https://paladinsec.co/projects/mbd-financials/ Audit of the MBD Financials project (security artifact, auditor page).
Tier‑2 https://www.coingecko.com/en/coins/mbd-financials reference token card (aggregator; not proof of technology)
Tier‑2 https://coinmarketcap.com/currencies/mbd-financials/ reference token card (aggregator; not proof of technology)

No comments to display

Back to top