← All posts · June 20, 2026 · 7 min read

Custodial vs non-custodial copy trading on Polymarket

One awkward question decides more about a copy trading tool than any feature list: how does it place trades in your account?

A trade needs a signature from your wallet's private key. So either the tool has access to a key that can sign for you, or it doesn't — and everything about how safe the tool is flows from that one design choice. This post explains both models plainly, walks through the hack that made this topic urgent, and tells you exactly what to ask any tool. Including us.

What "custodial" actually means here

Forget the exchange definition for a second. For copy bots, the split looks like this:

Non-custodial tools never touch a key that controls money. Pure wallet trackers are like this — they watch addresses and alert you, and you place trades yourself. Some trading interfaces also stay non-custodial by having your own wallet sign each order in your browser. The tradeoff is obvious: if a human has to click, you're not copying a trade 2 seconds after it lands. You're copying it whenever you happen to look at your phone.

Custodial tools hold signing power for a trading wallet, so a server can fire your order the moment the copied wallet moves. That's the entire reason automated copy trading works at all. It's also a real risk you're accepting: whoever holds that key — or the server where it lives — can spend what's in that wallet.

Telegram bots are the extreme end of this. Most of them generate a fresh wallet for you in the chat, which means the key was born on their server and has lived there its whole life. You never held it first. Some will show you the key once; either way, the bot's backend can sign anything it wants, whenever it wants. We compared that model to web dashboards in more detail in Telegram bots vs web copy trading.

The Polycule hack: what happens when this goes wrong

In January 2026, Polycule — at the time one of the most popular Telegram trading bots on Polymarket — was hacked for about $230,000 of user funds. The team took the bot offline, patched, and promised reimbursement, but the post-mortem is the part worth reading.

According to ChainCatcher's breakdown, the attackers chained three things: a server-side request forgery bug that let them reach internal systems, forged copy-trading events that tricked the bot into "copying" transfers to attacker contracts, and — the killer — user private keys stored on the backend with reversible encryption. Reversible means the server could decrypt them, which means anyone who owned the server could too.

Notice what the copy-trading feature itself became: an attack surface. A system built to automatically move your money when an external event fires will move your money when a fake external event fires, if the tool doesn't verify events properly. That's not a Telegram-specific problem. It's a custodial-copy-bot problem, and it applies to every tool in this category — Odaily's write-up framed the incident as a security wake-up call for prediction-market tooling generally, not just for one bot. We're keeping a running timeline of incidents like this in the bot hacks post.

Questions to ask any copy trading tool

• Where does the key come from? Generated on their server, or provided by you from a wallet you created? A key that was born on someone else's machine was never only yours.
• How is it stored? "Encrypted" alone means little — Polycule's keys were encrypted too. Ask whether it's encrypted at rest, who or what can decrypt it, and whether it ever leaves the server.
• What can the key actually do? Can the tool only place Polymarket orders, or can it withdraw to arbitrary addresses? Are withdrawals to anywhere but your own address possible at all?
• What happens if they get breached? Is there any public statement about incident response or reimbursement, or is the plan "hope"?
• Can you leave cleanly? Can you stop copying, withdraw everything, and rotate to a fresh wallet in five minutes?

Any tool that gets cagey about these has answered them.

Where btc5min sits — honestly

btc5min is custodial in the signing sense. You give it a private key for a trading wallet, we store it encrypted server-side, and our server uses it to sign your orders — that's how a copy fires in about 2 seconds without you touching anything, and there's no way around that tradeoff at that speed. The key is encrypted at rest, it's used for signing Polymarket orders, and it never appears in your browser or in logs.

But I'm not going to tell you to trust any service with your life savings, ours included. The advice we give our own users is the advice I'd give about a competitor:

Do that and the custodial-vs-non-custodial question shrinks from "can this tool destroy me" to "is this tool worth the fee." Which is where it should be.

So which model should you pick?

Depends what you're doing. If you just want to study wallets before committing anything, you don't need custody at all — watch first, copy later, exactly as we laid out in the step-by-step copy trading guide. If you want actual automated copying, some server somewhere will be signing for you, so the real question is which operator you give a small, capped wallet to — and whether their answers to the checklist above hold up.

And if a tool tells you it's "fully non-custodial" while also placing trades for you automatically, ask them to explain how. One of those two claims is doing a lot of work.

btc5min is an independent tool and is not affiliated with, endorsed by, or operated by Polymarket. Nothing here is financial advice. Prediction markets are risky, copying another trader does not guarantee profit, and you can lose the money you trade with.