Native BTC, token representations and exchange balances

Three records can display a BTC-shaped number

BTC is the unit used by the Bitcoin network. Bitcoin's documentation describes a shared transaction record and signatures that authorize spending under the network's rules. A public address or transaction record does not by itself identify a person's legal identity.

An exchange may display a BTC-denominated account balance in its own books. A token on BNB Smart Chain or another network may be designed to represent or track BTC, but that token is a separate contract asset. Its ticker and claimed backing do not turn it into native Bitcoin or establish a redemption right.

Evidence: Bitcoin public ledger and signatures · U.S. custody and intermediary limitations · BEP20 token-contract interface specification

Bitcoin-specific explanation of its public ledger and private-key signatures; it does not define every blockchain or determine legal ownership.

U.S. investor education. The bulletin describes how an unregistered intermediary may hold crypto assets through keys it controls; it is not a universal legal classification, a determination of title to a specific asset or terms for Binance.com/Binance.US.

Used only for the BEP20 token-contract interface and the methods/events named in the specification. It does not prove that a particular deployed contract conforms, is authentic, safe, issued by a named party, backed by reserves or equivalent to an asset on another network. The file contains historical Beacon Chain wording that is not treated as current migration guidance.

The control and evidence depend on the system

A custodial service can record a customer balance in its own account system while the customer does not control the corresponding on-chain private keys. The SEC Office of Investor Education and Advocacy and FINRA described this arrangement for crypto assets held with unregistered intermediaries in a U.S. investor bulletin dated July 12, 2023; that example is not a universal legal rule. For Binance, identify the exact service and applicable terms: Binance.com and Binance.US are separate services with different terms, and the brand name alone does not prove which entity or withdrawal route applies.

A token standard such as BEP-20 defines a contract interface, not authenticity, reserves, issuer solvency or a conversion promise. A bridge is a separate system with its own custody or verification design and risks. A real token claim requires evidence for the exact contract, network, issuer and redemption terms; a matching BTC ticker is only a label.

Evidence: Binance.com terms and ADGM entities · Binance.US terms and named operator · BEP20 token-contract interface specification · Bridge risks · BSC overview · U.S. custody and intermediary limitations

The page currently names Nest entities regulated in ADGM. This is evidence for the entities and scope stated on that page only, not a universal operator list or terms for every region, product or customer.

These are Binance.US terms, not Binance.com terms. The page names BAM Trading Services Inc. and related entities for those services; this does not establish the operator or user rights for another region or product. Read the terms applicable to the specific account and jurisdiction.

Used only for the BEP20 token-contract interface and the methods/events named in the specification. It does not prove that a particular deployed contract conforms, is authentic, safe, issued by a named party, backed by reserves or equivalent to an asset on another network. The file contains historical Beacon Chain wording that is not treated as current migration guidance.

General bridge concepts from ethereum.org. Designs differ; this source does not verify any named bridge, BTC representation, issuer backing or redemption promise.

Used only for BNB Smart Chain identity and EVM compatibility. The same page includes time-bound performance, fee and adoption figures; they are not treated as current facts or a current support/availability list.

U.S. investor education. The bulletin describes how an unregistered intermediary may hold crypto assets through keys it controls; it is not a universal legal classification, a determination of title to a specific asset or terms for Binance.com/Binance.US.

Solved fictional check: classify before interpreting

Fictional worksheet, not a live account: an exchange screen says 0.0100 BTC; a BSC explorer page shows a made-up token called BTCx at a fictional address; no Bitcoin transaction hash is supplied. The first item establishes only that the screen displays an account entry denominated in BTC. The second is a token record on BSC, not proof of native BTC or redeemability. Nothing here establishes that the records are related.

Solution: keep three rows in your notes—service account claim, BSC token record and Bitcoin network record. Without a transaction ID or account terms, you cannot infer which system holds an asset, whether it is withdrawable, or what backs BTCx. Do not add the amounts together: the units may refer to different rights and systems.

Evidence: U.S. custody and intermediary limitations · Bitcoin public ledger and signatures · BEP20 token-contract interface specification

U.S. investor education. The bulletin describes how an unregistered intermediary may hold crypto assets through keys it controls; it is not a universal legal classification, a determination of title to a specific asset or terms for Binance.com/Binance.US.

Bitcoin-specific explanation of its public ledger and private-key signatures; it does not define every blockchain or determine legal ownership.

Used only for the BEP20 token-contract interface and the methods/events named in the specification. It does not prove that a particular deployed contract conforms, is authentic, safe, issued by a named party, backed by reserves or equivalent to an asset on another network. The file contains historical Beacon Chain wording that is not treated as current migration guidance.

Verify the claim without sending funds

Record the service name and region, the exact asset label, the network shown in the service's current receive or withdrawal instructions, and whether evidence is an exchange record, Bitcoin transaction or token contract. If a transfer has already happened, use only the transaction hash and network that the sender actually used. A wallet showing the same address on two networks is not proof that a balance moved between them.

Do not send a small test just to learn what a label means. Confirm support and deposit/withdrawal status in the exact service's current instructions first. If a representation's issuer, backing or redemption terms cannot be independently documented, mark those fields unknown. The safe answer to the fictional worksheet is: BTC-denominated exchange balance, separate unverified BSC token, no evidence of a Bitcoin transaction.

Evidence: Binance.com terms and ADGM entities · Binance.US terms and named operator · Bitcoin public ledger and signatures · Bridge risks

The page currently names Nest entities regulated in ADGM. This is evidence for the entities and scope stated on that page only, not a universal operator list or terms for every region, product or customer.

These are Binance.US terms, not Binance.com terms. The page names BAM Trading Services Inc. and related entities for those services; this does not establish the operator or user rights for another region or product. Read the terms applicable to the specific account and jurisdiction.

Bitcoin-specific explanation of its public ledger and private-key signatures; it does not define every blockchain or determine legal ownership.

General bridge concepts from ethereum.org. Designs differ; this source does not verify any named bridge, BTC representation, issuer backing or redemption promise.