$AIRDROP HUNTERFarm airdrops, safely
简体中文 English
Advanced

Where's the Line with Multiple Wallets? Run the Numbers Before You Open a Second One

Pixel-art cover: a yellow pixel wallet icon against a dark background, with the article title in Chinese beside it
Before you open another wallet, be clear about what it gives you and what it asks you to pay.

The bottom line first, so you don't have to scroll to the end: if your reason for opening a second wallet is "so I can claim one more share of the airdrop", the math doesn't work out for the vast majority of people. Not because it breaks a rule — nobody on-chain cares how many addresses you open — but because the reward side gets diluted faster than you'd think, while the cost side multiplies faithfully with every wallet you add, with no discount whatsoever. There are real reasons worth opening a second wallet, but they have little to do with airdrop eligibility. In this piece I lay out both sides so you can see for yourself which way the numbers tip.

The pull of multiple wallets is really a multiplication problem

Why is the idea of multiple wallets so tempting? Because in your head it's a simple multiplication: one wallet gets one share, five wallets get five, and all it costs is a bit more gas. Almost everyone who has farmed airdrops has toyed with the idea. Nothing to be embarrassed about — I won't pretend it never crossed my mind either.

But for that multiplication to hold, three assumptions all have to be true at once. Chances are you haven't checked a single one:

  • Assumption one: every wallet actually qualifies. Creating an address doesn't count for anything. Each address has to complete deep enough interactions on its own and build up enough time on its own before it counts as a share.
  • Assumption two: the size of each share doesn't shrink because you opened more. In other words, the rules for splitting the pie don't depend on how many people take part.
  • Assumption three: in the project team's eyes, these wallets are several people, not one person wearing several disguises.

Spoiler for the next few sections: the first assumption multiplies your costs by the number of wallets; the second doesn't hold under most distribution mechanisms; the third is outside your control, and if it fails, everything you've put in is wiped out together.

Why that multiplication falls apart in practice

Think of your resources as a bucket of water: you only have so much money and so much time, and the total is fixed. With one wallet, the whole bucket goes on one tree; open five, and each tree gets a fifth.

The trouble is that airdrop eligibility usually isn't awarded proportionally. Many projects draw a line first: clear it and you get something, fall just short and you get zero. Five trees that each got a fifth of the water may well all end up below the line — at that point you don't have five shares, you have none, and the water is already used up. Pour it all on one tree and at least that one has a shot at clearing the line.

Even when you come across a points system that looks like "do more, get more", don't celebrate too soon. What really counts in a points system is usually sustained, in-depth activity, not the size of any single transaction (that mechanism is broken down in how to earn airdrop points the genuine way). And "sustained" and "in-depth" happen to be the hardest things to split evenly: you only have so much time, and if you rotate between several accounts, each one's activity can only be patchy, and none of them gets deep.

There's another layer almost nobody accounts for: opening more wallets in itself dilutes the size of each share. Plenty of airdrops are split from a roughly fixed pool; the bigger the denominator, the smaller each share. You think you're adding, but when lots of people are doing the same thing, the overall effect is to push down the value of every share — including the one in your hands. That's also why the feeling that "airdrops are worth less and less" has become so widespread in recent years: more people taking part means more people splitting the same pool. It's structural, not a case of projects getting stingy.

So why is "more accounts = more money" still going strong? Because back in earlier days it really did work — fewer people were doing it, project distribution rules were crude, and there wasn't much in the way of serious linking analysis, so quantity really could be turned into results. The problem is that this experience got passed down as a general rule, while the conditions it depended on are long gone. Most of the multi-account stories you hear today are echoes from that period, not a manual for now. The most useful way to judge whether a piece of farming wisdom still holds is to ask: what conditions made it work back then, and are those conditions still here?

There are four costs, and most people only count the first

The cost side is the easiest to underestimate, because most people only think of gas — and only of "how much one gas payment costs", not "how many payments in total". There are really four costs, each better hidden than the last.

Cost one: gas, multiplied directly by the number of wallets. Every wallet has to be funded, interact and claim separately, and the chain won't give you a discount because the same person is behind them. To get a feel for how steep that multiplication is, use the gas fee calculator to estimate what one round of interactions costs for a single wallet, then multiply by the number you plan to open — plenty of people lose interest once they've done the multiplication. What gas actually is and when it's cheap is covered in what a gas fee is, so I won't go into it here.

Cost two: time, also multiplied by the number of wallets — and it's usually more expensive than gas. Switching accounts, confirming pop-ups one by one, logging progress one by one, watching claim windows one by one: none of this has economies of scale, and however many accounts you have, that's how many times you do it. The only difference is that you can see gas leaving your wallet, but you can't see time leaving your life. Convert it at your own hourly rate and most people find this is the biggest cost of all.

Cost three: your capital gets chopped up and tied down. Every wallet needs to keep a bit of the native coin for gas: keep too little and you get stuck mid-operation, keep too much and it just sits idle. Add the working capital the interactions need, and once your money is split into several pots, each one is too small to do anything meaningful, yet together they tie up a sizeable sum. Loose change scattered across five places and one lump sum in one place are simply not equally usable.

Cost four: the chance of a mistake rises with the number of wallets — and not linearly. You have several seed phrases to store, several addresses to keep track of, and approvals to check in each wallet. Once people get tired they start cutting corners: seed phrases end up in screenshots and notes apps, transfer addresses stop getting checked character by character, approvals don't get revoked. Every one of the 10 mistakes beginner airdrop farmers make most becomes easier to walk into the more wallets you manage. And the thing about these accidents is that a single one can cost you more than a whole year of farming brought in.

⚠ It's not just money that doubles

Double the number of wallets and it's not only the gas that doubles — so do the secrets you have to keep, the approvals you have to review, and the chances of a slip on every operation. Security incidents are the "one hit and you're back to zero" kind of risk. Having more accounts doesn't spread them thinner; it only makes them more likely to happen.

What can actually be seen on-chain

To work out where the line is, you first have to accept one fact: everything you've ever done on-chain is public and permanent, and anyone can replay it from the start after the fact. That's different from a centralised platform — a platform's risk-control data is visible only to the platform itself, whereas on-chain data can be pulled and analysed by anyone, and it's the complete history starting from an address's very first transaction.

Specifically, what's public falls into a few categories: every incoming and outgoing transfer for each address and who the counterparty was, the timestamp of each transaction, which method on which contract was called and for how much, and whether direct or indirect transfer paths exist between any set of addresses. Put these together and you have a map of the relationships between addresses — and drawing it needs no insider data at all.

The point was never how suspicious any single address looks on its own, but what a group of addresses' relationships and rhythms reveal when they're laid side by side. Look at one account alone and you may not find anything wrong; put several into the same map and the pattern surfaces on its own.

There's one more thing many people don't realise: there's no point at which you're "in the clear". Analysis usually happens after your interactions are done, with the full history there to be examined at leisure. In other words, while you're doing it you don't know how it will be read, and once it's done you can't change it — there's no undo button on-chain. What a wallet's history can reveal is broken down in more detail in how to do on-chain interactions and check your history.

What makes several wallets look like one person to a project

The categories below are the linking signals most often mentioned in public discussion. I'm not listing them so you can dodge them — quite the opposite. The point is: every one of these is a structural trait that multi-account setups can't avoid, precisely because they exist to save effort — not a small oversight you can patch.

  • Common source of funds. Several wallets whose starting capital came from the same address, or from one withdrawal that was then split up — that "one-to-many" path is laid out plainly on-chain. Consolidating everything from those wallets into one place to cash out later is the other half of the same story.
  • Clustered timing. A batch of addresses that first appear around the same time, are active around the same time, and go quiet together once they're done. Real people keep scattered schedules; batch operations keep synchronised ones.
  • Near-identical behaviour. The same contracts, in the same order, with amounts of the same size, at the same intervals. The more someone tries to save effort, the heavier these copy-paste traces get.
  • Direct dealings between addresses. Wallets transferring to each other, granting each other approvals, or all having dealt with the same intermediary address — all of this ties them into a web.
  • A thin story, thin in the same way. Several addresses with no trace beyond the handful of interactions "done to qualify", and all equally thin.

Why are these five "unavoidable"? Put simply, the whole point of multiple accounts is saving effort — producing more records that "look qualified" with less time and less thinking. But the moment you start saving effort, batching, templates, shared funding and synchronised timing grow out of it automatically. To make several addresses genuinely different from one another, the time and money you'd have to spend is exactly the part you were trying to save. It's a snake eating its own tail: save effort and you leave traces; don't save effort and there's no point in opening more.

Notice that none of these five mentions IP addresses, devices or browsers. On-chain analysis looks at addresses' behaviour and fund relationships; it couldn't care less what network you were on when you clicked. So "switch environments and they're isolated" is a pretty expensive misconception.

As for what happens once wallets are judged to be linked, and how much that costs you, that's a whole topic of its own: what a sybil attack is and why multi-accounts get disqualified covers the consequences side, so I won't repeat it here. From this section, just remember one line: these traits don't need you to "slip up" to show up — they're the natural by-product of running multiple accounts.

Some multi-wallet setups are legitimate — they just have nothing to do with farming

Don't get me wrong at this point: I'm not saying one person only deserves one wallet. Multiple wallets are perfectly fine in themselves; what's wrong is the motive of "opening one to claim an extra airdrop share". The reasons below are not only legitimate, I'd actively recommend them:

  • Asset segregation. Keep long-term holdings you won't touch in a wallet that's barely ever connected and never grants any approvals (a hardware wallet is even better), and use a separate one holding only small amounts for everyday interactions. That way, if the everyday one gets phished, your loss is capped.
  • An empty wallet for testing the waters. When you need to visit a site you don't know or sign an approval you don't fully understand, try it first with an empty wallet that holds just a little gas. This approach is covered in more detail in wallet security: seed phrases, private keys and approval management.
  • Separating by purpose. For example, keeping NFTs and DeFi apart, or separate main addresses for different chains, so your own bookkeeping and tracking stay easy. The goal is tidiness, not disguise.
  • Separating for privacy. If you have an address that's already tied to your real identity (say you've posted it publicly, received payments to it, or linked it to a domain name), and you don't want it connected to everything you own, opening another one is reasonable. Note that this solves "people can't see everything you own at a glance", not "people can't work out that these two addresses are related" — that's a different matter, much harder, and something most people can't pull off.

These uses have one thing in common: they don't mind at all if others can tell the wallets belong to the same person. You don't need them to be strangers to each other; you only need their risks not to spread from one to another. That's the dividing line — legitimate multiple wallets manage risk boundaries; multi-account farming gambles on identity boundaries. The first is yours to decide; the second isn't.

Putting both sides together: when the math doesn't add up

Put the previous sections on one table and the numbers become clear.

On the reward side, you need three things to go your way at once: the project actually launches a token, every one of your addresses clears the line, and the token is still worth something. These three hurdles are already a chain of shrinking probabilities (how much you can earn farming works through exactly this structure), and opening more wallets makes the second hurdle harder to clear, because every account gets spread thinner.

On the cost side, gas, time, capital tied up and the chance of mistakes all multiply with the number of wallets, and not one of them comes at a discount.

And there's one cost that isn't on the books: opportunity cost. The time you spend switching accounts, reconciling and watching windows could have gone into taking one wallet deeper, or into researching a new direction altogether. The grind of multiple accounts is very real, but what it buys is mostly a feeling of being busy, not better odds. Busy and effective aren't the same thing, and that shows especially clearly in airdrop farming.

Then stack the linking risk on top: once several addresses are judged to be the same entity, you've paid several sets of costs and may get back zero. This isn't the difference of "earning a bit less" — it changes your payoff distribution from "a small chance of making money" to "a small chance of making money, while carrying a sizeable chance of losing everything".

So under this set of assumptions my conclusion is blunt: as long as opening more wallets doesn't raise the odds on the three hurdles — "the project launches a token, the address clears the line, the token is still worth something" — and the size of each share doesn't grow because you opened more, concentrating your resources in one wallet is the better deal. It can go deeper and stay more consistent, so its chances of clearing the line are actually higher; spread across several, each one struggles below the passing line while you carry a tail risk for nothing. If any one of these assumptions doesn't hold for the project you're looking at, the conclusion needs recalculating.

If you don't buy my reasoning, that's fine — run the numbers yourself. Open the airdrop farming ROI estimator, scale the "Average monthly gas / interaction cost" field up by the number of wallets you plan to open, leave everything else unchanged, and see how the result moves. To be clear about what this step calculates: it's a cost-stress scenario in which rewards don't increase, and it can prove only one thing — when eligibility odds and per-share allocation stay the same, costs drag your returns down; it does not prove that opening more wallets is a bad deal on every project. To get closer to reality, you'd need to fill in these assumptions yourself: the odds of each address clearing the line on its own, whether per-share allocation shrinks as more people claim, the odds of several addresses being judged the same person and disqualified together, and what rate you put on the extra time. For any of these you have no basis for, honestly write "unknown", then go back to the specific terms of the project you want to join and check them one by one — don't round off the conclusion with a number you pulled out of thin air. The numbers are yours, and so is the conclusion.

If you still open a second one, hold at least these lines

If you've read this far and still decide to open one, here are a few bottom lines. Let me be clear up front: these are not about making several wallets look unrelated to each other — this site doesn't write that kind of thing and never will. They're only about keeping your own risk in check as far as possible once you've already decided to open more.

  • Don't use them to chase the same allocation on the same project. This is the most important one. Stacking accounts on one project runs straight into the linking traits above, and the rewards dilute each other too — of all the ways to use extra wallets, it's the worst deal.
  • Store every seed phrase to the same standard as your first. Written down offline, verified to restore, never in your photo gallery or chat history. If you can't manage that for a given number of seed phrases, don't open that many wallets — a wallet you can't safeguard is a hole waiting to happen.
  • Write down a cost ceiling before you open anything. How much gas you're willing to spend this month in total, and how many hours — on paper. The biggest hidden risk of multiple wallets is a budget that gets away from you: each account only costs a little extra, but together they blow past the limit before you notice.
  • Keep separate books; don't just look at the total. What each wallet has spent and what it's received, one line each. Merge it all into one total and you'll never see which account has been losing money all along.
  • Clear approvals on idle wallets regularly too. Unused doesn't mean safe: the approvals you once granted on it are still open, and you've stopped looking at it.
  • Think of "one more wallet" as one more cost, not one more chance. Get that mindset right and you'll hold yourself back, without anyone else having to stop you.

Instead of agonising over how many to open, ask this one question

The question beginners ask me most is "how many accounts should I open?", but the question itself is aimed the wrong way. There's only one question that really matters: is this one wallet of mine genuine enough yet?

"Genuine enough" has a concrete meaning: has it been across several chains, touched several different kinds of protocol, is its activity spread over a fairly long stretch of time, does real money flow in and out, and are there signs of normal use that have nothing to do with farming? Each of these dimensions has a ceiling, and most people's first wallet is nowhere near it. Opening a second before the first is built out is a classic case of covering a lack of depth with breadth — it looks busy, but neither side is really there.

Think this question through and most people find they don't have the resources to open a second wallet at all. When the day comes that your first wallet has done everything it should and you still have time and budget to spare, that's soon enough to think about expanding; by then your feel for the costs will be sharper, and you won't need anyone to talk you out of anything. To take your first wallet down its path in the right order, the complete farming workflow lays out the full route.

▶ A comparison that costs nothing

You can see all this clearly without opening any accounts: in a block explorer, find an active address that's been in use for a long time, then find one obviously created just for a single campaign, and look at the two pages side by side. The one in real use has transactions spaced unevenly, all sorts of counterparties, amounts large and small, and several kinds of protocol; the throwaway one usually has a few interactions crammed into a short window, a single path, and nothing afterwards. You can spot this difference without any specialist tools. It also makes one thing plain: raising several addresses to look like the first kind takes several times the time and money, and no trick removes that multiplier — the "line", put simply, is a limit on resources, not on cleverness.

Frequently asked questions

Should I open a second wallet or not?

It depends on what you're opening it for. If the aim is to claim one more airdrop share, the math usually doesn't work: gas and time multiply with the number of wallets, the interaction depth of each wallet actually gets spread thinner, and you add the risk of being seen as the same person. If the aim is to keep long-term holdings apart from everyday interactions, that's a legitimate need for asset segregation, has nothing to do with airdrop eligibility, and you should go ahead and open one.

Do multiple addresses derived from the same seed phrase count as multiple wallets?

On-chain, they're separate, independent addresses. In practice, though, they're usually managed together in the same wallet app, and funds often move back and forth between them — and those transfers are publicly visible. So derived addresses help you sort assets into separate compartments; they don't make you look like different people. Using them as a storage tool is fine; using them as a way around linking is heading in the wrong direction.

If a family member and I each farm on our own from the same computer, will we be treated as one person?

Possibly, but probably not because of the computer. Linking judgements mainly look at on-chain fund relationships and behaviour patterns, not at who sits at which machine. If two people's starting funds come from the same source, they tend to operate together at the same time, and their paths are identical, then on-chain that really is hard to tell apart from one person running two accounts. Two people who each use their wallets independently and spend their own money don't usually end up looking like that.

I've already opened several wallets. Is it too late to stop?

It isn't, and stopping beats adding more. Stopping doesn't mean deleting wallets; it means not adding any more and not mixing their funds together any further. Pick the one you actually use and put your future gas and effort into it. The costs you've already spent won't come back, but at least you can keep them from growing.

You can check the "visible on-chain" claims in this article yourself: enter any address into the block explorer Etherscan (Ethereum) or BscScan (BNB Chain) and you'll see all of its incoming and outgoing transfers, counterparties and timestamps. How any given project treats multi-account participation is set by its official announcements and campaign terms; rules change, this article doesn't represent any project's criteria, and it isn't investment advice.