聊天记录
共 8 条,显示第 1-8 条
Is there a server-side fix planned so signature_type=3 validates the API key against the EOA that controls the deposit wallet?
Is there a server-side fix planned so signature_type=3 validates the API key against the EOA that controls the deposit wallet?
Is there a server-side fix planned so signature_type=3 validates the API key against the EOA that controls the deposit wallet? GitHub issues #64, #70, #71, #344
Is there a server-side fix planned so signature_type=3 validates the API key against the EOA that controls the deposit wallet? GitHub issues #64, #70, #71, #344
Thanks~ Appreciate it. still didnt work - my bot is not placing live trades error still exists
Thanks~ Appreciate it. still didnt work - my bot is not placing live trades error still exists
Following up this question. thanks
Following up this question. thanks
I tried looking it up here but didn't really find a solution as there were multiple messages overlapping <:Bidensmile:1040247925420339251>
I tried looking it up here but didn't really find a solution as there were multiple messages overlapping <:Bidensmile:1040247925420339251>
Yes thank you
Yes thank you
I'm a developer trying to use the Python CLOB API with a deposit wallet account (signature_type=3). I'm getting 'the order signer address has to be the address of the API KEY' on every order. This matches GitHub issues #64, #70, #71 on py-clob-client-v2. Is there a working workaround or timeline for a fix?
I'm a developer trying to use the Python CLOB API with a deposit wallet account (signature_type=3). I'm getting 'the order signer address has to be the address of the API KEY' on every order. This matches GitHub issues #64, #70, #71 on py-clob-client-v2. Is there a working workaround or timeline for a fix?
I'm a developer trying to use the Python CLOB API with a deposit wallet account (signature_type=3). I'm getting 'the order signer address has to be the address of the API KEY' on every order. This matches GitHub issues #64, #70, #71 on py-clob-client-v2. Is there a working workaround or timeline for a fix?
I'm a developer trying to use the Python CLOB API with a deposit wallet account (signature_type=3). I'm getting 'the order signer address has to be the address of the API KEY' on every order. This matches GitHub issues #64, #70, #71 on py-clob-client-v2. Is there a working workaround or timeline for a fix?