Lasterie

Thanks! I ran into another issue though. Could it be correct that Gdax requires the input for "size" to have a maximum number of decimals? I have orders placed via...

That makes sense, but I place an order > 0.01: ``` Wednesday, Aug 09, 2017 at 03:56:07 PM UTC || PLACING ORDER { "size": "0.015", "type": "market", "side": "sell", "product_id":...

Yes, I checked but the orders are not there. There is one: an order of 0.01000000. It is placed by the vickitrix script. But by hard setting the "size" to...

Quick follow-up, I even tried with a larger amount, but the market order didn't get placed: ``` Wednesday, Aug 09, 2017 at 04:12:30 PM UTC || PLACING ORDER { "size":...

When I copy/paste the size in Gdax (the website itself, not via the API), it displays this error: https://i.imgur.com/4TxjcaH.png "Enter a valid value. The two closest values are 0,02873181 and...

Yeah sure, can you point me to a doc with info how to setup live debugging?

I tried it with a limit order, but the issue remains: the order doesnt get placed in Gdax, while the script says it said it did: Config: ``` 'orders' :...

I even tried it without the "*0.1", so with the entire btc funds. Script said it placed the order, but it didn't make it to gdax. Again, it does work...

I found it. As I thought, the problem is the number of decimals of "size" when the order is placed. I "hacked" this into __init__.py on line 127 to ensure...

Thanks, that's a better approach indeed! I fixed the typo (the second "currency" should be "available"), but I still get this error when I run the script: ``` [Traceback (most...