margin terminal is now FREE - bots for over 30 exchanges

[ofnadave]

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'

[1714241321]

1714241321

[1714241321]

1714241321

[1714241321]

1714241321

[leonArdo@margin]

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'

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 support@marginsoftware.de

Thanks!
Jonathan

[embrance]

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.

[mk26]

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

[ofnadave]

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)

[hackbyte]

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

[Grumble Guff]

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

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.

[embrance]

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.

[Grumble Guff]

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.

+1

[hackbyte]

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.

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

[leonArdo@margin]

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

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

[Grumble Guff]

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 

[money4good]

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!  

[wfthkttn]

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.
I think i have deleted keys i licensed with long time ago. :C

[gnoe]

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.

[hackbyte]

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

Heya yeah, that is a really nice advantage for ultra customers.

Thanks for that info.

Hacky

[hackbyte]

While it is really good product for a price, it lacks development and scale.
I think i have deleted keys i licensed with long time ago. :C

Well, that is not really true. They're working on it constantly and we get new features and even new included exchange APIs every few weeks. Additional, they usually answer a mail sent to support@marginsoftware.de within hours..

So ... hey ... they had a _ton_ of new customers in the last months and have to cope even with that. But they're still really fast whenever a problem arises.

If you have still access to you email account you used back then when you registered your API keys, i think you could simply send them an email and i'm sure they will happily change your keys if you send them the new ones.

Greetings,

hacky

[Amaralluis]

Bittrex error message are more and more weirderer....

02/06 01:31:41 pm bittrex:LTC/BTC: [Method:public/getorderbook (params: &type=sell) ] error in DefaultMarketInterface::httpPOST: network error: [http code: 503(Service Unavailable)]: ServiceUnavailable (the server is unable to handle the request at this time.) (try 1 of 10), message received: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN""http://www.w3.org/TR/html4/strict.dtd">
<HTML><HEAD><TITLE>Service Unavailable</TITLE>
<META HTTP-EQUIV="Content-Type" Content="text/html; charse...

02/06 01:35:56 pm bittrex:LTC/BTC: [Method:market/getopenorders (params: ) ] error in DefaultMarketInterface::httpPOST: network error: [http code: 530()]: UnknownServer (an unknown error related to the server response was detected) (try 1 of 10), message received: <!DOCTYPE html>
<!--[if lt IE 7]> <html class="no-js ie6 oldie" lang="en-US"> <![endif]-->
<!--[if IE 7]>    <html class="no-js ie7 oldie" lang="en-US"> <![endif]-->
<!--[if IE 8]>    <html class="...

[rothcom65]

While it is really good product for a price, it lacks development and scale.
I think i have deleted keys i licensed with long time ago. :C

Well, that is not really true. They're working on it constantly and we get new features and even new included exchange APIs every few weeks. Additional, they usually answer a mail sent to support@marginsoftware.de within hours..

So ... hey ... they had a _ton_ of new customers in the last months and have to cope even with that. But they're still really fast whenever a problem arises.

If you have still access to you email account you used back then when you registered your API keys, i think you could simply send them an email and i'm sure they will happily change your keys if you send them the new ones.

Greetings,

hacky

I agree. Customer support is doing a great job ( in my case, Sarah, she responded to my inquiries within 15-30 minutes).

[cryptolelefla]

While it is really good product for a price, it lacks development and scale.
I think i have deleted keys i licensed with long time ago. :C

Well, that is not really true. They're working on it constantly and we get new features and even new included exchange APIs every few weeks. Additional, they usually answer a mail sent to support@marginsoftware.de within hours..

So ... hey ... they had a _ton_ of new customers in the last months and have to cope even with that. But they're still really fast whenever a problem arises.

If you have still access to you email account you used back then when you registered your API keys, i think you could simply send them an email and i'm sure they will happily change your keys if you send them the new ones.

Greetings,

hacky

I agree. Customer support is doing a great job ( in my case, Sarah, she responded to my inquiries within 15-30 minutes).

confirm that support is really good