client - Where is the data folder for Bitcoin-Qt ...

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]

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]

Lightning node on Windows - testing, get not connected

Ok after testing BTCPay, C-Lightning, LND on Ubuntu I said ok let's try also the Windows implementation, is just few clicks and done (as it is promoted).
So I followed this github guide that actually send you to this one.
OK, started Bitcoin-core client on Windows 7 x64, with an already synced data folder. Empty bitcoin.conf (none of guides says how to configure the conf file). Wait until the client is full synced. And then launched the windows-node-launcher (from a subfolder inside Bitcoin folder). All good, started slowly and a small popup appeared in systray saying Bitcoin node is syncing. Reviewed the config of Bitcoin and LND through that little app in systray and saw that bitcoin.conf was already filled with some settings. Didn't change anything. After 1 day (with the bitcoin blockchain already synced), the systray popup still says that is syncing and have a red dot. In the tutorial says that we have to leave it to sync until is blue and then green.
I said, ok maybe it has more things to do. So I open that LND Output link, to see what is going on... And I see that LND is not well. Says: 2019-04-06 21:11:29.772 [INF] LTND: Version: 0.6.0-beta commit=v0.6-beta-rc3, build=production, logging=default 2019-04-06 21:11:29.772 [INF] LTND: Active chain: Bitcoin (network=mainnet) 2019-04-06 21:11:29.774 [INF] CHDB: Checking for schema update: latest_version=8, db_version=8 2019-04-06 21:11:29.808 [INF] RPCS: password RPC server listening on 127.0.0.1:10009 2019-04-06 21:11:29.808 [INF] RPCS: password gRPC proxy started at 127.0.0.1:8080 2019-04-06 21:11:29.808 [INF] LTND: Waiting for wallet encryption password. Use lncli create to create a wallet, lncli unlock to unlock an existing wallet, or lncli changepassword to change the password of an existing wallet and unlock it. 2019-04-06 21:11:32.673 [INF] LNWL: Opened wallet 2019-04-06 21:11:33.183 [INF] LTND: Primary chain is set to: bitcoin unable to create chain control: unable to connect to bitcoind: unable to subscribe for zmq block events: dial tcp 127.0.0.1:18502: connectex: No connection could be made because the target machine actively refused it. 2019-04-06 21:11:36.087 [INF] LTND: Shutdown complete unable to connect to bitcoind: unable to subscribe for zmq block events: dial tcp 127.0.0.1:18502: connectex: No connection could be made because the target machine actively refused it. 2019-04-06 21:11:39.229 [INF] LTND: Version: 0.6.0-beta commit=v0.6-beta-rc3, build=production, logging=default
Now the bitcoin.conf have this: printtoconsole=1 rpcallowip=::/0 whitelist=0.0.0.0/0 datadir=C:\Users\Admin\AppData\Roaming\Bitcoin prune=0 txindex=1 server=1 disablewallet=0 timeout=6000 rpcuser=user rpcpassword=defaultxzxxxxx zmqpubrawblock=tcp://127.0.0.1:18502 zmqpubrawtx=tcp://127.0.0.1:18503 dbcache=2408
And LND.conf have this: (#) Auto-Generated Configuration File (#) Node Launcher version 6.0.2 debuglevel=info restlisten=127.0.0.1:8080 rpclisten=127.0.0.1:10009 tlsextraip=127.0.0.1 listen=127.0.0.1:9735 alias=aliasme color=#00aa7f bitcoin.active=1 bitcoin.node=bitcoind bitcoind.rpchost=127.0.0.1:8332 bitcoind.rpcuser=user bitcoind.rpcpass=defaultxxxxx bitcoind.zmqpubrawblock=tcp://127.0.0.1:18502 bitcoind.zmqpubrawtx=tcp://127.0.0.1:18503
So what is going on here? I will have to wait indefinitely? Somebody can give some help or explanation? Is this LND node working on Windows Server 2008 or 2012?
submitted by Mr--Robot 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]

04-07 09:48 - 'Lightning node on Windows - testing, get not connected' (self.Bitcoin) by /u/Mr--Robot removed from /r/Bitcoin within 845-855min

'''
Ok after testing BTCPay, C-Lightning, LND on Ubuntu I said ok let's try also the Windows implementation, is just few clicks and done (as it is promoted).
So I followed this [github guide]1 that actually send you to [this one]2 .
OK, started Bitcoin-core client on Windows 7 x64, with an already synced data folder. Empty bitcoin.conf (none of guides says how to configure the conf file). Wait until the client is full synced. And then launched the windows-node-launcher (from a subfolder inside Bitcoin folder). All good, started slowly and a small popup appeared in systray saying Bitcoin node is syncing. Reviewed the config of Bitcoin and LND through that little app in systray and saw that bitcoin.conf was already filled with some settings. Didn't change anything. After 1 day (with the bitcoin blockchain already synced), the systray popup still says that is syncing and have a red dot. In the tutorial says that we have to leave it to sync until is blue and then green.
I said, ok maybe it has more things to do. So I open that LND Output link, to see what is going on... And I see that LND is not well. Says: 2019-04-06 21:11:29.772 [INF] LTND: Version: 0.6.0-beta commit=v0.6-beta-rc3, build=production, logging=default 2019-04-06 21:11:29.772 [INF] LTND: Active chain: Bitcoin (network=mainnet) 2019-04-06 21:11:29.774 [INF] CHDB: Checking for schema update: latest_version=8, db_version=8 2019-04-06 21:11:29.808 [INF] RPCS: password RPC server listening on 127.0.0.1:10009 2019-04-06 21:11:29.808 [INF] RPCS: password gRPC proxy started at 127.0.0.1:8080 2019-04-06 21:11:29.808 [INF] LTND: Waiting for wallet encryption password. Use lncli create to create a wallet, lncli unlock to unlock an existing wallet, or lncli changepassword to change the password of an existing wallet and unlock it. 2019-04-06 21:11:32.673 [INF] LNWL: Opened wallet 2019-04-06 21:11:33.183 [INF] LTND: Primary chain is set to: bitcoin unable to create chain control: unable to connect to bitcoind: unable to subscribe for zmq block events: dial tcp 127.0.0.1:18502: connectex: No connection could be made because the target machine actively refused it. 2019-04-06 21:11:36.087 [INF] LTND: Shutdown complete unable to connect to bitcoind: unable to subscribe for zmq block events: dial tcp 127.0.0.1:18502: connectex: No connection could be made because the target machine actively refused it. 2019-04-06 21:11:39.229 [INF] LTND: Version: 0.6.0-beta commit=v0.6-beta-rc3, build=production, logging=default
Now the bitcoin.conf have this: printtoconsole=1 rpcallowip=::/0 whitelist=0.0.0.0/0 datadir=C:\Users\Admin\AppData\Roaming\Bitcoin prune=0 txindex=1 server=1 disablewallet=0 timeout=6000 rpcuser=user rpcpassword=defaultxzxxxxx zmqpubrawblock=[link]3 zmqpubrawtx=[link]4 dbcache=2408
And LND.conf have this: (#) Auto-Generated Configuration File (#) Node Launcher version 6.0.2 debuglevel=info restlisten=127.0.0.1:8080 rpclisten=127.0.0.1:10009 tlsextraip=127.0.0.1 listen=127.0.0.1:9735 alias=aliasme color=#00aa7f bitcoin.active=1 bitcoin.node=bitcoind bitcoind.rpchost=127.0.0.1:8332 bitcoind.rpcuser=user bitcoind.rpcpass=defaultxxxxx bitcoind.zmqpubrawblock=[link]3 bitcoind.zmqpubrawtx=[link]4
So what is going on here? I will have to wait indefinitely? Somebody can give some help or explanation? Is this LND node working on Windows Server 2008 or 2012?
'''
Lightning node on Windows - testing, get not connected
Go1dfish undelete link
unreddit undelete link
Author: Mr--Robot
1: g*thub.c*m/light**ng**o*e*-users/no**-launc**r 2: me*ium.*o**lig*tn**g-p*wer-users/w*n**ws-m**os-l**ht*i*g-ne*work-2*4bd5034340 3: 127.0.0**:1*5*2 4: 127*0.0**:185*3 5: 1**.0.0*1:185*2 6: 12*.0**.1:*8503
Unknown links are censored to prevent spreading illicit content.
submitted by removalbot to removalbot [link] [comments]

Bitcoind over tor. A miniguide from personal experience (I'm not an expert)

The problem

Light SPV clients are today the best solution to use bitcoin on a mobile without leaving your secret key in the hands of a company but:

Mitigation

1) With many SPV light clients today you can connect to nodes you choose and they can so be either trusted or even controlled by you (es: one node at home and one node at the office)
2) If this connection is over Tor you can avoid being eavesdropped by someone being it a criminal or a malicious or censoring third part
3) Your transactions are not linked to a given or known IP address

The setup

1) Download and synchronize the blockchain with your node
mv BitcoinDatadipeers.dat /tmp 
this will move the file peers.dat to /tmp (which is better for your privacy).
2) From your tor setup directory
cp torrc.sample torrc tor --hash-password "" ->  
to set up a control port and a password for an external application in our case is bitcoin
https://stem.torproject.org/tutorials/the_little_relay_that_could.html
3) add these lines to your torrc file

torrc

ControlPort 9051 CookieAuthentication 1 HashedControlPassword  
add these lines to your bitcoin.conf file

bitcoin.conf

 proxy=127.0.0.1:9050 listen=1 onlynet=onion listenonion=1 discover=0 torcontrol=127.0.0.1:9051 torpassword= 
4) start tor
tor 
5) start bitcoind
bitcoind -daemon 
On your mobile setup your SPV client to run on Tor.
Greenbits works well with Orbot.
Tell your client to connect via SPV to your new onion address.
Bonus: you don't need to open any port on your router at home or at the office.
This is a mini straight forward guide by a non expert.
I encourage you to study the documentation at
https://www.torproject.org/docs/documentation.html.en
as well as:
https://github.com/bitcoin/bitcoin/blob/mastedoc/tor.md
submitted by gabridome to Bitcoin [link] [comments]

Why is my BCC tx via btcABC showing on bitcoin blockchain and not BCC.

This should be impossible no? I close my bitcoin core 13.2. I install and run btcABC with datadir="X:/mybitcoincoredatadir" to save myself a few hundred gigs of duplicate chain data. I create a BCC deposit address on bittrex. I send .005 BCC to the address while 8 days behind on sync. I wait for it to broadcast.... wait.... wait.... still no broadcast after an hour so I grab the raw tx and open the console and do "sendrawtransaction blahb9blasdhfblahb9dsfh8486blah3145926etcetcetc" seems to finally broadcast. Now showing as not in mempool, no confs. I check tradeblock and blockchair and lo and behold: It's showing on bitcoin chain but not BCC. Good thing I don't control that address on the bitcoin chain ell oh ell.
I saw the "attempting to spend btc that are affected by not-yet-displayed txs will not be accepted" but fail to see the relevance as these are from inputs "already displayed"---a few weeks old that is. What the hell happened here? Is this client still so alpha that something as basic as sendrawtransaction is still propagated through the bitcoin chain? I'm not asking rhetorically or trying to be flippant here---I'd really like to know how this can be.
submitted by ohituna to btc [link] [comments]

How to easily make your own trustless BU Docker image for 1.0.0

Docker is awesome for running a BU node, but at the same time, I always felt very ambivalent about trusting bitcoin software being delivered by a 3rd party. What if they sneak in some kind of back door into my client?
For this reason, I think the best thing to do is to write your own basic docker package and build it yourself. Here's a basic sample for a Dockerfile to build BU 1.0.0 (I found it online and updated it slightly):
FROM debian:jessie ARG VERSION=1.0.0 ARG SHA256HASH=65b2061c7de35afa2f094f27aa48ef6c5a75a54ea0516948303a04c65ecbc2d5 RUN apt-get update && \ apt-get install -y wget ca-certificates && \ apt-get clean && \ wget https://www.bitcoinunlimited.info/downloads/bitcoinUnlimited-${VERSION}-linux64.tar.gz && \ echo "${SHA256HASH} bitcoinUnlimited-${VERSION}-linux64.tar.gz" | sha256sum -c - && \ tar -xzvf bitcoinUnlimited-${VERSION}-linux64.tar.gz -C /uslocal --strip-components=1 && \ rm bitcoinUnlimited-${VERSION}-linux64.tar.gz VOLUME /vabitcoin EXPOSE 8333 ENTRYPOINT ["bitcoind","-printtoconsole","-datadir=/vabitcoin","-dbcache=4000"] 
Anyone with a basic knowledge of Unix should be able to verify this script as legit. It downloads BU directly from the BU website over HTTPS. It checks the hash. It is all contained in this one file, so there's no code to chase around and verify. On Mac, I installed Docker using the package that the docker team provides on their website (rather than using brew) -- it's nice.
Create a new directory and place the above text into a file called "Dockerfile". From there, simply run:
docker build -t bitcoin-unlimited . docker image save bitcoin-unlimited | gzip > bitcoin-unlimited.tar.gz 
Congrats, now you have a docker archive created. You can generally import this archive wherever you want. For example, my Network Attached Storage server has support for containers, so I just imported it there using the web UI.
Note: the script I gave doesn't set up the bitcoin RPC stuff for being able to use bitcoin-cli. If you want to set that up, do something more like this guy's scripts: https://github.com/jrruethe/docker-bitcoin-unlimited
@ BU Team would love to have an official docker + vm image delivered securely from your site
submitted by garoththorp to btc [link] [comments]

everiToken's RocksDB

everiToken’s RocksDB
The boom of bitcoin prices brought the technology of block chain to the public, opened the era of block chain version 1.0. Later, the smart contract made the Ethereum known to everyone and opened up the era where everyone can Issue Tokens. However, block chain technology has a certain threshold, which is difficult for non programmers.
The block chain can be defined as a comprehensive technical solution consisting of encryption, producing blocks, consensus, storage and so on. Each individual can be used as a solution to practical problems. Similar to the traditional Internet industry, the development of block chain network can not be separated from three parts: computing power, bandwidth and storage.
The Ethereum represented the block chain version 2.0 which received hot attention. Not only for its smart contract, the underlying storage technology is also the focus of the technology enthusiasts.
From the Ethereum whitepaper we knew that Ethereum uses LevelDB as its Database. The Ethereum Clients can download the data from the nearby nodes and save them locally.
Ethereum’s LevelDB
LevelDB is Google’s open source key-value database, based on LSM algorithm. It can achieve efficient performance and support billions data.
We have known that a block contains a block header and a block body, but how is a block stored? The block information and transactions are finally stored in the LevelDB database, which maybe like datadigeth/chaindata. All data are stored in key-value pairs in Ethereum. In general, key is related to the hash while value is the data’s RLP code.
The advantages of using LevelDB database are:
- There is no need to run additional software as the LevelDB is in the process database.
- Using C++ native implementation, supports all cross platform operations supported by Go language.
- Key-value storage, value can be arbitrary binary encoding, no architectural constraints.
- Mature data storage, delamination of disks.
- Mature tracking records, allows many companies and other database to operate above it.
With smart contract’s storage standard, combined account’s StorageRoot to traverse all the key-value pairs in the LevelDB database. According to encoding rules, data reverse analysis and display are implemented which provides convenient and quick data operations for Dapp’s development and debugging.
Ethereum uses hash to identify the content. However hash is a uniform random distribution of identifiers. LevelDB stores keys alphabetically on disk so accessing hash-related values is costly. For a state tree, there will be hundreds of thousands of nodes that scatter and point to the disk. If there is no specific database modeled for Ethereum, it will be very difficult to optimize.
LevelDB is originally designed by Google for the disk backup memory database, performed well at first. As more and more disk access is needed, performance will gradually decrease. In addition, LevelDB is most efficient in using single thread insertion. Facebook’s RocksDB tries to solve these problems and multithreadeded background compression. Both written in C++, the RocksDB is more powerful.
The data storage scheme in Ethereum is not the perfect solution. Because of the characteristic of MPT, the update operation of the massive data storage account will bring the index level data access, which makes the execution of Ethereum’s smart contract very inefficient.
everiToken’s RocksDB
RocksDB is a key value database developed by Facebool. It has done a lot of optimization on the basis of LevelDB, which not only improves the performance, but also greatly increases the extensibility. RocksDB is a LevelDB’s upgrade version. In benchmarking, RocksDB performs better as well.
The design of everiToken not only draws the advantages of traditional matue database like LevelDB, but also takes into account the expensive cost of storage of pure memory(such as EOS.IO). The hybrid method can guarantee speed demand and ensure a certain economy. In general, it has high cost performance.
First, everiToken adopted RocksDB’s PlainTableFormat to its own characteristics. PlainTable is the RocksDB’s SST file format, optimized for pure memory queries with low latency or real low latency media. It has following advantages:
- Build a memory index to replace ordinary binary search with hash + binary search. That is to say, the keyword is not directly used as an array subscript, but the corresponding subscript is calculated according to the keyword, which is more in line with the complex storage.
- Bypass block catching to avoid block replication and LRU cache maintenance overhead.
- Avoid using any memory copy when querying. This method can reduce memory usage and speed up operation.
In short, PlainTableFormat does not optimize query performance maximization, but rather balances between query performance and memory consumption. PlainTable query performance is not as good as those hash tables that are specially designed, but it keeps the memory overhead at the lowest level while maintaining the same order of magnitude.
Secondly, everiToken's RocksDB adopts PrefixKey mode. Most LSM engines do not support efficient range lookup because all data files are accessed during lookup operations. For example, LevelDB does not support multithread merging. The support for key range lookup is still very simple, and no optimization measures are taken. RocksDB optimizes the corresponding underlying implementations based on these application scenarios.
The key point of PrefixKey's pattern design is to save time for lookup and to store key with the same prefix in the same place, so that all data will not be retrieved during the search, which greatly improves the use efficiency of the database.
Finally, everiToken tunes the parameters of RocksDB according to the characteristics of itself, which improves the database performance in various scenarios. Parameter tuning includes many aspects, not only some digital adjustments, but also related network structure adjustments and some function adjustments.
RocksDB parameter adjustment not only needs to support the configuration of various parameters in high pressure random reading, random writing, or the performance of the two, but also to prevent network problems, data security, and so on.
EveriToken uses RocksDB to make multifaceted modification according to the actual needs of its own project. This hybrid method is guaranteed in the aspects of scalability, performance, speed and so on. At the same time, it can also ensure a certain economy. Overall, the cost performance is very high, and the data storage technology may be popular in the future.
Conclusion
In the Internet world, computing power, storage and bandwidth are three core configurations, and block chains are the same. However, the public chain is in the early stage of development, and there are many places to be used for reference. The RocksDB database is a traditional industrial database model. This behavior on the shoulders of giants will be more convincing and more feasibility.
From above, in addition to the security of the traditional database, it also has a high cost performance, and is more in line with the practical application scene.
submitted by everiToken to u/everiToken [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]

everiToken's RocksDB • u/everiToken

everiToken’s RocksDB
The boom of bitcoin prices brought the technology of block chain to the public, opened the era of block chain version 1.0. Later, the smart contract made the Ethereum known to everyone and opened up the era where everyone can Issue Tokens. However, block chain technology has a certain threshold, which is difficult for non programmers.
The block chain can be defined as a comprehensive technical solution consisting of encryption, producing blocks, consensus, storage and so on. Each individual can be used as a solution to practical problems. Similar to the traditional Internet industry, the development of block chain network can not be separated from three parts: computing power, bandwidth and storage.
The Ethereum represented the block chain version 2.0 which received hot attention. Not only for its smart contract, the underlying storage technology is also the focus of the technology enthusiasts.
From the Ethereum whitepaper we knew that Ethereum uses LevelDB as its Database. The Ethereum Clients can download the data from the nearby nodes and save them locally.
Ethereum’s LevelDB
LevelDB is Google’s open source key-value database, based on LSM algorithm. It can achieve efficient performance and support billions data.
We have known that a block contains a block header and a block body, but how is a block stored? The block information and transactions are finally stored in the LevelDB database, which maybe like datadigeth/chaindata. All data are stored in key-value pairs in Ethereum. In general, key is related to the hash while value is the data’s RLP code.
The advantages of using LevelDB database are:
- There is no need to run additional software as the LevelDB is in the process database.
- Using C++ native implementation, supports all cross platform operations supported by Go language.
- Key-value storage, value can be arbitrary binary encoding, no architectural constraints.
- Mature data storage, delamination of disks.
- Mature tracking records, allows many companies and other database to operate above it.
With smart contract’s storage standard, combined account’s StorageRoot to traverse all the key-value pairs in the LevelDB database. According to encoding rules, data reverse analysis and display are implemented which provides convenient and quick data operations for Dapp’s development and debugging.
Ethereum uses hash to identify the content. However hash is a uniform random distribution of identifiers. LevelDB stores keys alphabetically on disk so accessing hash-related values is costly. For a state tree, there will be hundreds of thousands of nodes that scatter and point to the disk. If there is no specific database modeled for Ethereum, it will be very difficult to optimize.
LevelDB is originally designed by Google for the disk backup memory database, performed well at first. As more and more disk access is needed, performance will gradually decrease. In addition, LevelDB is most efficient in using single thread insertion. Facebook’s RocksDB tries to solve these problems and multithreadeded background compression. Both written in C++, the RocksDB is more powerful.
The data storage scheme in Ethereum is not the perfect solution. Because of the characteristic of MPT, the update operation of the massive data storage account will bring the index level data access, which makes the execution of Ethereum’s smart contract very inefficient.
everiToken’s RocksDB
RocksDB is a key value database developed by Facebool. It has done a lot of optimization on the basis of LevelDB, which not only improves the performance, but also greatly increases the extensibility. RocksDB is a LevelDB’s upgrade version. In benchmarking, RocksDB performs better as well.
The design of everiToken not only draws the advantages of traditional matue database like LevelDB, but also takes into account the expensive cost of storage of pure memory(such as EOS.IO). The hybrid method can guarantee speed demand and ensure a certain economy. In general, it has high cost performance.
First, everiToken adopted RocksDB’s PlainTableFormat to its own characteristics. PlainTable is the RocksDB’s SST file format, optimized for pure memory queries with low latency or real low latency media. It has following advantages:
- Build a memory index to replace ordinary binary search with hash + binary search. That is to say, the keyword is not directly used as an array subscript, but the corresponding subscript is calculated according to the keyword, which is more in line with the complex storage.
- Bypass block catching to avoid block replication and LRU cache maintenance overhead.
- Avoid using any memory copy when querying. This method can reduce memory usage and speed up operation.
In short, PlainTableFormat does not optimize query performance maximization, but rather balances between query performance and memory consumption. PlainTable query performance is not as good as those hash tables that are specially designed, but it keeps the memory overhead at the lowest level while maintaining the same order of magnitude.
Secondly, everiToken's RocksDB adopts PrefixKey mode. Most LSM engines do not support efficient range lookup because all data files are accessed during lookup operations. For example, LevelDB does not support multithread merging. The support for key range lookup is still very simple, and no optimization measures are taken. RocksDB optimizes the corresponding underlying implementations based on these application scenarios.
The key point of PrefixKey's pattern design is to save time for lookup and to store key with the same prefix in the same place, so that all data will not be retrieved during the search, which greatly improves the use efficiency of the database.
Finally, everiToken tunes the parameters of RocksDB according to the characteristics of itself, which improves the database performance in various scenarios. Parameter tuning includes many aspects, not only some digital adjustments, but also related network structure adjustments and some function adjustments.
RocksDB parameter adjustment not only needs to support the configuration of various parameters in high pressure random reading, random writing, or the performance of the two, but also to prevent network problems, data security, and so on.
EveriToken uses RocksDB to make multifaceted modification according to the actual needs of its own project. This hybrid method is guaranteed in the aspects of scalability, performance, speed and so on. At the same time, it can also ensure a certain economy. Overall, the cost performance is very high, and the data storage technology may be popular in the future.
Conclusion
In the Internet world, computing power, storage and bandwidth are three core configurations, and block chains are the same. However, the public chain is in the early stage of development, and there are many places to be used for reference. The RocksDB database is a traditional industrial database model. This behavior on the shoulders of giants will be more convincing and more feasibility.
From above, in addition to the security of the traditional database, it also has a high cost performance, and is more in line with the practical application scene.
submitted by Brady_everiToken to u/Brady_everiToken [link] [comments]

Guidance please on how to import .dat file in BTC core 0.16.0

Hi guys!
Backstory:
My old friend, somehow bought BTC before the mtgox hack, somewhere in 2013 probably. In fact he doesn't really remember. He gave me his MacBook, from which I've extracted the wallet.dat file, and made a couple of backups of said file.
Specs: Windows 10, x64 install of BTC core, have not fully synced the blockchain as of yet.
My current problem:
I've tried following this really helpfull guide, but I'm getting stuck since I cant find the datadir file to replace the wallet.dat file. (please note that I've installed the program files as well as the blockchain location on my secondary drive because that has enough space for the blockchain, and am currently trying again with program data in C, blockchain data in D).
My anticipated problem:
He has a guess about the passphrase its something in the format of 'vaalkeo12' or something. After I've exhausted the most logical combinations is there still a (semi-noobfriendly way to crack the passphrase)?
Assuming this goes well I'd then dumpwallet for a human readable version of the private key, said private key I could then import into for example electrum wallet, and then send the files to a new wallet, and make a paper wallet/usb stick backup of it.
To summarize my questions: - How do I replace the BTC Core wallet.dat if I cant find the datadir? (bitcoin.it's guide says you can choose a datadir by rightclicking the exe under properties but I see no such option? - If I cant find the right passhprase any reccomended course of action? - Once I have the private key, which client do you recommend me to import it in? - Any other pointers or things I should anticipate?
Any advice would be greatly appreciated!
Sorry for spelling/grammar, throwaway for privacy reasons!
Thank you for reading.
submitted by discardez to Bitcoin [link] [comments]

Bitcoin-qt keeps crashing - Fatal Error

Hello,
I've been using BTC since '10 and have always used the -QT client. PC died after a powercut yesterday and now I'm having huge issues trying to get bitcoin-qt up and running.
I have deleted the entire blockchain off my PC as I originally thought that was the issue.
From the debug.log this is what keeps appearing, followed by -qt shutting down.
2016-05-07 18:07:40 *** System error while flushing: CDB: Error -30974, can't open database 2016-05-07 18:07:42 UPnP Port Mapping successful. 2016-05-07 18:07:43 ERROR: ProcessNewBlock: ActivateBestChain failed 2016-05-07 18:07:43 addcon thread interrupt 2016-05-07 18:07:43 opencon thread interrupt 2016-05-07 18:07:43 net thread interrupt 2016-05-07 18:07:43 msghand thread interrupt 2016-05-07 18:07:44 scheduler thread interrupt 2016-05-07 18:07:44 Shutdown: In progress... 2016-05-07 18:07:44 StopNode() 2016-05-07 18:07:44 UPNP_DeletePortMapping() returned: 0 2016-05-07 18:07:44 upnp thread interrupt 2016-05-07 18:07:44 *** System error while flushing: CDB: Error -30974, can't open database 2016-05-07 18:07:45 CDBEnv::EnvShutdown: Error -30974 shutting down database environment: DB_RUNRECOVERY: Fatal error, run database recovery 2016-05-07 18:07:45 Shutdown: done 
I've started the client up again and it begins to connect to the network and re-download the blockchain but still crashes at about 4 years to go.
I don't think its a hdd space issue, I start the client with a datadir= set to a 50GB disk. (And now tried with 300gb drive)
I'm using latest version of the client.
Any ideas?
Thanks
submitted by just_some_guy101 to Bitcoin [link] [comments]

A simple script to ban peers from your node

#!/bin/bash # autoban.sh # shell script to automatically identify and ban certain bitcoin clients # developed and tested on Raspi3 (Raspian) # Step 1) Adjust BTC_CLI variable so it calls bitcoin-cli with the right parameters # My setup requires the -conf and -datadir parameters BTC_CLI="/uslocal/bin/bitcoin-cli -conf=/home/pi/bitcoin.conf -datadir=/media/usb0/btcdta" # Step 2) Enter the list of nodes you wish to ban separated with a comma # make sure the peer version doesn't contain any commas BANNED="/ViaBTC:bitpeer.0.2.0/,/BitcoinUnlimited:1.0.3(EB16;AD12)/,/Satoshi:1.14.4(2x)/,/bitcoinj:0.14.5/" #3) The main script based on mawk (not tested with awk or gawk) $BTC_CLI getpeerinfo | mawk -F":" -v banned="$BANNED" -v btccli="$BTC_CLI" -- ' BEGIN { split(banned,BAN,","); } /\"id\"*/ { id=substr($2,2,length($2)-2);ID[id]=id; } /^....\"addr\"/ { if (substr($2,3,1)=="[") { sadr = substr($0,index($0,":")); start = index(sadr,"["); end = index(sadr,"]"); IP[id]=substr(sadr,start,end-3); } else { IP[id]=substr($2,3); } } /\"subver\"*/ { s=length($1)+4; VER[id]=substr($0,s,(length($0)-s-1)); } END { for (id in ID) { for (banned in BAN) { if(VER[id]==BAN[banned]) { system(btccli" setban "IP[id]" add"); } } } }' #4) add script to the crontab to run periodically! 
submitted by kretchino to Bitcoin [link] [comments]

Database Encryption

Version 0.10.1 contains a bug fix for the database encryption and now the feature is usable if anyone wants to use it.
This has not yet made it into the user interface but if you're running the client and server separately or running the server on a remote machine you can use it.
The encryption covers your bitcoin wallet keys, order history, and chat messages. It does not cover your browsing history.
To use encryption you would run:
./openbazaar-go encryptdatabase 
And it will ask you for your password. It also takes a --datadir flag to specify the data directory if you want.
When you run the server with the start command it will ask you to enter your password.
submitted by Chris_Pacia to OpenBazaar [link] [comments]

Installing a Bitcoin XT full node to access your BCC

If you are already running a satoshi client, you can be up and running pretty quickly with BCC, using the invalidateblock method below to get yourself onto the Bitcoin Cash chain.
I tested this with XT release G. If you are using another satoshi-derived Bitcoin Cash full node implementation, please look for instructions for that client.
STEP 1
Make a copy of the entire data directory -- including the wallet file, if you want access to your BCC coins. Once you create this new copy of your wallet, treat it just as you treat any other independent wallet. Make backups. From the moment you start sending/receiving BCC, this wallet will contain different information than the BTC wallet you copied from (and that original wallet still controls your BTC!)
Another way to bring your coins over that some prefer is to export and import the private keys.
STEP 2
Getting ready to launch your XT client.
Use the -datadir parameter to point your new BCC client at your newly copied data directory when launching. If you accidentally forget to do this, and start doing BCC stuff with your existing directory, your wallet may quickly become broken for use with BTC
The easy, but very slow way to get onto the correct chain is, in addition to the -datadir parameter, specify the -reindex command-line parameter when launching Bitcoin XT the first time. The reindexing process could last several days before the program finishes launching.
Also, if you use -reindex, REMOVE it from your launch shortcut / command line before running next time, or you will start the whole reindex process over again next time!
QUICK METHOD TO GET ONTO THE RIGHT CHAIN
Launch with new -datadir as specified above, but do not use -reindex. Launch should be as quick as usual, but you will be on the wrong chain. You'll see your BTC balance (displayed as BCC) but you won't see any new blocks.
To get onto the right chain, go to Help->Debug Window->Console tab (or use bitcoin-cli on the command line), and issue the command
invalidateblock 00000000000000000019f112ec0a9982926f1258cdcc558dd7c3b7e5dc7fa148
This is the post-fork block on the BTC side.
This will take you back to the fork point, which is at block height 478558. It may take a while (an hour for me) for this to happen. The debug window doesn't provide status updates but you can look in the debug.log file for UpdateTip messages that show block height decreasing toward 478558 (and a log of SIGHASH_FORKID errors from all the unwound transactions that are not valid to Bitcoin Cash)
To make sure you don't get stuck at the fork point, also issue this command:
reconsiderblock 000000000000000000651ef99cb9fcbe0dadde1d424bd9f15ff20136191a5eec
This is the post-fork block on the BCC side.
At this point Bitcoin Cash blocks should begin arriving and you'll soon sync to the end of the Bitcoin Cash chain.
submitted by biosense to btc [link] [comments]

How to use OTS with local instance of bitcoin regtest, local OTS server & client?

Some problem I stumbled upon. I initialized local bitcoin regtest (bitcoin.conf file with regtest=1):
bitcoind -datadir=/home/wannamit/.bitcoin -daemon 
connected local OTS-server with that bitcoin server:
./otsd --btc-regtest --btc-min-confirmations 3 --btc-min-tx-interval 60 
Used OTS client to timestamp a FILE:
./ots -v -w s -c http://localhost:14788 FILE 
OTS Client log:
Calendar http://127.0.0.1:14788: No timestamp found Timestamp not complete; waiting 30 sec before trying again Checking calendar http://127.0.0.1:14788 for 5a799a175353bd5bf08d763b8e30d6986d425012defb7d00d37d521127d9e469cfed8eb7e1141d86a9d87129 ...
Mine some block in local bitcoin:
bitcoin-cli -datadir=/home/wannamit/.bitcoin generate 101 
OTS-server logs this while generate coin:
New block 1bc74a3bccfea0db820a2cffda21c21ca04f4addbcf8eafa423e650e11be6ad3 at height 278 New block 0304b3e0c075bfa78b03ffe674dbf848e1754816e61a931e010ebc8e6bebb5ae at height 279 ...
OTS-server logs this while client is waiting for verify:
127.0.0.1 - - [06/Feb/2018 18:05:10] "GET /timestamp/5a799d201baf82a0c6d50570d6af498955aedb8ac26d60ff71f9e2b5f61b354239b37949a6fe0edcb8ba666a HTTP/1.1" 404 - ...
This runs for long time still no stamping. Am I missing something for local OTS time stamping? Do we need multiple time stamping request in multiple file to built merkle tree before its gets timestamped or single file also works fine?
submitted by wannamit to u/wannamit [link] [comments]

Question: How to split Bitcoin Core data directory (Windows)

Hi,
Anyone could tell me how do I split the different parts of the data directory in windows between different folders?
Currently I have:
I'm using a "modified shortcut" with the "-datadir" command to run the app (in my PC) using the datadir everytime I plug the drive the external USB drive. (From what I read this should improve performance using an SSD without spending a lot of space in the SSD)
A shortcut with something like this: -datadir=X:\BTC\Bitcoin (this folder has my wallet and is over 80GB).
What I would like to achieve is to have the "chainstate" folder (It's a 2-3GB folder) in my local C: drive (SSD). But ALL the rest in my external USB drive.
So,
A) Is this possible? (To have chainstate and client in C: and the rest of the data directory with wallet in an external USB?)
Additionally. I'm going to buy a 1TB SSD. When that happens, I would like to have everything BUT the wallet in that local SSD. And the wallet, in an external drive. So everytime I want to run Bitcoin, I connect the USB drive (with the wallet) before opening the app. So:
B) How can I have the Wallet in an external USB drive, and all the rest of the data directory (without wallet) in my local drive?
Currently, the -datadir command is not useful, because I can't split the different components of the data directory.
BTW, I got this idea from here:
https://en.bitcoin.it/wiki/Data_directory#chainstate_subdirectory
https://en.bitcoin.it/wiki/Splitting_the_data_directory
I've tried to cut/paste the chainstate to another folder, but failed (because started to create a new chainstate folder) and now rolled back the original chainstate folder, and the app is "Rescanning"
Thanks!
EDIT: Ok I've done this. Now I understand the tutorial from https://en.bitcoin.it/wiki/Splitting_the_data_directory With the "mklink" a "symbolic link" is created. So: 1) I moved the "chainstate" folder from the external drive to the C: drive. 2) I created this symbolic link in my external USB drive. The link created is pointing to my C: drive's chainstate folder. I've never used symbolic links before....(had some idea of them from Android, but never in windows). I'll give this a try. So far the speed to build a block has been triplicated, maybe more. My progress increase per hour was 4%, now is 14% with 3GB cache
submitted by amenotef to BitcoinBeginners [link] [comments]

Bitcoin ABC won't sync, stuck at forking block

I tried running bitcoin abc by copying the datadir of bitcoin core and pointing it towards that, but the client won't sync. It's stuck at block 478558. I'm running in pruned mode.
submitted by iwakan to BitcoinABC [link] [comments]

Lost Bitcoin Address, Bitcore Core client

Hello, I'm in a state of panic right now. I had recently decided to transfer my bitcoin from an online wallet (Blockchain.info) into a local wallet(Bitcoin Core).
I had send bitcoin to one of the pre-generated receiving addresses, prior to syncing up with the block chain. After the client had finally finished, the receiving address was no longer listed.
I can view the transaction and the address on blockchain.info, and tried to use dumpprivkey on in using the debug window, but it said the private key for the address isn't known.
I'm not sure if this is relevant, but during the block chain syncing process, my SSD ran out of space, so I followed a tutorial to use my secondary HDD which has a larger capacity. The instructions told me to paste "-datadir=F:" into the target field of the program.
Please help.
submitted by fuckswithmoreducks to Bitcoin [link] [comments]

My Private Key = My Encryption Password?

Hello
I understand (rudimentary) that my Private key is equal to the access and ability to send my coins (BTC or Otherwise). My question though - is my private key, the same as the password I used when I setup "Encrypt Wallet" under the options menu? How can I get access to my private key to write it down and store it in a safe-deposit box?
I'll explain my setup, and you can tell me if it's awful or good?
I have an encrypted true-crypt flash-drive.
I have my bitcoin-qt shortcut pointing it's data-directory to the true-crypt flash-drive. (I deleted the old files from %appdata% and wiped them from the trashbin with CCleaner)
I insert my encrypted flash drive, mount the drive with truecrypt, then launch my Bitcoin-QT client which uses the truecrypt drive as its datadir. I DID select to "encrypt" the wallet within the bitcoin -qt application itself, irregardless of Truecrypt.
I signed up for coinbase and linked my bank accounts. I added some coins from USD a little while ago. Then I went into my addresses section of my wallet, and sent my coins to that address.
My question:Which file is the HOT file that I need to protect with my life? The entire "Wallet" set of files and their backups? WHere can I actually see my private key? Is my private key the same as my encryption password?
Please help me!
submitted by enolja to BitcoinBeginners [link] [comments]

The smoothest way to save all your block chain data on a different disk in Windows.

I've seen a lot of people ask about how they can save the block chain data on another disk than their C:\-drive. They usually get the answer to use -datadir , but this has a big drawback: You have to include the flag every time you open the client! Therefore I thought I'd write a little guide on how to set up a symbolic link in windows so that all your data are located at another disk without the client becoming confused. Here we go:
This will navigate you to the AppData folder.
This will create a symbolic link in the appdata folder by the name DarkCoin that will be pointing at the folder DarkCoin in your new location. Thus, if you or the client try to open DarkCoin in appdata you or it will see all the contents of the folder in your D:\-drive as if it never got moved, but it is in reality saved in your D:\-drive :)
I hope this little guide have been able to help a few people to save some of that precious SSD-space :)
edit: Format is a bitch, lol.
submitted by Darkcoins to DRKCoin [link] [comments]

zend server установка и настройка локально 3 часть CoinminingFarm Introduction - YouTube Home Networking 101 - How to Hook It All Up! - YouTube Changing cryptocurrency wallet location (Dogecoin - Bitcoin - Litecoin ....) Running an SQL Injection Attack - Computerphile - YouTube

I don't run my bitcoin client here very often (flash drive, re: datadir, etc) but I also noticed it didn't even use the par setting, maxconnections, addnodes, etc. ed: hmm, nm. no clue why it doesn't work. 1. Install Bitcoin-Qt Since version 0.9, Bitcoin-Qt was renamed to Bitcoin Core t o reduce confusion between Bitcoin-the-network and Bitcoin-the-software. Bitcoin Core is a full Bitcoin client. It is a thick client, meaning it requires the full blockchain (explained below) on local disk to operate and expose blockchain back to the network to help relay and verify transactions. Bitcoin's taking a lot of space on my C drive, and I would like to move it to another drive. I've figured out to do it using symbolic links, but the problem is that my Bitcoin client is currently Accordingly, the only thing you need to accept bitcoins is a bitcoin client on the server. It is called bitcoind, it’s just a console version of the client, with all the same familiar functionality. It works through the JSON-RPC protocol, is located under port 8332. All that remains after installation is to set up the client and Node.js. Install Bitcoind . To install, you will need to run ... bitcoin-core client datadir bitcoincore-gui. share improve this question follow edited Sep 16 at 11:36. Michael Folkson. 2,347 4 4 silver badges 14 14 bronze badges. asked Jun 20 '12 at 2:36. Chris Moore Chris Moore. 14.2k 5 5 gold badges 56 56 silver badges 83 83 bronze badges. I see questions which answer this for particular operating systems, but would like an answer to be able to ...

[index] [37481] [41458] [50036] [50154] [26276] [48998] [26635] [21982] [15956] [14585]

zend server установка и настройка локально 3 часть

In this a very nerdy, and requested video. We will be going over the basics of Home Networking. How to hook everything up, and what everything does. BREAKDOW... watchdog is a meme lmao Client: Sight https://www.sightclient.win/ Config: https://www.youtube.com/watch?v=xXcuC8oqJBM Bitcoin address for donations: 1FvXc5e... Welcome to part 4 of my Ethereum from scratch series. In the previous video we showed how to create and deploy your first smart contract on your local private test network and this week we take it ... COIN MINING FARM is an investment company, whose team is working on making money from the volatility of cryptocurrencies and offer great returns to our clients. Just how bad is it if your site is vulnerable to an SQL Injection? Dr Mike Pound shows us how they work. Cookie Stealing: https://youtu.be/T1QEs3mdJoc Rob Mi...

#