Futures
Access hundreds of perpetual contracts
TradFi
Gold
One platform for global traditional assets
Options
Hot
Trade European-style vanilla options
Unified Account
Maximize your capital efficiency
Demo Trading
Introduction to Futures Trading
Learn the basics of futures trading
Futures Events
Join events to earn rewards
Demo Trading
Use virtual funds to practice risk-free trading
Launch
CandyDrop
Collect candies to earn airdrops
Launchpool
Quick staking, earn potential new tokens
HODLer Airdrop
Hold GT and get massive airdrops for free
Launchpad
Be early to the next big token project
Alpha Points
Trade on-chain assets and earn airdrops
Futures Points
Earn futures points and claim airdrop rewards
The strategy works, so I wanted to spin up multiple accounts to diversify risk, but got stuck for a whole day.
The problem wasn't the strategy—it was infrastructure.
Same codebase, Account A trades normally, Account B shows $0 balance no matter what. API auth is fine, address is correct, wallet clearly has $600.
Debugged address mapping, proxy architecture, regenerated API credentials—nothing worked.
Finally found it: Polymarket's Google login and wallet login use different signature protocols under the hood. The code had a hardcoded number 2 when it should be 1. A single constant difference turned the entire account into a ghost account.
Between "strategy runs" and "multiple accounts run," there's a whole layer of engineering problems:
- Account type determines signature protocol—not all accounts are the same
- Zero balance returned doesn't mean no funds, could mean querying the wrong dimension
- Fail-closed security mechanisms make the issue look like "strategy stopped" instead of "config wrong"
Running a single account is a personal project. Deploying multiple accounts is systems engineering.