My Raspberry setup is running without issues and crashes for the last days 24/7.
One market (Bitstamp) with six open pairs, three of them running Margin Bot.
Had some crashes last month, but Christian from support helped me and after installing swapspace, everything is stable.
Thanks Christian & support team.
Topic: margin terminal - over 25 spot and futures exchanges! Bots and more - page 62. (Read 268900 times)
February 06, 2018, 02:33:58 AM
February 05, 2018, 07:16:00 PM
I just want to say THANK YOU to all the guys at leoNardo for a fantastic product at a very reasonable price!
It’s a pleasure to have this community and such a responsive and supportive group of devs. It’s still a work in progress but you guys are doing a great job and I couldn’t be more pleased that this was the product I chose for myself. Keep up the great work fellas!
While it is really good product for a price, it lacks development and scale.It’s a pleasure to have this community and such a responsive and supportive group of devs. It’s still a work in progress but you guys are doing a great job and I couldn’t be more pleased that this was the product I chose for myself. Keep up the great work fellas!
I think i have deleted keys i licensed with long time ago. :C
February 05, 2018, 03:38:13 PM
I just want to say THANK YOU to all the guys/gals at leoNardo for a fantastic product at a very reasonable price!
It’s a pleasure to have this community and such a responsive and supportive group of devs. It’s still a work in progress but you guys are doing a great job and I couldn’t be more pleased that this was the product I chose for myself. Keep up the great work!
It’s a pleasure to have this community and such a responsive and supportive group of devs. It’s still a work in progress but you guys are doing a great job and I couldn’t be more pleased that this was the product I chose for myself. Keep up the great work!
February 05, 2018, 02:36:44 PM
As an ultra customer you can replace exchanges. So if you maxed out seven exchanges you can replace the ones you added before
Just add the new secret at the usual URL and drop us a mail:
http://www.marginsoftware.de/registration.html
All the best,
Rene
Brilliant, thanks Rene
February 05, 2018, 01:09:03 PM
Heya guys...
I have a question. I'm owner of a ultra license and have registered four exchanges up to today.
I'm actually using the newest 3.8 release on those four, from which one (bittrex) is still unusable up to today.
I'm now thinking about adding kraken and binance to my "portfolio" and began to wonder, how this licensing thing will go on in the long run.
I looked at your page and found that you write, the ultra license includes 7 exchanges, which clarified it a bit for me at least.
So .. now the real question. What should we (ultra license owners) expect in the future when new exchanges are added?
I imagine, i can just add 3 more exchanges to my existing 4, which might fill all seven slots. If i want to add another exchange, do i (or do we) need to buy another license slot?
I don't wanna rant about that, i'm just a bit curious about it.
oh any btw, any news on the bittrex situation?
Greetings,
hacky
I have a question. I'm owner of a ultra license and have registered four exchanges up to today.
I'm actually using the newest 3.8 release on those four, from which one (bittrex) is still unusable up to today.
I'm now thinking about adding kraken and binance to my "portfolio" and began to wonder, how this licensing thing will go on in the long run.
I looked at your page and found that you write, the ultra license includes 7 exchanges, which clarified it a bit for me at least.
So .. now the real question. What should we (ultra license owners) expect in the future when new exchanges are added?
I imagine, i can just add 3 more exchanges to my existing 4, which might fill all seven slots. If i want to add another exchange, do i (or do we) need to buy another license slot?
I don't wanna rant about that, i'm just a bit curious about it.
oh any btw, any news on the bittrex situation?
Greetings,
hacky
Good point hacky.
I purchased the ultra licence in December with 7 exchanges. I definitely won't be using Bitfinex and I would like to use Binance instead.
As an ultra customer you can replace exchanges. So if you maxed out seven exchanges you can replace the ones you added before
Just add the new secret at the usual URL and drop us a mail:
http://www.marginsoftware.de/registration.html
All the best,
Rene
February 05, 2018, 11:03:37 AM
Feature requeest:
Add the ability,with ONE button to pause all bot and then resume.So we dont have to go manyually over all bots to restart Leonardo.
Add the ability,with ONE button to pause all bot and then resume.So we dont have to go manyually over all bots to restart Leonardo.
You can just close leonardo, so it will remember which bots had been running so you can resume them after restart of leonardo.
But yeah, resuming more than one bot at once might be nice.
Hacky
February 05, 2018, 09:30:54 AM
Feature requeest:
Add the ability,with ONE button to pause all bot and then resume.So we dont have to go manyually over all bots to restart Leonardo.
Add the ability,with ONE button to pause all bot and then resume.So we dont have to go manyually over all bots to restart Leonardo.
+1
February 05, 2018, 08:33:18 AM
Feature requeest:
Add the ability,with ONE button to pause all bot and then resume.So we dont have to go manyually over all bots to restart Leonardo.
Add the ability,with ONE button to pause all bot and then resume.So we dont have to go manyually over all bots to restart Leonardo.
February 05, 2018, 06:47:25 AM
Heya guys...
I have a question. I'm owner of a ultra license and have registered four exchanges up to today.
I'm actually using the newest 3.8 release on those four, from which one (bittrex) is still unusable up to today.
I'm now thinking about adding kraken and binance to my "portfolio" and began to wonder, how this licensing thing will go on in the long run.
I looked at your page and found that you write, the ultra license includes 7 exchanges, which clarified it a bit for me at least.
So .. now the real question. What should we (ultra license owners) expect in the future when new exchanges are added?
I imagine, i can just add 3 more exchanges to my existing 4, which might fill all seven slots. If i want to add another exchange, do i (or do we) need to buy another license slot?
I don't wanna rant about that, i'm just a bit curious about it.
oh any btw, any news on the bittrex situation?
Greetings,
hacky
I have a question. I'm owner of a ultra license and have registered four exchanges up to today.
I'm actually using the newest 3.8 release on those four, from which one (bittrex) is still unusable up to today.
I'm now thinking about adding kraken and binance to my "portfolio" and began to wonder, how this licensing thing will go on in the long run.
I looked at your page and found that you write, the ultra license includes 7 exchanges, which clarified it a bit for me at least.
So .. now the real question. What should we (ultra license owners) expect in the future when new exchanges are added?
I imagine, i can just add 3 more exchanges to my existing 4, which might fill all seven slots. If i want to add another exchange, do i (or do we) need to buy another license slot?
I don't wanna rant about that, i'm just a bit curious about it.
oh any btw, any news on the bittrex situation?
Greetings,
hacky
Good point hacky.
I purchased the ultra licence in December with 7 exchanges. I definitely won't be using Bitfinex and I would like to use Binance instead.
February 05, 2018, 04:50:39 AM
Heya guys...
I have a question. I'm owner of a ultra license and have registered four exchanges up to today.
I'm actually using the newest 3.8 release on those four, from which one (bittrex) is still unusable up to today.
I'm now thinking about adding kraken and binance to my "portfolio" and began to wonder, how this licensing thing will go on in the long run.
I looked at your page and found that you write, the ultra license includes 7 exchanges, which clarified it a bit for me at least.
So .. now the real question. What should we (ultra license owners) expect in the future when new exchanges are added?
I imagine, i can just add 3 more exchanges to my existing 4, which might fill all seven slots. If i want to add another exchange, do i (or do we) need to buy another license slot?
I don't wanna rant about that, i'm just a bit curious about it.
oh any btw, any news on the bittrex situation?
Greetings,
hacky
I have a question. I'm owner of a ultra license and have registered four exchanges up to today.
I'm actually using the newest 3.8 release on those four, from which one (bittrex) is still unusable up to today.
I'm now thinking about adding kraken and binance to my "portfolio" and began to wonder, how this licensing thing will go on in the long run.
I looked at your page and found that you write, the ultra license includes 7 exchanges, which clarified it a bit for me at least.
So .. now the real question. What should we (ultra license owners) expect in the future when new exchanges are added?
I imagine, i can just add 3 more exchanges to my existing 4, which might fill all seven slots. If i want to add another exchange, do i (or do we) need to buy another license slot?
I don't wanna rant about that, i'm just a bit curious about it.
oh any btw, any news on the bittrex situation?
Greetings,
hacky
February 04, 2018, 11:29:18 PM
Can't use Binance to trade... crashes
02/04 07:36:03 pm binance:XRP/ETH: succsessfully adapted order
02/04 07:36:03 pm binance:XRP/ETH: could not adapt order association (in adapt): no association to order 13681524
02/04 07:58:02 pm binance:XRP/ETH: Network error in buffer[2](active orders: LocalError (as Error): http error while requesting open_orders: [http code: 400(Bad Request)]: ProtocolInvalidOperation (the requested operation is invalid for this protocol), Message: "Timestamp for this request is outside of the recvWindow." (Code: -1021)
02/04 08:07:39 pm binance:XRP/ETH: Network error in buffer(trades): LocalError (as Error): http error while requesting completed_trades: [http code: 400(Bad Request)]: ProtocolInvalidOperation (the requested operation is invalid for this protocol), Message: "Timestamp for this request is outside of the recvWindow." (Code: -1021)
02/04 08:15:59 pm binance: Network error in buffer(funds): http error while requesting funds: [http code: 400(Bad Request)]: ProtocolInvalidOperation (the requested operation is invalid for this protocol), Message: "Timestamp for this request is outside of the recvWindow." (Code: -1021)
02/04 07:36:03 pm binance:XRP/ETH: succsessfully adapted order
02/04 07:36:03 pm binance:XRP/ETH: could not adapt order association (in adapt): no association to order 13681524
02/04 07:58:02 pm binance:XRP/ETH: Network error in buffer[2](active orders: LocalError (as Error): http error while requesting open_orders: [http code: 400(Bad Request)]: ProtocolInvalidOperation (the requested operation is invalid for this protocol), Message: "Timestamp for this request is outside of the recvWindow." (Code: -1021)
02/04 08:07:39 pm binance:XRP/ETH: Network error in buffer(trades): LocalError (as Error): http error while requesting completed_trades: [http code: 400(Bad Request)]: ProtocolInvalidOperation (the requested operation is invalid for this protocol), Message: "Timestamp for this request is outside of the recvWindow." (Code: -1021)
02/04 08:15:59 pm binance: Network error in buffer(funds): http error while requesting funds: [http code: 400(Bad Request)]: ProtocolInvalidOperation (the requested operation is invalid for this protocol), Message: "Timestamp for this request is outside of the recvWindow." (Code: -1021)
February 04, 2018, 10:56:43 PM
Leonardo upsets me 
If there was a power outage, all orders should be monitored manually or Leonardo will sell them in negative :(sorry for bad English
If there was a power outage, all orders should be monitored manually or Leonardo will sell them in negative :(sorry for bad English February 04, 2018, 10:17:40 PM
Code:
02/05 05:13:45 am kraken: [Method:private/OpenOrders (params: trades=false) ] error in DefaultMarketInterface::httpPOST: document verification failed (docstr was: -{"error":["EAPI:Invalid nonce"]}- (try 4 of 10)
02/05 05:13:45 am kraken: error message returned by server for call to private/OpenOrders(trades=false): EAPI:Invalid nonce
02/05 05:13:49 am kraken: [Method:private/TradesHistory (params: trades=true) ] error in DefaultMarketInterface::httpPOST: document verification failed (docstr was: -{"error":["EAPI:Invalid nonce"]}- (try 2 of 10)
02/05 05:13:49 am kraken: error message returned by server for call to private/TradesHistory(trades=true): EAPI:Invalid nonce
02/05 05:13:53 am kraken: [Method:private/OpenOrders (params: trades=false) ] error in DefaultMarketInterface::httpPOST: document verification failed (docstr was: -{"error":["EAPI:Invalid nonce"]}- (try 5 of 10)
02/05 05:13:53 am kraken: error message returned by server for call to private/OpenOrders(trades=false): EAPI:Invalid nonce
02/05 05:13:57 am kraken: [Method:private/TradesHistory (params: trades=true) ] error in DefaultMarketInterface::httpPOST: document verification failed (docstr was: -{"error":["EAPI:Invalid nonce"]}- (try 3 of 10)
02/05 05:13:57 am kraken: error message returned by server for call to private/TradesHistory(trades=true): EAPI:Invalid nonce
02/05 05:14:01 am kraken: [Method:private/OpenOrders (params: trades=false) ] error in DefaultMarketInterface::httpPOST: document verification failed (docstr was: -{"error":["EAPI:Invalid nonce"]}- (try 6 of 10)
02/05 05:14:01 am kraken: error message returned by server for call to private/OpenOrders(trades=false): EAPI:Invalid nonce
02/05 05:14:05 am kraken: [Method:private/TradesHistory (params: trades=true) ] error in DefaultMarketInterface::httpPOST: document verification failed (docstr was: -{"error":["EAPI:Invalid nonce"]}- (try 4 of 10)
02/05 05:14:05 am kraken: error message returned by server for call to private/TradesHistory(trades=true): EAPI:Invalid nonce
02/05 05:14:09 am kraken: [Method:private/OpenOrders (params: trades=false) ] error in DefaultMarketInterface::httpPOST: document verification failed (docstr was: -{"error":["EAPI:Invalid nonce"]}- (try 7 of 10)
02/05 05:14:09 am kraken: error message returned by server for call to private/OpenOrders(trades=false): EAPI:Invalid nonce
02/05 05:14:13 am kraken: [Method:private/TradesHistory (params: trades=true) ] error in DefaultMarketInterface::httpPOST: document verification failed (docstr was: -{"error":["EAPI:Invalid nonce"]}- (try 5 of 10)
02/05 05:14:13 am kraken: error message returned by server for call to private/TradesHistory(trades=true): EAPI:Invalid nonce
Suddenly Kraken Bot cant make order,I cant see on top left what orders are pending and I constantly get an error on strategies being stopped. 02/05 05:13:45 am kraken: error message returned by server for call to private/OpenOrders(trades=false): EAPI:Invalid nonce
02/05 05:13:49 am kraken: [Method:private/TradesHistory (params: trades=true) ] error in DefaultMarketInterface::httpPOST: document verification failed (docstr was: -{"error":["EAPI:Invalid nonce"]}- (try 2 of 10)
02/05 05:13:49 am kraken: error message returned by server for call to private/TradesHistory(trades=true): EAPI:Invalid nonce
02/05 05:13:53 am kraken: [Method:private/OpenOrders (params: trades=false) ] error in DefaultMarketInterface::httpPOST: document verification failed (docstr was: -{"error":["EAPI:Invalid nonce"]}- (try 5 of 10)
02/05 05:13:53 am kraken: error message returned by server for call to private/OpenOrders(trades=false): EAPI:Invalid nonce
02/05 05:13:57 am kraken: [Method:private/TradesHistory (params: trades=true) ] error in DefaultMarketInterface::httpPOST: document verification failed (docstr was: -{"error":["EAPI:Invalid nonce"]}- (try 3 of 10)
02/05 05:13:57 am kraken: error message returned by server for call to private/TradesHistory(trades=true): EAPI:Invalid nonce
02/05 05:14:01 am kraken: [Method:private/OpenOrders (params: trades=false) ] error in DefaultMarketInterface::httpPOST: document verification failed (docstr was: -{"error":["EAPI:Invalid nonce"]}- (try 6 of 10)
02/05 05:14:01 am kraken: error message returned by server for call to private/OpenOrders(trades=false): EAPI:Invalid nonce
02/05 05:14:05 am kraken: [Method:private/TradesHistory (params: trades=true) ] error in DefaultMarketInterface::httpPOST: document verification failed (docstr was: -{"error":["EAPI:Invalid nonce"]}- (try 4 of 10)
02/05 05:14:05 am kraken: error message returned by server for call to private/TradesHistory(trades=true): EAPI:Invalid nonce
02/05 05:14:09 am kraken: [Method:private/OpenOrders (params: trades=false) ] error in DefaultMarketInterface::httpPOST: document verification failed (docstr was: -{"error":["EAPI:Invalid nonce"]}- (try 7 of 10)
02/05 05:14:09 am kraken: error message returned by server for call to private/OpenOrders(trades=false): EAPI:Invalid nonce
02/05 05:14:13 am kraken: [Method:private/TradesHistory (params: trades=true) ] error in DefaultMarketInterface::httpPOST: document verification failed (docstr was: -{"error":["EAPI:Invalid nonce"]}- (try 5 of 10)
02/05 05:14:13 am kraken: error message returned by server for call to private/TradesHistory(trades=true): EAPI:Invalid nonce
February 04, 2018, 01:44:05 PM
The Binance Margin Bot keeps stopping after the first trade was made!
l02/04 09:55:15 am binance:bot:XRP/ETH: [Margin-3] transition to "initializing"
02/04 09:55:16 am binance:bot:XRP/ETH: [Margin-3] transition to "creating sell order"
02/04 09:55:17 am binance:bot:XRP/ETH: [Margin-3] placing order sell 525 XRP @0.0009995 ETH
02/04 09:55:17 am binance:bot:XRP/ETH: [Margin-3] transition to "waiting for order to be placed"
02/04 09:55:24 am binance:bot:XRP/ETH: [Margin-3] transition to "order active"
02/04 10:01:20 am binance:bot:XRP/ETH: [Margin-3] current order is outdated, replacing order
02/04 10:01:20 am binance:bot:XRP/ETH: [Margin-3] transition to "check whether order must be adapted"
02/04 10:01:21 am binance:bot:XRP/ETH: [Margin-3] replacing the current sell order would result in an identical price of 0.0009995 so canceling/re-placing the order is skipped
02/04 10:01:21 am binance:bot:XRP/ETH: [Margin-3] transition to "order active"
02/04 10:07:22 am binance:bot:XRP/ETH: [Margin-3] current order is outdated, replacing order
02/04 10:07:22 am binance:bot:XRP/ETH: [Margin-3] transition to "check whether order must be adapted"
02/04 10:07:32 am binance:bot:XRP/ETH: [Margin-3] the current order must be adapted as the next sell price (0.000999) differs from the current price (0.0009995)
02/04 10:07:32 am binance:bot:XRP/ETH: [Margin-3] transition to "canceling order"
02/04 10:09:00 am binance: Network error in buffer(funds): http error while requesting funds: [http code: 400(Bad Request)]: ProtocolInvalidOperation (the requested operation is invalid for this protocol), Message: "Timestamp for this request is outside of the recvWindow." (Code: -1021)
02/04 10:10:38 am binance:XRP/ETH: Network error in buffer[2](active orders: LocalError (as Error): http error while requesting open_orders: [http code: 400(Bad Request)]: ProtocolInvalidOperation (the requested operation is invalid for this protocol), Message: "Timestamp for this request is outside of the recvWindow." (Code: -1021)
02/04 10:11:28 am binance:XRP/ETH: Could not query funds for cancel order in 5 tries: http error while requesting funds: [http code: 400(Bad Request)]: ProtocolInvalidOperation (the requested operation is invalid for this protocol), Message: "Timestamp for this request is outside of the recvWindow." (Code: -1021)
02/04 10:11:28 am binance:bot:XRP/ETH: [Margin-3] an exception occured while the bot was running :'error canceling order 13652310 stopping strategy to avoid double orders'og.....
02/04 10:07:32 am binance:bot:XRP/ETH: [Margin-3] the current order must be adapted as the next sell price (0.000999) differs from the current price (0.0009995)
02/04 10:07:32 am binance:bot:XRP/ETH: [Margin-3] transition to "canceling order"
02/04 10:09:00 am binance: Network error in buffer(funds): http error while requesting funds: [http code: 400(Bad Request)]: ProtocolInvalidOperation (the requested operation is invalid for this protocol), Message: "Timestamp for this request is outside of the recvWindow." (Code: -1021)
02/04 10:10:38 am binance:XRP/ETH: Network error in buffer[2](active orders: LocalError (as Error): http error while requesting open_orders: [http code: 400(Bad Request)]: ProtocolInvalidOperation (the requested operation is invalid for this protocol), Message: "Timestamp for this request is outside of the recvWindow." (Code: -1021)
02/04 10:11:28 am binance:XRP/ETH: Could not query funds for cancel order in 5 tries: http error while requesting funds: [http code: 400(Bad Request)]: ProtocolInvalidOperation (the requested operation is invalid for this protocol), Message: "Timestamp for this request is outside of the recvWindow." (Code: -1021)
02/04 10:11:28 am binance:bot:XRP/ETH: [Margin-3] an exception occured while the bot was running :'error canceling order 13652310 stopping strategy to avoid double orders'
l02/04 09:55:15 am binance:bot:XRP/ETH: [Margin-3] transition to "initializing"
02/04 09:55:16 am binance:bot:XRP/ETH: [Margin-3] transition to "creating sell order"
02/04 09:55:17 am binance:bot:XRP/ETH: [Margin-3] placing order sell 525 XRP @0.0009995 ETH
02/04 09:55:17 am binance:bot:XRP/ETH: [Margin-3] transition to "waiting for order to be placed"
02/04 09:55:24 am binance:bot:XRP/ETH: [Margin-3] transition to "order active"
02/04 10:01:20 am binance:bot:XRP/ETH: [Margin-3] current order is outdated, replacing order
02/04 10:01:20 am binance:bot:XRP/ETH: [Margin-3] transition to "check whether order must be adapted"
02/04 10:01:21 am binance:bot:XRP/ETH: [Margin-3] replacing the current sell order would result in an identical price of 0.0009995 so canceling/re-placing the order is skipped
02/04 10:01:21 am binance:bot:XRP/ETH: [Margin-3] transition to "order active"
02/04 10:07:22 am binance:bot:XRP/ETH: [Margin-3] current order is outdated, replacing order
02/04 10:07:22 am binance:bot:XRP/ETH: [Margin-3] transition to "check whether order must be adapted"
02/04 10:07:32 am binance:bot:XRP/ETH: [Margin-3] the current order must be adapted as the next sell price (0.000999) differs from the current price (0.0009995)
02/04 10:07:32 am binance:bot:XRP/ETH: [Margin-3] transition to "canceling order"
02/04 10:09:00 am binance: Network error in buffer(funds): http error while requesting funds: [http code: 400(Bad Request)]: ProtocolInvalidOperation (the requested operation is invalid for this protocol), Message: "Timestamp for this request is outside of the recvWindow." (Code: -1021)
02/04 10:10:38 am binance:XRP/ETH: Network error in buffer[2](active orders: LocalError (as Error): http error while requesting open_orders: [http code: 400(Bad Request)]: ProtocolInvalidOperation (the requested operation is invalid for this protocol), Message: "Timestamp for this request is outside of the recvWindow." (Code: -1021)
02/04 10:11:28 am binance:XRP/ETH: Could not query funds for cancel order in 5 tries: http error while requesting funds: [http code: 400(Bad Request)]: ProtocolInvalidOperation (the requested operation is invalid for this protocol), Message: "Timestamp for this request is outside of the recvWindow." (Code: -1021)
02/04 10:11:28 am binance:bot:XRP/ETH: [Margin-3] an exception occured while the bot was running :'error canceling order 13652310 stopping strategy to avoid double orders'og.....
02/04 10:07:32 am binance:bot:XRP/ETH: [Margin-3] the current order must be adapted as the next sell price (0.000999) differs from the current price (0.0009995)
02/04 10:07:32 am binance:bot:XRP/ETH: [Margin-3] transition to "canceling order"
02/04 10:09:00 am binance: Network error in buffer(funds): http error while requesting funds: [http code: 400(Bad Request)]: ProtocolInvalidOperation (the requested operation is invalid for this protocol), Message: "Timestamp for this request is outside of the recvWindow." (Code: -1021)
02/04 10:10:38 am binance:XRP/ETH: Network error in buffer[2](active orders: LocalError (as Error): http error while requesting open_orders: [http code: 400(Bad Request)]: ProtocolInvalidOperation (the requested operation is invalid for this protocol), Message: "Timestamp for this request is outside of the recvWindow." (Code: -1021)
02/04 10:11:28 am binance:XRP/ETH: Could not query funds for cancel order in 5 tries: http error while requesting funds: [http code: 400(Bad Request)]: ProtocolInvalidOperation (the requested operation is invalid for this protocol), Message: "Timestamp for this request is outside of the recvWindow." (Code: -1021)
02/04 10:11:28 am binance:bot:XRP/ETH: [Margin-3] an exception occured while the bot was running :'error canceling order 13652310 stopping strategy to avoid double orders'
Hmm, doesn't look good!
We will look into. I think it happens when the web socket connection becomes too slow. We saw it once and were already looking into it as far as I know. If you have any more information can you send it to [email protected]
Thanks!
Jonathan
February 04, 2018, 01:18:19 PM
The Binance Margin Bot keeps stopping after the first trade was made!
l02/04 09:55:15 am binance:bot:XRP/ETH: [Margin-3] transition to "initializing"
02/04 09:55:16 am binance:bot:XRP/ETH: [Margin-3] transition to "creating sell order"
02/04 09:55:17 am binance:bot:XRP/ETH: [Margin-3] placing order sell 525 XRP @0.0009995 ETH
02/04 09:55:17 am binance:bot:XRP/ETH: [Margin-3] transition to "waiting for order to be placed"
02/04 09:55:24 am binance:bot:XRP/ETH: [Margin-3] transition to "order active"
02/04 10:01:20 am binance:bot:XRP/ETH: [Margin-3] current order is outdated, replacing order
02/04 10:01:20 am binance:bot:XRP/ETH: [Margin-3] transition to "check whether order must be adapted"
02/04 10:01:21 am binance:bot:XRP/ETH: [Margin-3] replacing the current sell order would result in an identical price of 0.0009995 so canceling/re-placing the order is skipped
02/04 10:01:21 am binance:bot:XRP/ETH: [Margin-3] transition to "order active"
02/04 10:07:22 am binance:bot:XRP/ETH: [Margin-3] current order is outdated, replacing order
02/04 10:07:22 am binance:bot:XRP/ETH: [Margin-3] transition to "check whether order must be adapted"
02/04 10:07:32 am binance:bot:XRP/ETH: [Margin-3] the current order must be adapted as the next sell price (0.000999) differs from the current price (0.0009995)
02/04 10:07:32 am binance:bot:XRP/ETH: [Margin-3] transition to "canceling order"
02/04 10:09:00 am binance: Network error in buffer(funds): http error while requesting funds: [http code: 400(Bad Request)]: ProtocolInvalidOperation (the requested operation is invalid for this protocol), Message: "Timestamp for this request is outside of the recvWindow." (Code: -1021)
02/04 10:10:38 am binance:XRP/ETH: Network error in buffer[2](active orders: LocalError (as Error): http error while requesting open_orders: [http code: 400(Bad Request)]: ProtocolInvalidOperation (the requested operation is invalid for this protocol), Message: "Timestamp for this request is outside of the recvWindow." (Code: -1021)
02/04 10:11:28 am binance:XRP/ETH: Could not query funds for cancel order in 5 tries: http error while requesting funds: [http code: 400(Bad Request)]: ProtocolInvalidOperation (the requested operation is invalid for this protocol), Message: "Timestamp for this request is outside of the recvWindow." (Code: -1021)
02/04 10:11:28 am binance:bot:XRP/ETH: [Margin-3] an exception occured while the bot was running :'error canceling order 13652310 stopping strategy to avoid double orders'og.....
02/04 10:07:32 am binance:bot:XRP/ETH: [Margin-3] the current order must be adapted as the next sell price (0.000999) differs from the current price (0.0009995)
02/04 10:07:32 am binance:bot:XRP/ETH: [Margin-3] transition to "canceling order"
02/04 10:09:00 am binance: Network error in buffer(funds): http error while requesting funds: [http code: 400(Bad Request)]: ProtocolInvalidOperation (the requested operation is invalid for this protocol), Message: "Timestamp for this request is outside of the recvWindow." (Code: -1021)
02/04 10:10:38 am binance:XRP/ETH: Network error in buffer[2](active orders: LocalError (as Error): http error while requesting open_orders: [http code: 400(Bad Request)]: ProtocolInvalidOperation (the requested operation is invalid for this protocol), Message: "Timestamp for this request is outside of the recvWindow." (Code: -1021)
02/04 10:11:28 am binance:XRP/ETH: Could not query funds for cancel order in 5 tries: http error while requesting funds: [http code: 400(Bad Request)]: ProtocolInvalidOperation (the requested operation is invalid for this protocol), Message: "Timestamp for this request is outside of the recvWindow." (Code: -1021)
02/04 10:11:28 am binance:bot:XRP/ETH: [Margin-3] an exception occured while the bot was running :'error canceling order 13652310 stopping strategy to avoid double orders'
l02/04 09:55:15 am binance:bot:XRP/ETH: [Margin-3] transition to "initializing"
02/04 09:55:16 am binance:bot:XRP/ETH: [Margin-3] transition to "creating sell order"
02/04 09:55:17 am binance:bot:XRP/ETH: [Margin-3] placing order sell 525 XRP @0.0009995 ETH
02/04 09:55:17 am binance:bot:XRP/ETH: [Margin-3] transition to "waiting for order to be placed"
02/04 09:55:24 am binance:bot:XRP/ETH: [Margin-3] transition to "order active"
02/04 10:01:20 am binance:bot:XRP/ETH: [Margin-3] current order is outdated, replacing order
02/04 10:01:20 am binance:bot:XRP/ETH: [Margin-3] transition to "check whether order must be adapted"
02/04 10:01:21 am binance:bot:XRP/ETH: [Margin-3] replacing the current sell order would result in an identical price of 0.0009995 so canceling/re-placing the order is skipped
02/04 10:01:21 am binance:bot:XRP/ETH: [Margin-3] transition to "order active"
02/04 10:07:22 am binance:bot:XRP/ETH: [Margin-3] current order is outdated, replacing order
02/04 10:07:22 am binance:bot:XRP/ETH: [Margin-3] transition to "check whether order must be adapted"
02/04 10:07:32 am binance:bot:XRP/ETH: [Margin-3] the current order must be adapted as the next sell price (0.000999) differs from the current price (0.0009995)
02/04 10:07:32 am binance:bot:XRP/ETH: [Margin-3] transition to "canceling order"
02/04 10:09:00 am binance: Network error in buffer(funds): http error while requesting funds: [http code: 400(Bad Request)]: ProtocolInvalidOperation (the requested operation is invalid for this protocol), Message: "Timestamp for this request is outside of the recvWindow." (Code: -1021)
02/04 10:10:38 am binance:XRP/ETH: Network error in buffer[2](active orders: LocalError (as Error): http error while requesting open_orders: [http code: 400(Bad Request)]: ProtocolInvalidOperation (the requested operation is invalid for this protocol), Message: "Timestamp for this request is outside of the recvWindow." (Code: -1021)
02/04 10:11:28 am binance:XRP/ETH: Could not query funds for cancel order in 5 tries: http error while requesting funds: [http code: 400(Bad Request)]: ProtocolInvalidOperation (the requested operation is invalid for this protocol), Message: "Timestamp for this request is outside of the recvWindow." (Code: -1021)
02/04 10:11:28 am binance:bot:XRP/ETH: [Margin-3] an exception occured while the bot was running :'error canceling order 13652310 stopping strategy to avoid double orders'og.....
02/04 10:07:32 am binance:bot:XRP/ETH: [Margin-3] the current order must be adapted as the next sell price (0.000999) differs from the current price (0.0009995)
02/04 10:07:32 am binance:bot:XRP/ETH: [Margin-3] transition to "canceling order"
02/04 10:09:00 am binance: Network error in buffer(funds): http error while requesting funds: [http code: 400(Bad Request)]: ProtocolInvalidOperation (the requested operation is invalid for this protocol), Message: "Timestamp for this request is outside of the recvWindow." (Code: -1021)
02/04 10:10:38 am binance:XRP/ETH: Network error in buffer[2](active orders: LocalError (as Error): http error while requesting open_orders: [http code: 400(Bad Request)]: ProtocolInvalidOperation (the requested operation is invalid for this protocol), Message: "Timestamp for this request is outside of the recvWindow." (Code: -1021)
02/04 10:11:28 am binance:XRP/ETH: Could not query funds for cancel order in 5 tries: http error while requesting funds: [http code: 400(Bad Request)]: ProtocolInvalidOperation (the requested operation is invalid for this protocol), Message: "Timestamp for this request is outside of the recvWindow." (Code: -1021)
02/04 10:11:28 am binance:bot:XRP/ETH: [Margin-3] an exception occured while the bot was running :'error canceling order 13652310 stopping strategy to avoid double orders'
February 04, 2018, 11:53:09 AM
I'm in Demo mode trying 10 pair BB at Binance and 9 pair only have trade data back to Jan 16, and one pair, NANO/BTC, only has trade data for today, Feb 3.
The data is the data we collected since adding it to our data collection. We are looking into getting access to older data though.
More Info on the XRB rebranding is available at:
https://hackernoon.com/nano-rebrand-announcement-9101528a7b76
All the best,
Rene
February 04, 2018, 11:48:58 AM
I had some similar mishaps using BB (of several trades in a short time with no gain or even small losses), and I guess that it's due to using very short timeframe (like <6 hours) with no minimum gain set, when the price is relatively flat and the BB get very narrow.
So I started setting minimum gains with BB and even setting at some positive value the Sell band and Buy band parameters, and I even stopped using BB strategies on timeframes shorter than 6 hours, and after that I didn't have more events of that sort, even if trades get less frequent.
Speaking of possible improvements I'd like the addition of trailing stops, and an indication of what strategy triggered each executed order (because I use different strategies on different timeframes on the same markets).
+1
Both suggestions are very much needed.
We propably see them in a near future update.
Thanks
We are just getting started!Rene
February 04, 2018, 10:48:41 AM
I had some similar mishaps using BB (of several trades in a short time with no gain or even small losses), and I guess that it's due to using very short timeframe (like <6 hours) with no minimum gain set, when the price is relatively flat and the BB get very narrow.
So I started setting minimum gains with BB and even setting at some positive value the Sell band and Buy band parameters, and I even stopped using BB strategies on timeframes shorter than 6 hours, and after that I didn't have more events of that sort, even if trades get less frequent.
Speaking of possible improvements I'd like the addition of trailing stops, and an indication of what strategy triggered each executed order (because I use different strategies on different timeframes on the same markets).
+1
Both suggestions are very much needed.
We propably see them in a near future update.
February 04, 2018, 04:43:22 AM
I had some similar mishaps using BB (of several trades in a short time with no gain or even small losses), and I guess that it's due to using very short timeframe (like <6 hours) with no minimum gain set, when the price is relatively flat and the BB get very narrow.
So I started setting minimum gains with BB and even setting at some positive value the Sell band and Buy band parameters, and I even stopped using BB strategies on timeframes shorter than 6 hours, and after that I didn't have more events of that sort, even if trades get less frequent.
Speaking of possible improvements I'd like the addition of trailing stops, and an indication of what strategy triggered each executed order (because I use different strategies on different timeframes on the same markets).
+1
Both suggestions are very much needed.
We propably see them in a near future update.
February 04, 2018, 04:37:20 AM
I'm in Demo mode trying 10 pair BB at Binance and 9 pair only have trade data back to Jan 16, and one pair, NANO/BTC, only has trade data for today, Feb 3.
NANO/BTC is a new addition on Binance, former Raiblocks.
Jump to: