Can a crypto transaction be reversed? Who can freeze, block or claw back crypto
Why bitcoin and ether transfers can't be undone, and the exceptions: stablecoin issuers, exchanges, network security councils and hard forks like the DAO fork.
Figures checked against 7 official and primary sources on . See the sources · How we check
Key points
- A confirmed crypto transfer can't be reversed by the sender. Bitcoin.org says a bitcoin payment can only be refunded by the person who received it.
- But some parties can freeze or block funds: stablecoin issuers like Tether and Circle, exchanges and other services, and some networks with emergency powers.
- On Arbitrum, a Security Council of 12 members can take emergency actions with 9 approvals. TRM said it moved about $30 million away from the Binance attacker.
- Reversing history on a whole blockchain is rare. The 2016 DAO fork moved stolen ether back, and split Ethereum in two.
In this guide
One of the first things people learn about crypto is that transfers are final: there’s no bank to call and no “undo” button. That’s mostly true. But the October 2026 Binance hack showed that billions of dollars of stolen crypto can be frozen, and even moved, by the right parties.
This guide explains why most transactions can’t be reversed, and the exceptions that matter.
Why transactions are final
Once a transaction is confirmed on a public blockchain, it’s part of a shared record kept by the network’s nodes. There’s no central operator who can edit it.
Bitcoin.org puts it simply: a bitcoin transaction can’t be reversed; it can only be refunded by the person receiving the funds. ethereum.org says the same for Ethereum: once a transaction is confirmed, you can’t cancel it. Bitcoin.org advises doing business with people and organizations you know and trust, or who have an established reputation.
That’s why mistakes and scams are so costly. See how to send crypto safely.
Who can still freeze or block crypto
Reversing a transaction is different from stopping funds from moving. Several parties can do the latter.
1. Stablecoin issuers
Companies that issue stablecoins control their tokens’ smart contracts. Circle’s terms say it can block USDC addresses it judges may be linked to illegal activity, and block transfers to and from an address on chain. Tether’s terms let it freeze tokens and blacklist addresses too. After the Binance hack, TRM said issuers froze about $2.67 billion in stablecoins. See how stablecoin issuers freeze stolen crypto.
2. Exchanges and other services
Anything held on a platform can be frozen by that platform. After the 2025 Bybit hack, the FBI asked exchanges, bridges, blockchain analytics firms, DeFi services and node operators to block transactions with addresses used by the attackers.
3. Networks with emergency powers
Some newer networks give a group emergency control. On Arbitrum, an Ethereum layer-2 network, the constitution sets up a Security Council of 12 members who sign a multi-signature wallet. It can perform “Emergency Actions”, including software upgrades with no delay, with 9 of 12 approvals, but only in a “true security emergency”. Afterwards, it must publish a transparency report, and the ArbitrumDAO can curtail or remove these powers.
TRM said that after the Binance hack, Arbitrum’s Security Council used those powers to force two transfers out of the attacker’s wallet, moving 8,426 ETH and 74.6 million ARB, about $30 million, out of the attacker’s reach. See layer 2 rollups explained.
4. Rewriting history: hard forks
The most drastic option is for a whole network to agree on a hard fork that changes the record. It’s very rare. ethereum.org says the DAO fork of 20 July 2016 responded to an attack that drained over 3.6 million ETH from an insecure contract. The fork moved the funds to a new contract where anyone who lost funds could withdraw 1 ETH for every 100 DAO tokens.
The decision reached over 85% of votes, but some miners refused because the DAO incident wasn’t a defect in the protocol. They formed Ethereum Classic. See what is a hard fork?
What can’t be frozen
Bitcoin and ether held in a wallet whose keys you control can’t be frozen by an issuer, an exchange or a council. That’s why TRM said the Binance attacker still held about $2.4 billion in assets beyond any issuer’s reach. The same property protects ordinary self-custody users from having funds blocked, and it means mistakes can’t be undone.
Who has power over what
| Asset or location | Can be frozen or blocked? | By whom |
|---|---|---|
| Bitcoin or ether in your own wallet | No | Nobody, short of a network-wide fork |
| Stablecoins (USDT, USDC) in any wallet | Yes | The issuer |
| Any crypto on an exchange | Yes | The exchange |
| Assets on some layer-2 networks | Possibly | A security council with emergency powers, where one exists |
What this means for you
- Double-check every transfer. If you send to the wrong address, only the recipient can send it back.
- Know who has power over what you hold. Stablecoins and custodial accounts can be frozen; self-custodied bitcoin can’t.
- If you’re scammed, report fast. Freezes only work if funds reach a company that can act before they move on. See how to report crypto scams.
Frequently asked questions
Can I cancel a crypto transaction after sending it?
Can my exchange reverse a transfer I made by mistake?
Who can freeze crypto?
Has a blockchain ever been rolled back after a hack?
Does this mean crypto isn't really decentralized?
Sources
- Some things you need to know (Bitcoin payments are irreversible) — Bitcoin.org
- How to use a wallet — ethereum.org
- Timeline of all Ethereum forks (The DAO fork) — ethereum.org
- The Constitution of the ArbitrumDAO (Section 3: The Security Council) — The Arbitrum Foundation
- USDC Terms (last updated 15 October 2026) — Circle
- North Korea Responsible for $1.5 Billion Bybit Hack (PSA, 26 February 2025) — FBI, Internet Crime Complaint Center
- North Korea Steals USD 6.36 Billion From Binance in the Largest Hack in History (29 October 2026) — TRM Labs
First published . Spotted an error or an outdated figure? Tell us and we will check it against the source.