Critical floating-point precision drift in Polymarket SDK order placement (v2 market/limit orders)

[iambecause]

While using the Polymarket Python SDK (py_clob_client_v2), I observed a persistent floating-point precision issue when building and submitting market and limit orders.

Even when explicitly setting a clean input price such as:

0.936

the SDK internally transforms it into values such as:

0.936000936000936

Then i get this error the tick for this market is "0.001" btw so 0.936 fits perfectly.

STEPS TO REPRODUCE:

resp = client.create_and_post_market_order(
order_args=MarketOrderArgs(
token_id=token,
side=BUY,
amount = 2,
price= 0.936

),

options=PartialCreateOrderOptions(
tick_size="0.001",neg_risk=False),
order_type=OrderType.GTC

)

print(resp)

Edit : it seems an other user got same error as me (#59)

[iambecause]

Wait why do you open the same Commit?

Becausde the isssue is still not fixed . I can't trade on live markets even after your fix I get 0.936000936000936

[iambecause]

Wait why do you open the same Commit?

Becausde the isssue is still not fixed . I can't trade on live markets even after your fix I get 0.936000936000936

[Danielkis97]

Solved

The server validates the implied price from the final encoded maker/taker amounts. For amount=2 and price=0.936, the previous logic could encode makerAmount=2000000 and takerAmount=2136750, which reconstructs to 0.936000936000936.

I updated the PR so market order amounts are now derived from the reduced tick-price fraction. For 0.936 with 0.001 tick size, this uses 117/125 and encodes makerAmount=1999998, takerAmount=2136750, preserving an exact implied price of 0.936.

[Danielkis97]

PR 60