Troubleshooting Tips for Armory - Best Bitcoin Wallet Armory

The First-generation Terminal — MoonBot

The First-generation Terminal — MoonBot

Moonbot
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):
  • charts;
  • quotes;
  • orderbook;
  • real-time executed orders.
  • Authenticated information (unique to the users and which requires authentication access using the special keys): personal account status (wallet balances);
  • user transactions (such as the details of executed trades).
After receiving the various data information from the exchange, the terminal records these data in a local database for further processing and application.
Security Systems
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.
Tick 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.

https://preview.redd.it/rw6im5wl1m931.png?width=1095&format=png&auto=webp&s=0ce7e7287dae27a0a71970083435fa93e592e5b5
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.

https://preview.redd.it/3gsh12b42m931.png?width=1200&format=png&auto=webp&s=7f21bd7e7505f9bb5a95555cf355bb6f1f5efab4
Stop Loss
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:
  1. Additional and conditional Stop Losses – these are activated by a timer, and depend on the price reached. Thus Moonbot can raise the Stop Loss to a break-even point, or can be set to move upward to follow coin growth and to achieve higher profitability.
  2. BV/SV Ratio Stop Loss — this is a measure of buying/selling pressure and depends on the ratio of the volume of coin purchases compared against sales over a given time range. For example, if the number of sales exceeds the number of purchases, then this Stop Loss would be activated
  3. V-STOP — this is a stop which depends on the volume in the orderbook, where a price and volume level is set, which if broken will activate the Stop Loss.
  4. Trailing Stop — Trailing Stop is a General Stop Loss Management Tool. This very important feature allows the Trader to maximize profit in an automatic mode by following upward price movements, until the price reverses by a preset amount. At that stage the Stop Loss is activated.
    Take Profit
The Trader can fix the profit gained as the value of an asset increases in several ways:
  • By closing the position after a predefined profit percentage has been reached.
  • By remaining in the position, and setting the Stop Loss level to break-even, or to higher profit levels.

Algorithmic Trading
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.
https://preview.redd.it/rgm2d6z13m931.png?width=1084&format=png&auto=webp&s=521830b9386e2890620ace5d829f53c3a76ceeb3
Trusted Management
MoonBot includes a successful and well-tested Trusted Management feature, in other words — Copy Trading:
  • All trade actions from the Master Terminal are repeated on the Follower’s Terminal (slave terminal).
  • The Follower’s deposit remains securely in their own personal exchange account.
  • The Trusted Management feature does not have direct access to money, or to direct trading on someone else’s account, but manages only its own Exchange orders, simultaneously broadcasting encrypted messages to Followers terminals containing all Master actions.

https://preview.redd.it/h8ak7b4g3m931.png?width=1023&format=png&auto=webp&s=caf33dad55ad6b51ed9f1e44316df9182b875eff
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.
Community
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
  • bitcointalk.org/index.php?topic=2234450.0
  • bitcointalk.org/index.php?topic=2234198.0
    Websites
  • moon-bot.com — the official site of the MoonBot.
  • forum.moon-bot.com — MoonBot forum.
  • stat.moon-bot.com — trade statistics of the community members, TOP-50.
    Telegram Groups
  • t.me/moon_bot_crypto — the main RU-chat for communication.
  • t.me/Moon_Bot_Public — main ENG chat for communication and support.
  • t.me/MoonBotSettings — RU technical support chat.
  • t.me/moon_bot_kurilka — general RU chat.
    Telegram Channel
t.me/MoonBotNews — the latest news and updates.
Social Network
www.facebook.com/MoonBotTerminal
The current Support team is actively assisting users and resolving their issues through dedicated Telegram channels.
submitted by MoonTrader_io to Moontrader_official [link] [comments]

A Guide to Keeping Keys Offline Using Armory +rPi

Hi Redditors.
I am going to post in this thread my experiences in getting my Desktop (Debian) machine running Armory in watch-only mode, and coupling that with an offline Raspberry Pi (which holds my private keys) for signing the transactions previously made in watch-only mode.
I actually compiled Armory from source directly on my Pi. This guide is probably more for the bitcoin 'power user', as to run Armory online, and broadcast the signed transactions, you need to have a bitcoin full node running (bitcoind).
Basic requirements:
Aimed-for Setup:
I'll post the guide in digestible sections...

Section 1

I should begin by saying I installed source code from git, and got Armory to build the DB on my desktop initially, WITHOUT creating a wallet.. (This allowed me to debug what was going on a little!)
Go to Bitcoin.org, select Armory..
It leads to a Download from Git:
https://github.com/goatpig/BitcoinArmory/releases
Followed the procedure for Linux Debian verify code, compile, install, all straight-forward..
Began by running bitcoind, and telling Armory where to find it. This is the command I used, obviously it was all on one line and didn't include the arrows/explanations!:
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"
(NB the initial "Build Databases" took about 1.5h and my two CPUs were maxed the whole time, Temps up to 62C. Not ideal; Im not in a rush!)
I then wanted to import a watch-only wallet.
Before I did this, I took a full backup of the Armory data dir:
/ArmoryDataDi
(or ~/.armory in a default installation).
I'd hate to have to make Armory do another full sync with the bitcoind node!

Section 2

Next step: offline wallet (with Private Keys) is on a Raspberry Pi.
I downloaded the source and managed to compile it on the pi itself! :)
Though there were some gymnastics needed to setup the Pi.
My Pi is running Raspbian based on Wheezy.. quite old!
I did the following on the Pi:
apt-get update apt-get upgrade (<---took about an hour!) apt-get install autotools-dev apt-get install autoconf 
Then I followed the instructions exactly as I had done for my Debian Desktop machine, EXCEPT:
I had to increase the Pi's swap space. I upped it from 100Mb to 400Mb.
The compilation took 7 hours, and my poor SD card got a thrashing.
But after compilation, I put the Swap back to 100Mb and Armory runs ok with about 150Mb of memory (no swap needed).
Swap increase on the Pi:
use your favourite editor, and open the file /etc/dphys-swapfile
add/change the following line:
CONF_SWAPSIZE=400 
Then, REBOOT the Pi:
sudo shutdown -h -P now 
Once the compilation was done on the Pi, put the swap back, rebooted and created an Armory wallet.
I added manual entropy and upped the encryption 'time' from 250ms to 2500ms - since the Pi is slow, but I'll be happy to wait for more iterations in the Key Derivation Function.
Once the wallet was created, it obviously prompts you for backup.
I want to add a private key of my own (i.e. import), so don't do the backup until this is over.
I import my Private Key, and Armory checks that this corresponds to a Public Key, which I check is correct.
This is the point now where the Pi storage medium (e.g an SD card) has to be properly destroyed if you ever get rid of it.
I had thought that now would be a good time to decide if your new wallet will generate Segwit receiving addresses, and also addresses used to receive 'change' after a transaction..
But it seems Armory WON'T let you switch to P2SH-P2WPKH unless your Armory is connected to a node offering "WITNESS" service.
Obviously, my Pi is offline and will never connect to a node, so the following will not work on the Pi:
NB: I thought about setting this on the Debian "watch-only" wallet, but that would surely mean doom, as the Pi would not know about those addresses and backups might not keep them.. who knows...
So, end result:- no segwit for me just yet in my offline funds.

--If anyone can offer a solution to this, I'd be very grateful--

Section 3

Ok, now this is a good point to back up your wallet on the Pi. It has your imported keys. I choose a Digital Backup - and put it on a USB key, which will never touch the internet and will be stored off-site. I also chose to encrypt it, because I'm good with passwords..
NB: The Armory paper backup will NOT back up your imported private keys, so keep those somewhere if you're not sweeping them. It would be prudent to have an Armory paper backup anyway, but remember it will likely NOT help you with that imported key.
Now for the watch-only copy of the wallet. I want to get the "watch-only" version onto my Desktop Debian machine.
On the Pi, I created (exported to a USB key) a "watching-only" copy of my wallet.
I would use the RECOMMENDED approach, export the "Entire Wallet File".
As you will see below, I initially exported only the ROOT data, which will NOT capture the watching-only part of the Private Key I entered manually above (i.e. the public Key!).
Now, back on the Debian Desktop machine...
I stopped all my crontab jobs; just give Armory uninterrupted CPU/memory/disk...
I also stopped bitcoind and made a backup prior to any watch-only wallet being imported.
I already made a backup of Armory on my Desktop, before any wallet import.
(this was needed, as I made a mistake.. see below)
So on the Debian Desktop machine, I begin by firing up bitcoind.
my command for this is:
./bitcoind -daemon -datadir=/BlockChain/chain20180414 -dbcache=400 -maxmempool=400 

Section 4

I try running Armory like this:
(I'm actually starting Armory from a script - StartArm.sh)
Inside the script StartArm.sh, it has the line:
python ArmoryQt.py --ram-usage=4 --satoshi-datadir=/BlockChain/chain20180414/blocks --datadir=/ArmoryDataDi --dbdir=/ArmoryDataDidatabases 
I 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...
So... I aim to run with --ram-usage=X and --thread-count=X
(For me in the end, X=1 but I began with X=4)
I began with --ram-usage=4 (<--- = 4x128Mb)
The result is below...
TypeError: cannot concatenate 'str' and 'int' objects 
It didn't recognise the ram-usage and carried on, crippling my Debian desktop PC.
This is where it gets dangerous; Armory can gobble so much memory and CPU that the windowing environment can cease up, and it can take over 30 minutes just to exit nicely from bitcoind and ArmoryDB.
So, I ssh to the machine from another computer, and keep an eye on it with the command
"free -h" 
I'd also be able to do a "sudo reboot now" if needed from here.

Section 5

So, trying to get my --ram-usage command recognised, I tried this line (added quotes):
python ArmoryQt.py --ram-usage="4" --satoshi-datadir=/BlockChain/chain20180414/blocks --datadir=/ArmoryDataDi --dbdir=/ArmoryDataDidatabases 
But 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 

Section 6

So, I edit the Armory python file SDM.py:
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=4 
Also, even with ram-usage=4, it used too much memory, so I told it to quit.
It took over 30 minutes to stop semi-nicely. The last thing it reported was:
ERROR - 00:25:21: (StringSockets.cpp:351) FcgiSocket::writeAndRead FcgiError: unexpected fcgi header version 
But that didn't seem to matter or corrupt the Armory Database, so I think it's ok.
So, I get brave and change SDM.py as below, and I make sure my script has a command line for --ram-usage="ABCDE" and --thread-count="FGHIJ"; the logic being that these strings "ABCDE" will pass the IF criteria below, and my hardcoded values will be used...
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
(which uses command line:)
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...)
So, this is the command which it reports that it starts with:
(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=1 
Again, 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:
"free -h" 

Section 7

So, on the Debian Desktop PC, I inserted the USB stick with the watch-only wallet I exported from the Pi.
Start Armory...
Import "Entire Wallet File" watch-only copy.
Wait 4 hours..
YAY!!!
After running Armory for about 30m, the memory usage dropped by 400m... wierd...
It took ~2 hours to get 40% completion.
After 3.5 hours it's almost there...
The memory went up to about 1.7Gb in use and 900Mb of Swap, but the machine remained fairly responsive throughout, apart from a few (10?) periods at the start, where it appeared to freeze for 10-30s at a time.
(That's where my ssh session came in handy - I could check the machine was still ok with a "free -h" command)
Now, I can:
Create an unsigned transaction on my Desktop,
Save the tx to USB stick,
Move to the Pi,
Sign the tx,
Move back to the Desktop,
Broadcast the signed tx.

Section 8

My initial Mistake:
This caused me to have to roll-back my Armory database, using the backup. so you should try to avoid doing this..
On the Pi, I exported only the ROOT data, which will NOT capture the watching-only part of the Private Key
It is RECOMMENDED to use the Digital Export of Entire Wallet File from the Pi when making a watch-only copy. If you just export just the "ROOT data", not the "Entire Wallet File", you'll have problems if you used an imported Private Key in the offline wallet, like I did.
Using the ROOT data text import, after it finished... my balance was zero. So,. I tried a Help->Rescan Balance (Restart Armory, takes 1minute to get back up and running) No Luck. Still zero balance.
So, I try Rescan Databases.. This will take longer. Nah.. no luck.
So, I tried again, thinking it might be to do with the fact that I imported the text "root data" stuff, instead of following the (Recommended) export of watching-wallet file.
So, I used my Armory backup, and wound back the ArmoryDataDi to the point before the install of the (zero balance) wallet. (you should not need to do this, as you will hopefully use the RECOMMENDED approach of exporting the "Entire Wallet File"!)
submitted by fartinator to Bitcoin [link] [comments]

Disk Digger Pro Apk || DiskDigger Importance || Recover Lost Files

In the Present scenario, Technology is growing too fast and we all are experiencing that our smartphone, PC, and Laptops carrying various files with the help of SD cards and internal memory. We will think that our files are in very secure places but if any file deleted unexpectedly then what you will do?. Don't worry, I already told you that tech is growing as fast as it can. Here I'm going to discuss the best data recovery services aka (DiskDigger) which are a perfect example of it. Let's go down to get more details of DiskDigger( Deep file recovery from any drive).
DiskDigger is a tool which can recover deleted files like photos, documents, music, video and much more.
DiskDigger Features:
DiskDigger can recover lost files from most types of media that your computer can read: hard disks, USB flash drives, memory cards, CDs, DVDs, and floppy disks. (Note: Make sure that you have to connect your device with a USB port to recover lost data from Android and IOS devices ). And one more important thing is you have to download the diskdigger app on your android phone to recover lost files. Suppose if your Android device uses a microSD card for saving the data, please remove the card and connect it directly to your PC using a card reader, so that you can scan it directly using DiskDigger for Windows.)
DiskDigger has two processes which you have to choose every time while scanning a disk. These methods are named as “dig deep” and “dig deeper“.
Dig Deep:
Dig Deeper:
Advanced Features
To find more information go through remaining articles in our site like hard drive data recovery, SD card data Recovery, Android Data Recovery, USB flash drive data recovery, Linux Data Recovery etc.
submitted by diskdiggerproapk to u/diskdiggerproapk [link] [comments]

Bitcoin client comparison? Ease of use, functionality, security etc..

Hey everyone,
I've recently started using bitcoins, and been trying to figure out the best way to store them.. There are a bunch of desktop clients available, each with it's ups and downs, supporting different features, and using different amount of resources..
I wanted to find a nice overview of them all, but so far I'm not finding anything that I wanted to know.. So I think we should have some kind of wiki page, that describes them in more details. Explains how to start using each of them, and how to ensure it's safe.
For example, to try and secure my wallet files, I'm storing them in a TrueCrypt volume, that's archived to the cloud. This way they are backed up to multiple locations, incase my machine dies, and are also encrypted, in case one of the machines is compromised! I'm not sure if that's overkill or not :)
I thought I'd start with a short write-up of my opinions on some of the clients and my impressions of them. It's by no means a comprehensive review (that would take a lot more space than a single reddit post). All of this is just a subjective view on each of the clients.. I hope more people will add to it, maybe even compoling a nice and informative comparison of all the popular clients!
  1. Bitcoin-QT: The official client. Somewhat basic in functionality, advanced functions (like backing up the private key) available through the "debug" window., but works well for a lot of people.. You can backup the wallet.dat file in the TrueCrypt volume to secure the coins, but the client will store the main working copy of the wallet file in %APPDATA% in Windows - leaving it potentially compromised, unless you encrypt the wallet file (part of the client's functionality). There's no obvious way to change the storage location.
    The downside (upside for some?) of the client is that it stores the whole blockchain.. (almost 15GB atm) Initial synchronisation takes a lot of time.. If you don't use it for some time, you'll have to synchronise again, which takes time (and CPU resources btw)..
    At the end of the day, the wallet is as secure as your machine is. No support for paper wallets / watch-only wallets / offline storage, transactions.. But for basic use - it works perfectly fine.
  2. Bitcoin Armory: A popular powerful client, runs "on top" of Bitcoin-QT, which means the blockchain is also stored on the local drive.. On top of that, the Armory client will also build a local database to manage it, which means it needs more storage on it's own.. (at the moment, that's an extra 16GB on top of the blockchain!). Also, the synchronisation status is not very helpful, just saying the % synchronised.. At least Bitcoin-QT states how many weeks/days you are behind, so you can somewhat estimate how soon the sync will work.
    The Armory client supports multiple wallets, compared to the official client, which can be stored separately. The wallets use (correct me if I'm wrong?) a deterministic key to generate the private keys, which means if you backup your wallet in cold storage - you can restore it at any point, and restore all the new addresses generated after the backup - a very useful feature. The Armory client has more advanced functionality like paper backups (described above), offline wallets and offline transactions, and a lot more.. Some features are missing, like importing watch-only addresses. You can though create a watch-only backup of a wallet, and import that on a different machine, but if you only have an address - not supported atm.
    The client seems rather powerful, but also feels a bit clunky and hard to use.. Some functionality is missing, and just strange (not all private key formats are supported.. even if most other clients have no problems with them)
  3. MultiBit: A lite bitcoin client, that doesn't store the whole blockchain locally. This makes it a lot easier to start using, even on a new machine. It will only synchronise a part of the blockchain that is relevant for a specific address, which means you save on both time and storage when using it, but it can be (potentially, but quite unlikely) compromised, if the only nodes it can see are rogue.
    It also supports multiple wallets, you can select where to store the wallet files, and they can be password protected as well. You can store them on a TrueCrypt volume, to secure it even more. The app is still relatively simple to use, while providing more functionality than just the basics.
    Compared to Armory and Bitcoin-QT, you can also create a portable installation, which can be stored on a USB key / True Crypt volume along with the key files.
  4. Electrum: This is one of the clients I've hardly used so far.. It has a full and a portable version! With the portable version I can store they keys where I want, and keep them secure as I see fit. As MultiBit, it doesn't store the full chain, but instead will use a server to keep and manage the blockchain. But nothing is stopping you from running your own electrum server and connecting to it, if you're worried.
    The client seems rather simple, but powerful at the same time. Same as Armory - it will create a seed that will be used to generate addresses. The nice thing is that it will generate multiple receiving addresses, and will also maintain change addresses, which (if I'm right) means that each transaction will not reuse the same address twice, unless you force it to. My only gripe so far with it is that it's the only client so far where you can't send to multiple addresses in one transaction, forcing only a single recipient per transaction.. I hope that'll change in the future :(
submitted by artiomchi to Bitcoin [link] [comments]

The next big thing - THE NEW INTERNET

FreeSpeechMe-SPECIFIC IMPROVEMENTS WE PLAN TO DO:
Hide nmcontrol/namecoind windows on Windows
GNU/Linux users don't see the terminal windows for backend software; Windows users shouldn't be bothered by them either.
Don't try to visit .bit websites when blockchain isn't downloaded
Right now, visiting a .bit website with an incomplete blockchain will use an older version of that name's data. Usually this results in a failure to load the page with no good explanation of what's wrong, but in certain rare cases it could also hypothetically result in security issues such as hijacking. A better version of FreeSpeechMe should refuse to use incomplete blockchains.
Facilitate non-Firefox usage
FreeSpeechMe uses a networking method, HTTP, which is specific to website traffic. Replacing it with a different method, SOCKS, would make it much more flexible, so you could use Dot-Bit for non-website Internet applications such as SSH. It should also be possible to route other web browsers such as Chromium through FreeSpeechMe. FreeSpeechMe should support being installed as a standalone application for users who don't use Firefox (although obviously Firefox will remain the main method of installation).
Improvements for anonymous browsing
Right now FreeSpeechMe supports routing its traffic through anonymization proxies such as Tor and I2P (if they are installed), but it is not compatible with TorBrowser, so while attackers generally can't see your location or IP address, they can deduce that different activities you do online may have come from the same person. FreeSpeechMe should be improved to function in TorBrowser, which would prevent linkage of different online activities.
Improvements for anonymous hosting
FreeSpeechMe supports Tor and I2P hidden services (if the user has Tor or I2P installed), but does not support Freenet, OnionCat, GarliCat, or other anonymous hosting networks. This should be improved.
Support for next-gen TLS specification
FreeSpeechMe is using a method of specifying certificates to prevent hijacking which is deprecated in the Dot-Bit specification. While this method remains very secure, the newer specification has more features, and FreeSpeechMe should implement it.
HTTPS enforcement
Websites which claim to support HTTPS in their domain record should automatically be loaded in HTTPS, even if the user accidentally forgets the "s", to prevent hijacking in such cases. (Note for geeks: this is like the HSTS specification, but works even for sites you haven't visited before.)
Intelligent Redirecting
Websites that want to support Dot-Bit should be able to do so without changing their server configuration, and instead have FreeSpeechMe make the server think the preexisting domain is being requested. The user would still see the Dot-Bit URL in Firefox, and unlike iframe-based methods, the URL displayed in Firefox would change accordingly as the user clicks links..
Fix HTTP protocol bugs
Unencrypted HTTP Dot-Bit websites occasionally have odd behavior in FreeSpeechMe (sometimes manifesting as links not working properly); this is most frequently seen in WordPress websites. While we strongly encourage the use of HTTPS (which isn't subject to these bugs), we still want to fix the bugs with HTTP websites.
Round-Robin Load Balancing
Some large websites use multiple server IP addresses for a single domain. FreeSpeechMe should be able to randomly choose one.
OTHER NAMECOIN SOFTWARE IMPROVEMENTS
Some of this is possibly out of the scope of this one Indiegogo campaign, depending on funds raised. But these are things we're very interested in helping implement:
Rebase on the latest Bitcoin code
Namecoin is based on an outdated version of Bitcoin (0.3.x). We should rebase on a current release. We inquired with a well-qualified and well-respected contractor (who developed Namecoin-Qt) about how much this rebase would cost; the estimate was around $17,000-$35,000 US. Spending that much on one project would be out of the realm of this first campaign. However, it may be possible to reduce this cost significantly by rebasing on a codebase other than Bitcoin, such as libcoin.
Improve scalability
Namecoin currently requires having the entire blockchain for good security. While the 1.6GB blockchain isn't a large concern right now, future scalability requires that clients be able to securely resolve names without possessing the blockchain. There is a proposal for this called SPV+UTXO.
Automatic renewal of names
Losing your names because you forgot to renew them is a problem.
Names should be able to be renewed automatically. Preferably without decrypting the wallet each time the name is renewed, and maybe without even needing your client to be open when it renews. Any solution must be trust-free.
Cold storage of Namecoin name keys
To update a Namecoin name, the keys must be decrypted on a computer with Internet access; this could be a security risk if malware is installed on that computer. To fix this, cold storage should be used, as is possible with Bitcoin.
This is in two parts: (1) port the Armory client to Namecoin (this allows transactions to be signed offline), and (2) allow a cold-storage name to be used as a revocation key for a hot-wallet name (this is called the "import" field).
Optimize Speed
Dot-Bit is already much faster than other top-level domains for both name lookup and name propagation. However, it can be made even faster.
We estimate that pre-cached name lookup time can be decreased by 2- to 5-fold in some cases, uncached name lookup time can be decreased significantly, name update propagation can be reduced from 40 minutes to under 1 minute, and blockchain sync time can be reduced significantly.
Android support
Namecoin software currently does not support Android; this situation should be improved.
Better blockchain anonymity
Like Bitcoin, Namecoin can keep the location and IP address of name owners anonymous (if used with Tor), but the various activities of name owners can be linked by an attacker. This should be improved, e.g. by implementing Zerocoin.
Better blockchain privacy
Some name owners may wish their records to not be publicly accessible; encryption would improve this situation.
Decentralized website single sign-on
Namecoin can be used to log into websites in a secure way without needing a password (protecting people from database leaks or cracked passwords without trusting a third party such as "all your data are belong to us" systems like Facebook); this is implemented as the NameID library by domob. Unfortunately, this library is not easy for non-programmers to integrate with existing websites. Plugins should be created for major website backends such as Drupal, phpBB, WordPress, and SMF, to allow trust-free NameID sign-on to be as easy as checking a box.
Automated builds
Namecoin software should support automated builds and testing so that our developers and testers can work more efficiently. The builds should also be deterministic (as Bitcoin and Tor are doing) to improve security.
Offline signing of static websites
Verifying signatures of static websites against the blockchain would prevent hijacking even if a web server is completely compromised.
SSH client integration
Log into your servers remotely without trusting your network or manually verifying fingerprints, using the same anti-hijacking features that FreeSpeechMe first implemented.
submitted by kitthecar to Bitcoin [link] [comments]

Armory 0.90 keeps crashing in Ubuntu 13.10

Armory had been working fine for me up until a week ago when it crashed while loading up. I restarted it and had to close the Bitcoin-QT process in the background, Armory then appears to be loading until it gets to the scanning database part, then the GUI goes dark (like it does when the system is running out of memory) before the program disappears. When I restart it I have to go through the same process again.
On the Armory site it said to try deleting the database folder from /home//.armory - I done this and now all that happens is the program crashes even sooner, about 3% into building database.
Any help would be greatly appreciated! I do have a paper backup, so I'm guessing I just have to uninstall the program and then reinstall and import wallet?
submitted by ArmoryQuestion to BitcoinWallet [link] [comments]

Bitcoin Armory Troubleshooting Offline Node - YouTube Bitcoin Armory Walk Through Sending Bitcoin - Armory Guide How to import bitcoin paper wallets to your client Watching Only Wallet

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] [2157] [17212] [32539] [19309] [12549] [817] [4863] [23477] [5981] [6689]

Bitcoin Armory Troubleshooting Offline Node - YouTube

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.

#