PolymarketThat's a new one:
That's a new one:
cesare参与话题 1消息总数 17
该用户的聊天记录定位。
聊天记录
共 17 条，显示第 1-17 条seems a transient issue, still experiencing it? loads fine my end
seems a transient issue, still experiencing it? loads fine my end
There's a whole cluster of open GitHub
There's a whole cluster of open GitHub
Anyone else having issues after
Anyone else having issues after
@Cesare | Polymarket thanks for fixing
@Cesare | Polymarket thanks for fixing
or will it remain the same at all times
or will it remain the same at all times
Hey everyone, sorry for the disruption here. We should have handled the communication and rollout around this change better. We appreciate everyone who flagged it quickly. The remaining SDKs have now been updated to handle the new tick size behavior. Please update to the relevant version depending on what you are using: Clob Client v2 - TypeScript: https://www.npmjs.com/package/@polymarket/clob-client-v2/v/1.0.8 - Python: https://pypi.org/project/py-clob-client-v2/1.0.2/ Unified SDKs - TypeScript: https://www.npmjs.com/package/@polymarket/client/v/0.1.0-beta.11 - Python: https://pypi.org/project/polymarket-client/0.1.0-beta.12 Updated docs: https://docs.polymarket.com/trading/orders/overview#tick-sizes
Hey everyone, sorry for the disruption here. We should have handled the communication and rollout around this change better. We appreciate everyone who flagged it quickly. The remaining SDKs have now been updated to handle the new tick size behavior. Please update to the relevant version depending on what you are using: Clob Client v2 - TypeScript: https://www.npmjs.com/package/@polymarket/clob-client-v2/v/1.0.8 - Python: https://pypi.org/project/py-clob-client-v2/1.0.2/ Unified SDKs - TypeScript: https://www.npmjs.com/package/@polymarket/client/v/0.1.0-beta.11 - Python: https://pypi.org/project/polymarket-client/0.1.0-beta.12 Updated docs: https://docs.polymarket.com/trading/orders/overview#tick-sizes
What does DepositWalletBeacon do? I
What does DepositWalletBeacon do? I
hey <@369677279170658324> , will get a new build out today to support this. Sorry for the confusion, the release timing wasn't right.
hey <@369677279170658324> , will get a new build out today to support this. Sorry for the confusion, the release timing wasn't right.
u split with pUSD in the Deposit Wallet
u split with pUSD in the Deposit Wallet
not out of the box if I understand what you meant, mind expanding to make sure we are thinking the same thing?
not out of the box if I understand what you meant, mind expanding to make sure we are thinking the same thing?
Hi, stuck on deposit-wallet (POLY_1271
Hi, stuck on deposit-wallet (POLY_1271
Hey <@1280880548897882136> we had a report of an issue in this area which was addressed with yesterday release: https://github.com/Polymarket/py-sdk/issues/107#issuecomment-4731798730
Hey <@1280880548897882136> we had a report of an issue in this area which was addressed with yesterday release: https://github.com/Polymarket/py-sdk/issues/107#issuecomment-4731798730
see the Start Quoting > API Tab: https://docs.polymarket.com/market-makers/combos#api-2 Signature Type (like in CLOB) depends on the smart wallet you have: Poly Proxy, Safe Proxy, or more recent Deposit Wallet.
see the Start Quoting > API Tab: https://docs.polymarket.com/market-makers/combos#api-2 Signature Type (like in CLOB) depends on the smart wallet you have: Poly Proxy, Safe Proxy, or more recent Deposit Wallet.
Hey team @Danzu | Polymarket @Cesare
Hey team @Danzu | Polymarket @Cesare
oh wwait there is no python
oh wwait there is no python
get_balance_allowance() is not the right API for detecting fills. That endpoint is for account balance/approval state. For `COLLATERAL`, `balance` is your collateral balance and `allowances` are the allowances for the exchange/spender contracts. For `CONDITIONAL`, `balance` is the wallet balance for the specific `token_id`, but the allowances are still approvals for contracts, not token balances. It should not be used as the source of truth for “how much of this order filled”. It can also involve cached balance/allowance state. To reliably detect fills, use the order/trade data instead: - call `getOrder(orderId)` / open-order lookup while the order exists and inspect `size_matched` - call `getTrades(...)` filtered by market/token/time and inspect the returned trades / maker orders for your order id - treat `cancelAllOrders()` as canceling the remaining live quantity only; it does not mean no fill happened before the cancel/expiration landed So a partial fill showing up even though balance allowance looked like `0` is consistent with using the wrong endpoint for fill detection.
get_balance_allowance() is not the right API for detecting fills. That endpoint is for account balance/approval state. For `COLLATERAL`, `balance` is your collateral balance and `allowances` are the allowances for the exchange/spender contracts. For `CONDITIONAL`, `balance` is the wallet balance for the specific `token_id`, but the allowances are still approvals for contracts, not token balances. It should not be used as the source of truth for “how much of this order filled”. It can also involve cached balance/allowance state. To reliably detect fills, use the order/trade data instead: - call `getOrder(orderId)` / open-order lookup while the order exists and inspect `size_matched` - call `getTrades(...)` filtered by market/token/time and inspect the returned trades / maker orders for your order id - treat `cancelAllOrders()` as canceling the remaining live quantity only; it does not mean no fill happened before the cancel/expiration landed So a partial fill showing up even though balance allowance looked like `0` is consistent with using the wrong endpoint for fill detection.