Change Bitcoin Core Data Directory - BitcoinWiki

Bitcoin-qt datadir alternative storage location

I tried asking this in the bitcoincore sub yesterday, but it only has a handful of members and got no answers, so i now try here.
When bitcoin-qt is first started, it asks for the location of datadir. If it is set to a custom location, it remembers it on subsequent launches. Where is this location stored, as no bitcoin.conf is generated in the default location, and i have not seen any other documentation to specify datadir except command line option and bitcoin.conf file?
submitted by varikonniemi to Bitcoin [link] [comments]

Bitcoin-qt datadir alternative storage location (x-post from /r/Bitcoin)

submitted by ASICmachine to CryptoCurrencyClassic [link] [comments]

Help: Bitcoin Core does not auto start in Ubuntu with -datadir option

Please can someone help me out?
I have installed Ubuntu in VirtualBox to host Bitcoin Core. In VirtualBox I assigned a special disk with the blockchain. I am however new to Ubuntu. I am a Windows crack.
When I start bitcoin core from a terminal command prompt like:
bitcoin-qt -datadir=/media//Blockchain
then Bitcoin core starts correctly. "" is my username to login to Ubuntu. "Blockchain" is how the disk is named in VirtualBox. The host system is Windows 10.
However when I configure this command in the 'startup applications' of Ubuntu to start bitcoin core automatically when Ubuntu starts, I get the error message the path cannot be found.
While I am writing this post, I think it may be possible Ubuntu did not logged me in under username yet when auto starting bitcoin core, but this is a wild quess.
Is there an Ubuntu crack who can help me out please?
submitted by pdlvw to Bitcoin [link] [comments]

Despite what Core supporters may claim, bitcoin *has* hard-forked before (screenshot of what the hard-fork looks like included)

Many high-profile Core supporters have disingenuously claimed that bitcoin has never hard-forked before. They do this by twisting the definition of "hard-fork" around to suit their agenda. The fact of the matter is, if you run bitcoin version 0.7.2 or earlier with default configuration settings, you will not sync with the present-day blockchain. This is, by definition, a hard-fork: old nodes are incompatible, and must be upgraded in order to remain on the main chain.
Bitcoin's hard-fork occurred in the wake of the March 2013 event, in which the blockchain split due to non-deterministic behavior in older clients. I will put aside whether or not the events in March 2013 were a hard-fork or just a bug, because a measurable hard-fork event occurred a few months later after all nodes were required to upgrade. Indeed, even Core's post-mortem states "On 16 August, 2013 block 252,451 (0x0000000000000024b58eeb1134432f00497a6a860412996e7a260f47126eed07) was accepted by the main network, forking unpatched nodes off the network."
When I say this hard-fork is "measurable", I mean that anyone can test for themselves to see that old versions of the bitcoin software are not compatible with the current blockchain.
In order to test it yourself, you can follow these steps:
Now, you must wait (several hours at least). Once your 0.7.2 node reaches block height 252,450, you will see the result of the hard-fork yourself. The outdated node software will refuse to process the following block, and the debug.log file will start printing InvalidChainFound messages.
Here is a screenshot of what my 0.7.2 node looked like when it was hard-forked off the main chain: https://i.imgur.com/qIxAAjY.png
I encourage you to replicate this process yourself if you remain skeptical.
I hope this puts to rest once and for all the myth that bitcoin has never hard-forked before. The fact of the matter is, bitcoin has hard-forked before: with only a few months of preparation, all nodes on the network were able to successfully upgrade (or apply backports or special config), and the main chain hard-forked without any problems.
submitted by timepad to btc [link] [comments]

HowTo: Masterchest Wallet with Alternate Datadir for Bitcoin-QT

submitted by i-am-adam-i-approve to mastercoin [link] [comments]

Batch script to create pruned block data from full block data

TLDR; Produce a pruned block directory from a full block directory without copying any extra block data
I have a full node, but at times I want to run in a VM or on a RPi or something. Normally I have to clone my whole 300 GB block directory, enable pruning, then point bitcoin-qt.exe to the clone to finally arrive at a small 4 GB datadir. I found it frustrating that I was doing this 295 GB of pointless copy operations since once I enable pruning, the old blocks are discarded. I was also discouraged at the fact that .\Bitcoin\testnet3\blocks\blk00186.dat is different (by checksum) in a pruned and non-pruned directory.
So I finally came up with an answer. Basically, I copy over the latest few blk*.dat and rev*.dat files, then just make empty copies of the other blk*.dat and rev*.dat files. Then once bitcoin-qt.exe launches, it discards the empty files and rewrites the few files it needs. For Windows, it looks something like this:
set /a "sum=0" for /f %%I in ('dir /s /b /o:-n %full_blk%\blk*.dat') do ( set size=%%~zI set blkdat=%%~nxI set revdat=!blkdat:blk=rev! if !sum! GTR !pruned_mb! ( echo.> %pruned_blk%\!blkdat! echo.> %pruned_blk%\!revdat! ) else ( copy %full_blk%\!blkdat! %pruned_blk%\!blkdat! copy %full_blk%\!revdat! %pruned_blk%\!revdat! ) set /a "sum=!sum! -1 + !size!/(1024*1024)" )
I can stamp out a pruned blocks directory from my full blocks directory in seconds. Much easier... well for me.
Here's the source, but no guarantees. Just food for thought.
 
Update: I had originally thought to symlink the unused files, but turns out they are never read at all, so I can just dummy them out.
submitted by brianddk to Bitcoin [link] [comments]

Bitcoin datadir location storage

When bitcoin-qt is first run it asks where to put the datadir, and offers the default location ~/.bitcoin or lets you choose. Where is this choice stored as no bitcoin.conf is generated? How does it know on subsequent launches to look in the custom location?
submitted by varikonniemi to BitcoinCore [link] [comments]

is not pruned!

to have a bitcoin full node on Raspbi I loaded the blockchain with windows on a ssd (vfat), after connection to Raspbi (lubuntu) bitcoin-qt says: sorry your data is pruned, start resync (lasts 4 years). I definitely did not prune, started bitcoin-qt without any commandline options (despite datadir), any idea what went wrong?
submitted by 4piII to Bitcoin [link] [comments]

Gridcoin 4.0.5.0-Leisure "Elizabeth" Release

The core developers are pleased to present the 4.0.5.0 Elizabeth milestone leisure release. This is a leisure release primarily aimed at non-mandatory items and bug fixes leading up to the Fern mandatory milestone release.
This release also enables us to whitelist teams other than Gridcoin as a stepping stone for the implementation of no team requirement in Fern.
Enjoy!
https://github.com/gridcoin-community/Gridcoin-Research/releases/tag/4.0.5.0
Changelog...

Added

Changed

Removed

Fixed

submitted by jamescowens to gridcoin [link] [comments]

Installed 2nd Bitcoin client and invalidated blockchain progress

Hi, over the last couple of days I synchronized the block chain on an old version of Bitcoin QT where I still had funds in my wallet. It started out 90 weeks behind, then over the course of 4 days updated until it had 23 more weeks to go. At this point any progress stopped, seemingly getting stuck for 24 hours or longer and I couldn't find a solution to make it continue its synchronization.
I then installed Unlimited Bitcoin since I heard that new clients would synchronize much faster. I assumed that both clients would build their block chain separately from each other but the Unlimited Bitcoin installation corrupted any progress that Bitcoin QT had made and upon starting it the next time, it had to re-synchronize now being more than 200 weeks behind.
Unlimited Bitcoin however seems to refer to QT's progress status, also being 200+ weeks behind and not updating any quicker.
What would be the fastest way to get the blockchain up to date on my hard drive in a way that the funds on my QT wallet can be used?
Thanks in advance.
submitted by Andre_Dellamorte to Bitcoin [link] [comments]

Any wallets other than QT that support *.dat format?

So my ssd main drive crashed and I had to switch to a smaller one lying around here. So I don't have space for the blockchain anymore on my main drive. But I can't find any other wallet I can use to put my backed up files to use with, I know of blockchain.info but that is not my style...
Also if there is a permanent way of setting the datadir of bitcoin-QT I could happily do that. I used to run the largest node in my country so this is kinda sad for me.
submitted by kerstn to BitcoinWallet [link] [comments]

How to get Armory to use Bitcoin-Qt's block chain on OSX?

I have Bitcoin-Qt installed and synced on OSX Snow Leopard. When I open Armory, the status shown in the Dashboard area says "Preparing Database".
When I check out Armory Bitcoin Client > Preferences, I see that "Bitcoin-Qt/bitcoind management is not available on OSX".
Is it possible to get Armory to use Bitcoin-Qt's block chain on OSX, or will Armory need to download and verify a second, complete block chain?
edit: spelling
edit: It appears that Armory on OS X is configured by default to use the Bitcoin-Qt block chain. All I had to do is wait ~3 hours for synchronization.
edit: Bitcoin-Qt must be running at the same time as Armory. Shutting down Bitcoin-Qt will take Armory offline.
submitted by BobAlison to Bitcoin [link] [comments]

I just verified that BU and SV block chain data structures are compatible! No need to download the block chain from scratch if migrating to SV.

Since BU hasn't still officially announced nor released a Satoshi Vision compatible change set and time is running out, I started migrating cryptograffiti.info from Bitcoin Unlimited to Satoshi Vision (to guarantee that after 15th of Nov my service is still attached to what I perceive as the original Bitcoin).
I copy-pasted the blocks and chainstate directories from BU datadir to SV datadir and simply launched my nonmining node. After a couple of minutes of network discovery the node was properly synchronized with the network and downloaded new blocks as they were found. The RPCs are working as expected.
While SV lacks the qt binaries (GUI), it is still usable as a backend software for block chain services such as cryptograffiti.info . If you want to be on a correct chain after the 15th and can't wait for BU or ABC to implement SV- compatible changes then rest assured, you don't have to download the whole block chain from scratch.
submitted by 1Hyena to btc [link] [comments]

Run a 0.14 Full-Node on RaspberryPi3 Pruned(less than 16GB SD needed)

Hi!
Happy if this guide helps you.
Tip if you want: 19656Uwdwko5RjtnuwQENpjBwE3ChzD59v
UPDATE 04/06/17
Add 'uacomment=UASF-SegWit-BIP148' into your bitcoin.conf if you want to signal UASF.
UPDATE 03/13/17
ADDED a tl;dr; Version at the end of this Post.
UPDATE 03/12/17:
Just to test it - I reinstalled all on 8GB SD and it works as well. But maybe you should use at least 16GB for the beginning.
Using a 128GB card for the first version was a little bit stupid - so I reinstalled everything on a 8GB SD card. Including Linux and a pruned blockchain - and it works.
I used prune=550 and Jessie Lite (headless / command line) - without wallet and gui.
The SD is almost full, but it works so far
I also updated the whole manual a bit to make things more clear. Thank you for all your feedback!
Just started my Bitcoin Node today and wanted to share the way I did it with people who are interested in running their own full node. It took some time to write everything down - hopefully correct so far.
I am sure, many people around bitcoin are way more informed and educated as I am - I am the noob. So I wrote this manual to help users like me - noobs, to get started with a cheap, simple bitcoin node on raspberry pi.
Have fun!
I wanted to get my Raspberry Pi 3 working as a node to support the network. Actually the process of installing and running the node was more or less easy - but for Noobs (like I am) it might be a bit tricky to start the whole thing, because there are different ways.
Did you - like me - think you would need +120GB on the raspi, external USB HDD to be a full node? You won't!
If you have a Raspberry and you know what Bitcoin is, I guess, you are a little bit aware of linux, networks and of course bitcoin - so I won't go into detail too much.
This guide is just a little helper to get a full node running on your raspberry pi. Thanks to the help of the nice people in this sub and of course the documentation by the developers, I got it working - and of course also special thanks to raspnode.com - as I followed their tutorial to start - I went some other ways here and there - so please read carefully.
For the Part 2 I would suggest to have http://raspnode.com/diyBitcoin.html open and read through my manual.
I split the tutorial in 2 Parts - PART ONE is about installing the client on your PC and downloading the Blockchain.
PART TWO is about the setup of the raspberryPi and transferring the pruned blockchain to the pi and run it as a full node!
The first thing to be aware of is: You actually need to download the whole blockchain to get this working - if you already have your bitcoin client synced on the PC / MAC great you can reuse it!
Now you might think "but you said less than 16GB in the title!"
Yes, but the good thing is you won't need to download it on your Raspberry, neither you need to sync it completely on your raspberry which took ages (weeks!) before. When you finished this Guide, you will just have a max. 4GB Blockchain on your Raspberry Pi - but it still is a full node! The magic word is Pruning.
Maybe even a 8GB SD Card works just fine including Linux (jessie lite)!
So, if you already have a full node on your PC - Great you can almost skip PART ONE - BUT have at how to Prune in PART ONE if you don't know about it.
For PART TWO you'll need a Raspberry Pi 2 or 3 (I used 3) min. 8GB (works also) or better 16GB SD Card. (I used a 128GB for the first version of this manual - which is way too big)

PART ONE

This is the manual how to get started on you PC / MAC / Linux (I did it on Win7)
Go to: https://bitcoin.org/en/download and download the core Client for your Machine (I used win64).
Install it and configure it to save the Blockchaindata to the directory of your choice - so instead getting 120GB on your C drive, I would suggest to download it to another place like a USB drive.
You can set this up during the install. Standard folder for the blockchain folder is "%APPDATA%\Bitcoin" on Windows.
or you can do it after the install by creating a bitcoin.conf file inside your installation folder / or %APPDATA%\Bitcoin and add
datadir=l:\yourfolder
to the file. Line by line.
By the way here you could also just add dbcache - to use more memory to speed up the process a bit:
dbcache=4096
if you don't want to use the settings inside the program. (you can also set this inside the program under settings! If you have this inside the bitcoin.conf you will see the amount you set there from inside the program - it overrides the values)
You can check inside the windows client under settings, if you can see a manual dbcache is set by having a look at the left footer area. When your dbcache value shows up, everything is fine.
So the Blockchain download process will take time - maybe a few days! Depending on your machine, internet connection and HDD.
The Blockchain is huge as it contains every single transaction of the past until today. You won't need to keep your PC running all the time, you can turn it off and on and it will resync automatically when you start bitcoin-qt.exe!
Make sure to close the client always via "quit" - ctrl+q.
After you have your bitcoin core installed, the blockchain downloaded and synced - you are ready to PRUNE!
First - close the Client and let it close smoothly. After it is really closed you can follow these steps:
By pruning, your blockchain will dramatically shrink. From 120GB to just a few GB.
Be aware, that you will lose your Downloaded Blockchain as pruning will erase a big chunk of it! If you have enough space, you could of course keep the full blockchain saved somewhere on another HDD.
You can prune by editing your bitcoin.conf file by adding:
prune=550
I used prune=1024 - not sure where the differences are right now (min. prune=550). (for my 8GB version I used 550! I suggest to use this.)
Save the bitcoind.conf file and restart your windows client.
It will now clean up the Blockchain. So just the latest blocks are saved. The client should start without any problems. Maybe it takes some time to prune the blockchain data.
Check if everything works normally (the client opens as usual, you can see an empty wallet) than close the client.
Inside the Bitcoin Folder, you'll find two folders called:
blocks chainstate
those are the interesting folders containing the important data (now pruned) - and we will transfer those two to the raspberry later!
Now you are good to start the raspi transfer explained in the next part.

PART 2

Here is what I did:
1) I installed Raspian Pixel (https://www.raspberrypi.org/downloads/raspbian/) using a 128 GB SD - which is not needed because of "Pruning" - I think a 16GB card might work, too! (You can also install Raspian Jessie Lite - which saves you even more space, as it runs headless - only command line) (Updated: It is better to use Jessie Lite to save a lot of space - when you are fine with only command line)
2) I followed partly this tutorial to get everything running and setup:
http://raspnode.com/diyBitcoin.html
Please have a look at it - I have copied the Headlines in capitals to let you know what I did, and what I skipped.
On Tutorial Page: Start with RASPBIAN (OPTIONAL) CONFIG OPTIONS.
Set You RasPi up including "EDITING FILES" to save your Layout at the tutorial page and come back here.
I skipped the CONFIGURE USB AND SET AUTOMOUNT process, as we are going to use PRUNING to reduce the 120GB to a tiny filesize - so USB Devices are not needed here!
It was necessary to ENLARGE SWAP FILE to install bitcoin core - otherwise it didn't went through which ended in a frozen raspi.
So have a close look by following the raspnode tutorial at: ENLARGE SWAP FILE.
I have my raspi running via cable to router - but you can also WiFi setup everything described under NETWORKING ON THE RASPBERRY PI.
Now comes the interesting part: Follow the steps at DOWNLOADING BITCOIN CORE DEPENDENCIES - they work fine for 0.14.0 too. Git should be on Board already when you installed Pixel - otherwise you would need to install it.
sudo apt-get install git -y (only jessy lite)
I skipped the next command lines - as I don't use bitcoin-qt wallet. If you want to use it as wallet - do the step.
mkdir ~/bin cd ~bin
Now you are in the folder you want your bitcoin core data be downloaded to via git. I didn't Downloaded the Berkeley Database source code - so I also skipped the whole next command lines
[email protected]~/bin$ wget http://download.oracle.com/berkeley-db/db-4.8.30.NC.tar.gz [email protected]~/bin$ tar -xzvf db-4.8.30.NC.tar.gz [email protected]~/bin$ cd db-4.8.30.NC/build_unix/ [email protected]~/bin/db-4.8.30.NC/build_unix$ ../dist/configure --enable-cxx [email protected]~/bin/db-4.8.30.NC/build_unix$ make -j4
and went on with "INSTALLING BITCOIN"!
I followed the first part but instead downloading 0.13 I took of course the latest version:0.14
git clone -b 0.14 https://github.com/bitcoin/bitcoin.git cd bitcoin ./autogen.sh
this might take some time to start.
If you have trouble with hanging RESOLVING DELTAS - just restart the Raspberry Pi and remove the bitcoin folder inside /~bin using
rm -rf bitcoin
this command will delete the folder and you can reuse
git clone -b 0.14 https://github.com/bitcoin/bitcoin.git

For some reason RESOLVING DELTAS is a common problem with different downloads - so just retry it and at least after 3 times it should work!

as I didn't use the GUI/ Wallet, I ran
./configure --enable-upnp-default --disable-wallet
as I don't need the wallet functionality.
I didn't need to use "MAKE" which saves you maybe up to 2.5 hours.
instead you can just go ahead with:
sudo make install
(If I am wrong in doing so - please let me know)
The install takes some time - and just a heads up: when it gets stuck somewhere - just redo the installation process - it took three times to went through - stuck at some processing.
After the installation took place you can finally get your Raspberry Pi Node running in no time!
To test if the the installation went through - you can just start bitcoind using:
bitcoind &
than check if everything is working so far:
bitcoin-cli getinfo
after a few seconds you should see version: etc...
if not, something went wrong. Try to redo the steps in the raspnode tutorial.
(don't give up if it failed - retry! Ask your questions here)
IMPORTANT: you need to stop bitcoin on your raspberry now!
bitcoin-cli stop
If you don't need an external USB Drive - what I hope - as we are going to use pruning just go ahead and skip the USB part and create a file inside (or follow the raspnode tutorial on how to setup the USB drive):
cd .bitcoin
sudo nano bitcoin.conf
and enter the exact same pruning size you have used on your Desktop Machine to prune. I used 1024 but the minimum is 550. (used 550 for the 8GB SD card on PC and Raspberry)
prune=550
That's it for the raspi.
update: To signal UASF enter in a new line:
uacomment=UASF-SegWit-BIP148

TRANSFER

Now you have to transfer the two folders CHAINSTATE and BLOCKS from your PC bitcoind directory to your raspberry.
I am using a program called "WINSCP" - it is free and easy to use: https://winscp.net/eng/download.php
We need this to transfer the files to the Raspberry pi. Pretty sure you can also do it via SSH - but I am the noob. So let's keep it simple.
Open Winscp and put in the IP Address of your Raspberry Pi, User and Password (same as in SSH)
You should now see the directories on your Raspberry Pi. There is a folder called
.bitcoin
enter it and you will see the two folders
blocks & chainstate
you can delete them on the raspberry as they have some data from your previous test inside.
Make sure you can also see the bitcoin.conf file in that directory, which needs to contain the exact same prune line, like the one on your desktop machine. If not, make sure to edit it via SSH. The line "datadir=l:\yourfolder" is obviously not needed in the Raspberry bitcoin.conf file.
Now grab the two folders CHAINSTATE and BLOCKS from your PC and copy them to your .bitcoind folder.
I also copied banlist.dat, fee_estimation.dat, mempool.dat and peers.dat to the folder - not really knowing if needed! Not needed.
The whole copy process might take some minutes (against some weeks in the old way).
After copying is finished, you can now start bitcoind on the Raspberry.
bitcoind &
the & symbol let you still use the command line while the process is running btw.
The process - if succesfull - will take some time to finish.
bitcoin-cli getinfo
Will give you some informations what is going on right now. When you can see, that it is checking the blocks, this is good!
If you get an error - double check - if you have the correct prune size (same as on desktop machine) - in bitcoin.conf and that this file is inside .bitcoin on RaspberryPi. It took me some time, to find my mistakes.
Congrats! You are almost a part of the network!
To make your node now a fullnode, you will need to go to your router (often 192.168.1.1) and enable portforwarding for your raspberry pi - and open ports 8333 - that's it!
You can now go to: https://bitnodes.21.co/nodes/
scroll down to "JOIN THE NETWORK" and check check if your node IP is connected!
It will show up as soon as the blocks are checked and the raspi is running.
Well done!
Now you are running a full node, with a small Blockchain and got it working in Minutes, not weeks!
I really hope, my little tutorial worked for you and your are part of the Node network now.
If you have problems or I made a mistake in this helper tut, just let me know and I will try to make it better.
Have fun and NODL!
the noob
tl;dr; (if you are a real noob start with the non-tl;dr version!)
tl;dr; PART ONE
1) Download & install / setup bitcoincore @ https://bitcoin.org/de/download
2) change dbcache to something smaller than your memory and download the whole Blockchain (120GB).
3) create a file called bitcoin.conf put the line prune=550 (or higher) in to activate pruning on win inside %appData%/bitcoin
4) Open ports 8333 on your Router to make this a full node with a smaller Blockchain.
You are running a full node on your PC.
tl;dr; PART TWO
1) Install jessie lite and the needed dependencies on your SDCard - Raspberry
( >git clone -b 0.14 https://github.com/bitcoin/bitcoin.git )
  • see tutorial for more info.
2) create a file called bitcoin.conf inside .bitcoin and add the same prune=Number you had on your PC.
3) transfer the pruned folders BLOCKS and CHAINSTATE to the Raspberry Folder .bitcoin
4)Start "bitcoind &"
5) let everything sync
6) Make sure you have port 8333 opened on your router.
You are running a full node on your Raspberry with a super small Blockchain (I put all on a 8GB SDcard)
Tip if you want : 19656Uwdwko5RjtnuwQENpjBwE3ChzD59v
updated 03/12 - will update more, soon.
updated 03/12.2 - I updated the whole process a bit and also added some improvements.
updated 03/14/ Added a tl;dr version at the end.
submitted by I-am-the-noob 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 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]

[BitcoinXT] Change path to Bitcoin-Qt.conf under Linux

BitcoinXT by default creates a config file under /home/USE.config/Bitcoin/Bitcoin-Qt.conf (I'm not talking about the bitcoin.conf in the datadir).
Is there an option to have BitcoinXT use another path for this file?
I can't find anything even when grep-ing the source code.
submitted by GuessWhat_InTheButt to btc [link] [comments]

Bitcoin ABC node can't synchronize passed the fork block. Would adding other Cash nodes explicitly on my peer list help?

I'm trying to get my Bitcoin ABC node, which is running behind Tor in case that makes any difference, to synchronize. But it can't get passed the fork point. What makes sense since all my peers seem to be BSCore nodes...
Is there a list of trustworthy Bitcoin Cash nodes I could manually add in order to get the good chain?
Also, for some reason, even though I added the -listen option, my node isn't going above 8 connections. Shouldn't it automatically configure a hidden service, or do I still need to do it manually?
This is the list of command line parameters I run my node with:
./bitcoin-qt -bind=127.0.0.1 -proxy=127.0.0.1:9050 -listen -datadir=PATH_TO_BITCOINCASH_DATADIR -checkblocks=1 
Finally, another question: I saw Bitcoin ABC has a PPA, but it uses the same package names of Bitcoin Unlimited, which I'm using to connect to the Bitcoin Settlement network. Names which come from BSCore packages, actually. Would you guys mind having a different package name like BitcoinXT has? (I'm not using them either because they haven't updated their PPA with the Cash release, and because I wanted to check on this ABC implementation)
Thanks!
submitted by VedadoAnonimato to btc [link] [comments]

bitcoin-qt ready for use within half an hour … download an up-to-date pruned blockchain

Let us discuss how safe this is :-)
This tutorial is for Linux only but people using other operating systems will understand what to do.
Download the bitcoin blockchain
https://drive.google.com/drive/folders/0B0nH34wIYOSlSG81ZUZUZGZjVkE?usp=sharing
This will download (~20 minutes) the 2485 MB file:
bitcoin_blockchain_pruned_550MB_19aug2016.tar.gz
It contains only blocks, no wallet or log files. It has been created with -prune=550
Unpack
tar -zxvf bitcoin_blockchain_pruned_550MB_19aug2016.tar.gz
and observe it contains only blocks and chain state data. This will create the directory:
.bitcoin_pruned_550MB_19aug2016
Let’s assume you move this to ~/.bitcoin_pruned, so
mv .bitcoin_pruned_550MB_19aug2016 ~/.bitcoin_pruned
Run bitcoin-qt
When you start bitcoin-qt, a new wallet will be created: back it up first. My advice is to use bitcoin-qt 0.13.0rc3, because it creates a HD wallet that never runs out of addresses.
Start bitcoin-qt in fast start-up mode first:
bitcoin-qt –prune=550 –checklevel=2 –checkblocks=10 –checkblocksverify=10 –datadir=yourpath/.bitcoin_pruned
and let it sync quickly. Check more thoroughly next time with 10 -> 500000.
You can have a quick look at what’s happening:
tail ~/.bitcoin_pruned/debug.log.
 
FOR NOW, the drawback is that if you want to add addresses (watch-only or spendable) that already contain bitcoins, you have to create the pruned blockchain from scratch yourself, which takes a lot of time (or have someone with a full blockchain rescan the wallet for you). This is not really necessary: if the user is not interested in the history of his transactions, the balances can be obtained directly from the UTXO set. It has already been approved to add this feature in some future Core release:
https://github.com/bitcoin/bitcoin/issues?q=is%3Aissue+is%3Aopen+label%3AWallet, #8497.
I will automatically update the google drive with new up-to-date blockchains soon.
EDIT:
openssl dgst -sha256 bitcoin_blockchain_pruned_550MB_19aug2016.tar.gz SHA256(bitcoin_blockchain_pruned_550MB_19aug2016.tar.gz)= ce36bcb9ab691c358b27d3051f8f38452bc182ca636eae992563c60805a9d4b0
submitted by sumBTC to Bitcoin [link] [comments]

Sent BTC from wallet to another, both wallets empty

I wanted to move my bitcoins from Bitcoin QT to Electrum. I took electrum's address, sent it from QT and both wallets are empty. I had to do some critical system funcitons which was the impetus to this move. QT was 50% of my harddrive. I made the move, was too pressed for time to confirm the transaction, and deleted bitcoin folder.
I made a backup of the wallet just in case. A few days later, I noticed the funds never made it to electrum. Loaded the backup on QT just to be sure, and QT is empty as well.
Are the bitcoins gone or can I investigate this further? It was .91 BTC.
edit: Resolved! For anyone who may be having the same issue and searches for this.. There was a lot of good info but litecoin-p2pool pointed out that due to a datadir command I performed to mvoe the directory from C:\ to d:\, I inadvertently created a new wallet. Bringing the original wallet back to d:\ performed a rescan which turned up the coins.
submitted by pawsforbear to BitcoinBeginners [link] [comments]

The bitcoin-qt core wallet in pruned mode, cold storage and scaling: test results.

CONCLUSION
 
DETAILS
First a wallet was created in the following way:
bitcoin-qt -connect=wrong_ip_address -prune=550 -listen=0 -datadir=/home/use.bitcoin_pruned &
The trick here is to add a wrong ip address so bitcoin-qt won't start loading blocks. The -listen=0 makes it possible to run bitcoin-qt while bitcoind (as a full archival node) is running in the background on the same computer.
 
Now some "watch only" addresses, that already had some bitcoin in them, were added
(in bitcoin-qt: help -> Debug window -> Console)
importaddress watch_only_address "" false
The pruned blockchain was then created by inserting the correct ip address (pointing to my node) or by removing "-connect=ip_address" completely.
 
Because bitcoin-qt was not the only program, creating the pruned blockchain was a very long process that took about 5 days! I could speed up the process a lot by turning off bitcoind and running the pruned node as a bitcoind with some extra priority:
sudo /usbin/ionice -c 2 -n 0 /usbin/nice -n -20 ./bitcoind -datadir=/home/use.bitcoin_pruned/
Had I done that from the start, it could have been much faster and maybe 1 or 2 days would have been enough.
The final pruned blockchain has a size of: 2542 MB so about 2.5 GB.
 
I now moved the wallet.dat to wallet.dat_back and restarted bitcoin-qt. The program will create a new wallet that can be used to receive and then send transactions. If you now add a private key that already has some bitcoins in it, they will NOT be visible. There is no reason for that as the balances (not the history) are in the UTXO set.
 
I now started bitcoin-qt with the original wallet.dat file. The bitcoins in the watch only addresses are now visible. I then imported the private key of one of the addresses but the move of the bitcoins from "Watch only" to "Spendable" was not visible in bitcoin-qt. However, after a restart of bitcoin-qt the funds were visible in the "Spendable" section of the wallet. I then did a transaction to another address. Now in this case I want the change of the transaction to stay within MY "watch only" addresses and they shouldn't move to the (arbitrary) addresses created when the wallet was created. This is fortunate possible in bitcoin-qt. You have to choose in bitcoin-qt:
Settings -> Options -> Wallet -> Enable coin controle features.
It is then possible to choose the return address to be one of the watch only addresses (with or without bitcoins in them). It all worked just fine! It is not clear to me why bitcoin-qt has the option to "importprunedfunds", that doesn't seem necessary.
 
Of course, a big thank you to all developers who implemented the currently available great features.
submitted by sumBTC to Bitcoin [link] [comments]

Easy UASF Node in Debian VM tutorial

So if you have a moderately powerful gaming desktop with a Quad-Core CPU like an i5 or better and 8+GB of RAM, you can easily run your own little UASF node in the background. Once it's done syncing with the network, you won't even notice it's there. Here's how.
You will need :
The following assumes you know how to install Linux in a Virtual Machine
Step I. - Installation. Go through expert install and set up a base system with only ssh server enabled. For partitioning, you can do just one big disk and everything in one partition, but if you happen to have a computer that has both SSD's and HDD's, it would be optimal to create two virtual disks and use a small one for the OS on the SSD and a larger one on the HDD in a custom mount point for the blockchain. Reboot and ssh into the server.
Step II. - Build requirements. A few things need to be taken care of. First, you'll want to edit the /etc/network/interfaces file and set up a static IP. Once that's done, stop by your router and make sure that traffic on port 8333 is forwarded to your debian VM. Then, install some packages we need :
apt update apt upgrade apt install build-essential autoconf libssl-dev libboost-dev libboost-chrono-dev libboost-filesystem-dev libboost-program-options-dev libboost-system-dev libboost-test-dev libboost-thread-dev libevent-dev git libtool pkg-config 
The next one is a bit more annoying. We need Berkeley DB 4.8, and it's a little old. It's packages are in the Debian Squeeze archives, so in the /etc/apt/sources.list file, we need to add :
deb http://archive.debian.org/debian/ squeeze main 
Then remember to update again, and install the thing :
apt install libdb4.8++-dev libdb4.8-dev 
If you intend to also throw on xorg and a UI, you will want Qt as well. Otherwise skip this last step.
install libqt4-dev libprotobuf-dev protobuf-compiler libqrencode-dev 
Step III. - Build time
#Starting from /home/yourUser git clone https://github.com/UASF/bitcoin.git -b 0.14-BIP148 cd bitcoin ./autogen.sh ./configure make make install 
That's it! Well, mostly. Start it with
bitcoind -daemon -disablewallet -datadir=/whereveyou/want/youblockchain 
...and wait about thirty hours to sync with the network. You may want to visit the /whereveyou/want/youblockchain directory and create a permanent bitcoin.conf in there. To enable RPC calls to the server and get it to accept bitcoin-cli commands you'll want to use it to create a usepassword and copy that to your user's /.bitcoin/bitcoin.conf.
Minimal bitcoin.conf example
daemon=1 listen=1 disablewallet=1 server=1 rpcuser=bob rpcpassword=bob's password 
Security I recommend you disable password login and use private key authentication only on ssh, and also restrict iptables rules to the bare minimum that must be allowed for this application. You will need this in your iptables script :
# Allows BITCOIN traffic from anywhere -A INPUT -p tcp --dport 8333 -j ACCEPT # Allows RPC calls to the bitcoin server from localhost -A INPUT -p tcp -s 127.0.0.1 --dport 8332 -j ACCEPT 
Useful ressources :
submitted by the_bolshevik to Bitcoin [link] [comments]

-reindex option doesn't fix a corrupted blockchain, it's downloading all over again.

This is a follow up to the corrupted blockchain problem described by me 5 days ago: https://www.reddit.com/BitcoinBeginners/comments/8zysbx/error_when_running_a_bitcoin_core_node_corruption/
As bitusher suggested, I ran:
./bitcoind.exe -reindex --datadir=G:\Bitcoin\Bitcoin_core\Bitcoin\blockchain 
Before that I had even tried the option -reindex-chainstate but it failed for some reason.
After about 8 hours, the reindex finished but it's downloading the blockchain all over again although I already have 200 GB of blockchain data. I can see this by running:
Bitcoin\daemon> .\bitcoin-cli.exe getblockcount 323136 (wait some minutes...) Bitcoin\daemon> .\bitcoin-cli.exe getblockcount 326069 
The point when it went from reindexing to downloading the blockchain all over again looks like this in debug.log:
2018-07-24 08:32:09 Reindexing block file blk01265.dat... 2018-07-24 08:33:57 Loaded 962 blocks from external file in 107945ms 2018-07-24 08:33:57 Reindexing finished 2018-07-24 08:33:57 Pre-allocating up to position 0x100000 in rev00000.dat 2018-07-24 08:33:58 UpdateTip: new best=00000000839a8e6886ab5951d76f411475428afc90947ee320161bbf18eb6048 height=1 version=0x00000001 log2_work=33.000022 tx=2 date='2009-01-09 02:54:25' progress=0.000000 cache=0.0MiB(1txo) 2018-07-24 08:33:58 UpdateTip: new best=000000006a625f06636b8bb6ac7b960a8d03705d1ace08b1a19da3fdcc99ddbd height=2 version=0x00000001 log2_work=33.584985 tx=3 date='2009-01-09 02:55:44' progress=0.000000 cache=0.0MiB(2txo) ... 2018-07-24 15:28:52 UpdateTip: new best=00000000000000000c84841e1450c8644dfe5a85528ae551f8862a688b55db61 height=331606 version=0x00000002 log2_work=81.568221 tx=52347394 date='2014-11-25 21:30:09' progress=0.149665 cache=2153.7MiB(16335495txo) 2018-07-24 15:28:52 Pre-allocating up to position 0x200000 in rev00200.dat 2018-07-24 15:28:53 UpdateTip: new best=0000000000000000103e002b3231dbee391cf38a2890e310b3e9ee3b785a172a height=331607 version=0x00000002 log2_work=81.568291 tx=52348058 date='2014-11-25 21:40:24' progress=0.149667 cache=2153.7MiB(16334996txo) 2018-07-24 15:28:53 UpdateTip: new best=00000000000000001ac7a4a8f8b910236cfbe1ec2343af4fbe9b8dd1691b7433 height=331608 version=0x00000002 log2_work=81.56836 tx=52348254 date='2014-11-25 21:42:35' progress=0.149667 cache=2153.6MiB(16334923txo) 2018-07-24 15:28:53 UpdateTip: new best=000000000000000006ecf1eb304f3edf56f8ebea62183f8ffbb37653433d196b height=331609 version=0x00000002 log2_work=81.56843 tx=52348821 date='2014-11-25 21:52:17' progress=0.149669 cache=2153.7MiB(16334989txo) 2018-07-24 15:28:53 UpdateTip: new best=00000000000000001864ff1e384b409d9c26745e3dc36a77cb3068959c6244f7 height=331610 version=0x00000002 log2_work=81.5685 tx=52349053 date='2014-11-25 21:55:54' progress=0.149670 cache=2153.7MiB(16335046txo) 2018-07-24 15:28:53 UpdateTip: new best=000000000000000019ff0a26dd1c684661a624f52a78185ba60ad63a464be92e height=331611 version=0x00000002 log2_work=81.568569 tx=52349229 date='2014-11-25 21:57:40' progress=0.149670 cache=2153.6MiB(16334946txo) 2018-07-24 15:28:54 UpdateTip: new best=00000000000000000775b876ee6d5ef4e74ec728d92ea37f249cf4183e8d8447 height=331612 version=0x00000002 log2_work=81.568639 tx=52350965 date='2014-11-25 22:27:56' progress=0.149675 cache=2153.7MiB(16335409txo) 2018-07-24 15:28:54 Pre-allocating up to position 0x1200000 in rev00199.dat 2018-07-24 15:28:54 UpdateTip: new best=000000000000000009547c69932fa9cc2a8d2c9f6449ef23db13da3f71ac8d40 height=331613 version=0x00000002 log2_work=81.568709 tx=52351547 date='2014-11-25 22:36:56' progress=0.149677 cache=2153.6MiB(16334933txo) 
I am feeling pretty frustrated because I can't run a simple bitcoin node every once in a while. Seems like every time I close bitcoind or bitcoin-qt the blockchain gets corrupted. I have found several people complaining about this problem online but I haven't found any definitive solution. Seems like avoiding windows is a good thing (I like to use the same blockchain folder that I store in an external hard drive in both windows and linux).
TLDR
1 - How to avoid getting a corrupted blockchain in both windows and linux and both bitcoin-qt and bitcoind?
2 - How to fix a corrupted blockchain quickly, if this is even possible. -reindex and -reindex-chainstate don't seem to work in my case.
If this doesn't get solved here, I am opening an issue in bitcoin's github.
submitted by johnturtle to BitcoinBeginners [link] [comments]

Running an SQL Injection Attack - Computerphile - YouTube Cambiar directorio principal APPDATA de Bitcoin-QT Boursorama - YouTube Changing cryptocurrency wallet location (Dogecoin - Bitcoin - Litecoin ....) Bitcoin: Kurs-Rallye durch Zahlungs-Revolution?

How do I move my Bitcoin Core data file. Safely exit Bitcoin Core (bitcoin-qtbitcoind). Make a new secure backup copy of your wallet.dat.; Move you entire .bitcoin folder to the new location, except for bitcoin.conf which you must leave where it is in the existing .bitcoin folder. Edit bitcoin.conf to add datadir={full path to new .bitcoin folder}.; Start Bitcoin Core and check properly that ... By default, Bitcoin (or bitcoind) will look for a file named 'bitcoin.conf' in the bitcoin data directory, but both the data directory and the configuration file path may be changed using the -datadir and -conf command-line arguments. Bitcoin-qt datadir alternative storage location. Close • Posted by just now. Bitcoin-qt datadir alternative storage location. I tried asking this in the bitcoincore sub but it only has a handful of members, so i now try here. When bitcoin-qt is first started, it asks for the location of datadir. If it is set to a custom location, it remembers it on subsequent launches. Where is this location ... If you want to store them in D:\BitcoinData then click on "Properties" of a shortcut to bitcoin-qt.exe and add -datadir=D:\BitcoinData at the end as an example: "C:\Program Files (x86)\Bitcoin\bitcoin-qt.exe" -datadir=d:\BitcoinData 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 ... If you want to store them in D:\BitcoinData then click on "Properties" of a shortcut to bitcoin-qt.exe and add -datadir=D:\BitcoinData at the end as an example: "C:\Program Files (x86)\Bitcoin\bitcoin-qt.exe" -datadir=d:\BitcoinData 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 ...

[index] [41980] [8061] [43801] [22035] [19402] [37320] [46492] [14628] [42304] [7063]

Running an SQL Injection Attack - Computerphile - YouTube

Donate some doge if it worked :D D9MgoqshfSKrEn44CDJyikyoYwfnXMYbTS Donate some Litecoin LKUhYUzviqPycCzvEEDRHYBQ9hNXvB6s87 Demo ! Demo ! Demo ! "C:\Program Files ... Qt Bitcoin Trader - trading client for Mt.Gox and BTC-e - Duration: 2:55. Андрій ... Vamos a ver como se cambia el directorio de APPDATA cuando instalamos nuestra cartera bitcoin: Lo primero es hacer una copia de seguridad de nuestra wallet, ya que vamos a tener que borrar la que ... In this video we look at Strings, Functions and import a Rust 'rand' crate. #Bioinformatics #Python #Rust [=== Video Notes/Links ===] Article version: https:... Enjoy the videos and music you love, upload original content, and share it all with friends, family, and the world on YouTube.

#