submitted by MoonTrader_io to Moontrader_official [link] [comments]
Our team has developed and is supporting the trading terminal MoonBot which was introduced in October 3, 2017. Currently, the performance of MoonBot surpasses that of most existing trading systems as a result of its advanced functionality and the high security features designed to protect your trading activities.
Secure Connection to the Exchange
The connection from MoonBot to an Exchange is carried out using special keys that the user receives from an exchange such as Binance or Bittrex.
MoonBot connects securely to cryptocurrency trading Exchanges through two special keys which are uniquely and only known to their owner. These are the API key, and the Secret key, both of which the users receives directly from the Exchange.
The MoonBot terminal then receives data and information from the exchange’s API collected at several different access levels, including:
Public information (publicly accessible data related to trading in general):
The MoonBot terminal provides completely private storage of all your personal data!
The MoonBot team has absolutely no access to personal data, you are the only one controlling its security and have complete control over access to your details.
The MoonBot team are not able to withdraw, nor to move, any funds from your personal Exchange account or wallet.
You can therefore safely use the terminal for trading, receiving public information from the Exchange, and should you wish to share with others, the trading data on your account.
You therefore are the only person with control and access to your Exchange wallet, and can be completely assured of the absolute security of your private funds.
Lightning-fast Execution of the Orders on the Exchange and Order Status Update
Depending on the distance of the user from the exchange servers, the delay in order execution should not exceed 1 second. Theoretically, the delay can be reduced to a minimum intangible — 10–20 ms. Below is presented a very short extract(4 seconds in total) of the MoonBot log text file with brief explanations and highlights of the key features.
The MoonBot log text file with brief explanations and highlights of the key features.
Tick Chart. Display of All Orders on the Chart
Thanks to the API connection to the exchange, the terminal receives stream data of all filled orders on the exchange as soon as they were processed by the exchange servers and immediately displays them on the chart.
Thus, the visualization of the current state of the market is provided in real time with an accuracy of tens of milliseconds and as detailed as displaying each order on the chart.
Auto Trading on Signals
Fully automatic processing and trading off Telegram signals as well as parced TradingView alerts.
Automatic Detection of Market Conditions and Reaction to its Changes
Thanks to streaming data acquisition, the terminal monitors all available markets simultaneously, and is therefore able to react almost instantaneously as favorable trading possibilities are presented. And due to the minimal delay in the execution of orders, MoonBot responds to abnormal changes almost instantly.
Advanced Orders. Stop Loss, Take Profit, Trailing Stop
OCO orders (one cancels the other) are one of the most sought-after functions from both the Exchanges providing liquidity to the markets, and applications running on top of the exchanges. The modern Trader cannot trade without the basic “smart” functions and addons to traditional exchange orders and considers them to be the minimum necessary set in their armory.
One of the most important tools for Traders is to be able to place orders whilst practicing safe money management in order to mitigate against losses. One of the most important safety tools is to use a Stop Loss, which is especially important in volatile, low liquidity markets.
With MoonBot, the user can set a Stop Loss threshold (either as a percentage of the order price, or as a number of price points), which their strategy can accept should the price move in the opposite direction to that expected. When this threshold value has been reached, the order will be closed automatically.
Technically, a Stop Loss can be set up in two ways: either as a stop-limit order placed directly on the exchange at the same time as the initial position is opened; or as a function controlled in real-time by the MoonBot terminal itself. Additional types of conditional Stop Loss functions include:
At the moment, MoonBot has 13 types of strategies in-built (manual) using specific and well-proven algorithms (algorithmic trading or algo-trading).
Together these have more than 200 adjustable parameters that can be adjusted to optimize their profitability across the wide range of trending and ranging markets that occur.
MoonBot includes a successful and well-tested Trusted Management feature, in other words — Copy Trading:
Trust Management is successfully implemented and used by members of our community. The statistics of those TM Traders who share their results can be reviewed on the website — stat.moon-bot.com on the RatingTM tab.
During the two years of development of the MoonBot terminal, more than 30,000 copies have been registered and used by our Community of Traders.
Every day several thousand people trade cryptocurrencies using the MoonBot terminal, making daily approximately one hundred thousand manual and automatic transactions only on the leading crypto-currency exchange — Binance.
The existing community of traders is actively developing. The MoonBot project has its own active pages on popular social networks, in dedicated Telegram channels divided by topics, and also its own Trader’s forum available to subscribers.
Topics on the BitcoinTalk Forum
The current Support team is actively assisting users and resolving their issues through dedicated Telegram channels.
python ArmoryQt.py \ --satoshi-datadir=/BlockChain/chain20180414/blocks \ # <-----(where my bitcoind blocks live) --datadir=/ArmoryDataDi \ # <-----(this is instead of ~/.armory) --dbdir=/ArmoryDataDidatabases # <-------(again, non std. place used for Armory's databases.. my choice.)So, on the Desktop, after the initial "build databases"
apt-get update apt-get upgrade (<---took about an hour!) apt-get install autotools-dev apt-get install autoconfThen I followed the instructions exactly as I had done for my Debian Desktop machine, EXCEPT:
CONF_SWAPSIZE=400Then, REBOOT the Pi:
sudo shutdown -h -P nowOnce the compilation was done on the Pi, put the swap back, rebooted and created an Armory wallet.
./bitcoind -daemon -datadir=/BlockChain/chain20180414 -dbcache=400 -maxmempool=400
python ArmoryQt.py --ram-usage=4 --satoshi-datadir=/BlockChain/chain20180414/blocks --datadir=/ArmoryDataDi --dbdir=/ArmoryDataDidatabasesI know from bitter experience that doing a scan over the blockchain for a new wallet takes a looong time and a lot of CPU, and I'd like it to play nicely; not gobble all the memory and swap and run my 2xCPUs both at 100% for four hours...
TypeError: cannot concatenate 'str' and 'int' objectsIt didn't recognise the ram-usage and carried on, crippling my Debian desktop PC.
"free -h"I'd also be able to do a "sudo reboot now" if needed from here.
python ArmoryQt.py --ram-usage="4" --satoshi-datadir=/BlockChain/chain20180414/blocks --datadir=/ArmoryDataDi --dbdir=/ArmoryDataDidatabasesBut no, same error...
Loading Armory Engine: Armory Version: 0.96.4 Armory Build: None PyBtcWallet Version: 1.35 Detected Operating system: Linux OS Variant : ('debian', '9.4', '') User home-directory : /home/ Satoshi BTC directory : /BlockChain/chain20180414 Armory home dir : /ArmoryDataDi ArmoryDB directory : /ArmoryDataDidatabases Armory settings file : /ArmoryDataDiArmorySettings.txt Armory log file : /ArmoryDataDiarmorylog.txt Do wallet checking : True (ERROR) ArmoryUtils.py:3723 - Unsupported language specified. Defaulting to English (en) (ERROR) ArmoryQt.py:1833 - Failed to start Armory database: cannot concatenate 'str' and 'int' objects Traceback (most recent call last): File "ArmoryQt.py", line 1808, in startArmoryDBIfNecessary TheSDM.spawnDB(str(ARMORY_HOME_DIR), TheBDM.armoryDBDir) File "/BitcoinArmory/SDM.py", line 387, in spawnDB pargs.append('--ram-usage=' + ARMORY_RAM_USAGE) TypeError: cannot concatenate 'str' and 'int' objects
if ARMORY_RAM_USAGE != -1: pargs.append('--ram-usage=4') #COMMENTED THIS, SO I CAN HARDCODE =4 # ' + ARMORY_RAM_USAGE)Running it, I now have acknowledgement of the --ram-usage=4:
(WARNING) SDM.py:400 - Spawning DB with command: /BitcoinArmory/ArmoryDB --db-type="DB_FULL" --cookie --satoshi-datadir="/BlockChain/chain20180414/blocks" --datadir="/ArmoryDataDi" --dbdir="/ArmoryDataDidatabases" --ram-usage=4Also, even with ram-usage=4, it used too much memory, so I told it to quit.
ERROR - 00:25:21: (StringSockets.cpp:351) FcgiSocket::writeAndRead FcgiError: unexpected fcgi header versionBut that didn't seem to matter or corrupt the Armory Database, so I think it's ok.
if ARMORY_RAM_USAGE != -1: pargs.append('--ram-usage=1') #COMMENTED THIS, SO I CAN HARDCODE =1 # ' + ARMORY_RAM_USAGE) if ARMORY_THREAD_COUNT != -1 pargs.append('--thread-count=1') #COMMENTED THIS, SO I CAN HARDCODE =1 #' + ARMORY_THREAD_COUNT)So, as usual, I use my script and start this with: ./StartArm.sh
python ArmoryQt.py --ram-usage="ABCDE" --thread-count="FGHIJ" --satoshi-datadir=/BlockChain/chain20180414/blocks --datadir=/ArmoryDataDi --dbdir=/ArmoryDataDidatabases(this forces it to use my hard-coded values in SDM.py...)
(WARNING) SDM.py:400 - Spawning DB with command: /BitcoinArmory/ArmoryDB --db-type="DB_FULL" --cookie --satoshi-datadir="/BlockChain/chain20180414/blocks" --datadir="/ArmoryDataDi" --dbdir="/ArmoryDataDidatabases" --ram-usage=1 --thread-count=1Again, this is where it gets dangerous; Armory can gobble so much memory and CPU that the windowing environment can cease up. So I ssh to the machine and keep an eye on it with:
Armory. Created by Alan Reiner on 13 July, 2011. Forked by goatpig in February 2016. Armory is a full-featured Bitcoin client, offering a dozen innovative features not found in any other client software! Manage multiple wallets (deterministic and watching-only), print paper backups that work forever, import or sweep private keys, and keep your savings in a computer that never touches the ... Thanks for the info but I'm just gonna transfer the money. I'm not happy with Armory for the following reasons: 1) dependency on Bitcoin-Qt 2) Poor UX (eg: after sending money I have to wait for two screen changes and a potential popup before the transaction is done and none of this is messaged to the user) 3) Constant crashes 4) Bad update system (I was repeatedly prompted to update to 93 ... It's written in C++ and uses Bitcoin Core itself to read the data, so it's always 100% compliant with the latest Bitcoin release. I abstracted away the database functions, so you can implement "drivers" for any other DB system. I've been playing with it on MySQL but perhaps others would prefer Neo4J or Cassandra for nosql graph analysis. I am fairly new to Bitcoin, but one year ago, I made a Bitcoin address on Bitcoin-Qt, but I stopped using it, because the whole database downloading took so much space on my disk. I have my wallet.dat file, but I don't know, where can I use it. I tried Electrum, but it seems that the wallet.dat import doesn't work there. NOTE. On 3 FEB 2016, Armory project transitioned from etotheipi to goatpig as the lead maintainer.Consequently, for latest news and release please see btcarmory.com or the Bitcoin Talk discussion thread. BEST BITCOIN WALLET. Armory is the most secure and full featured solution available for users and institutions to generate and store Bitcoin private keys.
[index]          
Here is a tutorial how to import your old bitcoin wallet into a new wallet in easy steps. I was able to import 1.7 old forgotten bitcoin from 2013. I used Armory wallet to import my mini private keys but the process should be similar with other wallets that supports importing mini private key. This video is also available in Swedish: https ... Watch me walk you through getting your Armory and Bitcoin Core working in sync again. Armory Ver 96.2: https://btcarmory.com/0.96.2-release/ Bitcoin Core V 1... - How to transfer bitcoin TO an offline wallet. - And how to transfer bitcoin FROM an offline wallet. Prerequisites: - PC with an internet connection, running Ubuntu and Armory (see my other ... How to make an offline bitcoin wallet using Armory - Duration: 14:55. TheMetaTainment 38,239 views. ... Importing private key with Blockchain app - Duration: 0:35. Pluto BTM 6,079 views.