01-16-2019, 03:21 PM
(This post was last modified: 01-16-2019, 03:37 PM by crypto49er.)
I'm glad we're able to figure out that Kraken uses string instead of float.
I think I know why the trade executes (post to the order book) on Kraken. Although I can't open a Kraken account, I'm glad they have no restriction on accessing their interface.
![[Image: attachment.php?aid=333]](https://forum.gekko.wizb.it/attachment.php?aid=333)
Looking at the spread for ETH/EUR, there's a difference of 21 cents between the bids and asks. So adding 0.03 would just put you on top of the order book, instead of trading across the book. I underestimated how big a spread can be for different exchanges even for fiat/crypto trade pairs. Since we are aiming to get the "rejected" trade error, we should go for as high a number as possible, adding 10% to the price of crypto should absolutely put the order across the book. So a r(Number(ticker.bid)*1.1) should do the trick.
I think I know why the trade executes (post to the order book) on Kraken. Although I can't open a Kraken account, I'm glad they have no restriction on accessing their interface.
Looking at the spread for ETH/EUR, there's a difference of 21 cents between the bids and asks. So adding 0.03 would just put you on top of the order book, instead of trading across the book. I underestimated how big a spread can be for different exchanges even for fiat/crypto trade pairs. Since we are aiming to get the "rejected" trade error, we should go for as high a number as possible, adding 10% to the price of crypto should absolutely put the order across the book. So a r(Number(ticker.bid)*1.1) should do the trick.
If it isn't crypto, it isn't worth mining, it isn't worth speculating.
https://www.youtube.com/c/crypto49er
https://www.youtube.com/c/crypto49er