If you have spent any time exploring apps on Base, you have probably run into one that would not let you connect, or that stopped you partway through with a request for a photo ID and a selfie. It can feel contradictory. Isn't the entire point of a self custody wallet that nobody can stop you from using it?
The short answer is that the blockchain and the app in front of it are two different things, and they follow two different sets of rules. This guide explains that split, why it exists, and what it actually means for you as a wallet user.
The protocol and the front end are not the same thing
Base, like Ethereum, is a public network made of smart contracts and validators. Nobody owns it, nobody can switch it off, and nobody checks your passport before letting a transaction through. If you have a wallet, some ETH for gas, and the address of a contract, you can interact with it directly.
Most people do not do that. They use a website, often called a front end or an interface, that gives the contract a search bar, a swap button, and a clean layout. That website is usually built and hosted by a specific company or team. It runs on ordinary servers, it has a domain name, and it is subject to the laws of wherever that company is legally based, the same as any other business with a website.
This is the split that causes the confusion. The smart contract underneath is permissionless. The website sitting on top of it is not automatically permissionless, because it is operated by a legal entity that can be sued, fined, or regulated.
Why a company would restrict its own front end
A few different pressures push interface operators toward adding KYC checks or blocking certain countries.
Securities and derivatives rules. Some tokens or products, especially anything that resembles a leveraged position, a yield product, or a synthetic asset, can fall under securities or derivatives regulation in specific countries. Rather than assess every user's situation individually, a front end operator sometimes finds it simpler to block the jurisdictions where that product would need a license the company does not hold.
Sanctions compliance. Companies operating a front end are expected to avoid knowingly serving users or wallet addresses tied to sanctioned individuals, entities, or countries. This can lead to IP-based blocking for certain regions and, in some cases, wallet address screening against sanctions lists before a transaction is allowed through the interface.
Anti-money laundering obligations. If a front end also offers a way to move funds toward a bank account, a card, or a centralized exchange, it starts to resemble a regulated financial service in the eyes of many regulators. That can trigger the same identity verification requirements that apply to a bank or a payment processor, even if the underlying swap or transfer is happening through a smart contract.
Consumer protection concerns. In some jurisdictions, regulators have taken the position that a polished, easy to use interface to a complex financial product creates a duty of care that a bare smart contract does not. Some companies restrict access in those regions rather than build in the disclosures or safeguards regulators would expect.
None of these pressures apply to the smart contract itself, because a smart contract is not a legal person and cannot hold a license or be sued in the way a company can. They apply to whoever chose to build a convenient door in front of it.
What KYC on a front end actually involves
When an interface asks for identity verification, it is typically collecting a government ID, sometimes a selfie for liveness matching, and occasionally proof of address, then storing that information with a compliance vendor. Depending on the app, this might be a one time check before your first transaction, or a check tied to certain features like fiat off-ramping or higher transaction limits.
It is worth treating this the way you would treat KYC on a centralized exchange. Only complete it on the app's actual domain, never through a link sent to you in a message, and be wary of any site that asks for your recovery phrase as part of an identity check. No legitimate verification process needs your seed phrase. If it asks for one, it is a phishing attempt, not compliance.
What geoblocking looks like in practice
Geoblocking is usually done by checking your IP address against a list of restricted countries when the page loads. If your IP resolves to a blocked country, the front end refuses to load fully, or it loads but disables the connect wallet button.
This is a front end restriction, not a network restriction. The underlying contract has no concept of countries. In principle, someone could reach the same contract through a different interface, a command line tool, or a block explorer's read and write tabs, and the transaction would go through exactly the same way. Using a VPN to route around a geoblock is technically straightforward for the same reason, but it is worth being clear eyed about what that means: you would be knowingly bypassing a restriction the operator put there for a compliance reason, and depending on your local laws and the platform's terms of service, that carries its own risk that has nothing to do with the blockchain layer. This article describes how the restriction works, it is not a recommendation to circumvent it.
Why Simple Base Swap and other minimal interfaces look different
Not every front end takes this approach. Some interfaces are built to do one narrow thing, connect a wallet and submit a swap, without adding an off-ramp, a lending product, or anything else that would pull the operator into a broader regulatory category. A narrower app generally means a narrower set of obligations, which is part of why some Base wallets and swap tools stay lighter on gatekeeping than a full featured exchange style platform.
That does not mean every simple looking app is automatically free of restrictions everywhere, and it does not mean an app with no restrictions today will have none forever. Regulatory categories can shift, and a company can add checks later that were not there when you first used the app. It means the amount of friction you encounter tends to track how much the front end is doing beyond the basic swap itself.
What this means for you
A few practical takeaways follow from all of this.
First, if an app blocks you or asks for ID, that is a decision made by the company running that specific website, not a limitation of Base or your wallet. Your wallet, your funds, and the underlying contracts are unaffected.
Second, the same underlying liquidity is often reachable through more than one front end. If one interface adds restrictions you would rather avoid, check whether the same pool or protocol is accessible through a different, less restrictive interface, keeping in mind that any interface you use should still be one you trust with your transaction, since a malicious or careless front end can still show you the wrong information before you sign. See our guide on connecting your wallet to a dapp safely before trying an unfamiliar one.
Third, KYC requested by a front end is a different thing from a transaction requiring gas or a token requiring approval. It is worth pausing and reading exactly what is being asked for and why, the same way you would with any financial service, rather than assuming that because you are in crypto, no identity checks should ever apply.
The permissionless part of Base is real, and it lives in the contracts. The interface in front of it is a business decision made by whoever built it, and businesses answer to the laws of the places they operate in, the same as any other company with a website and a bank account.