该用户的聊天记录定位。
Based on what?
Based on what?
Polymarket cannot operate as a charity indefinitely
Polymarket cannot operate as a charity indefinitely
Fees are the main way that Polymarket makes a return on its platform
Fees are the main way that Polymarket makes a return on its platform
Almost every company in the world exists to create profit and provide an ROI for those who funded the startup
Almost every company in the world exists to create profit and provide an ROI for those who funded the startup
Up until like 48~ hours ago, numbers were way better for me
Up until like 48~ hours ago, numbers were way better for me
These numbers are on a slow book
These numbers are on a slow book
Are the live crypto markets just that dogshit?
Are the live crypto markets just that dogshit?
🤨
🤨
Polymarket US app, or Polymarket international?
Polymarket US app, or Polymarket international?
I'm not asking Claude but I bet someone who's dead has been appointed to a senior role in the US government
I'm not asking Claude but I bet someone who's dead has been appointed to a senior role in the US government
So it's not even a rules cuck
So it's not even a rules cuck
Yeah maybe it's already allowed
Yeah maybe it's already allowed
They might change the law and allow dead people to be senate majority leaders
They might change the law and allow dead people to be senate majority leaders
Why the hell doesn't the URL take you to the off endpoint
Why the hell doesn't the URL take you to the off endpoint
Style control is "on" by default with their link is why
Style control is "on" by default with their link is why
Why doesn't gpt-5.6-sol-xhigh qualify?
Why doesn't gpt-5.6-sol-xhigh qualify?
Wait, what?
Wait, what?
https://klipy.com/gifs/soccer-england-6
https://klipy.com/gifs/soccer-england-6
REFUND
REFUND
+1k
+1k
ACL probably gone
ACL probably gone
Prayge for the cage
Prayge for the cage
<a:praygeBlessed:856940595741851699>
<a:praygeBlessed:856940595741851699>
ppv dot to is offline
ppv dot to is offline
Where do I stream the fight
Where do I stream the fight
I'm observing intermittent live data now that doesn't seem possible (available orders at a strike price that heavily crosses the book) and I'd like to be able to diagnose what the hell is happening
I'm observing intermittent live data now that doesn't seem possible (available orders at a strike price that heavily crosses the book) and I'd like to be able to diagnose what the hell is happening
Is there a data source that would allow me to check all WS pushes from a specific event?
Is there a data source that would allow me to check all WS pushes from a specific event?
Sure, I'm saying that if you press an LLM on optimization, it can optimize
Sure, I'm saying that if you press an LLM on optimization, it can optimize
How many Rs in strawberry
How many Rs in strawberry
Well, what part is the partially untrue bit? 😆
Well, what part is the partially untrue bit? 😆
<@369314624203653121>
<@369314624203653121>
Well, you can presign like $10,000 99c and fire that out, you can also have a presign for a range of strikes/prices
Well, you can presign like $10,000 99c and fire that out, you can also have a presign for a range of strikes/prices
I'm able to presign "Buy token X" and then just add the strike price/quantity in after the fact without having to compute anything?
I'm able to presign "Buy token X" and then just add the strike price/quantity in after the fact without having to compute anything?
My understanding was that you can presign most of the order, but work still needs to be done depending on what strike price/share quantity you're after. Is that not true?
My understanding was that you can presign most of the order, but work still needs to be done depending on what strike price/share quantity you're after. Is that not true?
A generic vibe coded signing procedure is like 20ms, Fable has optimized mine to 0.3ms
A generic vibe coded signing procedure is like 20ms, Fable has optimized mine to 0.3ms
https://polymarket.com/event/will-trump-praise-allah-again-by-july-31-20260709152510180/will-trump-praise-allah-again-by-july-31-20260709152510180 You missed praise be to allah
https://polymarket.com/event/will-trump-praise-allah-again-by-july-31-20260709152510180/will-trump-praise-allah-again-by-july-31-20260709152510180 You missed praise be to allah
I'd say 80% of the time it's good and you can click on the bin as the poster if you want to get rid of it.
I'd say 80% of the time it's good and you can click on the bin as the poster if you want to get rid of it.
Does any signature type have an inherent advantage over the others, or are they all equal?
Does any signature type have an inherent advantage over the others, or are they all equal?
Seems so
Seems so
"5:47 AM]Cesare | Polymarket: the 0.0025 tick size is supported in 1.0.2 yes"
"5:47 AM]Cesare | Polymarket: the 0.0025 tick size is supported in 1.0.2 yes"
fix — READY, asking for deploy - Root cause verified in the installed SDK (py_clob_client_v2/order_builder/builder.py:141): ROUNDING_CONFIG[options.tick_size] KeyErrors on "0.0025" — the table stops at 0.0001-style keys; the TickSize Literal is typing-only, no other runtime gate. - The patch (19 lines added, nothing removed, compile-checked, in wc-main which hash-matches the deployed cf981631): a. Module-level: seed ROUNDING_CONFIG["0.0025"] with the "0.0001" RoundConfig — exact, since every 0.0025 multiple fits in 4 decimals (and our limit prices are 2-decimal anyway, valid on every grid). b. Generic runtime guard _ensure_rounding() on every _token_meta resolve (sub-µs dict check, both cache-hit and fresh-fetch paths) — any future unknown tick gets mapped to the 4dp config with a warning, so this class of SIGN_FAIL can never recur. - All-markets check: they did NOT switch wholesale. Of 25,623 cached tokens: 22,636 @ 0.01, 2,955 @ 0.001, only 32 @ 0.0025. And stale-cache scenarios are benign for us — 2-decimal prices are valid on all these grids.
fix — READY, asking for deploy - Root cause verified in the installed SDK (py_clob_client_v2/order_builder/builder.py:141): ROUNDING_CONFIG[options.tick_size] KeyErrors on "0.0025" — the table stops at 0.0001-style keys; the TickSize Literal is typing-only, no other runtime gate. - The patch (19 lines added, nothing removed, compile-checked, in wc-main which hash-matches the deployed cf981631): a. Module-level: seed ROUNDING_CONFIG["0.0025"] with the "0.0001" RoundConfig — exact, since every 0.0025 multiple fits in 4 decimals (and our limit prices are 2-decimal anyway, valid on every grid). b. Generic runtime guard _ensure_rounding() on every _token_meta resolve (sub-µs dict check, both cache-hit and fresh-fetch paths) — any future unknown tick gets mapped to the 4dp config with a warning, so this class of SIGN_FAIL can never recur. - All-markets check: they did NOT switch wholesale. Of 25,623 cached tokens: 22,636 @ 0.01, 2,955 @ 0.001, only 32 @ 0.0025. And stale-cache scenarios are benign for us — 2-decimal prices are valid on all these grids.
Oh you mean legit liquidity farmers, not Polymarket's in-house provision when a market kicks off
Oh you mean legit liquidity farmers, not Polymarket's in-house provision when a market kicks off
99c 400 shares 98c 200 shares 97c 100 shares 96c 50 shares
99c 400 shares 98c 200 shares 97c 100 shares 96c 50 shares
Just a stready stream down to -$500k
Just a stready stream down to -$500k
Those accounts have crazy graphs
Those accounts have crazy graphs
Did a deeper audit: it seems like the trade confirmations are very delayed, but matching is "normal"?
Did a deeper audit: it seems like the trade confirmations are very delayed, but matching is "normal"?
What's annoying: I switched my setup to a brand new server with more capacity from the same location, but I did this during the last downtime window - now I'm getting absolutely awful CLOB matching times
What's annoying: I switched my setup to a brand new server with more capacity from the same location, but I did this during the last downtime window - now I'm getting absolutely awful CLOB matching times
I have terrible latency right now - just me?
I have terrible latency right now - just me?
If he just held the top for a little longer it's 1:1
If he just held the top for a little longer it's 1:1
Burj Khalifa
Burj Khalifa