Binance-Peg BTCB
We reject BTCB because it is a single-entity custodial claim on Bitcoin, not Bitcoin. Binance mints it 1:1 on BNB Smart Chain under an upgradeable-proxy contract that Binance itself controls, and redemption requires depositing BTCB into a Binance.com account rather than using a permissionless on-chain burn-and-claim process. One entity holds the reserve, controls upgrades to the token’s logic, and serves as the only redemption gate. This is the same class of instrument that this registry rejects for CEX-issued liquid-staking tokens under the cex-wrapped-staking rule, applied here to Bitcoin instead of staked ETH or SOL. We identified no independent reserve attestation for BTCB specifically.
- 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
Watched nightly: a warning on its venues or files, or a cited document that changes, reopens the memo. The first confirmation is due 2026-11-17.
The research file
Mechanism
Binance issues BTCB (Binance-Peg BTCB Token, BEP-20 contract 0x7130d2a12b9bcbfae4f2634d864a1ee1ce3ead9c on BNB Smart Chain) under its ”Project Token Canal.” A user deposits BTC to a Binance-controlled custodian address, and Binance mints BTCB 1:1 on BSC. The contract uses an AdminUpgradeabilityProxy that delegates to a BinancePeggyToken implementation, so Binance controls upgrades to the token’s logic as well as custody of the underlying reserve.
Control and governance
Binance controls minting, the underlying BTC reserve, and, through the upgradeable proxy, the contract logic itself. There is no on-chain governance process. We found no independent reserve-attestation mechanism specific to BTCB 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 converting it back to BTC. A holder who only transacts on-chain has no path to par redemption at all.
Incident record
We identified no BTCB-contract-specific depeg or custody failure. One nearby incident is worth noting for context, not 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. That was a failure of the third party’s oracle design, not BTCB’s mint, custody, or redemption process. We found no case of Binance freezing or blacklisting BTCB holder addresses specifically, though the upgradeable-proxy admin design means that capability likely exists 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 only on-chain. A holder can exit on the secondary market by selling BTCB on a DEX without a Binance account, but that route exposes the holder to market depth and slippage rather than offering par redemption. It also offers no protection if confidence in Binance’s custody or the peg itself falls, since the underlying claim still depends on Binance to honor it.
Comparison
Native BTC held directly has 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 entity holding both custody and upgrade authority. BTCB puts every point of control in Binance alone. It also gates redemption behind an exchange account rather than any documented multisig-triggered process. This structure is more centralized than WBTC’s current structure, not less centralized.
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 research above describes the protocol layer. Every position also inherits the asset it holds and the chain it settles on. The layer with the most administrative power sets the position’s effective control; that describes control, not quality or suitability.
| Chain | Verdict | Control | Control constraint |
|---|---|---|---|
| BNB Smart Chain | Rejected | Issuer can freeze | the validator set concentrates around one company, and the chain has been halted by decision. |