Setup guide: How to use anti-detect browsers for wallet isolation

If you are running more than one wallet from the same browser, you are leaking correlation data with every click. Protocols and their Sybil detection layers do not only look at on-chain patterns, they also fingerprint the browser environment, the canvas hash, the WebGL renderer, the installed fonts, the timezone, and the IP address. When those signals cluster around the same values across multiple accounts, the accounts get flagged and disqualified together. I have watched entire batches of wallets get wiped from airdrop allocations for exactly this reason.

Anti-detect browsers solve this by virtualising the browser fingerprint. Each profile presents a different device signature to the website, and when you pair each profile with a dedicated proxy, you get genuine network-level isolation on top. This guide is for operators who are already farming airdrops with multiple wallets and want to stop bleeding allocations to Sybil filters. It assumes you are comfortable with basic crypto wallet setup and have some budget for tooling.

By the end of this guide you will have a working multi-profile setup where each wallet lives inside its own isolated browser environment, each environment has a unique fingerprint, and each is routed through a separate IP. That is the baseline that serious operators run. The full article index at /blog/ has companion pieces on wallet generation and on-chain behaviour strategy if you need those first.

what you need

Anti-detect browser. The four tools I see operators using most are AdsPower, GoLogin, Multilogin, and Dolphin Anty. AdsPower has a free tier (up to 5 profiles) and paid plans starting around $9/month. GoLogin starts around $49/month for 100 profiles. Multilogin is the most established but also the most expensive, around $99/month for 100 profiles. Dolphin Anty has a free 10-profile tier popular with CIS-based operators. Prices change, so check each vendor’s current pricing page before committing.
Proxies. You need one proxy per profile. Residential proxies are preferred because they are less likely to be flagged by datacenter detection. Mobile proxies give better quality but cost more. Budget roughly $1-3 per IP per month for residential, $10-30 for mobile. Avoid free proxies entirely.
A seed phrase storage system. A password manager with encrypted notes, a local KeePass database, or a hardware wallet per cluster. Never store seeds in the browser profile itself.
A spreadsheet or simple database. You need to track which wallet address belongs to which profile, which proxy, and which accounts on which protocols. Without this you will lose track quickly.
Time. Initial setup for 20 profiles takes about 3-4 hours the first time.

step by step

step 1: understand what you are isolating against

Before touching any software, it is worth reading the W3C guidance on browser fingerprinting to understand what signals exist. The short version: browsers expose dozens of passive signals including screen resolution, timezone, language, installed plugins, canvas rendering output, WebGL vendor strings, audio context fingerprints, and more. The EFF’s Cover Your Tracks tool lets you see your own fingerprint. Run it once in your normal browser so you understand what you are dealing with.

Anti-detect browsers spoof or randomise these signals per profile. the key insight is that the fingerprint needs to be internally consistent. a Windows Chrome fingerprint with a macOS font list is a red flag. good anti-detect tools handle this coherence automatically.

If it breaks: if Cover Your Tracks shows your fingerprint as “unique” after setting up a profile, check that WebRTC is disabled in the profile settings and that your timezone matches the proxy’s geographic location.

step 2: choose and install your anti-detect browser

I recommend starting with AdsPower for most operators because the free tier lets you test the workflow before paying, and the paid tier is affordable at scale. Download it from the official site and install it locally. Do not use cracked or third-party builds, the risk of seed phrase exfiltration is not worth whatever you save.

Create an account. You do not need to provide payment information to use the free tier.

If it breaks: on Linux, AdsPower may require additional dependencies. Run sudo apt-get install libgbm1 libasound2 if the browser profiles fail to launch.

step 3: set up your proxy pool

Source your proxies before creating profiles, because you want to assign one proxy at profile creation time rather than changing it later. I use residential proxies for most airdrop farming. The proxy format you will enter in most anti-detect browsers is:

protocol://username:password@host:port

For example:

http://user123:[email protected]:8080

Test each proxy before assigning it. Most anti-detect browsers have a built-in proxy checker, or you can use:

curl --proxy http://user123:[email protected]:8080 https://api.ipify.org

That should return the proxy’s IP, not your real IP.

If it breaks: if the proxy times out, check that you are using the correct protocol (http vs socks5). Some residential proxy providers only support socks5.

step 4: create your first browser profile

In AdsPower (or your chosen tool), go to “New Profile.” The key settings to configure:

Operating system: pick Windows or macOS and stick to it consistently within a batch. mixing OS types within the same campaign is a fingerprint inconsistency.
Browser version: use a recent but not bleeding-edge Chrome version. too new and the user agent is rare, too old and it looks neglected.
Timezone: match the timezone to your proxy’s exit IP location. if your proxy exits in Germany, set the timezone to Europe/Berlin.
Language: match language to the proxy location.
Proxy: paste in your proxy string and verify it connects.
WebRTC: set to “Disabled” or “Fake.” real WebRTC can leak your actual local IP even through a proxy.

Save the profile. Launch it and visit coveryourtracks.eff.org inside the profile to check that the fingerprint looks different from your main browser.

If it breaks: if the fingerprint shows “Canvas Unique,” go into the profile’s advanced fingerprint settings and enable canvas noise injection.

step 5: install your wallet extension inside the profile

Launch the profile and install your wallet extension from the official browser extension store. For EVM chains this is usually MetaMask. You can verify the official MetaMask extension at metamask.io. The extension ID for MetaMask in the Chrome Web Store is nkbihfbeogaeaoehlefnkodbefgpgknn. verify this matches before installing.

Do not import an existing seed phrase into this profile yet. create a new wallet first to generate fresh keys.

If it breaks: some anti-detect browsers intercept extension install pages. if the extension page is blank, try manually entering the Chrome Web Store URL for the extension.

step 6: create and record the wallet

Create a new wallet inside the extension. Write down the seed phrase in your secure storage immediately. Record the wallet address and map it to the profile name and proxy IP in your tracking spreadsheet. a minimal spreadsheet looks like:

Profile ID | Wallet Address | Proxy IP | Protocol Accounts | Notes
profile_001 | 0xABC... | 12.34.56.78 | zksync, linea | created 2026-05-19
profile_002 | 0xDEF... | 98.76.54.32 | zksync, scroll | created 2026-05-19

Close the profile. Do not leave it running when not in use.

If it breaks: if the wallet extension forgets the account between sessions, check that the profile’s local storage is set to persist (not “clear on close”) in your anti-detect browser settings.

step 7: verify isolation between profiles

Launch two profiles simultaneously and have each visit coveryourtracks.eff.org or browserleaks.com. check that:

the IP addresses are different
the canvas fingerprints are different
the WebGL renderer strings differ or are appropriately varied
the timezone and language settings match each proxy’s geography

If two profiles share a canvas hash, your anti-detect browser is not spoofing correctly. check your subscription tier, some tools only enable full fingerprint spoofing on paid plans.

If it breaks: restart the anti-detect browser application entirely if profile settings are not taking effect. config changes sometimes require a full restart, not just a profile relaunch.

step 8: build an operating checklist

Before using any profile for farming activity, run through this check every session:

[ ] proxy is responding (curl test or built-in checker)
[ ] IP shown in profile matches proxy's expected exit IP
[ ] wallet address in extension matches spreadsheet record
[ ] timezone in profile matches proxy geography
[ ] no other profiles are open with the same protocol logged in

This sounds tedious for 10 profiles. at 100 profiles it is mandatory. the operators I have seen lose allocations most often are the ones who skipped the verification step and accidentally used a profile with a dead proxy, meaning the session fell back to their real IP.

common pitfalls

Using one proxy for multiple profiles. this defeats the purpose of fingerprint isolation. even if the fingerprints differ, the same exit IP links the accounts together. one proxy, one profile, always.

Forgetting timezone matching. a fingerprint that claims to be in Japan but routes through a German IP is inconsistent. Sybil detection tools flag this. keep geography coherent across IP, timezone, and language settings.

Storing seeds inside the profile. some operators save seed phrases in the browser profile’s password manager or notes. if the profile is compromised or the anti-detect vendor is breached, those seeds are exposed. keep seeds outside the browser.

Running too many profiles on one machine without RAM headroom. each profile is essentially a sandboxed browser. 20 simultaneous profiles on a machine with 8GB RAM will cause crashes and data corruption. budget at least 512MB per active profile.

Reusing wallets across batches. if a wallet address is already associated with an old fingerprint cluster, moving it to a new profile does not help. on-chain history links it. treat each campaign as a clean start with fresh wallets.

scaling this

10 profiles: manageable manually. a spreadsheet and a single anti-detect browser subscription covers this. you can run campaigns across 3-4 protocols without tooling beyond what is described above.

100 profiles: manual operation becomes a bottleneck. at this scale you need profile bulk creation (most anti-detect browsers support CSV import for batch profile creation), a structured proxy provider with API access for bulk IP provisioning, and a tracking database rather than a flat spreadsheet. the antidetectreview.org/blog/ has comparison coverage of which tools handle bulk profile management best.

1000 profiles: you are into semi-automation territory. operators at this scale typically use browser automation (Playwright or Puppeteer) connecting to anti-detect browser APIs to drive profile sessions programmatically. AdsPower and GoLogin both expose local REST APIs for this. profile creation, wallet generation, and basic on-chain interactions can all be scripted. you also need dedicated server infrastructure because running 1000 browser profiles locally is not realistic. a VPS cluster with 64GB+ RAM per node is common. see our guide at /blog/vps-setup-for-airdrop-farming/ for infrastructure options.

where to go next

/blog/proxy-types-for-airdrop-farming/ covers residential vs mobile vs datacenter proxies in detail, including which protocol types flag datacenter exit nodes.
/blog/wallet-generation-and-funding-strategy/ walks through generating wallets at scale and funding patterns that avoid on-chain clustering.
For in-depth comparisons of anti-detect browsers including benchmark test results, multiaccountops.com/blog/ publishes regular tool reviews updated when vendors push major version changes.

Written by Xavier Fok

disclosure: this article may contain affiliate links. if you buy through them we may earn a commission at no extra cost to you. verdicts are independent of payouts. last reviewed by Xavier Fok on 2026-05-19.