do I need to update py_clob_client or something? (im posting orders 1c 2c 3c with no decimals) but getting error
do I need to update py_clob_client or something? (im posting orders 1c 2c 3c with no decimals) but getting error
2026-07-11 · Polymarket · 5 条相关讨论
do I need to update py_clob_client or something? (im posting orders 1c 2c 3c with no decimals) but getting error
do I need to update py_clob_client or something? (im posting orders 1c 2c 3c with no decimals) but getting error
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.
Just use eggplant sdk
Just use eggplant sdk
"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"
Yes that’s only because it needs tx confirmation, but that’s always been the case
Yes that’s only because it needs tx confirmation, but that’s always been the case