bogdanteodoru/py3cw

3c.exchange ignoring paper orders

riodda opened this issue · 15 comments

Hi, from the last 10 days 3c.exchange is ignoring totally all the paper orders, anybody else is having this issue ? Thanks.

@riodda what do you mean "ignoring" ? Do you get an OK response from 3commas or any error whatsoever?

No errors, it simply ignores the orders while i get corretly all the prices.

@riodda I'll link this up to the official GitHub because it seems to be a problem from their side.

No I actually receive and error:

Order Result {'error': 'signature_invalid', 'error_description': 'Provided signature is invalid'}

But my api hasn't changed and my code hasn't changed.
i'm using 3c.exchange i read somewhare that the endpoint url has changed for 3c.exchange from 3commas.io it might be the issue ? How is possilbe to set the endpoint ?
The strange thing is that the market data is downloaded correctly.

Hmm... seems that the signature is invalid. Can you re-generate the API keys and try to see if it works with the new ones?

I have re generated api but i still have the same error.
my order function is

`def close_all_deals(_bot_id):
_error,_data = p3cw.request(
entity='bots',
action='panic_sell_all_deals',
action_id=_bot_id,
payload={ 'bot_id': _bot_id})
if _error == None:
return True
else:
return False

def start_deal(_bot_id):
_error,_data = p3cw.request(
entity='bots',
action='start_new_deal',
action_id=_bot_id,
payload={ 'bot_id': _bot_id})
if _error == None:
return _data
else:
return _error`

What about the end url ? Should be different now between 3c.exchange and 3commas.io ?

@riodda, the base endpoint is: https://api.3commas.io/public/api

Wasn't replaced for 3c.exchange ?

This what I found on their Github so not sure.

@riodda, @MoroZvlg confirmed that in fact, 3c.exchange endpoint ignores paper trades.

What?
you have an "invalid_signature" error. How it's related to "ignores paper trades".
As I understand from current issue "ivalid_signature" was a real problem

Signature error is only for trades, with the same api you can use all the rest of the api.

@riodda I have deployed a new version (0.0.15). Please update to that and see if you encounter any other issues. The "invalid signature" problem should be fixed. Thanks.