It is useful to think of a cryptocurrency purchase not as a single transaction, but as a chain of activity that leaves three kinds of records. The first consists of records held by intermediaries: exchanges, banks, payment services, or exchangers. The second consists of technical data held by the services and apps used to make the transaction. The third is the blockchain record itself. Each layer shows something different: the blockchain records the movement of assets, while an intermediary may know who initiated the transaction. When these records are combined, a pseudonymous address can sometimes be linked to a specific person. That link is not a property of the blockchain itself; establishing it requires additional evidence from outside the chain.
How a Blockchain Records a Transfer
Bitcoin uses the UTXO model—unspent transaction outputs. Coins are not held in an account bearing the owner’s name. Instead, they exist as outputs from previous transactions that can be spent by someone who controls the required key. A new transaction specifies which outputs are being spent and creates new outputs for the recipients. In simplified terms, the total value of the inputs equals the total value of the outputs plus the network fee. The blockchain shows the addresses, amounts, and links between the outputs being spent and the new outputs; it does not show the owners’ names.
For example, a wallet spends an output worth 0.015 BTC, sends 0.010 BTC to a recipient, creates 0.0049 BTC in change for the sender, and pays a 0.0001 BTC network fee. This is an illustrative example, but it highlights an important point: a transaction can include not only a payment to the recipient, but also a change output. An observer can see the transaction’s structure, but cannot determine from that alone who controls each address. Analysts may form hypotheses about links between addresses, but clustering addresses and identifying a person are different tasks based on different kinds of evidence.
Ethereum-based networks work differently. Accounts have public addresses and states, and a signed transaction can do more than transfer ETH: it can call a function in a smart contract. As a result, a DEX transaction may show the address that submitted it, the contract address, the function called, the call data, and events emitted by the contract. For example, a token swap may show that a wallet interacted with a DEX contract, while event logs may show which tokens moved and in what amounts. This still does not automatically reveal the wallet owner’s name, but it creates a detailed public record of the address’s activity.
Buying Through a Centralized Exchange
Suppose Anna deposits €1,000 into a centralized exchange, buys BTC, and withdraws it to a personal wallet. The exchange may be able to link her account to her KYC documents, deposit method, purchase time and amount, withdrawal address, and transaction ID. Her bank, in turn, can see the transfer to the exchange. The Bitcoin blockchain records the withdrawal to the specified address, and subsequent transactions involving that address remain part of the public history.
This creates a chain of connections: the bank knows Anna sent money to the exchange; the exchange knows which account bought the BTC and where it was withdrawn; and the blockchain shows the subsequent movement of funds from that address. This does not mean that every observer can immediately see Anna’s name. But the exchange may have a direct link to her account, while an outside analyst may be able to establish a link if exchange data or other evidence becomes available through lawful means. An exchange may also use an internal ledger: a purchase made within the platform is not necessarily a separate blockchain transaction. A public blockchain record usually appears when cryptocurrency is deposited or withdrawn.
In some jurisdictions, transfers between crypto service providers are subject to requirements commonly known as the Travel Rule. Regulated providers may be required to collect and transmit information about the sender and recipient for certain transfers. Applicability, thresholds, and the information required vary by country and circumstance, so there is no single universal threshold that applies everywhere.
Buying Through P2P
Now suppose Anna buys BTC from another person through a P2P marketplace and sends that person €1,000 by bank transfer. If the transaction takes place through a marketplace, the platform may retain records of the parties’ accounts, the listing, messages, transaction time and amount, and any dispute. The bank may retain information about the payment, including the sender, recipient, amount, and time. The seller sees the payment and the address to which the BTC is sent; the blockchain records the crypto transfer itself.
If the parties arrange the deal directly, without a marketplace, there will be no marketplace records. But that does not remove the bank record if a bank transfer was used, nor does it erase a cryptocurrency transfer from a public blockchain. P2P changes who holds the information: instead of one centralized service, records may be distributed among the bank, the parties, and the platform, if one was involved.
DEXs and Self-Custody Wallets
When using a DEX, users generally do not transfer their assets to an exchange account with a personal balance. Instead, they sign a transaction from their own wallet. Suppose Anna’s wallet swaps 1,000 USDC for ETH. The blockchain may record a call to a DEX contract, the wallet address, and the result of the swap, including token movements reflected in contract events. The DEX itself may not know Anna’s name if she has not created an identifiable account, but the address and transaction are public.
In addition to the blockchain record, technical requests may pass through the DEX website, an aggregator, or a network access provider. These services may receive technical information about requests; the specific data collected and how long it is retained depend on their architecture and policies. If the address was previously funded by an exchange where Anna completed KYC, the connection between the address and her account may have been created not by the DEX, but when she deposited or withdrew through the exchange. The absence of a document check during the swap does not mean the transaction history is hidden from blockchain observers.
What an Exchanger May Retain
The term “exchanger” can refer to different kinds of services: a website that arranges a swap, an intermediary, a custodial service, or a platform that forwards an order to a partner. Depending on how it operates, a service may retain an order number, timestamp, exchange rate, amount, sending and receiving addresses, transaction IDs, support messages, and contact information if the customer provided it. Some services may request documents or additional information about a transaction; others may not. So the absence of KYC for a particular exchange does not mean there are no records at all: transaction records may remain on the public blockchain, while order details may be held by the service or its partners.
How BTC, XMR, and ZEC Differ
Bitcoin is pseudonymous, but public. Its blockchain allows observers to see transactions, addresses, amounts, and the movement of coins. An owner’s name is not recorded in a transaction, but an address may be linked to a real person through exchange data, a bank payment, a publicly posted address, or other sources. As such links accumulate, it may become possible to examine the history of the associated addresses. However, an analytical inference should not be confused with a name being directly recorded on the blockchain: address clustering suggests that addresses may be controlled by the same party, while attributing them to a specific person requires separate external evidence.
Monero, or XMR, works differently: by default, the protocol hides several key elements of a transaction. Ring signatures make it harder to determine which output was actually spent; one-time recipient addresses make it harder to match a public address to a specific incoming payment; and RingCT hides the amount while still allowing the network to verify that the transaction is valid. This changes what can be learned from the public blockchain, but it does not eliminate possible records outside it—for example, exchange records, bank payments, messages, or information disclosed by the user.
Zcash, or ZEC, supports both transparent and shielded transactions. Transfers between transparent addresses show the sender, recipient, and amount on the blockchain. Shielded transactions use zero-knowledge proofs so the network can verify that a transaction is valid without publishing those details. It is therefore important to distinguish not only the asset, but also the transaction type: transparent and shielded transfers expose different amounts of information on the public chain. Movements between the transparent and shielded parts may also reveal information on the public side of the transition. An exchange or exchanger may still keep its own records of a ZEC purchase or withdrawal.
Написать Join — чтобы участвовать в обсуждении.