Setting up Dolphin{anty} for crypto airdrop ops
Setting up Dolphin{anty} for crypto airdrop ops
Running airdrop campaigns across multiple wallets requires more than just spinning up separate MetaMask instances. every major protocol today tracks browser fingerprints, canvas hashes, WebGL signatures, and behavioral patterns. if two of your wallets share the same fingerprint, the airdrop team will cluster them and either disqualify both or mark you for future monitoring. i’ve been burned by this, and it’s not a fun conversation to have with yourself at 2am when allocations drop.
this tutorial is for people already doing airdrop ops who want a reliable, scalable setup using Dolphin{anty}. it’s not for absolute beginners to crypto, and it’s not a promise that fingerprint isolation alone guarantees allocations. what it does is give you a technically clean foundation where each wallet lives inside its own isolated browser identity, each with a separate proxy, separate fingerprint, and no cross-contamination. that foundation is what serious operators use before they layer on behavioral randomization and on-chain strategy.
by the end of this, you’ll have Dolphin{anty} installed, your first batch of profiles configured with unique fingerprints, proxies assigned per-profile, and a basic workflow for managing 10 to 50 wallets without everything bleeding into each other.
what you need
software and accounts - Dolphin{anty} desktop app (Windows or macOS, Linux not officially supported as of 2026) - Dolphin{anty} account, free tier covers up to 10 profiles, paid plans start around $89/month for 100 profiles, check current rates on their site - MetaMask or Rabby for in-browser wallet management - a proxy subscription, residential or mobile preferred for airdrop work (datacenter proxies get flagged on most L2 testnets and mainnet campaigns)
infrastructure - one proxy per profile, minimum. shared IPs across profiles defeats the whole exercise - a seed phrase manager, i use a local KeePass database, not a cloud password manager - a spreadsheet or Notion table tracking wallet address, profile ID, assigned proxy, funded status, target protocols
costs to expect - Dolphin{anty} free tier: $0, works for testing but 10 profiles isn’t a real operation - 100-profile plan: approximately $89/month - residential proxies: $3-10 per GB depending on provider, figure $20-50/month for light to moderate usage - total entry point for a modest 20-50 wallet operation: $60-120/month in tooling
step by step
step 1: install Dolphin{anty} and create your account
download the client from dolphin.ru/en. install as you would any desktop app. on first launch it asks you to log in or create an account. create a new account using an email you don’t connect to any of your personal crypto activity. you’ll be storing profile data in their cloud sync, so treat the Dolphin account itself as part of your operational security.
expected output: Dolphin{anty} opens to a blank profiles dashboard.
if it breaks: if the app fails to launch on Windows, check that your Visual C++ redistributables are current. the error usually surfaces as a missing DLL on startup. download the latest Visual C++ 2015-2022 bundle from Microsoft’s official site and retry.
step 2: understand the fingerprint model before touching settings
before creating a single profile, spend ten minutes reading the fingerprint basics in Dolphin’s documentation. the key concept is that each profile has a browser fingerprint generated from a real device’s parameters, not fabricated values. fabricated fingerprints (random canvas hashes that don’t match any real GPU) are detectable by tools like CreepJS, which some protocols use.
Dolphin{anty} pulls fingerprints from a real-device database. your job is to not override these values manually unless you have a specific reason. most operators get into trouble by going into the fingerprint settings and randomizing things that were already set correctly.
expected output: you understand which settings to leave alone.
if it breaks: if you’ve already randomized something and aren’t sure what’s correct, delete the profile and start fresh rather than trying to patch a broken fingerprint mid-operation.
step 3: create your first browser profile
click “New Profile” in the top right. give it a naming convention you can scale, i use [network]-[wallet_number], e.g. arb-001, zk-001. this keeps things sortable when you’re managing 50+ profiles.
under the OS section, match the OS to one you actually own. if you’re on a Mac, set profiles to macOS. fingerprint consistency between the host OS and the profile OS reduces anomaly signals.
set the browser version to a recent Chromium version, typically within the last 2-3 major versions of Chrome. don’t use old versions, they stand out.
leave WebRTC set to “Real” unless your proxy provider explicitly supports WebRTC leak prevention. if you’re not sure, set it to “Disabled” as a default.
expected output: a profile appears in your dashboard with a green status indicator.
if it breaks: if the profile shows a fingerprint warning icon, open the profile settings and look for any fields flagged in red. these are usually mismatched values Dolphin detected internally. reset them to auto.
step 4: assign a proxy to the profile
in the profile settings, go to the Proxy tab. enter your proxy credentials in the format:
Protocol: HTTP or SOCKS5 (match what your provider gives you)
Host: your.proxy.host
Port: 12345
Username: proxy_user
Password: proxy_pass
click “Check Proxy” before saving. Dolphin will return the detected IP, country, and timezone. important: the timezone assigned to this profile should match the proxy’s geographic location. if the proxy is in Germany, set the timezone to Europe/Berlin. Dolphin{anty} can auto-set timezone from proxy, enable that toggle.
expected output: proxy check returns a non-local IP. timezone auto-populates.
if it breaks: if the proxy check times out, verify the credentials with your provider’s dashboard directly. if the IP returns but the timezone doesn’t auto-set, set it manually. a timezone mismatch between your proxy location and the browser is a known detection vector for airdrop sybil filters.
for proxy sourcing strategy at scale, proxyscraping.org/blog/ has detailed comparisons of residential proxy providers specifically tested for Web3 use cases.
step 5: configure the wallet inside the profile
launch the profile by clicking “Run”. it opens a Chromium browser window. install MetaMask (or Rabby) fresh from the Chrome Web Store inside this profile. do not import a seed phrase you’ve used in any other profile or in a non-isolated browser.
generate a new wallet inside this profile. write the seed phrase in your KeePass database, tagged with the profile ID and the proxy IP.
for Ethereum-compatible wallets, each new MetaMask installation is a clean state. there’s no shared storage between profiles in Dolphin{anty}, each profile’s browser data lives in its own isolated directory.
expected output: MetaMask shows a fresh 0x address you haven’t seen before.
if it breaks: if MetaMask shows an existing wallet from a previous session, the profile was not clean. check whether you accidentally launched the wrong profile or imported instead of creating new.
step 6: fund the wallet through a clean path
don’t fund directly from a CEX account linked to your real identity if operational separation matters to you. common practice is: CEX withdrawal to an intermediary wallet, then forward to the airdrop wallet. this is not legal advice, and tax treatment of wallet-to-wallet transfers varies by jurisdiction, consult a crypto tax professional in your country.
keep a record of each wallet’s funding transaction hash in your spreadsheet.
expected output: wallet shows incoming transaction in MetaMask.
if it breaks: if the transaction is stuck, check the RPC endpoint in MetaMask. Dolphin profiles sometimes inherit a default public RPC that’s congested. switch to a dedicated RPC from Alchemy or Infura.
step 7: bulk profile creation for scale
once your single profile is working correctly, use Dolphin{anty}’s bulk creation feature. go to the profiles list, click the arrow next to “New Profile”, select “Mass creation”. you can specify count, OS distribution, browser version range, and proxy list import.
prepare a CSV file with your proxy list in this format:
host,port,username,password,protocol
proxy1.example.com,10000,user1,pass1,socks5
proxy2.example.com,10001,user2,pass2,socks5
import this CSV in the proxy manager under Settings > Proxies, then during mass creation, assign proxies from list sequentially.
expected output: 10 or 20 profiles created, each with a unique proxy, each needing a wallet installed.
if it breaks: if proxy assignment fails during mass creation, assign proxies manually per profile after creation. bulk assignment occasionally errors on the first run in a fresh account.
step 8: test fingerprint isolation
with two profiles open simultaneously, visit a fingerprint audit tool like browserleaks.com in each. confirm that canvas hash, WebGL renderer, screen resolution, and user agent differ between profiles. if any values match across two profiles, investigate which setting is being shared, usually happens if you’ve cloned a profile without regenerating the fingerprint.
expected output: every audited parameter differs between profile A and profile B.
if it breaks: if canvas hash is identical across profiles, go to profile settings > Fingerprint > Canvas, and click “Generate New”. do this for each profile that shows duplication.
common pitfalls
reusing seed phrases across profiles. this is the fastest way to link wallets on-chain regardless of fingerprint isolation. one seed phrase, one profile, always.
ignoring timezone and locale. a proxy in Japan with a browser set to en-US and America/New_York timezone is a detectable inconsistency. use Dolphin’s auto-timezone feature or set it manually to match the proxy location.
bulk-creating profiles with the same browser version. if all 50 of your profiles report Chrome 124.0.0.0 exactly, that homogeneity is itself a signal. spread versions across 2-3 recent major releases during mass creation.
launching multiple profiles from the same machine on the same IP without proxies. Dolphin{anty} fingerprint isolation means nothing if all traffic exits your home IP. every profile needs a proxy active and checked before use.
funding wallets in the same block from the same source address. on-chain clustering analysis tools used by airdrop teams can trace wallet relationships through transaction graphs regardless of what browser they came from. if you’re running a serious operation, stagger funding transactions over time and use intermediate hops.
scaling this
10 profiles is manageable manually. you open profiles one by one, do the protocol interactions, close them. no automation needed.
100 profiles requires a naming and proxy management system. you’ll spend more time on organization than on the actual interactions. at this scale, consider using Dolphin{anty}’s API to automate profile launching and closing. their REST API lets you start and stop profiles programmatically:
curl -X POST http://localhost:3001/v1.0/browser_profiles/{profile_id}/start \
-H "Authorization: Bearer YOUR_API_TOKEN"
pair this with Playwright or Puppeteer connecting to the launched browser’s remote debugging port.
1000 profiles is a different operation entirely. you need dedicated servers (Windows VMs or bare metal), a proxy rotation system pulling from a large residential pool, a database instead of a spreadsheet, and scripted wallet generation and funding pipelines. the Dolphin{anty} Team or Enterprise plan is required at this scale. you’ll also want to review how multi-account farming communities handle detection evasion at volume, airdropfarming.org/blog/ covers operational patterns at that tier.
where to go next
- Best antidetect browsers for multi-account crypto work covers how Dolphin{anty} compares to Multilogin, AdsPower, and Incogniton for airdrop-specific use cases
- Residential proxies for airdrop farming: provider comparison goes deep on proxy provider reliability, geo coverage, and cost per GB for Web3 operations
- Back to the blog index for all tutorials and reviews on antidetect tools and multi-account infrastructure
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.