Polymarket + OKX Trading Automation
Automation built for
Automation built for
BTC 5-minute markets
Two independent execution paths: Polymarket for BTC Up/Down markets and OKX for BTC-USDT perpetual futures. Monitor both in one console while starting, configuring, and maintaining each engine separately.
Independent Engines
Paper + Live
Protection + Recovery
Desktop + Cloud
Two Independent Engines
Two automation paths, one clear control surface
The engines share one product experience while keeping configuration, runtime state, positions, and execution independent so activity in one market does not interfere with the other.
PolymarketBTC Up / Down
Prediction-market discovery, signals, orders, settlement, and runtime maintenance organized into one automated lifecycle.
- Independent configuration, state, and order history
- Time-window-aware automated execution
- Local and long-running cloud operation
OKX FuturesBTC-USDT-SWAP
Signals are generated from formally closed BTCUSDT 5-minute candles, while OKX handles isolated-margin execution, protection orders, and position recovery.
- Paper and live trading modes
- Dynamic leverage, stop loss, and trailing protection
- Market chart, position details, and full order history
Control & Operations
See both automation engines clearly while each runs independently
The global overview keeps both runtimes and account summaries visible. Each market page then exposes its own chart, configuration, orders, positions, and logs. The control experience is unified; execution and risk remain separate.
Dashboard Center
A control surface built for live monitoring, demos, and daily operation
The overview combines Polymarket and OKX account and runtime state, while each market retains its own chart, positions, orders, and logs. Global summaries keep refreshing regardless of the open page.
- Read both markets' key state and account data at a glance.
- Start, stop, and maintain each engine without ambiguity.
- Built for local monitoring and unattended cloud operation.
Automation Flow
Enter the trading window only with a complete execution context
Data loading and account checks that can happen early are warmed before the trading window. After a candle closes, the engine only appends fresh data, evaluates the signal, and executes within its short validity window.
- Uses formally closed candles and no future information.
- Warms required data before time-sensitive execution.
- Preserves exception logs while throttling routine noise.
Risk & Execution
Signals, risk, position protection, and recovery work as one lifecycle
A signal is only the starting point. Balance, minimum order size, existing positions, stale orders, leverage, protection orders, and market-data health all belong to the execution loop.
Each engine follows its own market rules and formal time boundaries.
Data and checks that can run early stay out of the critical window.
Stops, trailing protection, recovery, and exits share one lifecycle.
A failure on one market does not enter the other engine's state.
Public Research
Auditable
Only information available at the time may influence a decision.
Fees, slippage, and execution constraints are part of the public assumptions.
Full-sample, segmented, and recent results reveal stability and drift.
Drawdown, losing streaks, leverage, and failure conditions stay visible.
Historical backtests and simulations cannot guarantee live performance.
Editions
Windows, planned macOS, and Linux cloud delivery
Finished packages are published through GitHub Releases. Purchasing, licensing, and download access remain managed by the existing client workspace. Desktop suits local operation; cloud suits supervised long-running execution.
Windows Edition
A full Windows build for local operation, monitoring, and complete product experience.
- Graphical control interface
- Well suited for monitoring and demos
- Ready for structured commercial delivery
Mac Edition (In Development)
A native macOS desktop experience is planned to expand local operating options.
- macOS release is planned
- Native desktop experience in development
- Availability will be announced later
Cloud Edition
A server-oriented build designed for compatibility-sensitive, long-running environments.
- Cloud-ready deployment
- CentOS7-compatible delivery
- Better suited for 24/7 operation
FAQ
Clear answers to the most important product questions
Who is PolyNexus for?
It is built for operators who want Polymarket or OKX BTC futures execution to run as a disciplined system and who understand automation, leverage, and market risk.
Do the two automation engines affect each other?
No. Polymarket and OKX keep separate configuration, runtime state, positions, orders, and recovery paths. They only share the control surface.
Is 20x OKX leverage suitable for everyone?
No. It is a high-risk setting where small price moves may cause material losses. Validate in paper mode and at low leverage first.
What does exclusive OKX instrument control mean?
Once enabled, the software adopts positions and manages regular and conditional orders for the configured BTC-USDT-SWAP instrument. Use a dedicated account or sub-account and do not trade it manually or run another bot.
Contact
Talk to us about demos, editions, licensing, and deployment
If you want to explore the desktop build, the cloud package, or the right delivery path for your environment, the fastest next step is to reach out on Telegram.