How I Run 20 Wallets on Variational With an AI Agent and BitBrowser MCP
Running 20 wallets on Variational is a housekeeping problem before it is a trading one: 20 sets of keys, 20 sessions and 20 chances to sign from the wrong account. This is the routine I use to keep them apart, with one browser profile per wallet and an AI agent that opens them one at a time through BitBrowser's MCP service.
One thing up front, because the title could be read another way. This is not a method for multiplying Variational points. I did the arithmetic in section 3, and splitting your volume across 20 wallets earns you fewer points than keeping it in one. The setup is about safety and order.
The profiles live in BitBrowser. I picked it because every profile keeps its own extension storage, and because since version 7.1.5 an AI client can manage the profiles for me in plain language.
📌 In short: one wallet per profile, a register that says what each wallet is for, an agent that opens one profile at a time and never signs anything, and a clear look at what Variational's rules reward.
What's in this post
- Why anyone has 20 wallets
- Variational in three paragraphs
- The points program, and why 20 wallets don't multiply it
- The real danger is the browser
- One wallet, one profile
- My wallet register
- Connecting the agent
- The daily round
- The Friday review
- Phones, and the one thing that never goes on them
- What my agent never does
- FAQ
1. Why anyone has 20 wallets
Wallets pile up the way email addresses do. One for long-term holdings that I rarely touch. One per strategy, so a basis trade and a directional bet don't share margin or muddy each other's results. A few for testing new venues with small money before anything serious goes near them. A couple that hold nothing and exist only to receive.
None of that is exotic. Every security guide tells you to separate a holding wallet from an active one. Twenty is just where that advice lands after a few years of taking it.
What matters is that each wallet has a reason you can say out loud. If the only reason is "more wallets, more rewards", stop here, because the next section is going to disappoint you.
2. Variational in three paragraphs
Variational is a trading protocol on Arbitrum. Its app, Omni, offers perpetuals with zero trading fees. You don't trade against an order book of other users. The Omni Liquidity Provider quotes you a price, drawing on liquidity from exchanges and other venues behind the scenes.
Collateral is USDC on Arbitrum. Omni is still in private beta at the time of writing, so you need a whitelisted address or a referral code to get in, and it isn't available to US or Canadian persons. If that describes you, the answer isn't a proxy. It's a different venue.
Two features get the attention. A loss refund pool gives a small chance of having a losing trade refunded, with better odds at higher volume tiers. And a points program has been running since 17 December 2025, ahead of a VAR token that Variational has said will send half its supply to the community. The token event is currently expected in the last quarter of 2026. Nothing here is financial advice.
3. The points program, and why 20 wallets don't multiply it
Here is how points work, from Variational's documentation and current trackers. A fixed number of points is distributed every Friday for the previous week's activity. Your share follows your trading volume, not your profit. On top of that sit two boosts: one for your reward tier, which depends on your trailing 30-day volume, and a 10% boost for accounts that traded before the program launched.
Now split one trader into 20 wallets and see what moves.
| What you earn from | One wallet | Same volume across 20 wallets |
|---|---|---|
| Base points (share of weekly pool by volume) | Full share | Same total share |
| Tier boost (by 30-day volume per account) | Higher tier | Each wallet drops to a lower tier |
| 10% early-account boost | Kept, if the account is old enough | Lost on every wallet created after launch |
| Referral points | From real referrals | Only if you refer yourself |
| Loss refund draws | One account's odds | More accounts, each at lower-tier odds |
Take a concrete case. Say you trade $6 million in 30 days. In one account, tier tables at the time of writing put that in Silver, with a 1% boost. Cut into 20 wallets, each does $300,000 and sits in the lowest tier with no boost. Same volume, same spread paid, fewer points. If the single account also carried the early-account boost, the gap is wider still.
The only lines in that table where 20 wallets could come out ahead are the last two, and both are the kind of thing a team notices. Referring your own wallets is self-referral. Opening extra accounts to get more refund draws is gaming a pool that other traders fund.
Variational's documentation is short on this and clear enough. It reserves the right to modify the program or anyone's point totals at its sole discretion, and it names inorganic behaviour and breaches of the Terms of Use as examples. Its trading competition rules go further and disqualify wash trading, multi-accounting and matched trades by name.
⚠️ My reading: several wallets with real, separate purposes are ordinary. Wallets created to squeeze the program are "inorganic" by any sensible definition, and they don't even pay. On-chain funding links are public, so a tidy browser setup hides nothing.
4. The real danger is the browser
Once the points question is out of the way, what's left is the risk that grows with every wallet you add.
Everything sits in one extension. Twenty accounts in one wallet extension, in the browser you also use for email and group chats, means one bad extension update or one careless approval can reach all of them.
The wrong wallet is always one click away. The active account is whichever you used last. Sending from the wrong wallet is a mistake that gets likelier with every account in the dropdown.
Fake front ends only need one signature. A sponsored search result, a link in a Discord reply, a lookalike domain. If the wallet that holds real size shares a browser with your daily clicking, the distance between a mistake and a drained account is a single approval.
Being careful doesn't fix this, because nobody is careful every day for a year. Structure fixes it. The setup has to make the careless moment small.
5. One wallet, one profile
So every wallet gets its own browser profile, and the profile holds nothing else.
A BitBrowser profile carries its own cookies, local storage and extension data. I install the wallet extension inside the profile, add exactly one account to it, and that key material exists there and nowhere else. The next profile has its own copy of the extension and a different wallet. They can't see each other.
My rules for a wallet profile:
- One wallet extension with one account.
- No other extensions of any kind.
- One bookmark, to the real Omni address, typed by hand once and checked twice. I only ever arrive through the bookmark.
- A name that says what the wallet does:
VAR-03-basis,VAR-08-test,VAR-15-hold. - A hardware wallet behind anything with real size, so the profile holds a connection and the signature needs a button press on a device in my hand.
I don't put a different proxy on each profile. I'm not hiding that the wallets are mine, so they all use my normal connection. And nobody should use a proxy to look like they're outside a country Variational doesn't serve.
6. My wallet register
The register is a spreadsheet with a row per wallet. It's dull, and it's the thing I'd rebuild first if I lost everything else.
| profile | label | address (short) | purpose | signer | notes |
|---|---|---|---|---|---|
| VAR-01-dir | Directional | 0x7a3...e1c | discretionary perps | hardware | main size |
| VAR-03-basis | Basis | 0x19b...04d | funding trades | hardware | |
| VAR-08-test | Test | 0xc42...9aa | new features, small money | extension | never above $200 |
| VAR-15-hold | Holding | 0x5d0...b77 | idle USDC | hardware | no trading |
No seed phrases, no private keys, no API secrets. Short addresses and labels only. I save it as wallets.csv in the folder where I run the agent.
The purpose column earns its keep twice. It tells me in six months why a wallet exists. And if a protocol ever asks why one person has several accounts, a register with a reason on every row is a real answer.
7. Connecting the agent
BitBrowser's MCP service runs inside the desktop app. In Settings, then Browser Settings, then Local API, I switched on Enable Authentication Control and copied the API token. With Claude Code, one command adds the server:
claude mcp add --transport http bitbrowser http://127.0.0.1:54345/mcp --header "x-api-key: YOUR_API_TOKEN"
Cursor, Codex and other clients take the same address and header in their own settings. The server only listens on your own machine, and the token deserves the same care as a password.
Every session starts with the same two instructions:
Before any action that creates, updates or deletes something in BitBrowser, show me the plan and wait for me to type "go".
Open only one profile whose name starts with VAR- at a time. Close the open one before you open the next.
The second instruction is the whole reason I use an agent for this. One wallet on screen means the wallet I'm looking at is the wallet I sign with.
It's worth being exact about what the agent can do. BitBrowser's MCP manages profiles, groups, tags, windows and cloud phones. It doesn't click inside a page, it can't read my keys, and it can't approve a wallet prompt. I wouldn't use it if it could.
8. The daily round
My morning looks like this.
Read wallets.csv and list the VAR- profiles in this order: anything with an open-position tag first, then the rest by name.
Open VAR-01-dir.
The profile opens on the bookmark. I check positions, margin and funding, and act if I need to, signing by hand. Then:
Close VAR-01-dir and tag it checked. If I said I have a position open there, keep the open-position tag. Open the next profile on the list.
When something needs a second look, I don't stop the round:
Tag VAR-03-basis with follow-up and note: "funding turned, review after the next interval".
And to finish:
Close every open profile. List VAR- profiles that are not tagged checked. Then clear the checked tag everywhere and write today's notes to a dated file in the logs folder.
Most wallets take a minute or less, because most of them hold nothing that changes daily. The round exists so that the few that matter get looked at every day and the rest get looked at at all.
9. The Friday review
Points land on Fridays, which makes it a natural day for upkeep.
Compare the profile column in wallets.csv with the BitBrowser profile list. Show me profiles that aren't in the sheet and rows with no profile.
List every profile tagged follow-up with its note, oldest first.
List VAR- profiles I haven't tagged checked on any day this week, going by the log files.
With the first prompt I catch drift, such as a test profile I made on Tuesday and forgot to register. The last one catches neglect. A wallet nobody has opened in a week is either fine or forgotten, and it's better to decide which.
I also export each active wallet's trade history from Omni and file it under the wallet's label. Tax rules differ by country, but every version of them is easier when each wallet has a purpose and its own paper trail.
10. Phones, and the one thing that never goes on them
Some of the job is mobile. Price alerts, the project's Discord and Telegram, and checking how a page behaves on a phone.
For that I don't want a drawer of handsets. A cloud phone is a remote device you open from your desk. BitBrowser has BitCloudPhone for Android and BitCloudPhone-iOS for cloud iPhones, and its MCP guide lists cloud phone actions, so the agent that opens my profiles can start a phone and shut it down again.
The line I won't cross: no seed phrase, private key or signing wallet goes on a rented device, from any provider. A cloud phone is someone else's hardware. It's fine for alerts and chat. Signing stays on a hardware wallet or a machine I own.
11. What my agent never does
No trading. It can't, and I won't add anything that lets it. An agent placing orders across many wallets is automated, coordinated activity, and it's the picture a protocol has in mind when it writes "inorganic".
No shuffling funds between my wallets to create activity. If two of my wallets could ever end up on opposite sides of a trade, the strategies are wrong and I fix the strategies.
Referrals are off limits. My wallets don't refer each other.
Secrets stay out. Nothing sensitive goes in a prompt, the register or the log.
BitBrowser's own guide makes the same point from the tool's side: MCP doesn't grant permission to break a platform's rules. On Variational the rules are its Terms of Use and its points documentation. Read both yourself.
12. FAQ
Do 20 wallets earn more Variational points than one?
No. Base points follow volume, so the total is the same, and tier boosts depend on each account's own 30-day volume, so splitting lowers them. New wallets also miss the 10% boost for early accounts.
Does Variational ban multiple wallets?
Its points documentation reserves the right to change point totals for inorganic behaviour or Terms of Use violations, and its competition rules disqualify multi-accounting. Wallets with separate real purposes are a different matter from wallets made to work the program. Check the Terms of Use for the exact position.
Do separate browser profiles hide that the wallets are mine?
No. Funding paths are public on-chain. Profiles isolate keys and sessions so one mistake can't reach every wallet.
Can the AI agent trade or sign for me?
No. BitBrowser's MCP service manages profiles, groups, tags, windows and cloud phones. It doesn't act inside pages or approve wallet prompts.
Is Variational available everywhere?
No. Omni is in private beta, needs a whitelisted address or referral code, and isn't available to US or Canadian persons.
When is the VAR token?
Variational has pointed to the last quarter of 2026 and a 50% community allocation. Points have no published conversion rate, and dates have moved before.
Disclosure: I do content work for BitBrowser and BitCloudPhone, and the BitBrowser link in this post is a referral link. This post is not financial advice.