Thanks all for following. We are cooking the best tool for the trading strategy of prediction markets.
If you are looking for a easy tool to help you
- execute MM strategy
- kill all 15 mins markets
- trade and get airdrops
Stay tuned. Our product is on the way.
Leave a comment let us know what you need.
Polymarket SDK v0.4.0 is officially released 🎉
Thanks for all the support — we’ve reached 580 stars already!
https://t.co/jcNbpdyEat
In this release, we also implemented a 15-minute market strategy. Feel free to use it if you’re interested.
Strategy Overview (15-Minute Markets)
The core idea is simple:
Leg 1 (Entry):
Detect a sharp crash (e.g. 30% drop within 3 seconds) and buy immediately.
Leg 2 (Exit):
When the price reverts to a more rational level, sell to lock in profit.
Leg 1 Parameters
slidingWindowMs: 3000, // 3 seconds
dipThreshold: 0.3 // 30% dip
With these settings, if the market drops 30% within 3 seconds, the bot will buy automatically — regardless of YES or NO.
Leg 2 Parameter
sumTarget: 0.95
This means you can spend 0.95 USDC to obtain both UP and DOWN shares (worth 1 USDC).
Risk Control
We also added a stop-loss mechanism:
leg2TimeoutSeconds
For example, if set to 100, and Leg 2 hasn’t executed after 100 seconds, the bot will automatically sell the Leg 1 position to prevent it from going to zero.
Capital Efficiency Improvements
Auto-merge support:
After completing Leg 2, positions are automatically merged back into USDC.e, significantly improving capital efficiency.
Auto-rollover:
After each 15-minute market ends, the bot automatically enters the next market.
Any remaining positions will be redeemed once the market allows redemption.
So in practice, you can just let it run — though parameter tuning matters a lot.
Different parameters produce very different results. We strongly recommend avoiding overly aggressive settings. With fees now applied to 15-minute markets, high-frequency strategies are even less suitable.
Large Orders
If you’re trading large sizes, you can use splitOrders, which automatically splits a large order into multiple smaller ones.
Architecture Updates
Added a Binance service
Fixed the issue where only YES/NO was returned in previous versions
More details are available in the codebase.
We also welcome everyone to follow our project @catalystdotfun — our product will be released step by step very soon 🚀
🚀 Polymarket SDK v0.3.0 is out!
Thanks for all the support — the repo has reached 352 stars ⭐️
https://t.co/jcNbpdyEat
@Polymarket
You can now implement copy trading in just 10 lines of code.
Our new architecture:
Tomorrow I’ll go deeper into what’s new in v0.3.0 — beyond the new Smart Money Service, there are several other important updates.
That’s all for today — getting some rest now. Good night 😴
If you’re also interested in arbitrage, check my previous tweet — it includes a complete implementation you can directly reuse.
Yesterday I open-sourced polymarket-sdk for @Polymarket
https://t.co/jcNbpdyEat
Thanks for the support — the repo already has 223 stars and 63 forks ❤️
Today, we shipped a major update.
The SDK now covers almost everything you need to build on Polymarket:
🔄 Real-time arbitrage detection (WebSocket-based)
📊 Smart money analysis — track top traders and strategies
💱 Trading integration (GTC / GTD / FOK / FAK)
🔐 On-chain ops: split, merge, redeem CTF tokens
🌉 Cross-chain deposits from Ethereum, Solana, Bitcoin
💰 DEX swaps on Polygon (QuickSwap V3)
📈 Market analytics: K-lines, signals, volume
Today’s highlight: ArbitrageService 👀
We now officially support Polymarket arbitrage.
The idea is simple:
- If buying a YES+NO pair costs < 1 USDC, buy both and redeem on-chain
- If selling a YES+NO pair yields > 1 USDC, mint a pair for 1 USDC and sell
The hard part is execution.
In real markets, arbitrage windows are short —
there’s often no time to do on-chain actions when profit appears.
So the ArbitrageService uses dynamic position management:
- Maintain USDC ↔ YES/NO positions
- Keep USDC ratio between 20%–80%
- Always ready to buy or sell immediately when opportunities show up
Handling partial fills
Partial fills are inevitable and can leave you with unbalanced YES/NO positions.
The service automatically:
- Sells the excess side
- Keeps YES and NO close to 1:1
- Exposes a settlePosition helper to clean up exposure anytime
Full arbitrage theory + implementation details are documented in the repo.
GitHub: https://t.co/jcNbpdyEat
Arbitrage docs: https://t.co/gBiKosFx6W
Our Project: @catalystdotfun
Open-source, and happy hacking