Bithumb - Unexpected sudden order matched during trade
Closed this issue · 0 comments
sjanel commented
We need to better catch matched information about Bithumb, it's already done but it seems not sufficient:
[2023-05-12 08:55:51.248] [info] Considering Bithumb order as closed as no data received from them
[2023-05-12 08:55:51.248] [info] POST https://api.bithumb.com/info/order_detail?endpoint=%2Finfo%2Forder_detail&order_currency=XRP&payment_currency=KRW&order_id=CXXXXXX
[2023-05-12 08:55:51.654] [info] Trade XXXXX XRP -> KRW on bithumb_xxxx requested
[2023-05-12 08:55:51.654] [info] Step 1/1 - trade XXXXX XRP into KRW
[2023-05-12 08:55:51.654] [info] GET https://api.bithumb.com/public/orderbook/XRP_KRW?count=1
[2023-05-12 08:55:52.083] [info] Retrieved 1 markets (+ orderbooks) from Bithumb
[2023-05-12 08:55:52.083] [info] POST https://api.bithumb.com/trade/place?endpoint=%2Ftrade%2Fplace&order_currency=XRP&payment_currency=KRW&type=ask&price=XXXX&units=XXXXX
terminate called after throwing an instance of 'cct::exception'
[2023-05-12 08:55:52.464] [error] Full Bithumb json error: '{"message":"주문량이 사용가능 XRP을 초과하였습니다.","status":"5600"}'
what(): Bithumb error 5600
Aborted
주문량이 사용가능 XRP을 초과하였습니다. means that there is not enough XRP volume available in the account-> order has been matched.