Browser Wallet vs Hosted Bundlers: Who Holds Your Keys?
Browser-wallet and hosted pump.fun bundlers differ in who holds your launch wallet keys. Here is what each custody model means for speed, safety and control.
By DevBundler Team · · 5 min read
The short answer
With a browser-wallet bundler, your keys stay in your browser or wallet extension and you approve each signature yourself. With a hosted bundler like DevBundler, the keys are stored encrypted on the tool's server, which signs launches and multi-wallet trades for you instantly. Hosted is faster and simpler but custodial, so keep only what you need in those wallets.
Key takeaways
- The real difference between bundler types is where the private keys live and who can sign with them.
- Browser-wallet tools keep keys on your device, so nobody else can sign, but you approve more prompts and you own the backups.
- Hosted tools keep keys on their server, which is what lets one click sign an 11-wallet launch or a 10-wallet sell.
- DevBundler is hosted and custodial: keys are encrypted with AES-256-GCM using a key derived from your password with argon2id plus a server secret.
- With any model, use fresh launch wallets, fund them with only what you need and sweep profits out after.
Every bundler has to sign transactions from several wallets at once. The question that separates them is where those wallets' private keys live while that happens. In a browser-wallet tool, they live on your device and you approve the signatures. In a hosted tool, they live on the tool's server and it signs for you. DevBundler is the hosted kind, and that is a custodial choice with real trade-offs on both sides.
Why bundlers need keys in the first place
A bundled launch is the create transaction plus buys from other wallets, all sent as one Jito bundle. Every wallet in it has to sign. With a dev wallet and 10 buyers, that is 11 wallets signing in the few seconds before the blockhash goes stale.
Selling is the same. Selling 50% from ten wallets means ten signatures, quoted in order so each wallet's slippage minimum still holds after the sells before it.
So any tool that does this has to get at the keys somehow. There are two broad answers.
Model 1: keys on your device
Connect-wallet tools and browser extensions keep keys in your browser (sometimes in the page's local storage, sometimes in an extension) or in your wallet app. Nothing leaves your machine unless you sign it.
What that buys you: no third-party server can move your SOL. If the tool's company disappears, your keys are still where you left them.
What it costs you: more prompts, or a tool that stores generated wallets in browser storage where a cleared cache, a bad extension or a compromised computer is now the risk. Backups are your job. And signing ten wallets through a wallet app's approval screen is slower than one confirm.
Model 2: keys on the tool's server
Hosted tools generate wallets (or take keys you import) and store them on their server. When you press launch or sell, the server signs every wallet's transaction and sends them. That is what makes one-click launches and ten-wallet sells fast.
What it costs you: trust. You are relying on the operator to store keys well, run a secure server and stay honest. If you are not comfortable with that for a given amount of SOL, do not put that amount in.
The two custody models
| Keys on your device | Keys on the tool's server | |
|---|---|---|
| Who can sign | Only you | The tool's server, on your instruction |
| Speed of multi-wallet actions | Slower, more approvals | One confirm for many wallets |
| Main risk | Your device, extensions, lost backups | The operator's security and honesty |
| If the tool shuts down | Keys are still with you | You need to have exported or swept first |
| Backups | Your job | Tool stores them; export for your own copy |
| Works across devices | Only where the keys are | Anywhere you can sign in |
How DevBundler handles custody
We would rather you know exactly what you are trusting. Here is how it works:
DevBundler key handling
- Wallets are generated by DevBundler, or you import keys you already have.
- Keys are stored encrypted with AES-256-GCM.
- The encryption key is derived from your password with argon2id, combined with a server secret.
- Keys are never written to logs.
- Exporting a key asks for your password again and shows it for 10 seconds.
- Sessions lock automatically after idle time.
None of that changes the basic fact: the server can sign for the wallets you keep in DevBundler. That is the feature, and it is also the trade-off. How DevBundler stores wallet keys goes deeper on the encryption.
Which model fits you?
Neither model is right for everyone. Here is an honest split.
Choose keys-on-device if
- You want no third party able to sign, at any amount
- You launch rarely and do not mind approving each signature
- You are comfortable managing your own backups
- You are moving amounts you would not trust to any server
Choose hosted if
- You launch with many wallets and want one confirm
- You trade across wallets after launch and need it to be quick
- You want to sign in from any computer
- You keep only working amounts in launch wallets and sweep out
If you pick a hosted tool, the habits matter more than the encryption details: fresh wallets, small balances, regular sweeps. If you pick a device-based tool, the habits shift to device hygiene: a clean browser, few extensions, and backups stored offline.
Questions to ask any tool about custody
Whatever a tool's marketing says, these five questions tell you which model it really uses and how carefully it handles it.
- 1
Where do the keys live?
On my device, in my wallet app, or on your server? If the answer is "it depends", ask what it depends on.
- 2
How are stored keys encrypted?
A specific algorithm and key source is a good sign. "Bank-grade security" with no details is not.
- 3
Can staff or logs see keys?
Keys should never be written to logs or shown in support tools.
- 4
How do I export a key?
It should be possible, and it should ask you to prove who you are first.
- 5
What happens if I stop using you?
You should be able to sweep every wallet back to one address you control, at any time.
DevBundler's answers are in the checklist above. If a tool you are considering cannot answer all five, that alone is useful information.
What both models share
Some risks do not depend on custody at all.
- Fake tools. A phishing site or fake extension is dangerous in either model. Check the address you sign in to, and never paste a seed phrase into a site you reached from a DM.
- Market risk. Meme coins are speculative. No custody model protects you from a coin nobody wants.
For the full list of habits that keep launch wallets safe in either model, see how to keep launch wallets safe. If you are still comparing tools on more than custody, how to choose a pump.fun bundler has a scoring checklist.
Frequently asked questions
›Is a hosted bundler custodial?
Yes. If the tool's server can sign transactions for your wallets without you approving each one, it holds the keys, which makes it custodial for those wallets. That is true of DevBundler.
›Are browser-based bundlers safer?
They remove one risk, the tool's server holding your keys, but add others: malicious extensions, a compromised browser, and keys lost if you clear storage without a backup. Safer depends on which risk you are better at managing.
›Can I get my keys out of DevBundler?
Yes. You can export a wallet's private key after entering your password again, and it is shown for 10 seconds. You can also consolidate your wallets back into one at any time.
›Should I import my main wallet into a bundler?
No. Use fresh wallets for launches with any tool, browser-based or hosted, and keep your long-term holdings in a wallet that never touches a bundler.
›Why do hosted bundlers need my keys at all?
To sign many transactions from many wallets in one go. A launch with a dev wallet and 10 buyers needs 11 wallets to sign, and a hosted tool can do that in the moment you confirm.
Keep reading
How DevBundler Stores Wallet Keys (and What That Means for You)
A plain explanation of DevBundler's custodial key model: how keys are encrypted, why the server signs for you, and how to limit what you trust it with.
· 4 min read
How to Keep Your pump.fun Launch Wallets Safe
Practical wallet safety for pump.fun launches: separate your main wallet, fund only what a launch needs, sweep profits out and lock down the account you launch from.
· 5 min read
How to Choose a pump.fun Bundler: A Buyer's Guide With Scoring
How to pick a pump.fun bundler: the five types of tools, the criteria that matter (custody, Jito bundles, exits, fees) and an 18-point scoring checklist.
· 7 min read