Crypto from zero: what a blockchain record can prove

Start with the record-keeping system

“Crypto” is a broad label for digital assets and systems that use cryptographic tools. Some networks maintain a shared ledger; an exchange may also keep an internal account database; a contract or issuer may make separate promises. Those records answer different questions. Ask first: which system is this claim about, and who controls its rules?

A blockchain groups and orders data under a network protocol. A user-facing wallet or exchange screen is an interface to records and permissions; it does not contain coins in the way a pocket contains cash. The phrase “on-chain” means that a claim is represented in a particular network’s recorded state, not that every real-world fact about it is proven.

Evidence: Bitcoin public ledger and signatures · BSC overview

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

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.

What the chain can record

For Bitcoin, the official beginner explanation describes a shared public ledger where confirmed transactions are recorded and used to calculate spendable balances. On an EVM network, the recorded state can include account balances, contract code and contract storage. These are examples from different systems, not one universal data model.

A record can help verify that a transaction was included under a particular network’s rules, what its visible fields say and whether execution produced a recorded result. It cannot by itself prove who used an address, whether goods were delivered, whether a person made a truthful promise, or whether an exchange credited a customer account.

Evidence: Bitcoin public ledger and signatures · Ethereum account keys and contract accounts · BSC overview

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

Ethereum account documentation: externally owned accounts use keys while contract accounts are governed by code. Other networks may differ; a signature proves a key-controlled authorization, not a real-world identity.

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.

A signature is not a person’s identity

A private key can authorize a transaction that a network accepts as signed under its rules. Ethereum documentation distinguishes key-controlled externally owned accounts from contract accounts controlled by program logic. A public address can therefore show where data was recorded without naming the human, organization or legal owner behind it.

Key access can be shared, stolen, delegated or controlled by code. If a signature verifies against a key, that supports a statement about authorization by that key or account rule; it does not prove that the signer was the rightful owner or that the action was voluntary. Keep personal identity and legal rights as separate questions.

Evidence: Ethereum account keys and contract accounts · U.S. custody and intermediary limitations

Ethereum account documentation: externally owned accounts use keys while contract accounts are governed by code. Other networks may differ; a signature proves a key-controlled authorization, not a real-world identity.

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.

Do not turn a record into a guarantee

Networks differ in how they order transactions, describe confirmations and handle reversals or reorganizations. A successful execution result means that the transaction followed the network’s execution rules at that point; it does not certify the safety of a token, a dApp, an issuer or a promise connected to it.

A token symbol, explorer label or screenshot is also not a complete identity check. A contract may have administrative controls, upgrade behavior or limited liquidity. Service eligibility, custody, insolvency treatment and consumer protections depend on the exact product, entity, agreement and jurisdiction; the cited U.S. bulletin has only its stated U.S. scope.

Evidence: BEP20 token-contract interface specification · U.S. custody and intermediary limitations · Ethereum account keys and contract accounts

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.

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.

Ethereum account documentation: externally owned accounts use keys while contract accounts are governed by code. Other networks may differ; a signature proves a key-controlled authorization, not a real-world identity.

Apply the distinction to Binance, BNB and BNB Chain

The names sound related but refer to different objects. Binance is a brand used by services with specific operators and terms; a balance in one of those services is an account record. BNB is a cryptoasset. BNB Chain includes distinct networks such as BNB Smart Chain. Do not read one screen or ticker as proof about all three.

On BNB Smart Chain, native BNB and a BEP-20 token are different kinds of network balance. BEP-20 is an interface standard for token contracts; using that standard does not certify the issuer or token economics. Check the exact network and contract, then check the relevant service account separately.

Evidence: BSC overview · BEP20 token-contract interface specification · U.S. custody and intermediary limitations

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.

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.

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.

Worked fictional example: a token event

Hypothetical only: an explorer page for a fictional BSC token called TEST shows a contract event transferring 4 TEST from “Address A” to “Address B.” If you first verify that the page is on BSC and the contract is the one you intended to examine, the record supports that the contract reported that transfer event under BSC rules.

It does not identify the people behind Address A or B, prove that TEST has a particular value, establish a legal claim against the issuer, or show that an exchange credited an account. If the question is about a Binance service balance, the next evidence is that service’s own account history and applicable terms—not a chain event alone. No TEST token, address, page or transfer exists in this example.

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

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.

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.

A short evidence checklist

Write down the exact claim and the record system that could support it: a network transaction, a token contract, an exchange account entry, an issuer term or a real-world delivery record. Match each question to the system that can answer it. If a claim crosses systems, collect separate evidence for each step.

Before acting, identify the network, asset representation, contract or service operator, relevant account and date. Record what remains unknown. A chain check can reduce one kind of uncertainty while leaving price, custody, counterparty, legal and fraud risks open.

Evidence: Bitcoin public ledger and signatures · BSC overview · U.S. custody and intermediary limitations

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

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.