hello, is there something off about Market Websocket Channel, bcs i am getting this for 15 min btc up or down:
{
"market": "0x8d61b716f3f25c313eef23c44213bffb25e791ac4518ee852e6e8c404027f137",
"price_changes": [
{
"asset_id": "80555920378668285771235020613402482558140162486652400891327257746328320584887",
"price": "0.01",
"size": "7060.92",
"side": "BUY",
"hash": "c81ff7f2909e7fa75205503d13110b19556349d4",
"best_bid": "0.57",
"best_ask": "0.58"
},
{
"asset_id": "100994388721982042574286031485107460334747507409212950709997870952251894498408",
"price": "0.99",
"size": "7060.92",
"side": "SELL",
"hash": "856217046b13c4a05eced47752afdca284234284",
"best_bid": "0.42",
"best_ask": "0.43"
}
],
"timestamp": "1781346515177",
"event_type": "price_change"
}
hello, is there something off about Market Websocket Channel, bcs i am getting this for 15 min btc up or down:
{
"market": "0x8d61b716f3f25c313eef23c44213bffb25e791ac4518ee852e6e8c404027f137",
"price_changes": [
{
"asset_id": "80555920378668285771235020613402482558140162486652400891327257746328320584887",
"price": "0.01",
"size": "7060.92",
"side": "BUY",
"hash": "c81ff7f2909e7fa75205503d13110b19556349d4",
"best_bid": "0.57",
"best_ask": "0.58"
},
{
"asset_id": "100994388721982042574286031485107460334747507409212950709997870952251894498408",
"price": "0.99",
"size": "7060.92",
"side": "SELL",
"hash": "856217046b13c4a05eced47752afdca284234284",
"best_bid": "0.42",
"best_ask": "0.43"
}
],
"timestamp": "1781346515177",
"event_type": "price_change"
}
look at the price, bid and ask, they are off, is this how it should be
look at the price, bid and ask, they are off, is this how it should be
no they're not?
no they're not?
bug report: we are getting this reponse to post order, get order and cancel order requests:
error=PolyApiException message=PolyApiException[status_code=None, error_message=Request exception!]
but everytime the requests are successfully completed (order are being created or deleted)
bug report: we are getting this reponse to post order, get order and cancel order requests:
error=PolyApiException message=PolyApiException[status_code=None, error_message=Request exception!]
but everytime the requests are successfully completed (order are being created or deleted)
Trying to implement order creation with a deposit wallet / POLY_1271. Got pretty far, but now I'm getting "not enough balance / allowance: the balance is not enough -> balance: 0,", even though I moved $10 to that address: https://polygonscan.com/address/0xCFe77AB59C0c7326D287061d1d3c6e5443DE9eB9
Anyone can see what's wrong?
Trying to implement order creation with a deposit wallet / POLY_1271. Got pretty far, but now I'm getting "not enough balance / allowance: the balance is not enough -> balance: 0,", even though I moved $10 to that address: https://polygonscan.com/address/0xCFe77AB59C0c7326D287061d1d3c6e5443DE9eB9
Anyone can see what's wrong?
skill issue or polymarket broken?
It's listed in the requirements and imported at the top of polymarket_api.py:
from py_clob_client_v2.client import ClobClient
from py_clob_client_v2.clob_types import ApiCreds, OrderArgs, OrderType, BalanceAllowanceParams, AssetType
There's a known issue with this version right now — Polymarket disabled signature_type=2 (GNOSIS_SAFE) for maker orders, and the SDK has a bug falling back to signature_type=3 (POLY_1271/deposit wallet). Last I checked on June 11, it's blocked until either the SDK gets patched or Polymarket re-enables safe wallet orders.
skill issue or polymarket broken?
It's listed in the requirements and imported at the top of polymarket_api.py:
from py_clob_client_v2.client import ClobClient
from py_clob_client_v2.clob_types import ApiCreds, OrderArgs, OrderType, BalanceAllowanceParams, AssetType
There's a known issue with this version right now — Polymarket disabled signature_type=2 (GNOSIS_SAFE) for maker orders, and the SDK has a bug falling back to signature_type=3 (POLY_1271/deposit wallet). Last I checked on June 11, it's blocked until either the SDK gets patched or Polymarket re-enables safe wallet orders.
Can I get help with order placement? Getting py_clob_client_v2.exceptions.PolyApiException: PolyApiException[status_code=400, error_message={'error': 'not enough balance / allowance: the balance is not enough -> balance: 0, order amount: 1000000'}]
The wallet address is 0xCFe77AB59C0c7326D287061d1d3c6e5443DE9eB9, there is $10 on it and I confirmed that it is deployed
Can I get help with order placement? Getting py_clob_client_v2.exceptions.PolyApiException: PolyApiException[status_code=400, error_message={'error': 'not enough balance / allowance: the balance is not enough -> balance: 0, order amount: 1000000'}]
The wallet address is 0xCFe77AB59C0c7326D287061d1d3c6e5443DE9eB9, there is $10 on it and I confirmed that it is deployed
Found the fix?
Found the fix?
Hey, did anything change in the `wss://ws-live-data.polymarket.com/` `activity/trades` stream?
I now see multiple messages with the same `transactionHash`, sometimes both `BUY` and `SELL` sides of the same match.
Is this stream supposed to emit participant-side fills rather than unique executions?
Also, what is the recommended way to deduplicate these messages, and is there any field to distinguish maker/taker or limit vs marketable orders?
Hey, did anything change in the `wss://ws-live-data.polymarket.com/` `activity/trades` stream?
I now see multiple messages with the same `transactionHash`, sometimes both `BUY` and `SELL` sides of the same match.
Is this stream supposed to emit participant-side fills rather than unique executions?
Also, what is the recommended way to deduplicate these messages, and is there any field to distinguish maker/taker or limit vs marketable orders?
Hey, did anything change in the wss://ws-live-data.polymarket.com/ activity/trades stream?
I now see multiple messages with the same transactionHash, sometimes both BUY and SELL sides of the same match.
Is this stream supposed to emit participant-side fills rather than unique executions?
Also, what is the recommended way to deduplicate these messages, and is there any field to distinguish maker/taker or limit vs marketable orders?
like after June 10 smth changed
Hey, did anything change in the wss://ws-live-data.polymarket.com/ activity/trades stream?
I now see multiple messages with the same transactionHash, sometimes both BUY and SELL sides of the same match.
Is this stream supposed to emit participant-side fills rather than unique executions?
Also, what is the recommended way to deduplicate these messages, and is there any field to distinguish maker/taker or limit vs marketable orders?
like after June 10 smth changed
before in UI in activity tab I saw subsctiption to "trades" topic, but now "orders_matched" topic. This happened after 10 June?
before in UI in activity tab I saw subsctiption to "trades" topic, but now "orders_matched" topic. This happened after 10 June?
The chain link websocket that Polymarket provides; is there anyway to get every update? Like increase granularity?
The chain link websocket that Polymarket provides; is there anyway to get every update? Like increase granularity?
FIX GET_ORDER AND GET_TRADES. THEY ALWAYS RETURN NULL. FIX GET_ORDER AND GET_TRADES. THEY ALWAYS RETURN NULL. FIX GET_ORDER AND GET_TRADES. THEY ALWAYS RETURN NULL. FIX GET_ORDER AND GET_TRADES. THEY ALWAYS RETURN NULL. FIX GET_ORDER AND GET_TRADES. THEY ALWAYS RETURN NULL. FIX GET_ORDER AND GET_TRADES. THEY ALWAYS RETURN NULL. FIX GET_ORDER AND GET_TRADES. THEY ALWAYS RETURN NULL. FIX GET_ORDER AND GET_TRADES. THEY ALWAYS RETURN NULL. FIX GET_ORDER AND GET_TRADES. THEY ALWAYS RETURN NULL. FIX GET_ORDER AND GET_TRADES. THEY ALWAYS RETURN NULL. FIX GET_ORDER AND GET_TRADES. THEY ALWAYS RETURN NULL. <@624575779023355904> <@1361217824776786031>
FIX GET_ORDER AND GET_TRADES. THEY ALWAYS RETURN NULL. FIX GET_ORDER AND GET_TRADES. THEY ALWAYS RETURN NULL. FIX GET_ORDER AND GET_TRADES. THEY ALWAYS RETURN NULL. FIX GET_ORDER AND GET_TRADES. THEY ALWAYS RETURN NULL. FIX GET_ORDER AND GET_TRADES. THEY ALWAYS RETURN NULL. FIX GET_ORDER AND GET_TRADES. THEY ALWAYS RETURN NULL. FIX GET_ORDER AND GET_TRADES. THEY ALWAYS RETURN NULL. FIX GET_ORDER AND GET_TRADES. THEY ALWAYS RETURN NULL. FIX GET_ORDER AND GET_TRADES. THEY ALWAYS RETURN NULL. FIX GET_ORDER AND GET_TRADES. THEY ALWAYS RETURN NULL. FIX GET_ORDER AND GET_TRADES. THEY ALWAYS RETURN NULL. <@624575779023355904> <@1361217824776786031>
ask=50.00c attempt=3 err={"error":"order couldn't be fully filled. FOK orders are fully filled or killed.","orderID":"0x1b72dcdaa448ce4413a6144ea7617ed9f7ce8ac188f75ba4e1fbcc798e672505","status":400}
ask=50.00c attempt=3 err={"error":"order couldn't be fully filled. FOK orders are fully filled or killed.","orderID":"0x1b72dcdaa448ce4413a6144ea7617ed9f7ce8ac188f75ba4e1fbcc798e672505","status":400}
Can anyone share the formula for the `hash` field in CLOB market-channel `price_change` / `book` events — exact field list (including last trade price source), JSON key order, and hash algorithm? Reverse-engineering it for local-book verification but our recompute diverges.
Can anyone share the formula for the `hash` field in CLOB market-channel `price_change` / `book` events — exact field list (including last trade price source), JSON key order, and hash algorithm? Reverse-engineering it for local-book verification but our recompute diverges.
token spliting doesn' t work using builder api
token spliting doesn' t work using builder api
Using py-clob-client-v2. Maker orders from an older Polymarket Proxy
account (signature_type=1) work fine. But a newer/migrated account
fails with "maker address not allowed, please use the deposit wallet
flow." Switching to signature_type=3 (POLY_1271) then gives "the order
signer address has to be the address of the API KEY." Same as GitHub
issue #53 (https://github.com/Polymarket/py-clob-client-v2/issues/53). Is there a working deposit-wallet flow for new accounts,
or any solution? Thanks!
Using py-clob-client-v2. Maker orders from an older Polymarket Proxy
account (signature_type=1) work fine. But a newer/migrated account
fails with "maker address not allowed, please use the deposit wallet
flow." Switching to signature_type=3 (POLY_1271) then gives "the order
signer address has to be the address of the API KEY." Same as GitHub
issue #53 (https://github.com/Polymarket/py-clob-client-v2/issues/53). Is there a working deposit-wallet flow for new accounts,
or any solution? Thanks!
Using py-clob-client-v2. Maker orders from an older Polymarket Proxy
account (signature_type=1) work fine. But a newer/migrated account
fails with "maker address not allowed, please use the deposit wallet
flow." Switching to signature_type=3 (POLY_1271) then gives "the order
signer address has to be the address of the API KEY." Same as GitHub
issue #53 (https://github.com/Polymarket/py-clob-client-v2/issues/53). Is there a working deposit-wallet flow for new accounts,
or any solution? Thanks!
Using py-clob-client-v2. Maker orders from an older Polymarket Proxy
account (signature_type=1) work fine. But a newer/migrated account
fails with "maker address not allowed, please use the deposit wallet
flow." Switching to signature_type=3 (POLY_1271) then gives "the order
signer address has to be the address of the API KEY." Same as GitHub
issue #53 (https://github.com/Polymarket/py-clob-client-v2/issues/53). Is there a working deposit-wallet flow for new accounts,
or any solution? Thanks!
Using py-clob-client-v2. Maker orders from an older Polymarket Proxy
account (signature_type=1) work fine. But a newer/migrated account
fails with "maker address not allowed, please use the deposit wallet
flow." Switching to signature_type=3 (POLY_1271) then gives "the order
signer address has to be the address of the API KEY." Same as GitHub
issue #53 (https://github.com/Polymarket/py-clob-client-v2/issues/53). Is there a working deposit-wallet flow for new accounts,
or any solution? Thanks!
Using py-clob-client-v2. Maker orders from an older Polymarket Proxy
account (signature_type=1) work fine. But a newer/migrated account
fails with "maker address not allowed, please use the deposit wallet
flow." Switching to signature_type=3 (POLY_1271) then gives "the order
signer address has to be the address of the API KEY." Same as GitHub
issue #53 (https://github.com/Polymarket/py-clob-client-v2/issues/53). Is there a working deposit-wallet flow for new accounts,
or any solution? Thanks!
Using py-clob-client-v2. Maker orders from an older Polymarket Proxy
account (signature_type=1) work fine. But a newer/migrated account
fails with "maker address not allowed, please use the deposit wallet
flow." Switching to signature_type=3 (POLY_1271) then gives "the order
signer address has to be the address of the API KEY." Same as GitHub
issue #53 (https://github.com/Polymarket/py-clob-client-v2/issues/53). Is there a working deposit-wallet flow for new accounts,
or any solution? Thanks!
Using py-clob-client-v2. Maker orders from an older Polymarket Proxy
account (signature_type=1) work fine. But a newer/migrated account
fails with "maker address not allowed, please use the deposit wallet
flow." Switching to signature_type=3 (POLY_1271) then gives "the order
signer address has to be the address of the API KEY." Same as GitHub
issue #53 (https://github.com/Polymarket/py-clob-client-v2/issues/53). Is there a working deposit-wallet flow for new accounts,
or any solution? Thanks!