Replying to @mausbot_
Please fix iOS where it doesn’t update the chats - you can have chats on the computer and then when you open the app on iOS, it never loads the computer convo
36
Replying to @sanreds_
Can connect via other computers to the main server right? I.e. desktop app on MacBook connecting to Mac mini server
26
Replying to @sanreds_
Any iOS app? Does it support running one one server and desktop apps on other computers accessing the server
8
Replying to @aryanvij02
Are we able to host it on our own always on computer and access it via app/desktop app on other devices?
1
1
1,447
Replying to @nvandewetering
Switched to API usage when I maxed out the ultra, burning $150+ a day doing barely anything 🤮
12
Replying to @Abomination81 @AliInMotion
Amazing - if you don’t end up doing a platform soon are you going to make posts about the copy strats?
1
61
Replying to @Abomination81
How quickly are you getting the orders seen from when they are matched?
1
1
300
🚨 If you're copy trading Polymarket wallets with third-party tools… you have zero control.
Every millisecond is now life or death.
You're literally trying to slip into a move that someone else already saw, executed, and got filled on.
Most people realize this and quit, thinking copy trading doesn't work.
They're wrong.
The edge is extremely tight. For most wallets, you need sub-1ms hot path execution and rock-solid low latency infrastructure just to maintain a decent risk/reward.
We’re hitting same-block entries on almost every trade and still profitably copying 5-minute bots… but depending on liquidity, our fills range from +1¢ to +10¢+ worse — in the same block.
Now imagine what the guys who are 1-2 blocks behind are getting.
Moral of the story:
Stop renting someone else’s slow infrastructure.
Build your own low-latency setup first. That 10ms you shave off can easily be the difference between compounding profits and slowly bleeding out.
The real game isn’t just finding the right wallet.
It’s having the speed to actually follow it.
136
PolySocket.dev retweeted
Trading is currently degraded. We've identified the cause and are deploying a fix.
Live updates: status.polymarket.com/
Replying to @dextrabot @Polymarket
Is that a post close sniper?
If not, risssssskkkkky :| even if it goes 2 weeks with no issue, the 1 time it does it wipes everything
1
1
94
⚡ Latency hack for Polymarket bot builders:
If you’re a halfway decent Polymarket bot maker, you already know the basics:
don’t sign orders in the hot path.
When it’s execution time, your orders should already be signed and ready to fire.
But the harder problem is how you pre-sign.
Because once you start covering a lot of markets, outcomes, price levels, sizes, and retry depths…
the number of orders you need to prepare can explode.
50 markets
× 2 outcomes
× 100 price levels
× 50 possible sizes
× multiple retry levels
Suddenly your bot is trying to keep hundreds of thousands, or even millions, of signed orders ready.
That sounds good in theory.
In practice, it can quietly become the bottleneck.
Your pre-sign refresh takes too long.
Your cache goes stale.
Your bot stalls while rebuilding.
The trade arrives while you’re busy preparing for the trade.
And in copy trading, that’s brutal.
A few hundred milliseconds can be the difference between:
- getting the same fill as the source
- chasing a worse price
- or not executing at all
A better pattern is to keep full price coverage, but compress the sizing dimension.
Instead of pre-signing every exact dollar size:
$1, $2, $3, $4, $5 … $70
you pre-sign composable chunks:
$1, $2, $4, $8, $16, $32, $64
Then when you need $37, you use:
$32 + $4 + $1
Need $50?
$32 + $16 + $2
So your bot still has flexible sizing, but it doesn’t need to pre-sign every possible size at every possible price.
The hot path becomes simple:
1. source trade detected
2. choose the already-signed chunks
3. submit them as a batch
No signing.
No grid rebuild.
No expensive work when the opportunity appears.
One important caveat:
each child order still has to be valid on its own.
If a tiny chunk creates an order below the market’s minimum size, the whole batch can fail.
So the chunking logic needs to be minimum-order-aware.
But if you do it right, you get the best of both worlds:
wide price coverage, flexible sizing, and a much smaller pre-sign workload.
That means faster refreshes, less stalling, fewer stale orders, and a better chance of copying before the book moves.
If you want more execution tips like this, and you’re building Polymarket copy bots, join the Polysocket community below.
We’re putting together traders/builders who care about faster wallet detection, cleaner copy execution, and fewer missed fills.
discord.gg/kpze6ZVqk6
Replying to @fuchexcrypto @poly_data
Set limits, ceilings, floors, scale percentages, can also do things like wait for the wallet you’re copying to be profitable for X Hours before starting, etc.
1
10

