How To Install And Enable Bitcoin Core Wallet On Linux

How to get Energi Wallet running on Raspberry Pi 4

How to get Energi Wallet running on Raspberry Pi 4
I'm new to the Raspberry Pi and trying to get the NRG Core Cryptocurrency wallet running on my Raspberry. Finally I was able to compile the files after this commands:
Download and install the newest updates sudo apt-get update && sudo apt-get upgrade
Install the following major dependencies packages sudo apt-get install git build-essential libtool autotools-dev autoconf pkg-config libssl-dev libcrypto++-dev libevent-dev libminiupnpc-dev libgmp-dev libboost-all-dev devscripts libdb++-dev libsodium-dev
Install the following QT dependencies packages sudo apt-get install libqt5gui5 libqt5core5a libqt5dbus5 qttools5-dev qttools5-dev-tools libprotobuf-dev protobuf-compiler libcrypto++-dev libminiupnpc-dev qt5-default
Install bitcoin PPA files cd /etc/apt/sources.list.d/
sudo nano bitcoin.list
Add this line to the file: deb-src artful main
Close file
sudo apt-key adv --keyserver hkp:// --recv C70EF1F0305A1ADB9986DBD8D46F45428842CE5E
sudo apt-get update
Clone Github cd git clone
Install Libdb4.8 Libdb4.8-dev Libdb++ Libdb4.8++-dev
Compile the wallet cd energi ./ ./configure --with-boost-libdir=/uslib/arm-linux-gnueabihf make sudo make install
After compiling I see the files in /uslocal/bin
No I need to know how to use this files? Can someone help me please?
submitted by FCU4ever to energicryptocurrency [link] [comments]

[Lightning] I didn't believe it until I saw it

Moderately long post, tl;dr at the bottom.
I've seen lightning transaction gifs and videos over and over. Today, I decided to fire up a lightning node on my laptop and give it a shot.
I followed this walk-through for mac (I adapted it to Arch Linux) for setting up Bitcoin TestNet Node with Eclair Lightning (it's practically the same as Mac, except for the installation process). Running on Arch caused the problem of accidentally installing the latest dev version of Bitcoin Core (AUR:bitcoin-git) - also had some compilation issues because upstream moved some files and this hadn't been updated in the PKGBUILD.
The latest dev version of Bitcoin Core included the SegWit address generation by default, which was very nice, didn't have any bugs using it in the brief period I used it.
After a couple of hours of syncing the TestNet blocks on my laptop, I started up Eclair and got Eclair and Bitcoin Core connected (had to use bitcoin-qt --deprecatedrpc=addwitnessaddressbecuase Eclair calls a soon-to-be deprecated function), sent myself some tBTC, and started opening up channels. Once I had about 3 channels open, I went to everyone's favorite online coffee shop and rewarded myself with some imaginary coffee.
My mind was absolutely blown at how fast the transaction went through and how insanely low the fees were (10 sat).
I went to test a transaction with a couple more hops, bought myself an imaginary 100eur Steam voucher, paid 100 sat in fees, near instant transaction (my Eclair client took a couple seconds to find a route to bitrefill)
Lightning truly is an incredible addition to Bitcoin, big things are coming.
tl;dr - Saw a couple lightning transaction videos and gifs, didn't really sink in how amazing this really is, decided to give it a shot on linux, mind=blown
Edit: I've done a little further testing and noticed that Eclair doesn't warn you if you're opening a duplicate channel (open a second channel with the same node)
submitted by Kill3rism to Bitcoin [link] [comments]

(Updated) [Staking] Reddcoin Core client GUI wallet on a Raspberry Pi Model 3B


This thread is an update to my first Reddcoin staking tutorial that was written 7 months ago.
The reason for the update
My Reddcoin Core software crashed and became unusable. My Raspberry Pi 3B would lag and freeze, I couldn't stake anymore.
Instead of just redoing everything the same way, I wanted to see if I could improve on 3 points:
The updates
If you would like to tip me
Writing a tutorial like this takes time and effort; tips are appreciated. My Reddcoin address: RqvdnNX5MTam855Y2Vudv7yVgtXdcYaQAW.





This video shows how long it takes to start Reddcoin Core.   TL;DR:


Backup your wallet to prevent losing the RDDs in your wallet! There are two methods to backup, do both. Make new backups if you create a new receiving address!
Boot with only 1 USB drive plugged in:
Make sure only the USB drive (with the swap partition and data partition) is plugged in when you boot up your Raspberry Pi. This to make sure the swap partition (/dev/sda1) is recognized correctly.   If you boot up with multiple USB drives, Lubuntu might see the USB drive with the swap partition as the second drive (instead of the first drive), and ignore the 2 GB swap partition. If this happens, starting Reddcoin can render the Raspberry Pi unresponsive.
Connection issues If you have issues syncing the blockchain because you have 0 network connections, please follow the instructions in this thread.
Start Reddcoin Core easier
Run a shell script (.sh file), so you can start Reddcoin just by double clicking on an icon on your Desktop.
Minimization options
Adjust minimization options, so you can safely press on the X button (the close/exit button on the upper right corner).
RealVNC VNC Viewer (client) and VNC Connect (server): To remote connect to the Raspberry Pi, I use VNC Viewer ad VNC Connect from RealVNC.
Chromium as browser: The updates break Firefox, the browser crashes when you try to run it. Install another browser, Chromium, to solve this issue.
Updates / Upgrades
If Software Updater shows up and tells you that there is updated software available, do not install the updates using Software Updater. Use LXTerminal to update Lubuntu.  


Credits in previous tutorial:
submitted by Yavuz_Selim to reddCoin [link] [comments]

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

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 - 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 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)


This is the manual how to get started on you PC / MAC / Linux (I did it on Win7)
Go to: 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
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:
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:
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.


Here is what I did:
1) I installed Raspian Pixel ( 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:
Please have a look at it - I have copied the Headlines in capitals to let you know what I did, and what I skipped.
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 [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 cd bitcoin ./
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

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)
That's it for the raspi.
update: To signal UASF enter in a new line:


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:
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
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 and enable portforwarding for your raspberry pi - and open ports 8333 - that's it!
You can now go to:
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 @
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 )
  • 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, select Armory..
It leads to a Download from Git:
Followed the procedure for Linux Debian verify code, compile, install, all straight-forward..
Began by running bitcoind, and telling Armory where to find it. This is the command I used, obviously it was all on one line and didn't include the arrows/explanations!:
python \ --satoshi-datadir=/BlockChain/chain20180414/blocks \ # <-----(where my bitcoind blocks live) --datadir=/ArmoryDataDi \ # <-----(this is instead of ~/.armory) --dbdir=/ArmoryDataDidatabases # <-------(again, non std. place used for Armory's databases.. my choice.) 
So, on the Desktop, after the initial "build databases"
(NB the initial "Build Databases" took about 1.5h and my two CPUs were maxed the whole time, Temps up to 62C. Not ideal; Im not in a rush!)
I then wanted to import a watch-only wallet.
Before I did this, I took a full backup of the Armory data dir:
(or ~/.armory in a default installation).
I'd hate to have to make Armory do another full sync with the bitcoind node!

Section 2

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

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

Section 3

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

Section 4

I try running Armory like this:
(I'm actually starting Armory from a script -
Inside the script, it has the line:
python --ram-usage=4 --satoshi-datadir=/BlockChain/chain20180414/blocks --datadir=/ArmoryDataDi --dbdir=/ArmoryDataDidatabases 
I know from bitter experience that doing a scan over the blockchain for a new wallet takes a looong time and a lot of CPU, and I'd like it to play nicely; not gobble all the memory and swap and run my 2xCPUs both at 100% for four hours...
So... I aim to run with --ram-usage=X and --thread-count=X
(For me in the end, X=1 but I began with X=4)
I began with --ram-usage=4 (<--- = 4x128Mb)
The result is below...
TypeError: cannot concatenate 'str' and 'int' objects 
It didn't recognise the ram-usage and carried on, crippling my Debian desktop PC.
This is where it gets dangerous; Armory can gobble so much memory and CPU that the windowing environment can cease up, and it can take over 30 minutes just to exit nicely from bitcoind and ArmoryDB.
So, I ssh to the machine from another computer, and keep an eye on it with the command
"free -h" 
I'd also be able to do a "sudo reboot now" if needed from here.

Section 5

So, trying to get my --ram-usage command recognised, I tried this line (added quotes):
python --ram-usage="4" --satoshi-datadir=/BlockChain/chain20180414/blocks --datadir=/ArmoryDataDi --dbdir=/ArmoryDataDidatabases 
But no, same error...
Loading Armory Engine: Armory Version: 0.96.4 Armory Build: None PyBtcWallet Version: 1.35 Detected Operating system: Linux OS Variant : ('debian', '9.4', '') User home-directory : /home/ Satoshi BTC directory : /BlockChain/chain20180414 Armory home dir : /ArmoryDataDi ArmoryDB directory : /ArmoryDataDidatabases Armory settings file : /ArmoryDataDiArmorySettings.txt Armory log file : /ArmoryDataDiarmorylog.txt Do wallet checking : True (ERROR) - Unsupported language specified. Defaulting to English (en) (ERROR) - Failed to start Armory database: cannot concatenate 'str' and 'int' objects Traceback (most recent call last): File "", line 1808, in startArmoryDBIfNecessary TheSDM.spawnDB(str(ARMORY_HOME_DIR), TheBDM.armoryDBDir) File "/BitcoinArmory/", line 387, in spawnDB pargs.append('--ram-usage=' + ARMORY_RAM_USAGE) TypeError: cannot concatenate 'str' and 'int' objects 

Section 6

So, I edit the Armory python file
if ARMORY_RAM_USAGE != -1: pargs.append('--ram-usage=4') #COMMENTED THIS, SO I CAN HARDCODE =4 # ' + ARMORY_RAM_USAGE) 
Running it, I now have acknowledgement of the --ram-usage=4:
(WARNING) - Spawning DB with command: /BitcoinArmory/ArmoryDB --db-type="DB_FULL" --cookie --satoshi-datadir="/BlockChain/chain20180414/blocks" --datadir="/ArmoryDataDi" --dbdir="/ArmoryDataDidatabases" --ram-usage=4 
Also, even with ram-usage=4, it used too much memory, so I told it to quit.
It took over 30 minutes to stop semi-nicely. The last thing it reported was:
ERROR - 00:25:21: (StringSockets.cpp:351) FcgiSocket::writeAndRead FcgiError: unexpected fcgi header version 
But that didn't seem to matter or corrupt the Armory Database, so I think it's ok.
So, I get brave and change as below, and I make sure my script has a command line for --ram-usage="ABCDE" and --thread-count="FGHIJ"; the logic being that these strings "ABCDE" will pass the IF criteria below, and my hardcoded values will be used...
if ARMORY_RAM_USAGE != -1: pargs.append('--ram-usage=1') #COMMENTED THIS, SO I CAN HARDCODE =1 # ' + ARMORY_RAM_USAGE) if ARMORY_THREAD_COUNT != -1 pargs.append('--thread-count=1') #COMMENTED THIS, SO I CAN HARDCODE =1 #' + ARMORY_THREAD_COUNT) 
So, as usual, I use my script and start this with: ./
(which uses command line:)
python --ram-usage="ABCDE" --thread-count="FGHIJ" --satoshi-datadir=/BlockChain/chain20180414/blocks --datadir=/ArmoryDataDi --dbdir=/ArmoryDataDidatabases 
(this forces it to use my hard-coded values in
So, this is the command which it reports that it starts with:
(WARNING) - Spawning DB with command: /BitcoinArmory/ArmoryDB --db-type="DB_FULL" --cookie --satoshi-datadir="/BlockChain/chain20180414/blocks" --datadir="/ArmoryDataDi" --dbdir="/ArmoryDataDidatabases" --ram-usage=1 --thread-count=1 
Again, this is where it gets dangerous; Armory can gobble so much memory and CPU that the windowing environment can cease up. So I ssh to the machine and keep an eye on it with:
"free -h" 

Section 7

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

Section 8

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

Homelab collective ressources post!

Hey guys!
I'm fairly new to this sub and to having a home lab in general and I found this community to be so kind and helping, I wanted to give back what I've learned. I'm seeing a lot of questions asked around on improvements and on what to do with x extra hardware so I thought it would be nice to have a thread to regroup that.
I'll put here some stuff I gathered and the most common questions I've seen, feel free to contribute and i'll update the post along.
Latest Additions
Homelab Dashboard
Posts about dashboards have been growing lately and here are some of the best that were kind enough to provide us with their sources.
User Screenshot Source
yours truly
NiknakSi TBA
yourofl10 TBA
mescon & SyNiK4L
Or build yours from scratch: PRTG API, ELK, Grafana, freeboard, JumpSquares
Some other resources: Custom Monitoring Scripts by 0110010001100010
Credits to apt64 for his original post
= Pi specific =
= Download Automation =
= Virtualization =
= Monitoring =
= Media Center =
= Remote access =
= VOIP =
= Networking =
= File Servers/Storage/RAID =
= Cameras =
= Documentation =
= Dynamic DNS =
= Backup =
= Creating network diagrams =
= Guides =
= Misc =
That's all I could come up with on top of my head + some research, passing over to you guys so we can get a nice complete list!
Let's try and stick with free(or mostly) softwares, let me know if you guys feel otherwise.
submitted by Gabisonfire to homelab [link] [comments]

Walk through of how to claim BCD Bitcoin Diamond

I am completely naive when it comes to Linux, coding, compiling, etc., so I found it difficult to follow advice I found for compiling the bitcoin diamond code form git. I followed a few guides for bitcoin core first and could never get it to work. I got some help from someone that knows Linux and here's what finally worked for me with BCD.
Use rufus to make bootable usb with ubuntu iso. (
Boot from the usb and install ubuntu.
Follow this guide to compile bitcoin from git:
Do the entire guide with bitcoin core to ensure everything is working.
Make sure you replace "theusername" with your own each time it appears, or make "theusername" your user name from the beginning.
There was one small difference, at the end of the guide to run bitcoin-qt it is ./src/qt/bitcoin-qt
At the end when trying to run bitcoin-qt (./src/bitcoin-qt) it said there was no such file, which made me think that I did something wrong but you just have to find where the file is. Hey, I said I was a complete noob, go easy on me.
When you repeat the procedure for BCD there will be a few small changes:
git clone
git clone
mkdir bitcoin/db4/
mkdir BitcoinDiamond/db4/
../dist/configure --enable-cxx --disable-shared --with-pic --prefix=/home/theusername/bitcoin/db4/
../dist/configure --enable-cxx --disable-shared --with-pic --prefix=/home/theusername/BitcoinDiamond/db4/
./configure LDFLAGS="-L/home/theusername/bitcoin/db4/lib/" CPPFLAGS="-I/home/theusername/bitcoin/db4/include/"
./configure LDFLAGS="-L/home/theusername/BitcoinDiamond/db4/lib/" CPPFLAGS="-I/home/theusername/BitcoinDiamond/db4/include/"
when you get to this line: [email protected]:~/BitcoinDiamond$ ./
I got the following error:
bash: ./ Permission denied
this command will show some information about
[email protected]:~/BitcoinDiamond$ ls -l
-rw-rw-r-- 1 mmmmm mmmmm 527 Dec 30 21:26
same command comparing it to the bitcoin core version of
$ ls -l ../bitcoin/
-rwxrwxr-x 1 mmmmm mmmmm 527 Dec 30 21:03 ../bitcoin/
do this to make them the same
[email protected]:~/BitcoinDiamond$ chmod a+x
recheck and it should match the bitcoin core now
[email protected]:~/BitcoinDiamond$ ls -l
-rwxrwxr-x 1 mmmmm mmmmm 527 Dec 30 21:26
continue on
[email protected]:~/BitcoinDiamond$ ./
[email protected]:~/BitcoinDiamond$ ./configure LDFLAGS="-L/home/mmmmm/BitcoinDiamond/db4/lib/" CPPFLAGS="-I/home/mmmmm/BitcoinDiamond/db4/include/"
[email protected]:~/BitcoinDiamond$ make -s -j5
It will work a while and then you'll get the following error, among others:
/bin/bash: ../share/ Permission denied
It's the same error as with, so find it and fix it by the following:
[email protected]:~/BitcoinDiamond$ find . -name ./share/
[email protected]:~/BitcoinDiamond$ chmod a+x ./share/
continue on by restarting make
[email protected]:~/BitcoinDiamond$ make -s -j5
It should be good!
go to and run bitcoin-qt to start the gui
[email protected]:~/BitcoinDiamond/src$ cd qt
[email protected]:~/BitcoinDiamond/src/qt$ ./bitcoin-qt
bitcoin-wt will spend some hours syncing the entire blockchain so you have to wait.
When it is finished, import private keys by:
clicking in the "Bitcoin Core - Wallet" window to make it active
hover mouse in top left of the grey bar on the top of the deskto screen, not the "Bitcoin Core - Wallet" until it says "file settings help"
click on "help"
click on "Debug Window"
click on the "Console" tab
enter "importprivkey 5KJvsngHeMpm884wtkJNzQGaCErckhHJBGFsvd3VyK5qMZXj3hS" with your own key
make an account at where they are allowing deposits
sell!, or don't, maybe you're nuts, who am I to judge
submitted by Ozmodiar to BitcoinAirdrops [link] [comments]

Dogecoin on Linux - The Complete Beginner's Guide

I'm writing this because I couldn't find a single condensed guide on compiling the wallet and running mining software on linux, specficially Ubuntu/Linux Mint. I combed Bitcoin and Litecoin forums for similar problems I was running into and eventually got everything nailed down, so here it is in one place, for new Shibes.
If you want to make a Dogecoin directory in your downloads folder to keep things organized, you will need to modify these commands to refelct the change. So instead of going to ~/Downloads/ you will need to go to ~/Downloads/Dogecoin and be sure to put the zipped files there when you download them, but the commands will be the same otherwise.
cwayne18 put in the work to make a PPA for the QT client here.
Ubunutu/Mint/Debian users should be able to install the client with the following commands:
sudo add-apt-repository ppa:cwayne18/doge sudo apt-get update && sudo apt-get install dogecoin-qt 
To update using this method, run
sudo apt-get update && sudo apt-get upgrade dogecoin-qt 
Compiling the Wallet Manually
I suggest using the PPA above, but if you want to compile manually, here you go.
1)Download the newest source from here. If you want to check out the Github page, click here
2)Unzip the package with the native client OR, navigate to your downloads and unzip
cd ~/Downloads unzip 
3)Now it's time to compile. You will need to install the dependencies, just copy and paste the following code. It will be a fairly large download and could take some time. It is always important to update before installing any new software, so we'll do that first and then install the dependencies.
sudo apt-get update sudo apt-get upgrade sudo apt-get install libssl-dev libdb-dev libdb++-dev libqrencode-dev qt4-qmake libqtgui4 libqt4-dev sudo apt-get install libminiupnpc-dev libminiupnpc8 libboost-all-dev build-essential git libboost1.53-all-dev 
4)Once that is done, go to the doge-coin master directory and compile:
cd ~/Downloads/dogecoin-maste sed -i 's/-mgw46-mt-sd-1_53//g' qmake USE_UPNP=- USE_QRCODE=0 USE_IPV6=0 make -j3 
After running the qmake command you will likely see some text similar to
Project MESSAGE: Building without UPNP support Project MESSAGE: Building with UPNP supportRemoved plural forms as the target language has less forms. If this sounds wrong, possibly the target language is not set or recognized. 
It's perfectly normal, so don't worry about that.
Your Dogewallet is ready to go! The executable is in ~/Downloads/dogecoin-maste and called dogecoin-qt. Your wallet information is in ~/.dogecoin. You can run the wallet at any time by opening terminal and typing
cd ~/Downloads/dogecoin-maste ./dogecoin-qt 
Future upgrades to dogewallet are easy. Back up your wallet.dat, and simply follow the same directions above, but you'll be unzipping and building the newer version. You will likely need to rename the old dogecoin-master directory in ~/Downloads before unzipping the newest version and building. Also, it is likely that you will not need to install the dependencies again.
Alternate Method For Installing Dogecoin Wallet from Nicebreakfast
After installing the dependencies listed in step 3, open terminal, then navigate to where you want Dogecoin Wallet stored and run:
git clone ./ ./configure make 
then when the wallet is updated just run
git pull 
from the dogecoin directory.
GPU Mining
GPU mining requires CGminer. My suggestion is to get the executable already built. The creator of cgminer has removed the built file from his website, but I've uploaded it here
sudo apt-get install pkg-config opencl-dev libcurl4-openssl-dev autoconf libtool automake m4 ncurses-dev cd ~/Downloads tar -xvf cgminer-3.7.2-x86_64-built.tar.bz2 
Don't use anything newer than 3.7.2. The newer versions of CGMiner don't support GPU mining.
That's it! You have cgminer ready to go! You will run cgminer with the following syntax
cd ~/Downloads/cgminer-3.7.2-x86_64-built/ ./cgminer --scrypt -o stratum+tcp://SERVERNAME:PORT -u WORKER.ID -p PASS 
A good guide for fine tuning cgminer can be found here; follow the litecoin example.
I had trouble getting cgminer running with a single line command, but running it via an executable .sh file works. This is covered in the cgminer setup guide I posted above but I'll put it here too. In the same directory that has the cgminer executable, you need to make a file called and make it executable. It should contain the follwing:
export GPU_USE_SYNC_OBJECTS=1 export GPU_MAX_ALLOC_PERCENT=100 export DISPLAY=:0 find *.bin -delete sleep 5 ./cgminer 
Then you can call cgminer in terminal by doing ./ You will need a cgminer.conf file containing all your options. All of this is covered in the guide that is linked above.
A quick note about AMD drivers: They used to be a huge PITA to install and get working, but the newest Catalyst drivers are great. There's a GUI installer, everything works out of the box, and there is a lot of documentation. You can download them here: AMD Catalyst 14.6 Beta Linux
CPU Mining
For CPU mining I use minerd because it doesn't require any work to get running, simply download it and get to work. Download the built file for your machine 32-bit or 64-bit, and then unzip it and you're ready to go!
cd ~/Downloads tar -xvf pooler-cpuminer-2.3.2-linux-x86.tar.gz 
The executable is called minerd and it will be in ~/Downloads but you can move it to wherever you like. To run it, pull up terminal and do
cd ~/Downloads minerd --url=stratum+tcp://SERVER:PORT --userpass=USERNAME.WORKERNAME:WORKERPASSWORD 
You're done! Happy mining!
Common Issues
I ran into this and I've seen others with this problem as well. Everything installs fine but there is a shared library file that isn't where it should be. In fact, it isn't there at all. cannot open shared object file: No such file or directory 
In terminal, do
sudo updatedb locate 
And it will probably return a path /lib/x86_64-linux-gnu. Inside that directory there's a library file called You'll need to make a symlink (aka shortcut) that links to So, assuming you're working with do this
cd /lib/x86_64-linux-gnu sudo ln -s 
Now if you do
ln -l 
You should see -> ./ 
Meaning you've made the symlink. Also, the text for will be blue.
submitted by Boozybrain to dogecoin [link] [comments]

How to Mine BiblePay on Linux

This guide is outdated, please refer to:
IMPORTANT - Evolution Upgrade:
Quick Start
Evolution Upgrade Information
Getting Started with Evolution
Generic Smart Contracts
What is BiblePay Evolution?
Recommend 2GB RAM or can get stuck compiling (if 1GB RAM can use Swap File) Use Ubuntu 16.04
apt-get install build-essential libtool autotools-dev automake pkg-config libssl-dev libevent-dev bsdmainutils apt-get install libboost-system-dev libboost-filesystem-dev libboost-chrono-dev libboost-program-options-dev libboost-test-dev libboost-thread-dev apt-get install libqt5gui5 libqt5core5a libqt5dbus5 qttools5-dev qttools5-dev-tools libprotobuf-dev protobuf-compiler apt-get install git apt-get install curl build-essential libtool autotools-dev automake pkg-config python3 bsdmainutils cmake sudo add-apt-repository ppa:bitcoin/bitcoin sudo apt-get update sudo apt-get install libdb4.8-dev libdb4.8++-dev git clone prefix=x86_64-pc-linux-gnu cd biblepay-evolution/depends make -j4 # Choose a good -j value, depending on the number of CPU cores available cd .. ./ #Note: if echo `pwd` does not return your working directory, replace it with your working directory such as /biblepay-evolution/ ./configure --prefix `pwd`/depends/x86_64-pc-linux-gnu make # See more here: # 

NOTE: if server is 1GB RAM, before running last command "sudo make", set up a swap file
free #check if swap is 0 dd if=/dev/zero of=/vaswap.img bs=1024k count=1000 mkswap /vaswap.img swapon /vaswap.img free #check if swap is 1024 sudo make 

cd src ./biblepayd -daemon 
Your GUI program will be located in: /biblepay-evolution/src/qt
You can also run it in the background (to free up your terminal) if you call it with:
./biblepay-qt & 
To start mining, instructions are the same as for Windows: Go to Tools -> Debug Console
Execute this command (to start mining with 8 threads)
setgenerate true 8 
From there you can use all other commands such as getmininginfo, getwalletinfo, etc. Execute help command to get the list of all available commands.
Note: GUI will be built automatically only if you meet the requirements for qt library, i.e. make sure you ran this line before compiling:
sudo apt-get install libqt5gui5 libqt5core5a libqt5dbus5 qttools5-dev qttools5-dev-tools libprotobuf-dev protobuf-compiler 
BIBLEPAY is now Running!

Stop BiblePay and set up the config file to get starting nodes to sync with and enable mining:
./biblepay-cli stop cd ~/.biblepayevolution/ vi biblepay.conf gen=1 genproclimit=1 
Escape Key + : (Colon Key) + w + q + Enter (saves file and quits)

addnode --- adds a node to the list of nodes to connect to gen=1 --- turns on mining genproclimit --- sets number of threads to use when mining

Run BiblePay again and fully sync with network
cd ../biblepay-evolution/src ./biblepayd -daemon ./biblepay-cli getinfo 

./biblepay-cli help ./biblepay-cli getaccountaddress "" ./biblepay-cli getinfo ./biblepay-cli getmininginfo ./biblepay-cli setgenerate true 8 ./biblepay-cli sendtoaddress "insertAddressHere" 777 "" "" true ./biblepay-cli stop ./biblepayd -daemon top #CPU usage q to quit 

MINING THREADS: To change number of threads to use up for mining
a. Edit home/yourusername/.biblepayevolution/biblepay.conf file:
and restart BiblePay -or- b. Menu >> Tools >> Debug Console >> Type command:
setgenerate true X 
(Replace X with number of threads Use top command to view CPU usage)

NOTE: To use the pool you must now use the external miner, not the wallet miner
  1. Set up an account on pool website:
  2. Create Worker Username(s) - Workers tab >>> Add
  3. Enable pool and add Worker Username in ~/.biblepayevolution/biblepay.conf file, add these lines and save:
    pool= workerid=insertWorkerUsernameHere
4. Restart BiblePay
./biblepay-cli stop ./biblepayd -daemon 
Setup Auto-Withdraw Navigate to Account >>> Account Settings >>> Verify your BBP Receiving Address >>> Click Authorize-Auto-Withdraws


### Turn off/stop BiblePay
cd /home/yourname/biblepay-evolution/src ./biblepay-cli stop 

### Pull down latest Biblepay code and build it
cd /home/yourname/biblepay-evolution git pull origin master sudo make 

### Turn BiblePay back on and check version number
cd src ./biblepayd -daemon ./biblepay-cli getinfo ./biblepay-cli setgenerate true 8 

./biblepay-evolution/src/biblepay-cli stop ; cd && cd biblepay-evolution/ && git pull origin master && sudo make && cd src && ./biblepayd -daemon && sleep 90 && ./biblepay-cli getmininginfo 
Note: the ";" says do this after, regardless of the outcome Note: && says do this after only if previous command finished with no errors

To speed up the compile time, add -j4 or -j8 after make. This way it compiles using 4 or 8 threads instead of just 1.
./configure LDFLAGS="-L${BDB_PREFIX}/lib/" CPPFLAGS="-I${BDB_PREFIX}/include/" sudo make -j8 

RSYNC stop biblepay from your nodes compile on your fastest machine then rsync with your machines only src folder is required
rsync -avuz /root/biblepay-evolution/src/ [email protected]:/root/biblepay-evolution/src/
people make cron jobs and rsync automatically


Unofficial Bash Script

Official Ubuntu Package

Unofficial Ubuntu Package

Unofficial Mine in One Line


DOCKER IMAGES (NOTE: I havent tested these, use at your own risk)
submitted by togoshige to BiblePay [link] [comments]

WIP: Blackpi - a stake device based on raspberry

Warning: This is a WiP and it's using Blackcoin Lore which is still in beta. Please be aware of that and backup your wallet.dat before you put any real values in this!
I am currently trying to set up blackoin on raspberry. Community members asked for a tutorial to compile it, so I will start with this here. Maybe in the future it would even be possible to turn it into a headless (=without screen and keyboard) image to put on an SD card and just boot up the wallet.
I used the latest Blackcoin Lore by janko33 for this process, however it should be quite the same with the "original" core wallet by rat4/johndolittle. Blackcoin Lore is not deemed as stable as it is still in beta, so it's up to you what source tree you take.
Please be also aware, that compiling on a small computer like raspi can take a while. Please also note that Lore is still in beta. The names in the archive are still "bitcoin". There is an update comming where the naming is correct and also maybe a few bugfixes.
** Tutorial: **
You first need to get raspbian. The lite image will work, it's a small version of the operating system without a graphical interface, so you will need ssh to operate it. The image is 294 MB but you will want to have a bigger card. 2GB is certainly too small, better get 16 or even 32GB - you also will need space for the blockchain!
To install it I followed this guide
Get the raspdian image file from:
Also get Etcher from
Etcher is a tool to write img files to an SD card/USB-stick.
After writing, open the card in your explorer and add a file "ssh". The file sould be empty and just be called "ssh" (not ssh.txt or something). It will tell raspi to activate ssh on boot.
Then boot up your raspi with the card and plug it into your network. Consult your router's LAN-page to find the device, it should register to your router as "raspberry" or so. Open up Putty and login to your raspi using pi as username and raspberry as password.
After login you can configure your raspi, please read the guide linked above for more details.
Note: One important thing that you should configure is your timezone! Use
sudo raspi-config 
Go to 4. Localisation Options and set the time to your timezone. If your time is way off, you would get troubles with staking, so make sure you always have the time set right!
After you got everything set up, get the build environment ready:
sudo apt-get install build-essential libtool autotools-dev automake pkg-config libssl-dev libevent-dev bsdmainutils #Installs alot and can take a while git clone -b Blackcoin-Lore Blackcoin-Lore cd Blackcoin-Lore cd depends make -j 6 HOST=arm-linux-gnueabihf cd .. ./ ./configure --prefix=`pwd`/depends/arm-linux-gnueabihf 
# note: ` = is a "backtick" not an apostroph. It causes the outpupt of "pwd" being inserted there
make -j 6 # -j n tells the compiler to use more cores, speeds that up a little (n = 1.5*cores installed) sudo make install 
This should compile so far. Update: Lore does not need Berkeley DB 4.8 to be installed, so just go with the DB provided by the repository works (libdb++-dev). (Thanks patcrypt)
After compile you can run the wallet with
And after it synced you have bitcoin-cli to control the wallet.
Issue: Synching blocks takes an awfully long time on raspi for some reason, even with Lore (that syncs blocks in a few hours instead of a whole day on a normal computer). If anyone knows how to speed up that process, please let us know!
This thread is a WiP. Please post all issues and errors here, I will then edit the OP to make it into a real, working tutorial.
On a note it was mentioned, that using an USB-stick here instead of a card would make sense since the cards are more prone to failure than USB-sticks. I will include setting it up on USB in a later version of this tutorial.
Some tips and tricks
Since compiling takes a longer time, it is recommented to run it in the console in a screen. Screen is a terminal tool that supports multiple windows in the same shell and, most important, detaches when your ssh connection breaks. Using screen you can simply reconnect and use screen -r to attach to your running shell again. To use screen, you need to install and then start it before you start the whole build process within a screen-shell.
sudo apt-get install screen screen #Start install/build process here #Type [ctrl-a] [d] to detach from the screen and put it in the background #After reconnect type screen -r to jump back into your running shell 
If you want to see your blocks being processed while the wallet syncs to the network, use the following command on a second shell (new Putty instance or screen window which you can open in screen with [ctrl-a] [c] (hit [ctrl-a] [n] to cycle through the windows in screen)
watch -n 5 lore-cli getinfo #This will execute the command "bitcoin-cli getinfo" every 5 seconds and thus display live update of your wallet info 
How to use that thing?
Here are a few helpful CLI commands, call them with lore-cli
help - Returns available commands help  - Returns detailed help to a  getinfo - Returns a descriptive information of your wallet, including balance getwalletinfo - Returns short information about your wallet, including balance, unconfirmed balance, immature balance, number of tx ect getaccountaddress 'raspi' - Returns an address for your wallet. If the account does not need to exist, it will be created with new address sendtoaddress   - Sends  to  sendtoaddress   substractfeefromaccount - Sends  minus tx fee to  getnewaddress  - Returns a new address for  each time you call the command.  is optional 
Further plans for this tutorial/project
Have fun!
Donations: B4nn2Y3SFC6whNGNvcQ2MvV1aQbZp3cZVF
submitted by mindphuk to blackcoin [link] [comments]

A guide to sign a super bitcoin (SBTC) transaction offline with patched Electrum for paranoid. Supports any wallets supported by Electrum (including segwit-p2sh and bech32 and all BIP39 seeds). Later BCD will be added.

This is quite advanced. This guide assumes you have some basic experience with the command line, can run Linux and you understand the basics of keys/signing/broadcasting transactions. And that you can compile and run Bitcoin Core and run Electrum. Also, some JSON experience is also nice.
Move you bitcoins to safe addresses first. It is best to use a new seed. Although the procedure in this guide is safe even for hot addresses (containing bitcoins), there is always a risk of a critical mistake. So play it safe.
Why such a guide? I followed these steps because I did not want to expose the keys to any online machine at all. Even if the keys do not have any bitcoins, you can some day have bitcoins sent to these addresses or you have a fork that you have not claimed. All can be stolen if you exposed your key.
This procedure should work with everything that Electrum supports (except maybe F2A that may be not supported on the SBTC chain), so Electrum seed legacy or segwit, LedgeTrezor with legacy or segiwt-p2sh (m/'49) derivation. Similarly, any BIP39 seeds or a single key. are also fine.
  1. Download Electrum. git clone
  2. Apply my patch patch -P0 also this article. The guide assumes that you use patched Electrum from now on.
  3. Run the patched Electrum and catch up with your wallets you want to claim (the wallets can and rather should be watch only, or on ledgetrezor, otherwise your keys are exposed). Now go offline or set localhost as your server that Electrum connects to so no connection is performed. It's required so Electrum will not update the wallet after you edit it.
  4. You can manually create a transaction from the command line but you can use Electrum GUI. You need to locate the wallet file and remove all the transactions from the wallet file except for the one that funds the address you want to claim (the wallet obviously must not be encrypted but for watch-only this is OK). This is tricky. You need to make sure, you gave a proper JSON file, so all the final commas must be dropped. So "addr_history":, "transactions": , "tx_fees":, "txi", "txo", and "verified_tx3": should only contain the funding transaction(s), i.e. the one that you want to spend from.
  5. Run Electrum and check if the wallet is OK. Electrum will show an error if not. You will probably make a few errors so go back to editing the wallet.
  6. Download SBTC bitcoin core clone. git clone
  7. Compile it and let it sync the blockchain (it will take a long time). Run it it with as large -dbcache= as you can. If you have a Bitcoin blockchain you can copy the blocks up to the fork date and issue sbtcd with -reindex. It will just reindex them and it will be faster.
  8. Generate a sbtc address with sbtc-cli getnewaddress. You can skip this step and send directly to an exchange but this intermediate step is safer.
  9. Create a transaction in Electrum to this address. Select all the bitcoins and use as small fee as possible (SBTC blocks are empty so any fee above 1 SBTCsat/byte should be OK).
  10. Save the transaction to a pendrive
  11. Download and install Kubuntu 16.04 (Kubuntu has all the QT libraries for Electrum) on a pen drive.
  12. Copy patched Electrum and the save the transaction to a pen drive (separate from Kubuntu will be more convenient).
  13. Run Kubuntu from the USB without any network access. Run Electrum from the pendrive. Create a wallet from the seed or private keys. The wallets are stored in RAM so after you reboot the computer, they will be gone. Load the transaction, sign it and save it to the pen drive.
  14. Go back to the SBTC Core on the online machine. Display the raw transaction (starts with the hex=). Check in the SBTC Core if it is correct sbtc-cli decoderawtransaction hex
  15. If it looks fine (and your blockchain got synced), broadcast it sbtc-cli sendrawtransaction hex
If there is no error, congratulations, you sent the transaction to the specified address. If it is to your SBTC Core wallet, wait until it confirms and send it further with sbtc-cli setfee feeperkb sbtc-cli sendtoaddress "addr" value "" "" true true
I'm going to update this guide when I figure out the BCD transactions intrinsics. You can download and run the BitcoinDiamond Core clone in the meantime.
SBTC tips: 1KjuY8CTrwMhdLt3uF3hCcSgfkHMyo1ELf
submitted by PVmining to BitcoinAirdrops [link] [comments]

Meet the Team

Posted in the introduction channel on discord. Thanks CryptoHaga. 👍🏻
The Developers
Most of the developers have been around since the start of cryptocurrency. The core developers are:
Peter Bushnell aka Bushstar (Lead Developer): Peter launched Feathercoin in 2013 and joined UFO in 2014. His journey into cryptocurrency started in 2011 mining Bitcoin before shifting interest into the varied world of alternative cryptocurrencies. Before starting Feathercoin he worked for Brasenose, one of the Oxford University colleges, for 11 years developing administrative systems.
Ghostlander (NeoScrypt creator) Has been with Feathercoin development team since the early days. Currently leading the development on new hashing algorithm - Neoscrypt. Contributes to all things technical when we’re talking code, he and Bushstar work closely together hashing out the technical details with other members of the development team too. He is also the lead developer on Phoenixcoin after had volunteered to raise it out of the ashes, take care of their code and developments after previous developers abandoned the coin in dust. He is also the lead developer on Orbitcoin.
Wrapper (Developer, Analysis, Testing, Community support, Forum Mod/Admin) An early member of the Feathercoin forum, joining in the technical discussions. Helps out maintaining the forum, greeting new members, answering and analysing mining and technical support issues and mentoring new staff members. Monitors the block chain network and some development and testing. Has a PhD in Physics and was working as Maintenance Management systems consultant and Software designer at Manchester University earlier in his career.
uncle_muddy (Development and Merchant Adoption) Became involved with Feathercoin in late 2013. Has helped Feathercoin along its journey with the Prostate Cancer UK fundraiser, developing a building the OpenFeathercoinATM, assisting with the organisation of meet-ups, and is now working on FeatherPay - the handheld Point of Sales terminal.
ChekaZ (Community support, Developer, Social Media Expert) I am a German student who became involved in Feathercoin at May 2013. Since then I have been helping with merchant adoption in Germany with Dahms Winery being our first merchant. I also like doing my own little projects such as spearheading the special limited edition bottles of wine from the winery, also have taken a dabble in some development work and made MinerX – a mining tool for beginners.
Wellenreiter (Developer, Network Specialist, Forum Mod/Admin) Grey haired German, working as network specialist for a large company. Linux fan. Got involved with Feathercoin in summer 2013. Started with mining, and still mines with low hashrates. Does some programming and testing. Creates the Linux install packages and Android releases.
MrWyrm (Forum Mod/Admin) In his early thirties, he’s a community and people power enthusiast working in IT and retail systems. He found cryptocurrencies late but instantly fell in love with the technology and its potential to help communities. When not involved in cryptocurrencies he’s crossing stupidly hot chilli peppers on his allotment and currently enrolled as a Natural Sciences degree major.
AcidD aka AcidDude (Developer, Community Support, Forum Mod/Admin) IT Operations manager by trade, found FTC late 2013 and lurked till 2015. An Original BTC/LTC and now FTC GPU miner from the very early days of crypto. He just does whatever he can to help the community and coin. Creates the Windows and MacOS releases.
The developers are preferably contacted via the Feathercoin forum:
GitHub Link:
The Community
Feathercoin cannot be what it is today without the support and help from the community. The developers are directly in contact with the community using several channel servers. The channel servers which the community can be found are on:
Feathercoin Forum:
Social Media Twitter:
submitted by Frank5434 to FeatherCOin [link] [comments]

Groestlcoin Release September 2018


As always, the past 3 months since 22nd June have been crazy busy. The bears might still be around, but the show must go on and of course has not slowed the Groestlcoin development team in the slightest. Here’s a quick overview of what has already happened since the last release: - Integrated into the bitbns exchange, with the ability to buy Groestlcoin directly with the Indian Rupee. - Groestlcoin Rebrand Vote – Whilst there was much talk and push for a rebrand vote, the overall result was almost unanimously in favour of keeping our unique and conversation-starting name. With just 83 votes to Rebrand, and 2577 votes to No Rebrand. Thank you for all who voted, the funds raised are being used to fund ongoing hosting and development costs. - Integrated into the Cryptobridge exchange. Cryptobridge is a popular decentralised exchange where you always hold the private keys to your funds, only YOU have access to them. - Groestlcoin has been added to SimpleSwap – Groestlcoin can now be swapped with over 100 other cryptocurrencies, without signing up! - Groestlcoin has been added to UnoDax, one of the leading cryptocurrency exchanges in India, with TUSD, BTC and INR trading pairs. - Groestlcoin has been added to, where you can buy Groestlcoin using Bitcoin and over 50 other altcoins. Purchasing with VISA/Mastercard is coming VERY SOON. Discussed later: - Groestlcoin has been listed on #3 largest exchange in the world on volume, Huobi Global! More on this to come further on in the announcements. - Groestlcoin has been added to the Guarda Multi-Currency Wallet. - Groestlcoin has been added to Melis Multi-Device, Multi-Account, Multi-Platform, Multi-Signature advanced wallet! Already this list is far more than most other cryptocurrencies have achieved in the past 3 months. But this is just the tip of the iceberg of what has been developed.

What's been Happening?

GRSPay Released

We are so excited for this, that it has it's own separate reddit thread. Head over there now at to see more on this!

Melis Wallet

The the most advanced wallet for Bitcoin, Bitcoin Cash, Litecoin and now Groestlcoin.
With Melis you have the complete control of your bitcoins and private keys, you can define spending limits policies and make use of two or more factors authentication. Melis is open source, published on GitHub.

How Melis Works?

You can create as many accounts as you want. An account is a part of your wallet that can be customised to your requirements. You can choose how many co-signers are required to spend funds. The accounts are completely independent and act like separate wallets from each other but can be accessed via the same details. A core feature of Melis is the ability to set a ‘primary’ device. With this you can set an account as ‘Secure’ so it is only viewable (and accessible at all) from the Primary device. You can have a savings account hidden from the outside world whilst also having your ‘spending’ funds available on the go. With Melis you can create a multi-signature account between N people, where up to N signatures are required to sign a transaction, choosing if any of those should be mandatory.
Core Features:

Guarda Wallet

Safer than ever! Desktop Light Wallet - Anonymous and fast!
With Guarda Multi-currency Desktop Light Wallet you don’t need to register. Guarda has no access to your private keys or funds. You can receive, send, store, buy and exchange cryptocurrencies in complete anonymity and safety. All these features are available on Linux, Windows or MacOS. Choose the one that suits you!
More info about Guarda wallet on

Integrated into HolyTransaction

What is HolyTransaction?

HolyTransaction gives users access to the crypto world with a universal cryptocurrency wallet and instant exchange.


For more information, visit Holy Transaction here.

Integrated into NEXT Wallet

What is NEXT?

NEXT is a modern, next-generation stylish open-source Desktop wallet.


For more information, visit NextWallet here.

Integrated into Blockchain Financial

What is Blockchain Financial?

Blockchain Financial is a set of web based services for individuals and companies that want to make things happen with the Cryptocurrencies Ecosystem. - For those that don't know anything about cryptocurrencies, we offer tools that will let them receive, send and operate with an assortment of coins. - For those that are already riding the wave, we offer tools that will let them do all those things that they weren't able to do.

Blockchain Financials mission

We're not here to reinvent the wheel. We're here to make it run smoother for you, and we provide some of the most useful services you'll find on the internet, made in a way that is easy to understand and use on a daily basis. In short, we're a bunch of people that claim to be Crypto Evangelists. We strongly believe in cryptocurrencies, and our main promise is to push them up so more people get involved and take all the advantages they offer.

More information from Blockchain Financial

Back in 2014, the world was taken by storm when Facebook approved the first cryptocurrencies tipping apps. The first was for Dogecoin, and the second was for multiple coins.
The project was hosted on, and persisted for almost two years, built up a massive user community and gave a home to Bitcoin, Litecoin, Dogecoin and dozens of other bitcoin-based altcoins.
After very active months, the tipping hype started to fade away. Then, the developers decided to jump into the next stage: bringing not only tipping, but also mining and a widget that could be embedded on websites to allow everyone to accept payments. Sadly, the work was never completed because the project started to require an unsustainable amount of resources. Then, in a painful decision, a shutdown was announced by December 2015.
A couple of months after was closed, the source code was released by its creator as Open Source on GitHub. But it wasn't maintained.
Now, some of the original members of the dev and admin teams gathered up with a handful of the WhitePuma's elite users, and decided to make something good with the best pieces of the old source code. That, with fresh new ideas and the power of the BardCanvas engine, synthesized the core of Blockchain Financial.
More info about Blockchain Financial wallet on .
For more information, visit [Blockchain Financial](

Groestlcoin Listed on Huobi

Who are Huobi?

Huobi was founded in China and is now based in Singapore, with offices in Hong Kong, South Korea, Japan and the North America, currently sitting #3 in volume on Coinmarketcap. Huobi is a great leap forward for our growing presence in Asia and we are very excited to be listed here!
You can find the official Huobi announcement here.

Groestlcoin Core v2.16.3 - Please Update ASAP

A new major Groestlcoin Core version 2.16.3 is now available for download which includes both a Denial of Service component and a critical inflation vulnerability, so it is recommended to upgrade to it if you are running a full Groestlcoin node or a local Groestlcoin Core wallet.
v2.16.3 is now the official release version of Groestlcoin Core. This is a new major version release with a very important security updates. It is recommended to upgrade to this version as soon as possible. Please stop running versions of Groestlcoin Core affected by CVE-2018-17144 ASAP: These are 2.13.3 and 2.16.0.
As a result in this, all exchanges and services have been asked to upgrade to this version, so please be patient if wallets go in to maintenance mode on these services.

What's new in version v2.16.3?

This is a major release of Groestlcoin Core fixing a Denial of Service component and a critical inflation vulnerability ( exploitable by miners that has been discovered in Groestlcoin Core version 2.13.3 and 2.16.0. It is recommended to upgrade to 2.16.3 as soon as possible. If you only occasionally run Groestlcoin Core, then it's not necessary to run out and upgrade it right this second. However, you should upgrade it before you next run it. If you know anyone who is running an older version, tell them to upgrade it ASAP. Stored funds are not at risk, and never were at risk. At this time we believe over half of the Groestlcoin hashrate has upgraded to patched nodes. We are unaware of any attempts to exploit this vulnerability. However, it still remains critical that affected users upgrade and apply the latest patches to ensure no possibility of large reorganizations, mining of invalid blocks, or acceptance of invalid transactions occurs.

The Technicals

In Groestlcoin Core 2.13.3, an optimization was added (Bitcoin Core PR #9049) which avoided a costly check during initial pre-relay block validation that multiple inputs within a single transaction did not spend the same input twice which was added in 2012 (Bitcoin Core PR #443). While the UTXO-updating logic has sufficient knowledge to check that such a condition is not violated in 2.13.3 it only did so in a sanity check assertion and not with full error handling (it did, however, fully handle this case twice in prior to Thus, in Groestlcoin Core 2.13.3, any attempts to double-spend a transaction output within a single transaction inside of a block will result in an assertion failure and a crash, as was originally reported. In Groestlcoin Core 2.16.0, as a part of a larger redesign to simplify unspent transaction output tracking and correct a resource exhaustion attack the assertion was changed subtly. Instead of asserting that the output being marked spent was previously unspent, it only asserts that it exists. Thus, in Groestlcoin Core 2.16.0, any attempts to double-spend a transaction output within a single transaction inside of a block where the output being spent was created in the same block, the same assertion failure will occur. However, if the output being double-spent was created in a previous block, an entry will still remain in the CCoin map with the DIRTY flag set and having been marked as spent, resulting in no such assertion. This could allow a miner to inflate the supply of Groestlcoin as they would be then able to claim the value being spent twice.
Groestlcoin would like to publicly thank Reddit user u/Awemany for finding CVE-2018-17144 and reporting it ( You deserve gratitude and appreciation from cryptoworld, and you have ours. If you want to support him for his work, please consider donating to him on his bitcoin cash address: bitcoincash:qr5yuq3q40u7mxwqz6xvamkfj8tg45wyus7fhqzug5

Groestlcoin Electrum-GRS 3.2.2 - Ledger & Trezor Edition

What is Electrum-GRS?
Electrum-GRS is a lightweight "thin client" groestlcoin wallet Windows, MacOS and Linux based on a client-server protocol. Its main advantages over the original Groestlcoin client include support for multi-signature wallets and not requiring the download of the entire block chain.


Electrum-GRS Mobile Android

What is Electrum-GRS Mobile?

Electrum-grs is a lightweight "thin client" groestlcoin wallet Android based on a client-server protocol. Its main advantages over the original Groestlcoin client include support for multi-signature wallets and not requiring the download of the entire block chain.


Groestlcoin EasyVanity Released

Groestlcoin EasyVanity is a Windows app is built from the ground-up in C# and makes it easier than ever before to create your very own bespoke Groestlcoin address(es), even whilst not connected to the internet! You can even generate multiple keys with the same prefix and leave it on overnight whilst your CPU or GPU collects and stores these addresses locally.
If you're tired of the random, cryptic addresses generated by regular groestlcoin clients, then Groestlcoin EasyVanity is the right choice for you to create a more personalized address.


• Ability to continue finding keys after first one is found • Includes warning on startup if connected to the internet • Ability to output keys to a text file (And shows button to open that directory) • Ability to make your match case sensitive (Where possible) • Show and hide the private key with a simple toggle switch, and copy the private key straight to your clipboard • Show full output of commands • Includes statistics whilst the application is running • Ability to choose between Processor (CPU) and Graphics Card (GPU) • Automatically detects 32 or 64 bit systems • Features both a Light and Dark Material Design inspired Themes • EasyVanity's search is probabilistic, and the amount of time required to find a given pattern depends on how complex the pattern is, the speed of your computer, and whether you get lucky. • EasyVanity includes components to perform address searching on your CPU (vanitygen) and your OpenCL-compatible GPU (oclvanitygen). Both can be built from source, and both are included in the Windows binary package. • Prefixes are exact strings that must appear at the beginning of the address. When searching for prefixes, Easyvanity will ensure that the prefix is possible, and will provide a difficulty estimate. • The percentage displayed just shows how probable it is that a match would be found in the session so far. If it finds your address with 5% on the display, you are extremely lucky. If it finds your address with 92% on the display, you are unlucky. If you stop EasyVanity with 90% on the display, restart it, and it finds your address with 2% on the display, your first session was unlucky, but your second session was lucky. • EasyVanity uses the OpenSSL random number generator. This is the same RNG used by groestlcoin and a good number of HTTPS servers. It is regarded as well-scrutinized. Guessing the private key of an address found by EasyVanity will be no easier than guessing a private key created by groestlcoin itself. • To speed up address generation, EasyVanity uses the RNG to choose a private key, and literally increments the private key in a loop searching for a match. As long as the starting point is not disclosed, if a match is found, the private key will not be any easier to guess than if every private key tested were taken from the RNG. EasyVanity will also reload the private key from the RNG after 10,000,000 unsuccessful searches (100M for oclvanitygen), or when a match is found and multiple patterns are being searched for. • Free software - MIT. Anyone can audit the code. • Written in C# - The code is short, and easy to review.

Groestlcoin Sentinel (Android & Blackberry) – Mainnet + Testnet

What is Sentinel?

Groestlcoin Sentinel is the easiest and fastest way to track/receive/watch payments in your offline Groestlcoin Wallets. Groestlcoin Sentinel is compatible with any standard Groestlcoin address, BIP44 XPUB (Extended Public Key) BIP49 YPUB and BIP84 ZPUB
Groestlcoin Sentinel is a great solution for anyone who wants the convenience and utility of a hot wallet for receiving payments directly into their cold storage (or hardware wallets). Sentinel accepts XPUB's, YPUB'S, ZPUB's and individual Groestlcoin address. Once added you will be able to view balances, view transactions, and (in the case of XPUB's, YPUB's and ZPUB's) deterministically generate addresses for that particular wallet.

What's New?

The P2SH paperwallet supports creating P2SH paperwallets in bulk, keypair generation with QR codes and sweeping tool. Groestlcoin believes strongly in privacy, the live version does not collect and store IP or transaction data.
The BECH32 paperwallet supports creating BECH32 paperwallets in bulk, keypair generation with QR codes and sweeping tool. Groestlcoin believes strongly in privacy, the live version does not collect and store IP or transaction data.

Groestlcoin Web Wallet Update 1.4

What is Groestlcoin Web Wallet?
Groestlcoin Webwallet is an open source, multisignature, HD Wallet and more! Webwallet is a a open source browser based Groestlcoin webwallet.
Webwallet is a playground for Groestlcoin in javascript to experiment with. It supports multisig, OP_HODL, RBF and many more. Groestlcoin believes strongly in privacy, the live version does not collect and store IP or transaction data.
submitted by Yokomoko_Saleen to groestlcoin [link] [comments]

Git and Qt  How to use Git with Qt How to Install Bitcoin Core Wallet on Ubuntu 16 6. bitcoin-qt How To Build/Run a Bitcoin Node on Linux How to mine Bitcoin Using Linux [2019]

This tutorial explains how to install and use Bitcoin Core on Debian Linux. Bitcoin Core is the official Bitcoin Wallet from I will use the latest version from the GIT repository at We’re going to run the GUI version first, called bitcoin-qt, then we’ll exit it and run the non-GUI version called bitcoind, and then back to bitcoin-qt, with some steps and configuration in The generated configure script is currently missing, and you will need to install autotools and run ./ before you can run ./configure. This is the same as when checking out from git. Instead of running make simply, you should instead run BITCOIN_GENBUILD_NO_GIT=1 make. Notable changes P2P and network changes [email protected]:~$ sudo apt-get install git. install should be self explanatory, it’s like update, but for when you’re installing a specific package for the first time. It requires a package name. git is the name of the Git package, and is recognized as such by the list of sources the apt-get command refers to. It will also function as a The Bitcoin Core daemon (bitcoind) is not included in the .dmg file you may have downloaded to install Bitcoin-QT. Bitcoind, along with its support binaries, is instead included in the OS X .tar.gz file listed on the official Bitcoin Core download page. To download this file using Terminal, execute the following command:

[index] [21634] [25132] [13454] [19557] [14150] [28588] [13424] [2088] [17921] [19893]

Git and Qt How to use Git with Qt

RPC commands: - getbalance - getwalletinfo - getnewaddress - getblockcount - getnetworkinfo @402PaymentRequierd ... This is a tutorial on how to install and use git with Qt Creator. This is my first tutorial so apologies if the quality is not that great. Please feel free to ask me any questions if you have any. This video covers the method to install BitCoins on Ubuntu 16.04 Bitcoin is a virtual and crypto-currency created by Satoshi Nakamoto. For more explanation on this video: ... This episode will cover how to install Git on Windows, Linux and MacOS X. Installing Git on Linux and MacOS X is straightforward. On Windows there are ways for getting Git as well. Topics in this ... This short video shows how to compile the bitcoin source code on linux (ubunu). an easy task to do but it take some time (around 15 min) please read the instruction in the official github https ...

Flag Counter