BLOG · 15 Sept 2026 · 6 MIN
Where bundle wallet keys live, and why it matters
A bundler has to sign dozens of transactions in the same instant, and the usual conclusion is that it must therefore hold the keys. That conclusion is wrong, and it is worth understanding why — because it decides what happens to your funds on the worst day.
Why the assumption exists
The opening tax window is three seconds. Signing a transaction takes a couple of milliseconds; asking a person to approve thirty of them takes minutes. There is no version where a wallet extension prompts for each buy and the bundle still lands in time.
From there the reasoning usually goes: the signing has to be automatic, automatic signing needs the keys, therefore the service holds them. Every step follows except the last one.
What the last step misses
Automatic signing needs the keys to be reachable by whatever does the signing. It does not need them to be reachable by a server. A browser can generate keys, hold them locally, and sign thirty transactions in twenty milliseconds without any of them ever crossing the network.
What leaves the machine in that arrangement is a list of already-signed transactions — bytes that are useless for anything except being broadcast, and that reveal nothing about the keys that produced them.
Why it matters more than it sounds
Custodied keys concentrate risk in a place you do not control. A database that can be read, a backup that can be copied, an employee who can be compelled, a jurisdiction that can compel them. None of these require the operator to be dishonest.
Keys that never leave your browser remove the entire category. There is nothing on the server to leak, because the server was never given anything.
How to tell which kind you are using
The question that settles it: can the service show you a wallet's private key after you close the tab and open it on another device?
If yes, it has them. If the wallets only exist in the browser that made them, it does not — and you carry the responsibility of backing them up, which is the honest side of the trade.
- Keys generated locally, never transmitted
- Every transaction signed before anything is sent
- Export available at any time, without asking anyone
- Wallets you can use in any other tool, because they are ordinary keys
The responsibility that comes with it
Nobody can recover keys that were never given to anyone. Export them, keep the export somewhere real, and treat clearing your browser data as the serious act that it is.
That is a genuine cost. It is also the only arrangement where the answer to "what if the service is compromised" is: nothing happens to your funds.
Terms in this article: bundling, defined · how Arrow handles this
Keep reading
6 min read
How many wallets should a bundle use?
Between 5 and 32 wallets, and the right number depends on position size, gas overhead and how much dispersion you actually need. The trade-offs, with numbers.
6 min read
What a token bundler actually does
A bundler creates a token and buys its opening supply from several wallets in one coordinated move. Here is what that means mechanically, and what it does not mean.
7 min read
How to launch a token on PonsFamily, start to finish
Everything a launch needs on PonsFamily: what the fields mean, what is fixed forever, what it costs, and the three decisions that cannot be changed afterwards.