The short version — who each exchange is for
Bybit is for users who want the deepest BTC perpetuals book outside of Binance, are comfortable submitting an ID for KYC, and plan to scale up over time. The API is mature, the affiliate program is widely supported, and the fee structure rewards higher volume.
Toobit is for users who want to start fast, prefer minimal personal-data disclosure, or live in a region where Bybit's KYC requirements have tightened. The orderbook is thinner and the platform is younger, but for retail-size BTC perpetuals copy trading the difference is often invisible.
Glimpse supports both. The pick comes down to where you live, what KYC you're willing to do, and how large your tickets are. We list current support details on the exchanges page.
KYC — the biggest practical difference
Bybit has progressively tightened KYC over the past two years. To trade perpetuals at meaningful size and use the API, expect to submit a government ID and complete identity verification. The process is typically same-day, but it's a hard wall if you don't want to share documents.
Toobit operates with lighter KYC in many regions — in some jurisdictions you can fund, trade perpetuals, and create API keys with only an email and 2FA. This shifts as Toobit's regional licensing evolves, so check the current state when you sign up, not what someone wrote on Reddit six months ago.
Neither exchange is a way to evade tax obligations. In most jurisdictions, every closed trade is a taxable event regardless of which exchange it happened on, and tax authorities increasingly request data from exchanges directly. Pick on convenience and product fit, not on hiding income.
Liquidity and slippage on BTC perpetuals
Bybit's BTCUSDT perpetual is one of the deepest contracts in crypto — typically tens of millions of dollars within 5 basis points of mid. For copy-trade tickets in the $50–$5000 range, you'll get filled at essentially the screen price.
Toobit's BTC perpetual book is smaller. At retail size (single-ticket exposure under a few thousand dollars), slippage is usually negligible — measured in cents, not dollars. As tickets get larger, the spread widens faster than on Bybit, and during volatile minutes you may pay an extra few basis points.
For most Glimpse users this difference is academic — copy-trade sizing is proportional to your account, and most accounts aren't large enough to move either book. But if you're scaling to five-figure tickets, Bybit's depth becomes a real advantage.
Fee structures, side by side
Bybit's retail perpetual fees are approximately 0.06% taker and 0.06% maker at the base tier — the maker/taker spread is intentionally narrow to encourage usage. Volume-based tier reductions kick in around $5M monthly volume, which retail users rarely hit. There are also periodic fee promotions for new accounts.
Toobit's retail perpetual fees are in a similar range — approximately 0.06% taker and 0.02% maker at base tier, with their own VIP tier ladder. Maker rebates show up at higher tiers. The headline number is comparable; the practical cost depends on whether your strategy is maker-heavy or taker-heavy.
Copy trading is taker-heavy by nature — when the leader opens a position, the follower has to fill at market to match. So real-world fee drag on a copy-traded account is closer to the taker rate than the maker rate. Both exchanges land in the same ballpark for that workload.
API maturity and copy-trading reliability
Bybit's API has been hardened by years of high-frequency-trading firms using it. Rate limits are documented, websocket streams are stable, and the auth model (HMAC over query string) is the most widely supported. Almost every third-party copy-trading and bot platform supports Bybit first.
Toobit's API is newer. It works, it's documented, and Glimpse uses it for live copy fan-out — but the surface area is smaller, occasional symbol-format quirks exist, and recovery from intermittent network errors is less battle-tested than Bybit's. We've engineered around the gaps; you don't see them as a user, but they exist under the hood.
For setup specifics — the exact permissions to enable, IP whitelisting, and key rotation — see our Bybit API key setup guide.
Regional availability
Bybit serves most of the world but has restricted or excluded users in the US, UK, mainland China, and several others. The list shifts. If you're in a restricted region, Bybit's signup will block you at KYC even if the homepage looks accessible.
Toobit's regional footprint differs — it's available in some places Bybit isn't, and restricted in others Bybit serves. There's no clean universal answer. Both exchanges publish updated restricted-region lists in their terms of service; read those, not third-party blogs.
If you're in a region where one of the two won't onboard you, the answer is the one that will. Glimpse will route you to whichever exchange you can actually use, and our waitlist collects region info so we can flag eligibility issues before you spend an hour signing up.
Custody and security on each
Both exchanges hold customer funds in a mix of hot and cold wallets, both publish proof-of-reserves attestations, and both have insurance funds for socialized losses during liquidation cascades. Neither is risk-free — no centralized exchange is. The 2022–2024 era taught everyone that any single exchange is a counterparty.
The practical risk-reduction step is the same on either: connect to Glimpse with a trading-only API key, withdrawal permissions explicitly disabled, ideally with IP whitelisting if your setup supports it. That way the worst case from a Glimpse compromise is bad trades, not drained funds. We cover the full security model on the security page.
Don't park more on either exchange than you'd be comfortable losing if the exchange itself went down. This is general advice, not specific to Glimpse or to either exchange — it's how to live with centralized crypto venues at all.
Which one should you pick?
Pick Bybit if: you're comfortable with KYC, you're in a region Bybit serves, you might scale to larger tickets over time, and you want the most third-party-tool support. This is the default choice for most users.
Pick Toobit if: Bybit doesn't serve your region, you prefer faster onboarding without document upload (in regions where Toobit allows it), or your tickets will stay small and the orderbook-depth difference doesn't apply to you.
Pick both if you want to diversify exchange-counterparty risk. There's no rule that says you have to copy-trade on a single venue, and Glimpse supports either. Just be aware that running the same strategy on two accounts doubles your exposure to that strategy — it doesn't halve your risk. We explain the copy-trade mechanics in the copy trading guide.
Glimpse pricing is the same regardless of which exchange you connect — the tier you pick is about features and limits, not the exchange. Full breakdown on the pricing page.
How Glimpse handles the choice
Internally, Glimpse's bot runs on Bybit — that's where the founder's capital lives and where the public track record is generated. The fan-out layer publishes those positions to any supported user account, regardless of which exchange the user connected with.
The signal is the same; the execution venue is yours to pick. If you connect Toobit, your fills happen on Toobit's order book at Toobit's spread. If you connect Bybit, your fills happen on Bybit's. Slippage will differ slightly between the two venues, which means your tape won't be byte-for-byte identical to the public bot's tape — but it'll be close, and the direction and reasoning are always the same.
If you're not sure which to pick, the waitlist form has a region field and we'll tell you which one onboards you fastest based on where you are.