You open an app on Base, connect your wallet, and instead of the usual swap screen you get a message saying the address cannot be serviced, or that it has been flagged for a compliance review. Nothing about your wallet changed. You did not do anything unusual that day. It can feel like your funds have been frozen. They have not been, and understanding what is actually happening will save you a lot of unnecessary panic.
Base itself has no concept of a blocked address
The Base network, like Ethereum and every other EVM chain, does not maintain a list of addresses it refuses to process transactions for. If you hold the private key to an address, you can sign a transaction and the network will include it in a block. There is no protocol level switch that turns an address off. So if you were able to see a rejection, it did not come from the chain. It came from the application sitting on top of it.
Who is actually doing the blocking
Most consumer facing apps, wallets, and swap interfaces run a background check against an address before they let you use certain features. They usually do this by calling a third party screening service, companies like Chainalysis or TRM Labs are common examples, that maintain databases of addresses associated with sanctioned entities, hacks, mixers, or other flagged activity. The app sends your address to that service, gets back a risk score or a yes or no answer, and decides whether to show you the button or block it.
This is a decision made entirely at the interface level. The smart contracts you would have interacted with, the liquidity pool, the token contract, none of them know or care about any of this. A different front end that does not run the same check, or a direct contract call through a block explorer, will usually still work.
Why an address ends up on a list
There are a few distinct reasons an address can get flagged, and they are not all the same severity.
Direct designation. Governments occasionally sanction specific addresses by name, most often ones tied to state sponsored hacking groups or large scale theft. These are published lists, and apps that want to avoid regulatory exposure check against them directly.
Indirect exposure. Some screening tools do not just check your address, they check where your funds have been. If a wallet several hops upstream from yours once touched a flagged address, some tools will assign your address a lower risk score even though you never interacted with anything sanctioned yourself. This is sometimes called taint tracing, and it is one of the more debated parts of the industry because it can punish addresses that did nothing wrong.
Automated heuristics. Pattern based detection can flag addresses that look like they belong to a bot, a known scam cluster, or a drainer, sometimes correctly and sometimes not.
It is worth knowing that these lists are not permanent or infallible. Tornado Cash, a privacy tool, was added to the United States Treasury's sanctioned entities list in 2022, which caused many apps to block any address that had ever used it, including people who had used it for ordinary privacy reasons. That sanction was later challenged in court, and in 2025 a federal appeals ruling found the Treasury had exceeded its authority, after which the smart contracts and several associated addresses were formally removed from the sanctions list. The episode is a good reminder that a flag reflects a specific list at a specific point in time, not a permanent judgment about an address.
A flag is not the same as a freeze
This distinction matters a lot in practice. If an app blocks your address, your tokens have not moved anywhere and your keys still control them. You can usually still:
- View your balances on a block explorer like BaseScan
- Send tokens to another address you control from a different wallet app
- Use a different front end that does not run the same check, including interacting with a contract directly through a block explorer's write tab
What you generally cannot do is force a specific centralized front end to serve you if its compliance policy says no. That is a business decision by that app, not a limitation of Base.
What to do if your address gets flagged
Do not panic sell or rush to move funds through an unfamiliar bridge or mixer to "clean" them, that tends to create more problems than it solves and can make an address look more suspicious, not less. Instead, check your balance is intact on a block explorer, try a different reputable app, and if you believe the flag is a false positive, some screening providers and apps have a process for requesting a review. It is usually slow, but it exists.
Choosing where funds come from matters
The more practical lesson is upstream of any single flag. If you regularly swap, buy, or receive funds from unknown or low reputation sources, you raise the odds that some address in your transaction history eventually gets associated with something flagged, fairly or not. Favor receiving funds from exchanges and apps with clear provenance when you can, and keep basic records of where larger amounts came from, as covered in our article on keeping records of your Base wallet activity.
The bigger picture
Address screening exists because regulators expect the businesses that build on top of public blockchains to make some effort to avoid facilitating illicit finance, and most front ends would rather block a handful of addresses than risk their own licensing. That is a reasonable business reality, but it is also an imperfect, sometimes blunt tool layered on top of a network that was designed to never need anyone's permission in the first place. Knowing the difference between the two helps you react with the right amount of concern when you actually see one of these messages, rather than assuming the worst about your own wallet.
Sources: