Skip to content
This repository has been archived by the owner on Aug 12, 2024. It is now read-only.

Potential double spend (two orders with same clientOid) #468

Open
toliankir opened this issue Jun 20, 2023 · 2 comments
Open

Potential double spend (two orders with same clientOid) #468

toliankir opened this issue Jun 20, 2023 · 2 comments

Comments

@toliankir
Copy link

toliankir commented Jun 20, 2023

Potential double spend (two orders with same clientOid)
I tried to create orders using POST https://api.kucoin.com/api/v1/orders endpoint. According to documentation, clientOid - must be a unique id (e.g UUID).
But the API allows me to create several orders with the same clientOid = 8f26c401-39c4-47d0-9149-a9e5066168ed.

Data:
Used API key: 6485df87118c4d0001562bc2
Server side order ids:

  • 64917b91986f560001551e4b
  • 64917dff7527e300014cb1db
  • 64919a99de8382000167eea5
  • 6491bb6d4cd56900012c45a2
  • 6491bb80ebe9ad0001a917d2

Client OID: 8f26c401-39c4-47d0-9149-a9e5066168ed

@BabyDragon003
Copy link

Hello.
I am a Kucoin API user.
Excuse me, I send message because I have one problem when use Kucoin API.
How to create clientOid value in postOrder function?
Thank you.

@mbellmbell
Copy link

I think only enforced on active orders. Doesn't enforce against completed/cancelled orders.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants