Binance System Upgrade is scheduled for 2018/06/26 2:00 AM (UTC) and will take approximately 4 hours. Withdrawals and trading will be suspended during.. blah blah blah. Here we go again with Binance, just as soon as the market moves off ground zero (again) they need the systems for 4 hours. Plan accordingly.. In the event they are not back up until Thursday, again.  Thanks for posting CTShaman! Here is the post from Binance: https://support.binance.com/hc/en-us/articles/360005051732Best wishes, Jonathan |
|
|
|
Hello?? Is support@margine.de being monitored? I've filed 6 reports since the 14th, please acknowledge if someone is getting them. All I need to know at the moment is that they are being received. Thanks! Hi, No, support@margine.de is not being monitored. support@margin.de is. Is that the issue? Jonathan |
|
|
|
Is anyone else having issues this morning? Margin software will not launch after it crashed.
I'm using the latest release, on Ubuntu 16.04 LTS and Bittrex as the exchange.
Loads, I hit Login initialises Bittrex, checks bittrex credentials and then says checking crededtials and then crasshes, .
[code] $ ./run-margin.sh Running on Ubuntu 16.04 ./run-margin.sh: line 62: 11162 Segmentation fault (core dumped) QT_PLUGIN_PATH=$DIR/plugins ./margin.bin [/code] Could be a Bittrex issue though of course. Hi David, well, no matter what shenanigans Bittrex returns, margin shouldn't crash. Unfortunately though, I cannot reproduce this behavior. Logging into Bittrex directly on a fresh Ubuntu 16.04 install works fine for me... Does it happen every time you try to log into Bittrex directly without going through Poloniex first (weirdest workaround ever BTW)? How many currency pairs do you have selected? Anything unusual about your setup or any other potentially relevant information that could help us reproduce this? Sorry for your troubles and I'm glad you found some way around it, Christian |
|
|
|
|
Thanks to everyone, especially our beta testers, who have given us feedback on the latest patch version of margin.
It looks like we made really good progress and fixed some nasty bugs that were causing crashes.
All the best,
Jonathan
|
|
|
|
margin 1.1.2 patch releasedThis patch mainly focuses on stability fixes- New security mechanism for strategies in case of missing trade data
- Explicitly prevent static ping pong bot from running with a negative effective gain
- mArgin maker bot does not trigger stop-loss anymore before having bought
- Fixed a bug that caused mArgin maker bot to get stuck in 'creating sell order' when not enough funds are available
- Moving currency pairs, switching time windows or minimizing the program no longer resets the GUI
- Improved stability when moving currency pair tabs
- Fixed a possible race condition that caused issues when closing currency pair tabs
- Fixed a critical bug that could cause a crash when closing an active market with running strategies
- Removed a source of crashes when closing reddit widgets
- Additional stability fixes
- Minor layout fixes for the login window
- Minor main GUI layout fixes
- Fixed rendering of table headers (removed doubled borders and added horizontal padding)
The arm/Raspberry-PI version is also available again  There are two ways to grab it. Either click the Update Available link in the margin login window or login to your account on https://margin.de and download from the website.
Not a customer but want to try it out? Download our free Demo here.
|
|
|
|
 Heres an update of my testing of the EMA BOT. It finally got a sale with a nice profit of about 9.3%... not bad at all but I still think the lines should be reversed. Had it sold when it crossed the blue line the profit would have been higher. Hi Amaralluis, The bot logic is sound. Yes, in situations like what you depicted the bot would have made more profit if the lines where reversed. However, if the market turned against you would be left holding bags. With the current configuration if the market turns against you after a buy, a sell will be triggered causing a loss but allowing for a later buy back and for the bot to continue. Of course, setting a Min effective gain will negate that so while there are only a few parameters, configuring them is not a trivial task. There is no silver bullet. All the best, Jonathan |
|
|
|
...
(Margin team, can you clarify if the bot takes into consideration the direction of the short EMA, i.e. crossing from above or below?)
...
Hi Dorian, Thanks for jumping in. Yes, the bot knows the direction of the short EMA. It is important to note is that when using immediate mode many crossings can occur within a single candle as it is being formed. Best wishes, Jonathan |
|
|
|
Is there a guide for EMA Bot settings?
I dont understand how they work.
Hi Amaralluis, There is a help article on the website: https://margin.deJust go to the Help Centre and it’s one of the FAQs. Best wishes, Jonathan Thanks, In the Crossover tuning shouldnt the buy line swapped with the sell line? As it is right now it seems to indicate that the buy will happen at a higher value than it should and the sell viceversa? Or does it means that negative values should be used here? No, it is set correctly. It protects against too many trades being triggered as a candle forms and against the market turning against you. If the market turns against you a small loss will be incurred - as you observed but at the next crossover a gain should be made. Please try out in demo mode until you are comfortable with it! Best wishes, Jonathan |
|
|
|
Is there a guide for EMA Bot settings?
I dont understand how they work.
Hi Amaralluis, There is a help article on the website: https://margin.deJust go to the Help Centre and it’s one of the FAQs. Best wishes, Jonathan |
|
|
|
Hi support team,
Strangely enough, I was able to open Hitbtc using the leonArdo latest build 3.80.
But margin 1.1.0 version still has the error I mentioned.
I am sure that bandwidth is not an issue here.
Thank you,
Hi gtp425, Can you check is that you have also enabled 'Payment information' on your API key. Everything except Withdrawals should be enabled. And please upgrade to latest margin version 1.1.1 Best wishes, Jonathan |
|
|
|
Hi, The latest margin version (ARM) failed to connect to my HitBTC account. Keeps saying Credentials error. I'm sure that I have put in the correct API key/secret. Thanks, [Edit] It also happens with the latest margin on Mac. Screenshot:  https://prnt.sc/joib8aHi gtp425, I just tested it and could connect to HitBTC. Can you create a new API key pair and try again? Perhaps there is an issue with the one you are using? Best wishes, Jonathan |
|
|
|
margin 1.1.1 patch released- Stability fixes
- Improved EMA bot: added "immediate"-mode
- Improved visualization of negative buy/sell threshold offsets in EMA bot
- Added additional warning dialogs for certain combinations of parameters in EMA bot
- Partly reworked reddit integration (rendering, symbol visualization of votes)
- Smaller fixes in ADX indicator
- Added exchanges get immediate focus now
There are two ways to grab it. Either click the Update Available link in the margin login window or login to your account on https://margin.de and download from the website.
Not a customer but want to try it out? Download our free Demo here.
|
|
|
|
There will be a final version of leonArdo released.
Best wishes,
Jonathan
I still have problems with the bittrex api ... actually i'm able to set up orders, but no orders active or filled, are shown anymore.. Since months! That's pretty bad. On top of that, binance seems to have upgraded their exchange yesterday ( see https://support.binance.com/hc/en-us/articles/360004124472-System-Upgrade-Notice ) and since exact then, i'm unable to log on to the binance API at all. That's pretty bad and annpoying too. Can we expect this to get fixed for the final leonArdo release _anytime soon_? Or are we just doomed with a dead product now? Hacky EDIT: No change on the other reported problem about the dead binary anyways: agamemnon|hackbyte|08:21:17|~| 0> wget http://marginsoftware.de/lalalalalalala/leonArdo-linux.zip
--2018-05-25 08:21:24-- http://marginsoftware.de/lalalalalalala/leonArdo-linux.zip
Auflösen des Hostnamen »marginsoftware.de (marginsoftware.de)«... 188.40.30.87
Verbindungsaufbau zu marginsoftware.de (marginsoftware.de)|188.40.30.87|:80... verbunden.
HTTP-Anforderung gesendet, warte auf Antwort... 200 OK
Länge: 25946361 (25M) [application/zip]
In »»leonArdo-linux.zip«« speichern.
leonArdo-linux.zip 100%[=====================================================>] 24,74M 6,62MB/s in 3,6s
2018-05-25 08:21:27 (6,80 MB/s) - »leonArdo-linux.zip« gespeichert [25946361/25946361]
agamemnon|hackbyte|08:21:27|~| 0> unzip leonArdo-linux.zip
Archive: leonArdo-linux.zip
creating: leonArdo-linux/
inflating: leonArdo-linux/leonArdo
inflating: leonArdo-linux/run-leonArdo.sh
creating: leonArdo-linux/plugins/
creating: leonArdo-linux/plugins/platforms/
inflating: leonArdo-linux/plugins/platforms/libqxcb.so
creating: leonArdo-linux/lib/
inflating: leonArdo-linux/lib/libQt5Core.so.5
inflating: leonArdo-linux/lib/libQt5Widgets.so.5
inflating: leonArdo-linux/lib/libQt5WebSockets.so.5
inflating: leonArdo-linux/lib/libQt5XcbQpa.so.5
inflating: leonArdo-linux/lib/libQt5Svg.so.5
inflating: leonArdo-linux/lib/libicuuc.so.56
inflating: leonArdo-linux/lib/libQt5Gui.so.5
inflating: leonArdo-linux/lib/libicui18n.so.56
inflating: leonArdo-linux/lib/libQt5DBus.so.5
inflating: leonArdo-linux/lib/libQt5Network.so.5
inflating: leonArdo-linux/lib/libicudata.so.56
inflating: leonArdo-linux/license.txt
agamemnon|hackbyte|08:21:33|~| 0> cd leonArdo-linux/
agamemnon|hackbyte|08:21:35|~/leonArdo-linux| 0> ./run-leonArdo.sh
Running on Ubuntu 16.04
./leonArdo: lib/libQt5Core.so.5: version `Qt_5.10' not found (required by ./leonArdo)
agamemnon|hackbyte|08:21:44|~/leonArdo-linux| 1> cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=16.04
DISTRIB_CODENAME=xenial
DISTRIB_DESCRIPTION="Ubuntu 16.04.4 LTS"
agamemnon|hackbyte|08:21:58|~/leonArdo-linux| 0> uname -a
Linux agamemnon 4.13.0-41-generic #46~16.04.1-Ubuntu SMP Thu May 3 10:06:43 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
agamemnon|hackbyte|08:22:00|~/leonArdo-linux| 0>
Hey Hacky, You would want to change your tone or you won't be getting any more support from me. Period. ASAIK Binance didn't change their API. It works fine so please be more specific. Continue to write here if you like but if you want us to support your specific needs then open a ticket with us: support@margin.deAnd when writing, don't assume we know everything about your case. We have thousands of customers we have to support. Include the system you are running on and the issue you would like us to tackle. As I have already said there will be a final version of leonArdo that will address some of the issues you already raised. There is a new linux margin binary available that fixes the system library issue. Please download and install that if relevant. Looking into the leonArdo linux binary now. Jonathan |
|
|
|
Is this still an active project?
Most of the team were at the Consensus conference in New York last week so we have been a little quiet. However, our full customer support team was available the entire time. If you have any question I would refer you to support@margin.deHalf of us are back now and getting back on top of things. Best wishes, Jonathan |
|
|
|
When will 1.1.0 version for Raspberry Pi be released? It is still 1.0.2 on ARM.
Thanks.
Next week. Our Arm developer was ill and is currently on holidays. He gets back next week and will work on that. Best wishes, Jonathan |
|
|
|
Just to report a bug on the not-to-be-updated-anymore leonArdo bot.
On the "Show trade" table, only Buy are shown. No Sell are displayed.
Shall we expect a bug free version of leonArdo in the future, or shall we keep on with what we have?
There will be a final version of leonArdo released. Best wishes, Jonathan |
|
|
|
EMA crossover bot explainedThe EMA crossover bot can be started in one of three modes: buy, sell or any. In the 'buy' mode it will wait until a buy situation arises before triggering its first spot order. In 'any' mode it is ready to either buy or sell, whichever situation occurs first.
What triggers a buy?
A buy event is triggered when the short term EMA line crosses the long term EMA line from below.
What triggers a sell?
A sell event is triggered when the short term EMA line crosses the long term EMA line from above.
Important details
Please note that the EMA bot waits for a candle to fully form before calculating the current value of the two EMA lines. The actual value taken for each candle can be configured in the GUI, but the default is to take the closing value. This means that even though a crossover event may have occurred in a particular candle the bot will react one candle later. Reacting within a currently forming candle had the undesired effect of potentially multiple crossover events occurring.
It is also important to note that once the bot triggers a buy or sell event it places a spot order. This means that the resulting trade can be displaced from the crossover event due to having to overcome the spread and in cases where there is a shallow order book this can result in many partial order fills.
Crossover fine tuning
It is possible to add a buy or sell offset which provides more confidence that a crossover situation has occurred. These are visualised in the chart as separate lines ensuring you have a visual confirmation of their affect.
 
|
|
|
|
margin 1.1.0 released
We've been hard at work to bring you 3 major new features: A new EMA crossover bot, Drawing tools and Reddit integration!!
Major new features- EMA crossover bot
- Drawing tools (click on the pencil icon beside the indicator icon)
- Reddit integration (add a subreddit channel to a tools window - top left hand corner of margin)
We also fixed the issue that moving a currency pair tab resets the chart settings to an older state. Note that the Reddit thumbnail images are currently only available on Mac.
|
|
|
|
- constant saving log to text file
This is already available. Logs are saved in the hidden .margin and .leonArdo folders, respectively. These are in your home folder. Thanks, ill post the last log lines after next crash The logs are pretty huge, i don't think they follow the log level rules from the GUI. Do these ever get cleared? They get trimmed after 10K lines. We allowed them to get a little bigger as otherwise the important part was sometimes gone. The good thing is they are very compressible! Thanks, Jonathan I don't think the trimming works... i'm at 240k lines. >> https://imgur.com/a/61WeODQIll try running margin as admin hmm, not good. Will look into it! Thanks, Jonathan |
|
|
|
|
Show Posts
