What happens to your farm when two protocols merge
Protocol mergers don’t happen often, but when they do, they’re one of the messier events an airdrop farm has to deal with. Two teams combine, token economics get rewritten, and the rules you’d been farming against for months can change in a single announcement. This isn’t a doom post. It’s a walkthrough of what actually happens mechanically when protocols merge, and what that means for the wallets you’ve been running.
What a merger actually changes on-chain
“Merger” gets used loosely, but in practice it usually means one or more of these things happening at the contract level:
A token migration contract. Holders of token A swap it for token B at a fixed or algorithmic ratio, through a contract deployed by the team. This is the most common piece, and it’s the one most farms will interact with directly.
A new token generation event. Sometimes the merged entity issues a brand new token rather than just rebranding one side. That means a fresh distribution, fresh eligibility criteria, and often a fresh snapshot.
A snapshot re-basis. If either protocol had an existing points system or accrued eligibility, the merged team has to decide whether that history carries over. Sometimes it does 1:1. Sometimes it gets weighted down. Sometimes it’s dropped entirely and replaced with new criteria based on activity after the merge date.
Combined sybil review. This is the part that gets underdiscussed. When two user bases merge, the team merging them usually also merges their data. A wallet that looked unremarkable inside protocol A’s dataset alone can look very different once it’s cross-referenced against protocol B’s dataset, especially if the same wallet, or wallets funded from the same source, interacted with both.
None of these are guaranteed to happen in every merger, and none of them are things a farm operator controls. The team sets the rules. What you can control is how your wallet set behaves through the transition.
Why the migration window itself is a sybil event
Here’s the part that trips people up: the act of migrating tokens is itself a fresh, structured, cross-cutting transaction that touches every wallet you hold a balance in. If you’re running a meaningful number of wallets, that migration is the single most correlated thing those wallets will ever do together, because they’re all calling the same contract, often within the same window, often funded and swept through the same infrastructure that’s been managing them all along.
Chain analysts build wallet clusters from patterns like these: shared funding sources, identical or near-identical gas amounts, transactions landing in tight time windows, wallets that only ever interact with the same small set of contracts in the same order. A migration event compresses months of separate activity into one narrow window where all those signals line up at once. If your wallets were farmed independently and behaved with natural variance up to that point, a lockstep migration can undo a lot of that separation in a single afternoon.
This is why operators who take farming seriously treat the migration window as its own operational task, not an afterthought. Staggering when each wallet claims or migrates, using independent funding paths rather than one wallet sweeping gas to twenty others, and letting the claim transactions land at organically different times all reduce how tightly the migration event ties wallets together in an analyst’s dataset. None of this is about hiding a wallet’s history. It’s about not adding a brand new, easily-clustered data point on top of history that was otherwise kept separate.
Eligibility rules can change with no warning
A protocol merger is one of the few events where a team can legitimately rewrite eligibility criteria after the fact. If you farmed protocol A for six months expecting points to convert cleanly into the merged token, that conversion ratio, weighting, or even whether legacy activity counts at all, is entirely up to the team doing the merging. There’s no guarantee your historical activity survives the transition in the form you expected, and there’s no guarantee a merger produces any distribution to farmers at all. Some mergers are pure infrastructure consolidation with no token event attached to either side.
Read the migration documentation the team publishes directly. Mergers are also one of the highest-risk windows for phishing: fake “migrate your tokens here” sites spin up within hours of a legitimate announcement, using the same branding and often ranking in search results before the real migration page does. Confirm the migration contract address against the project’s official channels, not a link shared in a Telegram group or a search ad, before signing anything.
What changes on the infrastructure side
A merger sometimes moves activity to a different chain entirely, not just a different contract on the same chain. If that happens, check your RPC setup before you check anything else. An RPC endpoint pointed at the old chain, or rate-limited in a way that wasn’t a problem when you were making a handful of calls a week, can quietly fail mid-migration and leave a wallet in a half-claimed state. This is a good moment to confirm your RPC provider actually supports the destination chain and has the throughput for however many wallets you’re moving through it, rather than finding out when a batch of transactions times out.
Session isolation matters here too. If you’re running an anti-detect browser to keep wallet profiles separate, a merger is exactly the kind of event where it’s tempting to batch everything through one browser session to save time. That convenience is precisely what collapses the separation the browser profiles were set up to maintain. Keeping the same one-profile-per-wallet-cluster discipline through the migration that you’d use for any other high-value transaction is worth the extra time.
Tracking the announcement, not just the token
Airdrop trackers are built to flag new distributions and snapshot dates, but mergers often get announced through governance forums or team blog posts well before any tracker picks up a token-specific listing. If you’re farming a protocol that’s been in merger talks, the governance forum and the team’s own channels are the primary source, and they’ll usually be weeks ahead of aggregator sites. Trackers are useful for confirming claim windows and contract addresses once a migration is live, and for cross-checking that a contract address circulating on social media matches what the tracker also has listed, which is one more layer against phishing contracts during the window when scam sites are most active.
The honest summary
A merger is a rules change, a contract change, and a data event, all at once. It can improve your position if legacy activity carries over generously, or it can reset you to zero if the team decides otherwise, and either outcome is the team’s call to make, not something farming harder guarantees around. What you can control is not turning the migration itself into the most sybil-obvious thing your wallet set has ever done, verifying the migration contract against official sources before you sign anything, and making sure your RPC and browser setup actually hold up under a real migration event instead of the light usage they were tested on.
Treat it like the operational event it is. Nothing here is financial advice, and nothing about a merger guarantees a payout to anyone farming either side of it.
If you want more breakdowns like this on how protocol events actually work under the hood, and tested notes on the RPCs, wallets, and browser setups we run our own farms on, check out the rest of the site here.
Get new guides and videos first — join the Telegram channel.