Meridian Privacy (MDP) is a privacy protocol for the BNB Smart Chain, described as a non-custodial UTXO-based shielded pool using Groth16 zero-knowledge proofs to hide transaction amounts and participants. Its official website states it is “live on mainnet and testnet” and emphasizes open-source design and on-chain privacy for ERC-20 tokens. The native token contract is deployed at 0x7a67363885ebc01f1d2aef95b238e39ca1587777 on BSC, and is tracked on BscScan and Binplorer. The project’s whitepaper page repeats the same core description as the homepage, with no substantive technical or architectural detail beyond metadata. Social presence includes Twitter and Telegram channels, though no activity timestamps or follower metrics are supplied in evidence. The API snapshot from source_2 confirms the contract address, network, and token supply parameters (1B total, 0 circulating), and characterizes Meridian as a non-upgradable, non-pausable protocol—but offers no verification of deployment status, audit reports, or code availability. Key evaluation questions remain: Is the shielded pool operationally active? Where is the source code? Has any third-party audit been published? What evidence confirms live usage—not just deployment—of the Groth16 circuit or Merkle tree infrastructure?
Meridian Privacy claims to be a non-custodial UTXO shielded pool on BNB Smart Chain using Groth16 proofs, with live mainnet deployment. However, the supplied evidence contains no verifiable proof of operational status: no transaction history, contract audit reports, or functional wallet integration is present. The whitepaper and homepage (meridianprivacy.com, meridianprivacy.com/whitepaper) repeat identical metadata-only text — no technical architecture, circuit specifications, or testnet/mainnet verification details. Critically, the API source (CoinGecko) reports zero circulating supply and a fixed total/max supply of 1 billion MDP tokens, but provides no allocation breakdown, vesting schedule, team or treasury holdings, or unlock timeline. There is no evidence of token utility, revenue model, or user adoption — social links are unvisited and unverified; repository URLs are absent. The project’s core thesis — that it delivers private, composable, trust-minimized transactions — remains unsupported by code, on-chain activity, or third-party validation. Without evidence of working implementation, token distribution logic, or independent security review, the assessment cannot confirm viability or distinguish Meridian from conceptual or pre-launch proposals.
Overall score: 5/10 Confidence: Low
Meridian Privacy positions itself as a non-custodial UTXO shielded pool on BNB Smart Chain using Groth16 proofs, with claims of no upgrade, pause, or administrative functions (source_2). However, the supplied evidence contains no verifiable documentation of governance structure, decision rights, or loss allocation mechanisms. The whitepaper and website pages (meridianprivacy.com, meridianprivacy.com/whitepaper) provide only high-level product descriptions and metadata—no code repositories, audit reports, or technical specifications are present or linked. Crucially, there is zero evidence identifying team members, operators, or any accountable entity; the API snapshot (CoinGecko) states circulating supply is 0 and last updated its market data on 2026-09-25, but offers no treasury details, funding sources, or operational accountability. Incentive alignment cannot be assessed: no token distribution, vesting, or staking mechanics are disclosed, and the $1B max supply (CoinGecko) lacks context for utility or issuance schedule. The project’s core thesis—that it delivers functional, trust-minimized privacy on BSC—lacks verification: no deployed contract interaction evidence, testnet/mainnet transaction samples, or third-party validation is provided. Governance remains entirely opaque: no voting mechanism, multisig signers, timelocks, or emergency controls are described or linked. Without evidence of who controls protocol parameters or bears losses in failure, the incentive map collapses to speculation. This evidentiary gap triggers the rubric’s hard cap: low confidence and no score above 6.
Overall score: 5/10 Confidence: Low