Binance-Peg BTCB

Rejected venues wait the longest for re-review; a rejection has to earn another look before the scheduled date.

REJECTED. BTCB is a single-entity custodial claim on Bitcoin, not Bitcoin: Binance mints it 1:1 on BNB Smart Chain under an upgradeable-proxy contract Binance itself controls, and redemption requires depositing BTCB into a Binance.com account rather than a permissionless on-chain burn-and-claim. That combination — one entity holding custody of the reserve, upgrade authority over the token’s logic, and the only redemption gate — is the same class of instrument this registry already rejects for CEX-issued liquid-staking tokens under the cex-wrapped-staking rule, applied here to Bitcoin instead of staked ETH or SOL. No independent reserve attestation for BTCB specifically was identified.

Kill criteria: the events that revoke this verdict
• Binance publishes an independently audited, real-time proof-of-reserves attestation for BTCB specifically, not an aggregate exchange figure
• A genuinely permissionless burn-and-release redemption path is demonstrated that does not require a Binance.com account
• The upgradeable-proxy admin key is transferred to a disclosed multisig with published signers, or the contract is demonstrated immutable
• No realized freeze or blacklist event against BTCB holders occurs for 12 consecutive months after blacklist capability, or its confirmed absence, is publicly disclosed

The research file

Mechanism

BTCB (Binance-Peg BTCB Token, BEP-20 contract 0x7130d2a12b9bcbfae4f2634d864a1ee1ce3ead9c on BNB Smart Chain) is issued under Binance’s ”Project Token Canal”: a user deposits BTC to a Binance-controlled custodian address and Binance mints BTCB 1:1 on BSC. The contract deploys via an AdminUpgradeabilityProxy delegating to a BinancePeggyToken implementation, so Binance holds upgrade authority over the token’s logic, not merely custody of the underlying reserve.

Control and governance

Fully centralized: Binance controls minting, the underlying BTC reserve, and — via the upgradeable proxy — the contract logic itself, with no on-chain governance process. No independent reserve-attestation mechanism specific to BTCB was found in this pass. Redemption is not a permissionless on-chain burn: a holder must first deposit BTCB into a Binance.com account, a KYC’d off-ramp, before it can be converted back to BTC. A holder who only interacts on-chain has no path to par redemption at all.

Incident record

No BTCB-contract-specific depeg or custody failure was identified. One adjacent incident is worth noting for context rather than as a direct BTCB failure: a July 2026 oracle-price-manipulation attack on the Balance Coin/42DAO project used BTCB as attacker collateral against a falsified price feed on a third-party lending vault — a failure of that third party’s oracle design, not of BTCB’s mint, custody, or redemption process. No realized instance of Binance freezing or blacklisting BTCB holder addresses specifically was found, though the upgradeable-proxy admin design means that capability likely exists structurally even without a documented use.

Exit

Par redemption requires a Binance.com account and its KYC process; it is not available to a holder acting purely on-chain. Secondary-market exit — selling BTCB on a DEX — is available without a Binance account, but exposes the holder to market depth and slippage rather than par redemption, and offers no protection if confidence in Binance’s custody or the peg itself deteriorates, since the underlying claim still ultimately depends on Binance to honor it.

Comparison

Native BTC held directly carries no custodial or counterparty dependence. WBTC, reviewed separately in this registry and also rejected, at least uses a named multisig across three custodians rather than one single entity holding both custody and upgrade authority; BTCB concentrates every point of control in Binance alone, with redemption additionally gated behind an exchange account rather than any documented multisig-triggered process. This is a more centralized structure than WBTC’s current one, not a less centralized one.

Sources

The claims above trace to these. Where a number could not be independently verified, the thesis says so.

• BNB Chain Blog — Binance presents Project Token Canal · primary · accessed 2026-08-17
  Supports: issuance program, Binance-Peg design
• BNB Chain — token-canal-project repository · primary · accessed 2026-08-17
  Supports: BinancePeggyToken.sol, AdminUpgradeabilityProxy architecture
• Trust Wallet Community — what are Binance-Peg tokens · secondary · accessed 2026-08-17
  Supports: redemption requires Binance.com account
• OneKey — BTCB deep dive: token fundamentals, risks, and future trajectory · secondary · accessed 2026-08-17
  Supports: mechanism summary, risk overview
• Bitcoin Foundation — Balance Coin crashes after BTCB oracle attack · secondary · accessed 2026-08-17
  Supports: adjacent third-party oracle incident

Inherited controls

The verdict above grades the protocol layer. Every position also inherits the asset it holds and the chain it settles on. The least safe layer sets the position’s grade, and the position table names which one that is.