Armory Bitcoin Core - It is considered an extremely secure ...

Completely lost with Armory

Hey everyone, total noob here with BTC. I've downloaded the blockchain from Bitcoin Core and now I'm trying to get Armory (where I've set up a wallet and sent funds to already) to sync up. Armory still shows up as Offline and it's been "preparing databases" for a good two or three hours now. I'm not sure if I'm just going to be playing the waiting game until it does what it needs to do, or if I need to move a file somewhere, or if my settings are wrong.
I do have a printed backup of my wallet just in case. If I've completely f'd this up, is it possible to send that wallet's .dat over to Core or another program and have it sync up there? Thanks.
submitted by THECapedCaper to BitcoinBeginners [link] [comments]

Armory ate my BitCoins!! HELP!!

Fellow Redditors,
I've been using Armory on Linux for a couple of months now with no issues.
Yesterday, I sent 8.4 BTC (plus 0.0005 transaction fee) from my Armory wallet to my wallet.
Nothing unusual. From Armory's side, everything seemed to go ok. The transaction shows in the list of transactions, but the BTC never arrived @ LBC.
Looking into it further, some 24 hours later, the transaction is still showing as "Not in the blockchain yet" within Armory, and this is confirmed by a lookup on
So far I've tried, all to no effect:
The block count at the bottom of Armory screen matches the current block count in
I've quadruple checked the destination address, and it is correct. And I have since successfully sent a much smaller transaction (0.01 BTC) from the same wallet to the same address, which appeared in the blockchain within a couple of minutes.
It's almost as if the transaction is "stuck" within Armory, as the block chain has no knowledge of the transaction. This is why I thought (naively, it turns out) that recreating the wallet would only pick up actual transactions from the blockchain, and magically give me back my missing bitcoins. There's clearly a hole in my understanding of how BitCoin works... :-s
Does anyone have any clue what I might do?
ANY advice gratefully received.... :)
submitted by JJJT to Bitcoin [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, 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]

[HELP] bitcoin-qt.exe has stopped working

Hi guys, I'm fairly new to Bitcoins and I'm already scared that I've lost my wallet.
I used bitcoin-qt.exe to create a new one, let it sync, then transferred some funds over to it. Since then, every time I try to run it, it just crashes instantly. I'm running Windows 8.1 and neither the 32-bit nor 64-bit versions of bitcoin-qt work at all.
If I debug with Visual Studio 2012: it displays the following error:
Unhandled exception at 0x00B906CA in bitcoin-qt.exe: 0xC0000005: Access violation reading location 0x00000004.
I tried using Bitcoin Armory and that won't work either.
Is there any alternative Bitcoin client or some method I can use to recover my wallet and its bitcoins? I am desperate for help.
Thank you so much.
Apparently version 0.9.3 works fine. I'm going to see if I can recover my wallet with this version.
I uninstalled absolutely everything related to Bitcoin, deleted everything except my wallet, torrented bootstrap.dat, installed Bitcoin 0.10.0, and it works now, but it won't seem to recognize my wallet backup, even running with -rescan. I'll try some more. Thanks for the help though, you guys.
submitted by Huskehn to Bitcoin [link] [comments]

Switching from Bitcoin-QT

So after seeing THIS post this morning I opened up my QT client and had quite a startle. I was BitBroke! I quickly checked my transaction log to see if I was one of the victims of the Bitcoin-QT hack. As it turns out my wallet says I never was BitRitch to begin with. (my wallet showed NO addresses at all!!)
Que the panic.... Was I hacked? Was I robbed?
As it turns out at 2.35am on Dec 27 my wallet was created. Now the holidays were a bit blurry to me so I can't verify what exactly happened at that time so I said fuckit and went to my backup.
After multiple harrowing steps (renaming the backup wallet, running -rescan, crying) I was able to restore my wallet, I'm now in the process of synchronizing with the network. (I checked on blockchain, my BitLoot is still there in my wallet. WOOT!)
So the point of all this is multifaceted. 1) Don't holiday and compute at the same time. 2) make a backup 3) keep calm and mine on
I leave you all with a serious question; What is the best client and can i transfer the locally stored blockchain info from QT to another (say armory) ie. I don't want to wait for Armory to sync with the network when I already did that with Bitcoin-QT, can I just point another client at that 15.2GB folder and call it a day?
submitted by projkt4 to Bitcoin [link] [comments]

how to mine for bitcoin core Bitcoin Wallet Recovery Installing Bitcoin Armory Make Money Easily 850$ to 5k Per Week With Bitcoin Mining How to Recover & Reload a BITCOIN WALLET 0.8.1-beta Win 7

Où acheter bitcoin avec un compte bancaire. It runs on Bitcoin Armory Trezor vs. One thing to consider is how much money you want to store in each bitcoin wallet. If you have paper wallets, private keys, files, or brain wallets, they can be gold flecked linoleum imported into armory bitcoin core another wallet (Bitcoin QT, Electrum, Multibit,Frequently Asked QuestionsCuál es el "monedero ... This is because Armory uses a deterministic wallet; all of the addresses are derived from a specific root algorithmically. Yes, send me more helpful Bitcoin stuff like this No games, no spam.prompt$ bitcoin-qt -rescan This way the client to read again each block to see if there are transactions with your addresses. Open Bitcoin Armory (testnet), navigate to the settings panel, and deselect “Let Armory run Bitcoin-Qt/bitcoind in the background.” Next, navigate to the location of your Bitcoin Core installation, for example C:\Program Files\Bitcoin. Once there, it is easiest to click on the “bitcoin-qt” application and create a shortcut. The Bitcoin Core daemon (bitcoind) is not included in the .dmg file you may have downloaded to install Bitcoin-QT. Bitcoind, along with its support binaries, is instead included in the OS X .tar.gz file listed on the official Bitcoin Core download page. ... Running a node in pruned mode is incompatible with -txindex and -rescan. It also ... Armory does not need to rescan the blockchain anymore unless you import new private keys, or Armory experiences an unclean shutdown. With the exception of the first-time startup (to build the new databases), Armory should get into online mode within 10 seconds of Bitcoin-Qt/bitcoind finishing synchronization.

[index] [26984] [18201] [4450] [28601] [25566] [17200] [16033] [22663] [28187] [24550]

how to mine for bitcoin core

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 ... Standalone Bitcoin Offline Wallet Printer This is a demo of a protoype bitcoin paper wallet printer I have built. bitcoin bitcoin value bitcoin exchange rate... Bitcoin Armory - Creating a Lockbox. Bitcoin Armory - Creating a Lockbox. Skip navigation Sign in. Search. Loading... Close. This video is unavailable. Watch Queue Queue. Watch Queue Queue. bitcoin qt rescan bitcoin q a bitcoin q es bitcoins q son q son los bitcoins q es un bitcoin bitcoin rate bitcoin reddit bitcoin rig bitcoin register bitcoin r?knare bitcoin rich list This video is unavailable. Watch Queue Queue. Watch Queue Queue