Multi-Accounting: From Manual Control to Automation. Part 1
In the previous series of articles, we looked at the situation through the eyes of projects: how they identify Sybil clusters, what signals they consider, and how they use graph analysis. Now we change our perspective — we are talking not about project filters, but about how we manage a multi-account farm ourselves.
By account hygiene here, it is reasonable to understand a basic set of rules for carefully maintaining and separating accounts and wallets: how we create, use, and link addresses to each other. A portion of these rules can easily be followed manually.
Usually, such rules imply:
- Not linking the same CEX account to all wallets;
- Using an anti-detect browser and separate profiles;
- Working through different proxies rather than one shared IP;
- Ensuring that wallets have at least some history and do not appear solely for one airdrop.
Theoretically, this is enough for careful manual management of a farm. In practice, it is precisely the manual format that often leads to repetitive mistakes.
What can realistically be done manually
There are things that are genuinely convenient and straightforward to do by hand:
- Divide wallets into groups. For example, use some addresses in one ecosystem, some in another, and keep certain wallets as "long-living" profiles.
- Spread activity over time. Do not execute everything in one evening, but consciously distribute actions across different days without tying them to a single fixed hour.
- Do not collect rewards in a single wallet. Whenever possible, withdraw rewards to different addresses or do it gradually through various routes.
- Add organic activity. From time to time, use dApps outside of campaigns so that the history does not look like a continuous chain of tasks.
If you follow these principles, manual management already provides a decent level of order. But over time, the hardest thing to control comes into play — our habits.
Where manual control most often fails
Problems usually arise not from a lack of knowledge, but from routine and fatigue:
- We find a convenient route for completing a campaign and repeat it across multiple wallets;
- We work during roughly the same time intervals;
- We react identically to technical failures: we cancel transactions in similar places and repeat the same actions;
- From time to time, we return to our usual "central" wallets to collect rewards or withdraw funds more quickly.
At the level of a single profile, everything looks logical. But if you look at the farm as a whole, it turns out that many addresses behave far too similarly.
From the perspective of project analysis, this is no longer just a set of neatly configured addresses, but a group with noticeably repeating patterns: tight time windows, similar scenarios, and common points for depositing/withdrawing funds.
What an honest look at manual management leads to
To summarize, we arrive at an important point. Even when we fully understand the basic rules of working with multi-accounts and try to follow them manually, the human factor eventually leads to repetitive scenarios.
This does not mean the manual approach is "bad." It is simply its natural limitation: the more wallets you have, the harder it is to maintain behavioral diversity solely through attention and discipline.
At the same time, there is a common opinion among multi-account users that any automation only worsens the situation and makes behavior even more uniform — and this is largely true when it comes to simple bots rather than modern automators.
Hence, a logical question arises: how can we preserve the same rules for managing accounts but remove most of the routine and repetitive actions from the process?
In the second part, we will break down exactly how a simple "bot" differs from a modern automator, and why it is the automator that helps these rules work not only in theory but also at the level of your wallets' on-chain history.
