The Short Answer
A single PolySnipe instance is configured for one market at a time — either BTC 5-minute or BTC 15-minute. You cannot trade both from the same running application.
But you can run two instances simultaneously. One for each market. On the same machine, on the same account if you want, just started from separate folders and on different ports.
The setup takes about five minutes.
Why Two Instances Instead of One
The bot's strategy logic, position sizing, and timing parameters are all calibrated to the window length of the selected market. A 5-minute window and a 15-minute window behave very differently — different signal accumulation curves, different hold durations, different exit timing. Combining them in a single runtime would mean compromising the logic for both.
Running two separate instances keeps each one purpose-built and properly calibrated. Instance 1 handles the 5-minute market with its own configuration. Instance 2 handles the 15-minute market with its own configuration. They run independently, log independently, and do not interfere with each other.
What This Gives You in Practice
BTC 5-minute market: ~288 windows per day (24 hours × 12 windows per hour)
BTC 15-minute market: ~96 windows per day (24 hours × 4 windows per hour)
Running both: ~384 total market windows per day
The 15-minute market does not simply double your exposure — it adds a different class of opportunity. Longer windows create different microstructure dynamics. Some signals that are too slow for a 5-minute window are natural entries in a 15-minute context. The two markets complement each other rather than overlap.
Step-by-Step Setup
Step 1 — Create a second folder
Copy your existing PolySnipe installation folder to a new location. For example:
C:\PolySnipe\instance-5min\ ← your existing installation
C:\PolySnipe\instance-15min\ ← new copy for the second instance
All configuration, logs, and journal data are stored locally per folder. The two instances are completely isolated from each other.
Step 2 — Configure the second instance for a different port
Open the settings in the second instance. Change the port to anything other than the one your first instance uses. If your first instance uses port 8080, set the second to 8081 (or any unused port on your machine).
This prevents the two instances from colliding when both are running at the same time.
Step 3 — Select BTC 15-Min market in the second instance
In the second instance's settings, change the target market from BTC 5-minute to BTC 15-minute.
Leave the first instance on BTC 5-minute. Each instance now targets a different market.
Step 4 — Configure strategies independently
Each instance has its own strategy configuration. You can:
- Mirror the same strategies across both instances
- Use different strategies per market — for example, Reversal Snipe on the 5-minute instance and Conviction on the 15-minute instance
- Apply different position sizes per instance to reflect your risk allocation per market
The instances do not share state, so changes in one do not affect the other.
Step 5 — Start both instances
Launch each instance independently. Both will run in parallel, each watching its own market, executing its own trades, and writing to its own journal.
Same Account or Separate Accounts?
Both options work.
Same Polymarket account: Both instances trade from the same wallet. Position sizing across both instances draws from the same balance. Keep this in mind when configuring per-trade amounts — the combined exposure of both instances at once is what matters for risk management.
Separate Polymarket accounts: Each instance has its own wallet and balance. Capital is fully isolated between markets. This is the cleaner setup if you want independent P&L tracking per market and want to manage risk per account rather than across the combined balance.
Active Hours: Coordinating the Two Instances
Since both instances support active hours and active days scheduling, you can coordinate them precisely.
Example configuration:
- Instance 1 (5-min): active 08:00–22:00 UTC, all days
- Instance 2 (15-min): active 13:00–17:00 UTC (London/NY overlap only), Monday–Friday
Or run them both on the same schedule. The choice depends on what your journal data shows about each market's strongest sessions.
Independent Journals
Each instance writes its own journal. When reviewing performance, you can compare the 5-minute journal against the 15-minute journal to see which market is generating stronger edge under your configuration.
This makes it straightforward to adjust — if the 15-minute instance is underperforming, you tune or disable it without affecting your primary 5-minute setup at all.
Summary
| Instance 1 | Instance 2 | |
|---|---|---|
| Market | BTC 5-minute | BTC 15-minute |
| Windows/day | ~288 | ~96 |
| Port | 8080 (default) | 8081 (or any free port) |
| Account | Same or separate | Same or separate |
| Journal | Independent | Independent |
| Strategies | Configured independently | Configured independently |
Two instances. Two markets. ~384 total windows per day. Same machine, minimal overhead.
Ready to automate your Polymarket edge? PolySnipe Bot is the purpose-built Polymarket crypto sniper bot for BTC 5-minute and 15-minute prediction markets. One-time $49 � no subscriptions, full source code included.