bitcoin core - get Armory to use an existing blockchain ...

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, select Armory..
It leads to a Download from Git:
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 \ --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:
(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:
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 -
Inside the script, it has the line:
python --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 --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) - Unsupported language specified. Defaulting to English (en) (ERROR) - Failed to start Armory database: cannot concatenate 'str' and 'int' objects Traceback (most recent call last): File "", line 1808, in startArmoryDBIfNecessary TheSDM.spawnDB(str(ARMORY_HOME_DIR), TheBDM.armoryDBDir) File "/BitcoinArmory/", 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
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) - 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 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: ./
(which uses command line:)
python --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
So, this is the command which it reports that it starts with:
(WARNING) - 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..
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]

Armory Wallet Has Failed Me! Can I recover BTC?

So I opted to migrate from coinbase to a local wallet.
Naturally, I download Armory and shoot it a send for 1BTC. 225 confirmations on the SEND, but wallet never receives it.
Turns out, running Armory wallet has been corrupting my database. Every time I run it a background process it spawns causes Bitcoin-QT to fail.
I've tried uninstalling and re-installing bitcoin, armory wallet three times. I've deleted my bitcoin directory in %appdata%, ensured downloads are never interrupted.
Is there any way at all for me to recover the BitCoin I sent to armory wallet provided I can never get armory wallet to work correctly?
Any help appreciated. Here is the errors:
2015-08-21 14:48:15 init message: Activating best chain... 2015-08-21 14:49:23 Corruption: block checksum mismatch 2015-08-21 14:49:23 *** System error while flushing: Database corrupted
submitted by andhof-mt to Bitcoin [link] [comments]

Just sent BTC to myself (from one wallet to another) but it's not showing up at all in my new armory wallet. It's all synched and it's been 10 hours. What happened?

Edit: Could be related to the bitcoin core wallet (the first thing I installed, the full thing, it took 3 days to sync) eventhough I never used it. When I open bitcoin core, it gives me an error that it can't find a directory. A similar error happens when I open armory at the same time.
Edit 2: Problem solved, thanks everyone for the help. For the record, armory wasn't fully synched. For some reason it only reached around 460,000 blocks, even after several rescans. I finally just tried a "rescan and rebuild databases" from the help menu and now the blocks are at 473,000+ and the coins appeared in my wallet. :)
submitted by largonauta to Bitcoin [link] [comments]

BCH on MacOS

Time has come to be able to move and use my BCH. Since I used Armory before the fork, and Armory will need a full node as a backend, I will install BitcoinABC to fulfill that role.
But when I go to and click Download, two things worry me. In the osx download directory there are three downloads, and it is not clear which to use. The files bitcoin-0.14.6-osx-unsigned.dmg and bitcoin-0.14.6-osx-unsigned.tar.gz are probably the same delivered in two ways, I am fine with that. But I do not like the 'unsigned' part of the name. MacOS signature security is probably not perfect, but it is better than nothing. Lacking that, why is there not a PGP signature that I can download? What is my guarantee that the files on the site have not been altered since they were uploaded?
I then tried to download the third file, bitcoin-0.14.6-osx64.tar.gz hoping it at least contained a signed app. But the contents of that one looks like something aimed for Linux, it is certainly not a MacOS app.
Any advice?
submitted by gangtraet to btc [link] [comments]

Colored coin client preview #1 (based on Bitcoin Armory)

I think it's already good enough for people to play with it. (Although certainly it's not ready for anything serious.)
For people who are not familiar with concept, colored coins is a technology which allows people to represent arbitrary tokens (e.g. issue private currencies, stocks, bonds, etc.) using small quantities of bitcoins. It is interesting because it would allow us to create decentralized and secure markets. (As decentralized and secure as Bitcoin itself, at least in theory.) See here.
Notes about current release:
Windows binaries:
There are no Linux binaries, but it's really easy to build it on Ubuntu or Debian:
(Note: if you're already using Armory, it is a good idea to hide you ~/.armory so it won't be seen by this experimental Armory mod. Or, perhaps, just don't run this experimental mod.)
Before you run it, make sure that bitcoind or Bitcoin-Qt is running and fully sync'ed. Armory takes up to 10 minutes to start (this version is slower because it additionally scans for colored transactions) and requires ~ 1 GB of RAM.
At start it will offer to create a wallet, do not enable encryption, otherwise issuing colored coins won't work.
Send some bitcoins to this new wallet, 0.02 BTC is probably enough to issue some colored coins and to pay for tx fees.
There is a drop down to choose color. Balance is displayed for a currently chosen color (i.e. if you chose TESTcc it will show how many TESTcc units this wallet owns), and when you send coins you send coins of that color.
Initially 'uncolored' is selected, it means normal BTC. This drop down also has TESTcc ("test colored coins") and "All colors" (this mode is just for debugging, you cannot send coins in this mode).
Here's what you can do now:
  1. Ask somebody to send you TESTcc. (We want to make it automatic, Satoshi Dice style, but unfortunately that code isn't quite ready.)
  2. Find and install other color definitions.
  3. Issue your own colored coins and send them to somebody who wants them. (LOL.)
Let's start from option #3. There is 'Hallucinate' menu. (It is called 'hallucinate' because colors do not exist on blockchain level, it is a client-side convention.) Choose 'Issue colored coins'. Likely all you need to change is name, but you can tweak satoshi-per-unit and number of units if you want.
When you click Issue it will create a new transaction (using your uncolored BTC) and will create a color definition. Optionally it will also upload your color definition to color definition registry. (This registry runs on my server, it might be down.)
You should note ColorID, this is how other people can refer to these coins (name is ambiguous).
You can now choose this new color in drop down and it will show your balance. (E.g. 1000 units.)
Now you'll perhaps want to send these coins to somebody. That person would need to install your color definition first. If you send colored coins without warning they might be lost, i.e. mixed with uncolored ones. For same reason it makes no sense to send them to wallet which isn't color aware.
For example, you can post on some forum:
I've issued LOLwut coins (ColorID: 36738fe78a443656535503efb585fee140a37d54), each unit represents a bond with face value of 0.1 BTC payable by me, Trololo, via buy back. I promise to buy back all bonds in a month.
Now people who are interested in this LOLwut coin issue will copy ColorID, paste it into Hallucinate > Download color definition dialog, and if this color definition is published it will be downloaded and installed. Armory restart is required to complete installation.
After installation that person will be able to see these LOLwut coins.
Note that if you do not trust my registration server, you can publish color definition yourself: go to ~/.armory/colordefs, find 36738fe78a443656535503efb585fee140a37d54.colordef and upload it to your web server. Then you can give people URL like and they can download it by URL.
Or they can just obtain this file by any means and copy it to ~/.armory/colordefs directory. It is decentralized, nobody can prevent you from issuing colored coins.
I think that's all. There is also Hallucinate > Manage color definitions dialog, but I hope it's easy to figure out how it works.
We are working on improved version, particularly on p2p exchange feature.
I've set up an IRC channel for people to talk about trying out colored coins: #colored-coins-otc on Freenode.
submitted by killerstorm to Bitcoin [link] [comments]

Help needed with Bitcoin Cash and Armory Wallet.

I had a couple of bitcoins in an armory wallet from about 3-4 years ago and after the split I bought a Ledger Wallet and sent bitcoins in it, but encountered problems with bitcoins from the bitcoin cash chain.
I found a discussion on bitcointalk and tried to follow the instructions but I'm having trouble with it.
So far I installed Bitcoin Unlimited version of Bitcoin Cash and in the bitcoin directory settings of Armory wallet I indicated the directory where bitcoin unlimited stored the blockchain.
After that I rescanned and rebuilt the database the armory client connects to the bitcoin cash network and shows the correct amount of bitcoin but I am unable to send them to the Ledger Wallet. One of the settings is not there.
I'm sure that I skipped at least a step because in the first link they talk about a BCH signer and I dont know what it is.
Can anyone who encountered the same problem or knows something about this help me out, please.
Thank you.
submitted by Future_Me_FromFuture to btc [link] [comments]

Is this normal? Armory being very unstable so far.

Among many others looking to better understand bitcoin as a whole, I decided to buy a small amount and test a few things. Namely simple transfers, offline wallets, etc.
I ended up going with Armory as I liked the amount of videos/learning tools available on their site to operate the program. The videos are out of date in several areas, but it helped to get a general grasp of things.
So running Win10 64-bit, i5/8Gb/SSD 100Mb cable, Armory has crashed four times so far after building the database for three hours or so each time. The first time it crashed I re-opened and it went to the "Connected" state and appeared to be done. I created a wallet and initiated a transfer from my online wallet to my Armory wallet. The transaction showed verified on the site, but my local Armory wallet still showed 0.0. I closed and re-opened Armory and it started "Building Databases" again, which brings me back to the same old ~3hr per crash loop.
FWIW, the blocks directory in bitcoin-core gets bigger each time, and now sits at 55Gb (obviously not done yet). I didn't know how large this should have been at first or I would have waited to transfer. My question is, did I miss a step here? It seemed pretty straightforward at the time, download Armory, install bitcoin-core, allow to build?
submitted by ClutchGP to BitcoinBeginners [link] [comments]

How do I install Bitcoin Core rc 0.10.0 on Ubuntu 14.04?

I installed 0.9.x by doing this:
$ sudo apt-add-repository ppa:bitcoin/bitcoin $ sudo apt-get update $ sudo apt-get install bitcoin-qt 
I downloaded "bitcoin-0.10.0rc3-linux64.tar.gz" from
What do I do now?
EDIT: Solved!
Download the above mentioned .tar.gz to "Downloads"
Right-click on the file, "Extract here".
Copy the files into the ~/usr directory. This directory is write restricted, so you must open the terminal and write:
$ sudo cp -r /home/USERNAME/Downloads/bitcoin-0.10.0/bin /us $ sudo cp -r /home/USERNAME/Downloads/bitcoin-0.10.0/include /us $ sudo cp -r /home/USERNAME/Downloads/bitcoin-0.10.0/lib /us 
Open Bitcoin Core and it's now 0.10.0 !
EDIT2: To install armory_0.92.99.5-testing_ubuntu-64bit.deb download it through the armory secure downloader. If you do not want to, download it here:
Open terminal.
$ cd Downloads $ sudo dpkg -i armory_0.92.99.5-testing_ubuntu-64bit.deb python-twisted python-psutil python-twisted-conch python-twisted-mail python-twisted-lore python-twisted-names python-twisted-news python-twisted-runner python-twisted-words python-pyasn1 
submitted by Slipping_Tire to Bitcoin [link] [comments]

Tried to update Armory, lost my wallet?

Hi A few hours ago I read some posts on Bitcoin talking about BIP148 and how every node should be updated to support it (or whatever, ima noob). Not having a clue what to actually do, I decided to check on Armory's website if there were any recent versions (no auto-update?) and there was. So I downloaded and installed it. I read in their FAQ that my wallet and stuff like that wouldn't be compromised by updating the software, as the user information is stored in another directory. But when I launched Armory I was surprised to see that I had to download the whole blockchain back. Then I realized that I had moved the 100+Gb file on my second hard drive because the main one is a SSD (with less storage capacity). But I had forgotten how to tell Armory to use that directory. Anyway I figured it out and now apparently I'm "online" when I start Armory, but I get an error message: Armory failed to spawn the DB!
Now I have 2 problems: - this error message when I launch Armory - I imported my wallet from the older version of Armory but it says 0.0 BTC (I had 0.1 BTC on this wallet) HOW DO I RECOVER ???
Thanks and sorry for being a noob. I'm trying to invest my spare money in BTC while also helping by being a full node
submitted by edgar01600 to BitcoinBeginners [link] [comments]

armory install question

I installed bitcoin-qt onto my G drive using -datadir, when i install armory i installed it on the G drive and pointed it to the bitcoin-qt directory but it still puts the database on my C drive in appdata. My C drive is a relatively small SSD that is almost full now, I would like to have the databases on the G drive. Is there a way to do this?
submitted by gaben67 to Bitcoin [link] [comments]

Wallet security.

Hello all, I'm new to Reddit but have been following this subreddit for a little over a week. I thoroughly enjoy the information that everyone has contributed.
With that being said, I am very excited to join the bitcoin community. I have a small transaction to start off with pending at coinbase.
My concern is that I have taken such drastic steps to secure my offline wallet that I will be a burden to recover it in the event that I lose the original data file.
Here are the steps that I have taken.
Installed linux on an offline machine. Logical volume of offline machine is encrypted. Strong user password. Home directory where wallet.dat is stored is also encrypted. Armory wallet encrypted. Armory wallet digital backup stored in Truecrypt file container on new USB flash drive. Flash drive to be placed in safety deposit box.
Am I just being paranoid or is this overkill? I was also thinking of keeping another copy of the USB flash drive in a fireproof safe at home.
submitted by jsrob to Bitcoin [link] [comments]

How do I install Bitcoin Core rc 0.10.0 on Ubuntu 14.04?

I installed 0.9.x by doing this:
$ sudo apt-add-repository ppa:bitcoin/bitcoin $ sudo apt-get update $ sudo apt-get install bitcoin-qt 
I downloaded "bitcoin-0.10.0rc3-linux64.tar.gz" from
What do I do now?
EDIT: Solved!
Download the above mentioned .tar.gz to "Downloads"
Right-click on the file, "Extract here".
Copy the files into the ~/usr directory. This directory is write restricted, so you must open the terminal and write:
$ sudo cp -r /home/USERNAME/Downloads/bitcoin-0.10.0/bin /us $ sudo cp -r /home/USERNAME/Downloads/bitcoin-0.10.0/include /us $ sudo cp -r /home/USERNAME/Downloads/bitcoin-0.10.0/lib /us 
Open Bitcoin Core and it's now 0.10.0 !
EDIT2: To install armory_0.92.99.5-testing_ubuntu-64bit.deb download it through the armory secure downloader. If you do not want to, download it here:
Open terminal.
$ cd Downloads $ sudo dpkg -i armory_0.92.99.5-testing_ubuntu-64bit.deb python-twisted python-psutil python-twisted-conch python-twisted-mail python-twisted-lore python-twisted-names python-twisted-news python-twisted-runner python-twisted-words python-pyasn1 
submitted by Slipping_Tire to BitcoinBeginners [link] [comments]

My solution to a secure wallet [WARNING: Don't assume this is safe against hackers or yourself. I'm posting this as an idea for the community, and for any security experts who can find weak points in the security of it.]

I was looking for a safe offline wallet, and here is my current idea, and what I will probably use for now. If you see issues with it, or want to try your hand at hacking it, go for it. What I am sharing doesn't yet include my wallet info so there isn't anything to be stolen I hope.
Backstory: I have a CR-48 that I installed InsydeH20 BIOS on which lets me boot from USB. I also have a bootable tails distribution on a flash drive with an encrypted, persistent data store. Anything not in the persistent directory gets wiped every time.
Strengths of tails: Does its best to avoid using any hard drive. It does everything in ram, and takes the extra step of trying to overwrite all ram when you shut down.
What I did: I added several utilities in the /home/ directory in the ISO that can be useful for bitcoin wallets. What I plan on doing is keeping my CR-48 always offline. I will generate a wallet with this distribution. DO NOT KEEP THE WALLET ANYWHERE OTHER THAN THE PERSISTANT STORAGE FOLDER or you could lose your coins. Always keep a backup too. I just write mine down so I don't need to worry about trustworthiness of a printer.
(aside: dwarf fortress was added to the ISO just to provide more random data. It can be deterministic too. A seed will be able to produce a deterministic history of events in the fictional world that will consist of several thousand famous people and their actions through life. It takes several hours to generate, so it makes brute forcing less feasable)
At the moment I don't have much on there, but have the Armory client. I plan to generate the wallet there, keep backups in the encrypted persistant storage part of the flash drive and a paper backup, and create watch only wallets for my always online computers. Then if I need to make a transaction I can boot my distro, restore from a backup of my wallet, sign the transaction, and broadcast it on my online computers.
Does anyone see any points I could be attacked? I'm not sure how the persistant data section is encrypted, but assuming a strong password and encryption algorithm, even if the flash drive is stolen my coins should be safe right? Since the distribution boots the same way every time, can I be assured that there isn't any malicious software able to steal anything?
Anyway, the security is interesting to me, and this is my current idea for it. I wouldn't trust custom distributions from people I didn't know, so its up to you if you want to give my distribution any sensitive information. If you are interested in downloading and attempting to find a weak point in the security though, here is the distribution I am using:!0ls0gD6R!ISvWtwmJN4f6wYUAjkzWPmND-aNAaCw_yso0H5V4qd8
Since I don't know for sure if Mega will do any funny business, the file you download should be identical to mine if it is exactly 1233360896 bytes long, md5sum = 2d99f30b7b499eda826bb998e4767df4, and crc32 of f7b430fa for a little extra safety.
submitted by maccam912 to Bitcoin [link] [comments]

Armory Help

Hello, I am trying to setup Armory on a cloud server only from command line. I installed bitcoind, and cloned armoryd from git however, when trying to run python armoryd --supernode I get "(ERROR) - No wallets could be loaded! armoryd will exit." I tried running --satoshi-datadir=/home/armory/.bitcoin/ as well as creating a wallet using pywallet and putting it in the armory directory. Anyone knows how to bypass this?
submitted by hiir_m8 to Bitcoin [link] [comments]

How to Download and Verify the Armory Bitcoin Wallet Beginner's guide: Installing Bitcoin Armory on Windows 7 Create a Bitcoin Wallet on a Raspberry Pi Offline Wallet Installing Bitcoin-QT

Once Bitcoin Core is finished syncing, you can start Bitcoin Armory (testnet) and you will have access to the Test Network. *NOTE: Due to some quirks in the path resolution, if you want to use a custom directory for Armory and Bitcoin, the –datadir and –satoshi-datadir arguments are inconsistent. For instance, if you moved both your bitcoin ... Python-based fully-featured Bitcoin Wallet Software. Alternatively you can run “sudo make install” after building and it and it will install Armory onto your Ubuntu system, including but shortcuts in your the Applications –> Internet menu. Summary: How to Use Armory BTC Wallet. Visit Armory wallet’s homepage and download a client corresponding to your computer’s OS.; Download and install Bitcoin Core to achieve connection with the BTC’s blockchain network.; Create a backup of your wallet and generate passphrase which should be safely stored. The Armory developers (goatpig, droark, and achow101) support Segregated Witness as is in its current form, and also support Bitcoin Core. The Armory developers also oppose hard forks that may attack the original chain. Should a long-lasting hard fork that does not attack the original chain exist, we would consider implementing functionality required to allow Armory users to transact on that ... Start Bitcoin, now you will see all the files are created in the new data directory. Linux. By default Bitcoin will put its data here: ~/.bitcoin/ You need to do a "ls -a" to see directories that start with a dot. If that's not it, you can do a search like this: find / -name wallet.dat -print 2>/dev/null Mac. By default Bitcoin will put its data here: ~/Library/Application Support/Bitcoin ...

[index] [15198] [5226] [4517] [3248] [40250] [48789] [8044] [46230] [24005] [49011]

How to Download and Verify the Armory Bitcoin Wallet

For Help/Support and Discussions visit the forums: Sign up for a free account and join the community! In this video I sh... Bitcoin-QT is a Bitcoin wallet and does some other functions. Running this software is the backbone to the entire Bitcoin system. You may need to open port 8333 in your firewall. For more info see - How to install Armory on an offline computer. - How to set up an offline wallet and import a watching only version to your online computer. - How to transfer bitcoin TO an offline wallet. If you're new to Ubuntu and Linux, here's a beginner's guide to installing the newest version of the Armory wallet software along with the newest version of the underlying Bitcoin Core daemon. For ... How to install Armory 0.93 and Bitcoin Core 0.10 on Windows 7, and how to create your first wallet. A guide for beginners. Enable subtitles in the video. If you like the guide, feel free to send a ...