Download - Bitcoin

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 http://imgur.com/a/GhCNH https://github.com/Gabisonfire/dashboard-q
lastditchefrt http://i.imgur.com/5zQdao4.png https://github.com/d4rk22/Network-Status-Page
_SleepingBag_ http://i.imgur.com/Ql9ZM4W.png https://github.com/jsank/homelabdash
NiknakSi https://niknak.org/extras/sysinfo TBA
DainBramaged http://imgur.com/jYNlUEQ https://github.com/gordonturneBigBoard
michaelh4u https://i.imgur.com/XkZwMKj.png https://github.com/michaelh4u/homelabfrontpage
spigotx http://imgur.com/a/1zMht https://github.com/spigotx/HomeLab2
SirMaster https://nicko88.com/ https://github.com/dashbad/plex-server-status
yourofl10 http://imgur.com/a/AyROa TBA
TheBobWiley http://imgur.com/a/oU6d3 https://github.com/TheBobWiley/ManageThis-LandingPages
0110010001100010 http://i.imgur.com/iwtQcsL.jpg https://github.com/danodemano/monitoring-scripts
mescon & SyNiK4L https://i.imgur.com/gqdVM6p.jpg https://github.com/mescon/Muximux
ak_rex http://i.imgur.com/a/RJkrT https://github.com/ak-rex/homelab-dashboard
 
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]

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 dogecoin-master.zip 
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' dogecoin-qt.pro 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 https://github.com/dogecoin/dogecoin ./autogen.sh ./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.
EDIT
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 cgminer.sh 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 ./cgminer.sh 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.
 libudev.so.1: cannot open shared object file: No such file or directory 
In terminal, do
sudo updatedb locate libudev.so.0.13.0 
And it will probably return a path /lib/x86_64-linux-gnu. Inside that directory there's a library file called libudev.so.0.13.0. You'll need to make a symlink (aka shortcut) that links libudev.so.1 to libudev.so.0.13.0 So, assuming you're working with libudev.so.0.13.0 do this
cd /lib/x86_64-linux-gnu sudo ln -s libudev.so.0.13.0 libudev.so.1 
Now if you do
ln -l 
You should see
libudev.so.1 -> ./libudev.so.0.13.0 
Meaning you've made the symlink. Also, the text for libudev.so.1 will be blue.
submitted by Boozybrain to dogecoin [link] [comments]

How to Mine BiblePay on Linux

This guide is outdated, please refer to:
https://wiki.biblepay.org/POBH_Setup
https://wiki.biblepay.org/PODC_Setup
 
 
 
 
 
 
 
 
IMPORTANT - Evolution Upgrade:
Quick Start https://wiki.biblepay.org/Quick_Start
Evolution Upgrade Information https://wiki.biblepay.org/Evolution_Upgrade
Getting Started with Evolution https://wiki.biblepay.org/Getting_Started_with_Evolution
Generic Smart Contracts https://wiki.biblepay.org/Generic_Smart_Contracts
What is BiblePay Evolution? https://www.reddit.com/BiblePay/comments/bifvpk/biblepay_evolution_what_is_it/
Recommend 2GB RAM or can get stuck compiling (if 1GB RAM can use Swap File) Use Ubuntu 16.04
INFO
https://github.com/biblepay/biblepay-evolution/blob/masteBuildBiblePay.txt
INSTALL COMMANDS
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 http://github.com/biblepay/biblepay-evolution 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 .. ./autogen.sh #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: #https://github.com/biblepay/biblepay-evolution/blob/mastedoc/build-unix.md 

SWAP FILE
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 

RUN COMMAND LINE
cd src ./biblepayd -daemon 
OR
RUN GUI
Your GUI program will be located in: /biblepay-evolution/src/qt
./biblepay-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!

SETUP CONFIG
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 addnode=node.biblepay.org 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 

USEFUL COMMANDS
./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:
genproclimit=X 
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)

POOL
NOTE: To use the pool you must now use the external miner, not the wallet miner https://whitewalr.us/2019/biblepay-nomp-pool-mining.html
  1. Set up an account on pool website: https://pool.biblepay.org/
  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=https://pool.biblepay.org 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

UPDATE:

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

UPDATE IN ONE COMMAND:
./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

SPEED UP COMPILE:
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 
Reference: http://www.linux-databook.info/?page_id=2319

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/ 
https://stackoverflow.com/questions/3299951/how-to-pass-password-for-rsync-ssh-command https://www.thegeekstuff.com/2008/11/3-steps-to-perform-ssh-login-without-password-using-ssh-keygen-ssh-copy-id/
people make cron jobs and rsync automatically

OUTDATED

Unofficial Bash Script
https://gist.github.com/anonymous/d1c1d35e3c8f67f5fb2e204479fa5c6b

Official Ubuntu Package
https://launchpad.net/~biblepay-official

Unofficial Ubuntu Package
https://www.reddit.com/BiblePay/comments/7rwqqs/unofficial_ubuntu_packages_available/

Unofficial Mine in One Line
https://www.reddit.com/BiblePay/comments/7ryuk1/mine_in_one_line/
NOTE: DONT RUN ON A COMPUTER WITH COINS -- THIS IS A CLEAN INSTALL SCRIPT

COMPILE WITHOUT GUI: https://bitcointalk.org/index.php?topic=2042657.msg21878317#msg21878317 https://bitcointalk.org/index.php?topic=2042657.msg21878389#msg21878389
ADVANCED:

DOCKER IMAGES (NOTE: I havent tested these, use at your own risk) https://hub.docker.com/gagaha/biblepay/ https://hub.docker.com/cryptozero/biblepay-opt/
submitted by togoshige to BiblePay [link] [comments]

How to set up an incentivized node in Ubuntu [likely works for other Linux as well…]

There has been a post lately about how you can participate in a program by bitnodes which is intended to incentivize running a full node.
In the comment section of the post there were some instruction by AndrewToth as to how to set the whole thing up. Unfortunately it didn’t work for me directly. I would therefore like to share how I finally managed to get it done.
If you would like to run a scrip to do all the heavy lifting for you, please perform steps 1, 2 and 12 now and then just copy paste this into the terminal and hit enter: wget -O bitnodes-incentive.sh http://pastebin.com/download.php?i=607WQaBy && sed -i 's/\/' bitnodes-incentive.sh && chmod +x bitnodes-incentive.sh && ./bitnodes-incentive.sh The script will also advise you to do the required port forwarding. You can look at the script here.
1 Find out your local IP by opening a terminal and typeifconfig. You will see your local IP listed under eth0 as inet addr. In the subsequent steps of this tutorial it will be referenced as $localip. So whenever you read $localip it means, your local IP you have just found out. It would be helpful to make this IP static.
2 Set up a full node. You need to download Bitcon Core, run it until you are synchronized. It needs to allow more than 8 connections and you therefore need to turn on port forwarding on your router. So if the machine which runs the full node has $localip in your subnet, you need to tell your router to forward port 8333 to $localip port 8333. If you open Bitcoin-QT it will tell you on the lower right corner, how many connections it has. If the number turns >8 after 5-10 minutes, you are all set. If you need a more detailed tutorial, you may try this one. Beware, if you don’t run a full node yet, allow it between 12 and 24 hours to synch.
3 Now you need to know your own public IP address. You can e.g. find it out like this. In the subsequent steps of this tutorial it will be referenced as $ip, so whenever you reed $ip it means, your public IP you have just found out.
4 Get a Bitcoin address. Please use one which you control the key to. I guess you know the deal. In the subsequent steps of this tutorial it will be referenced as $address, so whenever you reed $address it means, your Bitcoin address.
5 Open a new terminal and copy paste the following into the terminal each followed by enter key (beware $address means your address, no “$” sign needed): mkdir bitcoin-address cd bitcoin-address vi index.html i $address You will see a lot of “~” in the terminal. Don’t worry. It’s supposed to be like that.
6 Hit the escape key.
7 Type :wq and hit enter key.
8 Type python -m SimpleHTTPServer 8000 and hit enter key. In case you should have to restart this web-server you will have to do it from the "bitcoin-address" directory created in step 5. want to use alternative port?
9 Now go back to your router configuration page and set it to forward port 80 to $localip port 8000. Beware, $localip is not your public IP which you have found out in step 3 but the subnet IP of the machine you run your node on which you have found out in step 1.
10 Confirm steps 5-9 worked by using a different internet connection (e.g. 4g on your phone) and type $ip in the address bar. You should see a simple webpage with only your Bitcoin address on. If you see that, you are set to go on.
11 Activate your node by opening your web browser and entering https://bitnodes.21.co/nodes/$ip-8333/ in the address bar. Beware of the $ip you have to replace with your specific parameter.
12 Open a new terminal and copy paste sudo apt-get install curl and hit enter key. You will be asked for your root password to do this step.
13 Open a new terminal and copy paste this:curl -H 'Accept: application/json; indent=4' -d 'bitcoin_address=$address' -d 'url=http://$ip' https://bitnodes.21.co/api/v1/nodes/$ip-8333/ Beware of the $address and $ip (2x) you have to replace with your specific parameters. There is a "success": true message in the terminal after this step.
14 Open your browser on the system with runs your node and the following in the address bar: https://bitnodes.21.co/api/v1/nodes/$ip-8333/ Beware of the $ip you have to replace with your specific parameter. Url and bitcoin_address parameters should not be empty. If you wait ten minutes and reload the page you should also get "verified": true. This means you are now in the node incentive program. Any incentives will be payed to your Bitcoin address, shall you receive any. I think it depends on luck.
15 Open your browser on the system which runs your node and the following in the address bar: https://bitnodes.21.co/nodes/$ip-8333/ Beware of the $ip you have to replace with your specific parameter. Alternatively just reload the page from step 11 if you still have it open. You can now see some statistics for your node plus you should also be able to see it’s Bitcon address and verification url.
16 You can see where your node is in the leaderboard by entering this into the address bar of your browser: https://bitnodes.21.co/nodes/leaderboard/?q=$ip Beware of the $ip you have to replace with your specific parameter. You can now see the PIX rank of your node. It needs to be above 8 to have your node successfully in the ballot. PIX rank explanation given on the site.
Thanks to bitnodes.io, Addy Yeow and AndrewToth for helping me out to set up my own incentivized node.
Now I wish you all the best! Please tell me if it works, I will be back later to answer questions or correct things.
Edit1: I have done lots of formatting updates. Added Point 14 16.
Edit2: Added steps proposed by Explodicle. Installation of curl and activation of node at bitnode.io.
Edit3: Added the dedicated folder for web-server index.html
Edit4: Alternative port options added as suggested by n00tz.
Edit5: Awesome script added to top section. All props to Explodicle.
Edit6: Changed instructions and the script to work with new address "bitnodes.21.co" instead of "getaddr.bitnodes.io"
submitted by SimonBelmond to Bitcoin [link] [comments]

Error compiling bitcoinfaith

Hey,
i can sucesfull compile bitcoin-qt but when i change to bitcoin faith i get error, even though i follow exactly the same steps (and i had no errors with bitcoin diamond for example)
[email protected]:~/bitcoinfaith$ make Making all in src make[1]: Entering directory '/home/chris/bitcoinfaith/src' make[2]: Entering directory '/home/chris/bitcoinfaith/src' CXX btfd-bitcoind.o In file included from ./uint256.h:15:0, from consensus/params.h:9, from chainparams.h:10, from bitcoind.cpp:10: ./crypto/common.h:16:20: fatal error: sodium.h: No such file or directory #include "sodium.h" ^ compilation terminated. Makefile:8105: recipe for target 'btfd-bitcoind.o' failed make[2]: *** [btfd-bitcoind.o] Error 1 make[2]: Leaving directory '/home/chris/bitcoinfaith/src' Makefile:9349: recipe for target 'all-recursive' failed make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory '/home/chris/bitcoinfaith/src' Makefile:747: recipe for target 'all-recursive' failed make: *** [all-recursive] Error 1
Anyone has a guesS?
submitted by adolfaberHitler to BitcoinAirdrops [link] [comments]

private key discrepancy VERY WORRIED

I took the private key from my QT client on my offline machine using the terminal. When I imported the key into electrum the amount of BTC was much less than what the QT client reported. The QT client has many different private keys but it said that the public key had more bitcoins than electrum is showing. I've verified the amount at a blockchain site and it looks like Electrum is showing the right amount and the QT client is showing the wrong amount.
I am worried though because I have been importing private keys and sending the full amount on. This way I should not have to keep backing up wallets or risk exposing the other private keys from the offline wallet. This private key has only 1 incoming transfer and no outgoing transfers so why would QT show an incorrect balance?
I am wondering is it safe to send this lower amount and also is there anyway I can truly know the balance of my QT wallet addresses if QT is not accurately reporting the amounts. Or is QT reporting the aggregate amounts properly but misreporting the individual address amounts. I am worried that I might have much fewer BTC than I had thought if QT is misreporting the total amount.
This is not an issue of syncing up with the blockchain.
submitted by privkeyquestion to Bitcoin [link] [comments]

private key discrepancy VERY WORRIED

I took the private key from my QT client on my offline machine using the terminal. When I imported the key into electrum the amount of BTC was much less than what the QT client reported. The QT client has many different private keys but it said that the public key had more bitcoins than electrum is showing. I've verified the amount at a blockchain site and it looks like Electrum is showing the right amount and the QT client is showing the wrong amount maybe.
I am worried though because I have been importing private keys and sending the full amount on. This way I should not have to keep backing up wallets or risk exposing the other private keys from the offline wallet.
I am wondering is it safe to send this lower amount and also is there anyway I can truly know the balance of my QT wallet addresses if QT is not accurately reporting the amounts. Or is QT reporting the aggregate amounts properly but misreporting the individual address amounts. I am worried that I might have much fewer BTC than I had thought if QT is misreporting the total amount.
This is not an issue of syncing up with the blockchain.
submitted by privkeyquestion to Electrum [link] [comments]

Cgminer on Linux mint

Machine is running Linux mint.
Downloaded files from http://ck.kolivas.org/apps/cgminer
Ran the following in terminal
Sudo-add-repository ppa:Bitcoin/Bitcoin Sudo-apt-get update Sudo-apt-install bitcoin-qt
I've read on different sites but seem somewhat lost. I joined a pool and have an account.
I am looking for help on how to get my machine running. I have a small miner, serious replies only please. I'm not looking for "bro! No profits no profits! Dig for gold in your backyard bro! There's no profits bro!"
Thank you all in advance
submitted by justanothershibehere to BitcoinMining [link] [comments]

[Hiring] Write some Bitcoin-Qt commands templates to sign transaction on offline machine.

Its not necessary to have too much experience with Bash, but I prefer making these scripts in Bash.
Or I need any solution to make my Ubuntu machine to be able to sign transactions (but receiving commands to move funds from Web-server or from FTP)
Anyway even if you're newbie in Linux but have experience with Bitcoin-Qt I am still interested in your skills, because I believe I could show you how easy it is to send commands to Bitcoin-Qt in Ubuntu Terminal (I will give an access)
I think the price here will be depending on hourly basis, so think about what is your hourly rate or other measure of payment and I will be glad to pay you Bitcoins.
submitted by XfsMonsta to Jobs4Bitcoins [link] [comments]

Bitcoin Core 0.13.2 released | Wladimir J. van der Laan | Jan 03 2017

Wladimir J. van der Laan on Jan 03 2017:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Bitcoin Core version 0.13.2 is now available from:
https://bitcoin.org/bin/bitcoin-core-0.13.2/
Or by bittorrent:
magnet:?xt=urn:btih:746697d03db3ff531158b1133bab5d1e4cef4e5a&dn;=bitcoin-core-0.13.2&tr;=udp%3A%2F%2Ftracker.openbittorrent.com%3A80%2Fannounce&tr;=udp%3A%2F%2Ftracker.publicbt.com%3A80%2Fannounce&tr;=udp%3A%2F%2Ftracker.ccc.de%3A80%2Fannounce&tr;=udp%3A%2F%2Ftracker.coppersurfer.tk%3A6969&tr;=udp%3A%2F%2Ftracker.leechers-paradise.org%3A6969&ws;=https%3A%2F%2Fbitcoin.org%2Fbin%2F
This is a new minor version release, including various bugfixes and
performance improvements, as well as updated translations.
Please report bugs using the issue tracker at github:
https://github.com/bitcoin/bitcoin/issues
To receive security and update notifications, please subscribe to:
https://bitcoincore.org/en/list/announcements/join/
Compatibility

Microsoft ended support for Windows XP on April 8th, 2014,
an OS initially released in 2001. This means that not even critical security
updates will be released anymore. Without security updates, using a bitcoin
wallet on a XP machine is irresponsible at least.
In addition to that, with 0.12.x there have been varied reports of Bitcoin Core
randomly crashing on Windows XP. It is not clear
what the source of these crashes is, but it is likely that upstream
libraries such as Qt are no longer being tested on XP.
We do not have time nor resources to provide support for an OS that is
end-of-life. From 0.13.0 on, Windows XP is no longer supported. Users are
suggested to upgrade to a newer version of Windows, or install an alternative OS
that is supported.
No attempt is made to prevent installing or running the software on Windows XP,
you can still do so at your own risk, but do not expect it to work: do not
report issues about Windows XP to the issue tracker.
but severe issues with the libc++ version on 10.7.x keep it from running reliably.
0.13.1 now requires 10.8+, and will communicate that to 10.7 users, rather than crashing unexpectedly.
Notable changes

Change to wallet handling of mempool rejection
When a newly created transaction failed to enter the mempool due to
the limits on chains of unconfirmed transactions the sending RPC
calls would return an error. The transaction would still be queued
in the wallet and, once some of the parent transactions were
confirmed, broadcast after the software was restarted.
This behavior has been changed to return success and to reattempt
mempool insertion at the same time transaction rebroadcast is
attempted, avoiding a need for a restart.
Transactions in the wallet which cannot be accepted into the mempool
can be abandoned with the previously existing abandontransaction RPC
(or in the GUI via a context menu on the transaction).
0.13.2 Change log

Detailed release notes follow. This overview includes changes that affect
behavior, not code moves, refactors and string updates. For convenience in locating
the code changes and accompanying discussion, both the pull request and
git merge commit are mentioned.

Consensus

RPC and other APIs

Block and transaction handling

P2P protocol and network code

Build system

GUI

Wallet

Tests and QA

Miscellaneous

Credits

Thanks to everyone who directly contributed to this release:
As well as everyone that helped translating on Transifex.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQEcBAEBCgAGBQJYa2IbAAoJEHSBCwEjRsmmiQsIALbkHVVwO7nViQKH1Ub2qpD4
TplOuAP0/4vYotizuI12Gqdnu8SjPmhKwAgIXhVinE6TS4OzGNjy+6LtWGzpcpud
B1pcziZ72Mlfxdbdd1UhDMWEjoBumS9RmXMSqzTlMVlHRv4iiISzdaAROu1jHvdF
YTsnmKXB8OvcXOecxRMY9LrnpSzLALM2MYTDmYwlhhExHIA8ZqI2niky6GCfyfDi
KD7bgfIFJzlgFTpAdhQXOXtWoRV5iHqN7T29ot8Y+yIhVCRhHYXS93Z50GKbkqYV
MXsVAkpZF3qqcKYSPFjbif7faMdrMqcEiII6QhXdDTRGI/35IfuTDbWzzQlnVyY=
=ncCY
-----END PGP SIGNATURE-----
original: https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2017-January/013412.html
submitted by dev_list_bot to bitcoin_devlist [link] [comments]

HOWTO: Run a Full Bitcoin Node + Armory

Estimated total time: Up to 2 hours, not including blockchain downloading.
You can install this on a VPS, a spare PC, or on your own PC. You can install it in Virtualbox on your own PC, or into Windows. If you just want to try it out, I recommend installing in Virtualbox.
  1. Download and install Virtualbox from (https://www.virtualbox.org/wiki/Downloads), and download an Ubuntu 14.04 64bit Desktop ISO from http://www.ubuntu.com/download/desktop, and follow the guide here (I recommend 2GB of RAM, 3GB if you can spare it): http://www.psychocats.net/ubuntu/virtualbox . It's a little outdated but close enough that things are the same.  
  2. After installing Ubuntu in Virtualbox, to make it fullscreen you will need Guest Additions. Run these commands by clicking on the swirl icon top right, typing ter and opening Terminal: sudo apt-get install build-essentials module-assistant and then sudo m-a prepare Before selecting Devices > Insert Guest Additions CD image, telling Ubuntu to install them, and shutting down. //Thanks go to http://www.binarytides.com/vbox-guest-additions-ubuntu-14-04 for those instructions.//  
  3. Next I went into the Virtual Machines settings and changed Network Adapter 1 to be "Attached to Bridged Network" instead of "Attached to NAT".  
  4. After booting the machine back up, I followed the steps here: https://bitcoin.org/en/full-node/#linux-instructions And installed both bitcoin-qt and bitcoind. Skip over the parts where you edit bitcoin-qt's settings to start at boot, or edit cron to start bitcoind at boot, since this will interfere with using armory.  
  5. Next I followed the instructions here to install Armory: http://bitzuma.com/posts/offline-installation-of-armory-on-tails-and-ubuntu-linux/ The reason I used these instructions was because I was having difficulty getting Armory to install (online or offline) on Ubuntu 14.04. Might just be me.  
  6. I then started up Armory in Offline Mode by clicking on the swirl icon top left and typing Armory. In the program, after clicking Skip, I scrolled down slightly, clicked on Download Bitcoin, Download, and agreed to let it do whatever it wanted to; (which was download and install Satoshi).  
  7. I then closed Armory Offline and opened Armory, which began downloading the blockchain from a torrent. I then went into File > Settings (top left of your screen, near the swirl; menu options will appear once the mouse hits that taskbar) and personally chose to Disable OS and version reporting. There is a setting here for "Enable settings for proxies/Tor" but I haven't ticked it yet, since I haven't set Tor up.  
  8. Follow the instructions here to set up port forwarding so your node is reachable, and to test this: https://bitcoin.org/en/full-node#network-configuration  
Next:
If I want to broadcast transactions over Tor, but not receive incoming connections over Tor, is that a problem for the health of the Bitcoin Tor network? Or will those transactions be broadcast out to "clearnet" nodes, as opposed to hidden ones?
Thanks to all writers of articles referenced here for your help.
By the way, even if you don't want to run a bitcoin node full time, I've read that running one even 6 hours a day is useful. These are instructions for ubuntu but you can also run it from Windows on the same machine you work on (I don't know about privacy implications). Perhaps someone should write an article about running a bitcoin node on your PC at work!
submitted by FullNodeGuide to Bitcoin [link] [comments]

[Meta] Re: Bitcoin Core 0.13.2 released | Luke Dashjr | Jan 07 2017

Luke Dashjr on Jan 07 2017:
I don't think release announcements are really appropriate for the bitcoin-dev
mailing list. People who want these can subscribe to the bitcoin-core-dev list
and/or the Core announce mailing list. Maybe sending to bitcoin-discuss would
also make sense, but not bitcoin-dev...
Luke
On Tuesday, January 03, 2017 8:47:36 AM Wladimir J. van der Laan via bitcoin-
dev wrote:
Bitcoin Core version 0.13.2 is now available from:
https://bitcoin.org/bin/bitcoin-core-0.13.2/
Or by bittorrent:
magnet:?xt=urn:btih:746697d03db3ff531158b1133bab5d1e4cef4e5a&dn=bitcoin-co
re-0.13.2&tr=udp%3A%2F%2Ftracker.openbittorrent.com%3A80%2Fannounce&tr=udp%
3A%2F%2Ftracker.publicbt.com%3A80%2Fannounce&tr=udp%3A%2F%2Ftracker.ccc.de%
3A80%2Fannounce&tr=udp%3A%2F%2Ftracker.coppersurfer.tk%3A6969&tr=udp%3A%2F%
2Ftracker.leechers-paradise.org%3A6969&ws=https%3A%2F%2Fbitcoin.org%2Fbin%2
F
This is a new minor version release, including various bugfixes and
performance improvements, as well as updated translations.
Please report bugs using the issue tracker at github:
https://github.com/bitcoin/bitcoin/issues
To receive security and update notifications, please subscribe to:
https://bitcoincore.org/en/list/announcements/join/
Compatibility

Microsoft ended support for Windows XP on [April 8th,
2014](https://www.microsoft.com/en-us/WindowsForBusiness/end-of-xp-support
), an OS initially released in 2001. This means that not even critical
security updates will be released anymore. Without security updates, using
a bitcoin wallet on a XP machine is irresponsible at least.
In addition to that, with 0.12.x there have been varied reports of Bitcoin
Core randomly crashing on Windows XP. It is [not
clear](https://github.com/bitcoin/bitcoin/issues/7681#issuecomment-2174398
91) what the source of these crashes is, but it is likely that upstream
libraries such as Qt are no longer being tested on XP.
We do not have time nor resources to provide support for an OS that is
end-of-life. From 0.13.0 on, Windows XP is no longer supported. Users are
suggested to upgrade to a newer version of Windows, or install an
alternative OS that is supported.
No attempt is made to prevent installing or running the software on Windows
XP, you can still do so at your own risk, but do not expect it to work: do
not report issues about Windows XP to the issue tracker.
From 0.13.1 onwards OS X 10.7 is no longer supported. 0.13.0 was intended
to work on 10.7+, but severe issues with the libc++ version on 10.7.x keep
it from running reliably. 0.13.1 now requires 10.8+, and will communicate
that to 10.7 users, rather than crashing unexpectedly.
Notable changes

Change to wallet handling of mempool rejection
When a newly created transaction failed to enter the mempool due to
the limits on chains of unconfirmed transactions the sending RPC
calls would return an error. The transaction would still be queued
in the wallet and, once some of the parent transactions were
confirmed, broadcast after the software was restarted.
This behavior has been changed to return success and to reattempt
mempool insertion at the same time transaction rebroadcast is
attempted, avoiding a need for a restart.
Transactions in the wallet which cannot be accepted into the mempool
can be abandoned with the previously existing abandontransaction RPC
(or in the GUI via a context menu on the transaction).
0.13.2 Change log

Detailed release notes follow. This overview includes changes that affect
behavior, not code moves, refactors and string updates. For convenience in
locating the code changes and accompanying discussion, both the pull
request and git merge commit are mentioned.

Consensus

  • #9293 e591c10 [0.13 Backport #9053] IBD using chainwork instead of
height and not using header timestamp (gmaxwell) - #9053 5b93eee IBD
using chainwork instead of height and not using header timestamps
(gmaxwell)

RPC and other APIs

  • 8845 1d048b9 Don't return the address of a P2SH of a P2SH (jnewbery)

  • 9041 87fbced keypoololdest denote Unix epoch, not GMT

(s-matthew-english) - #9122 f82c81b fix getnettotals RPC description
about timemillis (visvirial) - #9042 5bcb05d [rpc] ParseHash: Fail when
length is not 64 (MarcoFalke) - #9194 f26dab7 Add option to return
non-segwit serialization via rpc (instagibbs) - #9347 b711390 [0.13.2]
wallet/rpc backports (MarcoFalke)
  • #9292 c365556 Complain when unknown rpcserialversion is specified
(sipa) - #9322 49a612f [qa] Don't set unknown rpcserialversion
(MarcoFalke)

Block and transaction handling

  • 8357 ce0d817 [mempool] Fix relaypriority calculation error (maiiz)

  • 9267 0a4aa87 [0.13 backport #9239] Disable fee estimates for a confirm

target of 1 block (morcos) - #9196 0c09d9f Send tip change notification
from invalidateblock (ryanofsky)

P2P protocol and network code

  • #8995 9ef3875 Add missing cs_main lock to ::GETBLOCKTXN processing
(TheBlueMatt) - #9234 94531b5 torcontrol: Explicitly request RSA1024
private key (laanwj) - #8637 2cad5db Compact Block Tweaks (rebase of

8235) (sipa)

  • #9058 286e548 Fixes for p2p-compactblocks.py test timeouts on travis
(#8842) (ryanofsky) - #8865 4c71fc4 Decouple peer-processing-logic from
block-connection-logic (TheBlueMatt) - #9117 6fe3981 net: don't send
feefilter messages before the version handshake is complete (theuni) -

9188 ca1fd75 Make orphan parent fetching ask for witnesses (gmaxwell) -

9052 3a3bcbf Use RelevantServices instead of node_network in

AttemptToEvict (gmaxwell) - #9048 9460771 [0.13 backport #9026] Fix
handling of invalid compact blocks (sdaftuar) - #9357 03b6f62 [0.13
backport #9352] Attempt reconstruction from all compact block
announcements (sdaftuar) - #9189 b96a8f7 Always add
default_witness_commitment with GBT client support (sipa) - #9253
28d0f22 Fix calculation of number of bound sockets to use (TheBlueMatt)
  • #9199 da5a16b Always drop the least preferred HB peer when adding a
new one (gmaxwell)

Build system

  • 9169 d1b4da9 build: fix qt5.7 build under macOS (theuni)

  • 9326 a0f7ece Update for OpenSSL 1.1 API (gmaxwell)

  • 9224 396c405 Prevent FD_SETSIZE error building on OpenBSD (ivdsangen)

GUI

  • #8972 6f86b53 Make warnings label selectable (jonasschnelli)
(MarcoFalke) - #9185 6d70a73 Fix coincontrol sort issue (jonasschnelli)
  • #9094 5f3a12c Use correct conversion function for boost::path datadir
(laanwj) - #8908 4a974b2 Update bitcoin-qt.desktop (s-matthew-english)
  • #9190 dc46b10 Plug many memory leaks (laanwj)

Wallet

  • #9290 35174a0 Make RelayWalletTransaction attempt to AcceptToMemoryPool
(gmaxwell) - #9295 43bcfca Bugfix: Fundrawtransaction: don't terminate
when keypool is empty (jonasschnelli) - #9302 f5d606e Return txid even
if ATMP fails for new transaction (sipa) - #9262 fe39f26 Prefer coins
that have fewer ancestors, sanity check txn before ATMP (instagibbs)

Tests and QA

  • #9159 eca9b46 Wait for specific block announcement in p2p-compactblocks
(ryanofsky) - #9186 dccdc3a Fix use-after-free in scheduler tests
(laanwj)
  • #9168 3107280 Add assert_raises_message to check specific error message
(mrbandrews) - #9191 29435db 0.13.2 Backports (MarcoFalke)
  • 9077 1d4c884 Increase wallet-dump RPC timeout (ryanofsky)

  • 9098 ecd7db5 Handle zombies and cluttered tmpdirs (MarcoFalke)

  • 8927 387ec9d Add script tests for FindAndDelete in pre-segwit and

segwit scripts (jl2012) - #9200 eebc699 bench: Fix subtle counting issue
when rescaling iteration count (laanwj)

Miscellaneous

  • #8838 094848b Calculate size and weight of block correctly in
CreateNewBlock() (jnewbery) - #8920 40169dc Set minimum required Boost
to 1.47.0 (fanquake)
  • #9251 a710a43 Improvement of documentation of command line parameter
'whitelist' (wodry) - #8932 106da69 Allow bitcoin-tx to create v2
transactions (btcdrak) - #8929 12428b4 add software-properties-common
(sigwo)
  • #9120 08d1c90 bug: Missed one "return false" in recent refactoring in

9067 (UdjinM6) - #9067 f85ee01 Fix exit codes (UdjinM6)

  • 9340 fb987b3 [0.13] Update secp256k1 subtree (MarcoFalke)

  • 9229 b172377 Remove calls to getaddrinfo_a (TheBlueMatt)

Credits

Thanks to everyone who directly contributed to this release:
  • Alex Morcos
  • BtcDrak
  • Cory Fields
  • fanquake
  • Gregory Maxwell
  • Gregory Sanders
  • instagibbs
  • Ivo van der Sangen
  • jnewbery
  • Johnson Lau
  • Jonas Schnelli
  • Luke Dashjr
  • maiiz
  • MarcoFalke
  • Masahiko Hyuga
  • Matt Corallo
  • matthias
  • mrbandrews
  • Pavel Janík
  • Pieter Wuille
  • randy-waterhouse
  • Russell Yanofsky
  • S. Matthew English
  • Steven
  • Suhas Daftuar
  • UdjinM6
  • Wladimir J. van der Laan
  • wodry
As well as everyone that helped translating on
Transifex.
bitcoin-dev mailing list
bitcoin-dev at lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
original: https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2017-January/013442.html
submitted by dev_list_bot to bitcoin_devlist [link] [comments]

7. Upgrading Bitcoin Core Using CoinMe Bitcoin ATM machine at Southcenter, WA  Ryan Conley BitClub Network Mine Bitcoin For Free- Insane Profits [Streamed] - Compiling a Bitcoin Wallet for Windows How to prune the blockchain in Bitcoin-Qt

Bitcoin Core (formerly Bitcoin-Qt) is the third Bitcoin client, developed by Wladimir van der Laan based on the original reference code by Satoshi Nakamoto. It has been bundled with bitcoind since version 0.5. Bitcoin-Qt has been rebranded to Bitcoin Core since version 0.9.0 .. Bitcoin Core can be used as a desktop client for regular payments or as a server utility for merchants and other 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. Now we simply need to install the Bitcoin ABC client. Enter the following into the same terminal: sudo apt-get install bitcoind bitcoin-qt. Bitcoin ABC should now be in your list of installed programs The terminal offers an app for both, Android and iOS. 6. CoinKite. Business owners who like to keep things more traditional might be interested in exploring CoinKite, as their POS terminal looks exactly like credit card terminals in regular shops. CoinKite's customers receive their terminal with a debit card for Bitcoin, which is also made by Bitcoin-qt says "Failed to read block". Close. 0. Posted by. u/blackman1969. 3 years ago. Archived. Bitcoin-qt says "Failed to read block". I had recently bought some bitcoins and they should be in my wallet. Except when I open Bitcoin-qt, it says "failed to read block" , then shuts down.

[index] [76] [4053] [7507] [18897] [21750] [15444] [14272] [14364] [29229] [11498]

7. Upgrading Bitcoin Core

For Bitcoin Core Client updates: https://bitcoincore.org @bitcoincoreorg in Twitter Linux terminal commands: sha256sum, tar, cp, sudo, rm, exit, less * All other commands have been covered in ... bitcoin machine, bitcoin moon, bitcoin miner app, bitcoin market, alpha m bitcoin, m y bitcoin analiz, ... bitcoin qt, bitcoin queda, bitcoin q4 2018, bitcoin questions, bitcoin q&a, q es bitcoin, Bitcoin entrepeneur Ryan Conley with BitClub Network and FutureNet demos the Bitcoin ATM at the Southcenter Mall near Seattle, WA. Soon BitClub Network is launching their own ATM network across ... To add the PPA and install Bitcoin open a terminal window (press Ctrl+Alt+T) and copy+paste the following lines: sudo apt-add-repository ppa:bitcoin/bitcoin -y sudo apt update && sudo apt install ... You will need to use this code in Terminal to launch Bitcoin-Qt from now on. To launch terminal press cmd + spacebar, then search terminal. Following this guide will prune the blockchain on your ...

Flag Counter