Setup guide: Mobile wallet farms for Sui and Aptos airdrops
Setup guide: Mobile wallet farms for Sui and Aptos airdrops
Most airdrop guides assume you’re running desktop browser extensions on a single machine. that works fine for one or two wallets, but it breaks down fast when you’re trying to operate at scale on Move-based chains like Sui and Aptos. both networks have distributed meaningful token allocations to early users, and both continue to fund ecosystem activity through grants, points programs, and protocol-level incentives. the problem is that desktop fingerprinting is well-understood and easy to cluster, which means multi-wallet desktop setups get flagged early.
Mobile changes the equation. each device has a unique hardware profile, a distinct advertising ID, and a separate app sandbox. when you pair mobile wallets with residential mobile proxies, the fingerprint profile looks genuinely different per device, which is harder to cluster than a browser farm where every window shares the same GPU, fonts, and canvas hash. this guide is for operators who already understand the basics of airdrop farming and want to build a repeatable mobile-first setup for Sui and Aptos specifically.
by the end of this tutorial you’ll have a working device template, a proxy routing setup, funded wallets on both chains, and a rotation framework you can replicate across 10, 50, or 100+ slots. i’ll cover where things break and how to recover without losing your position in an ongoing campaign.
what you need
Devices - Android phones or tablets (minimum Android 10), or an Android emulator stack (LDPlayer 9 or MuMu Player 12 for x86 emulation) - at least 4GB RAM per device/emulator instance - physical devices: budget Android handsets work fine, Redmi A3 or similar at SGD 90-120 each - emulator route: one mid-range desktop can run 8-12 instances depending on RAM (32GB minimum for 8 instances)
Proxies - mobile residential proxies with per-IP rotation, one proxy per device slot - recommended providers: Brightdata mobile, IPROYAL residential mobile, or Oxylabs mobile - budget SGD 4-8 per GB depending on plan; a light-activity farm uses roughly 0.5-1GB per wallet per month
Wallets - Sui: Sui Wallet (official, from Mysten Labs), Nightly Wallet (multi-chain, available on Android) - Aptos: Petra Wallet (official Aptos Labs wallet), Pontem Wallet (Android) - both chains’ official wallets are documented at docs.sui.io and aptos.dev respectively
Accounts and infrastructure - one Gmail account per device slot (never reuse accounts across device profiles) - a seed phrase manager, either an offline spreadsheet with AES encryption or a self-hosted Bitwarden instance - starting capital: roughly 1-2 SUI per wallet for gas, 0.5-1 APT per wallet for Aptos gas - optional: a small VPS for running activity scripts via Aptos SDK or Sui TypeScript SDK
Costs at 10 wallets - devices (emulators): SGD 0 if you have the hardware - proxies: ~SGD 40-80/month - starting gas capital: ~SGD 80-150 depending on token prices - total one-time: SGD 200-300 to bootstrap a 10-wallet farm
step by step
step 1: set up your emulator template
install LDPlayer 9 on your farming machine. create one base instance, configure it cleanly, then clone it for all subsequent slots. this way you only do the initial setup once.
# after installing LDPlayer, use the built-in clone tool
# LDPlayer > Multi-Instance Manager > Copy Instance
# rename each instance: wallet_01, wallet_02, etc.
in each instance, go to Settings > Other > Use IP location and disable it. set the device model to a random mid-range Android device, not the default LDPlayer model. rotate the IMEI and Android ID from the instance settings panel before doing anything else.
expected output: you have N instances, each with a different device fingerprint, sitting at a clean Android home screen.
if it breaks: if instances are crashing on startup, your RAM is the bottleneck. drop to 2GB per instance in LDPlayer settings, or reduce your concurrent instances. 8 instances on 32GB RAM is the practical ceiling.
step 2: configure proxies per instance
in each LDPlayer instance, go to Settings > WLAN > long-press your network > Modify network > Advanced options > Proxy > Manual. enter the host and port from your mobile proxy provider. each instance gets a unique proxy credential.
do not use the same proxy IP across two instances. if your provider supports sticky sessions (same IP for 10-30 minutes), enable that, it prevents mid-session IP changes from breaking dApp interactions.
expected output: each instance shows a different IP when you visit a check-IP site inside the instance.
if it breaks: LDPlayer sometimes resets proxy settings on instance restart. check after every reboot and build a verification step into your rotation checklist.
step 3: install wallets and generate seeds
for Sui, install Sui Wallet from the Google Play Store inside the instance. for Aptos, install Petra. do not sideload APKs from third-party sources, use the official Play Store versions to avoid supply-chain risk.
generate a new wallet in each instance. write down the seed phrase. do not screenshot it inside the emulator; copy it to your offline seed store immediately.
# seed storage format (CSV, AES-encrypted at rest)
slot_id, chain, wallet_address, seed_phrase, proxy_id, gmail_account, date_created
01, SUI, 0x..., word1 word2 ... word12, proxy_iproyal_01, [email protected], 2026-05-22
01, APT, 0x..., word1 word2 ... word12, proxy_iproyal_01, [email protected], 2026-05-22
expected output: each instance has one Sui wallet and one Aptos wallet. all seeds recorded offline.
if it breaks: if Petra fails to connect to the Aptos mainnet, check whether the instance’s proxy blocks websocket connections. some budget proxies do. switch to a different port or provider.
step 4: fund wallets
consolidate your starting capital into one source wallet per chain. then batch-send gas to all farm wallets.
for Sui, use the Sui CLI or a simple script:
// fund_wallets_sui.ts (Sui TypeScript SDK)
import { SuiClient, getFullnodeUrl } from '@mysten/sui/client';
import { Ed25519Keypair } from '@mysten/sui/keypairs/ed25519';
const client = new SuiClient({ url: getFullnodeUrl('mainnet') });
// iterate recipient addresses, send 1 SUI each via programmable transaction block
for Aptos, use the Aptos TypeScript SDK documented at aptos.dev/en/build/sdks/ts-sdk:
// fund_wallets_aptos.ts
import { Aptos, AptosConfig, Network } from '@aptos-labs/ts-sdk';
const config = new AptosConfig({ network: Network.MAINNET });
const aptos = new Aptos(config);
// batch transfer 0APT_AMOUNT to each recipient
run funding scripts from a separate machine, not from inside the farm instances.
expected output: each wallet shows 1-2 SUI and 0.5-1 APT balance.
if it breaks: if transactions are failing, check that you haven’t hit the source wallet’s transaction rate limit. space out sends by 2-3 seconds minimum.
step 5: establish baseline on-chain activity
both Sui and Aptos snapshot user activity for airdrop eligibility. you need genuine-looking transaction history, not just a funded wallet sitting idle. the Aptos Foundation has explicitly noted on-chain engagement as a criterion in past grant and incentive program documentation.
minimum activity baseline per wallet per week: - 2-4 DEX swaps (Turbos or Cetus on Sui, Liquidswap or Thala on Aptos) - 1 liquidity provision or removal action - occasional NFT interaction if a campaign is running
do this manually for your first 5 wallets to understand the flow. after that, script light activity using the SDKs referenced in step 4. keep transaction amounts realistic, micro-swaps of $0.01 look like bots. use $2-10 equivalent per swap.
expected output: each wallet has a varied transaction history across multiple protocol types.
if it breaks: if a dApp blocks your proxy IP, rotate to a fresh IP via your provider’s dashboard and wait 24 hours before retrying that specific dApp from that slot.
step 6: set up a tracking spreadsheet
you need a single source of truth for all your wallet states. at minimum track:
| slot | sui_address | apt_address | proxy_id | last_active | campaign | notes |
|---|---|---|---|---|---|---|
| 01 | 0x… | 0x… | proxy_01 | 2026-05-22 | Sui DeFi season 2 | active |
update this after every activity session. if a slot goes dark for more than two weeks during an active campaign, you’re likely missing snapshot windows.
expected output: full visibility on farm status without logging into each wallet.
if it breaks: if you’re managing 50+ wallets, the spreadsheet approach doesn’t scale. look at a lightweight self-hosted Airtable or Notion database with API access, or a simple SQLite file you query with a script.
step 7: rotate and maintain
set a weekly calendar block for farm maintenance. each session: check balances, run 2-4 transactions per wallet, verify proxy IPs are still clean, update your tracker. for multi-wallet operations at this scale, the process discipline matters more than any single technical choice. check multiaccountops.com/blog/ for rotation frameworks that operators in similar setups use.
expected output: all wallets show recent activity, nothing has gone stale.
if it breaks: if you miss a window because you had too many slots to manually manage, cut your slot count before expanding again. 20 well-maintained wallets beat 100 neglected ones.
common pitfalls
reusing proxies across slots. one proxy per slot is the rule. if two wallets share an IP at any point, they can be clustered. providers log session data and airdrop teams have access to node-level IP logs.
identical transaction timing. scripted farms that send transactions at the same second across all wallets are trivial to detect. add random delays of 30-300 seconds between wallet actions, and stagger daily activity windows by hours, not minutes.
ignoring gas token prices. APT and SUI both have meaningful price volatility. if APT doubles while you’re running the farm, your gas costs halve in fiat terms but your on-chain amounts stay the same. re-evaluate your activity budget monthly against current prices.
using the same seed phrase format or derivation path across wallets. some operators generate seeds from a single master key with sequential derivation paths. this is detectable via on-chain analysis if the funding source is shared. use independently generated seeds for each slot.
not tracking which campaigns are active. farming general activity without knowing what a protocol is actually measuring is wasted effort. follow official announcement channels for Sui and Aptos ecosystem projects. the Sui ecosystem page lists active projects. subscribing to protocol Discord servers is the minimum viable intelligence gathering.
scaling this
10 wallets: everything above is manual with a spreadsheet. one person can manage this in 2-3 hours per week. this is the learning phase, don’t automate prematurely.
100 wallets: you need scripted activity. write per-chain transaction scripts using the official SDKs (Sui TypeScript SDK, Aptos TS SDK). run them from a VPS on a cron schedule with randomized delays. proxy management becomes a real cost center at this scale, budget SGD 400-800/month for clean mobile residential IPs. device management via emulators starts to require a dedicated farming machine per 20-30 slots. see antidetectreview.org/blog/ for fingerprint isolation tools that operators use at this tier.
1000 wallets: this is full infrastructure territory. you’re looking at a fleet of physical Android devices or a high-RAM server farm running headless Android emulation (e.g. via Android-x86 with QEMU). at 1000 slots you need a database-backed tracking system, automated proxy rotation via API, and alert systems for failed transactions. your biggest risk at this scale is a single protocol flagging your entire fleet in one batch, so segment your wallets across multiple behavioral clusters with different activity patterns and timing profiles.
where to go next
- Sui airdrop checklist: what protocols are actively measuring covers which Sui ecosystem protocols currently run points or incentive programs and what on-chain actions they weight.
- Aptos wallet setup and DeFi activity guide goes deeper on Aptos-specific protocol interactions, including Thala, Aries Markets, and Amnis Finance.
- all tutorials for the full article index on multi-wallet setup, proxy sourcing, and chain-specific farming.
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-22.