Install Bitcoind CryptoCoins Info Club

[Help] For some reason, my homescreen is very slow whenever I tried to swipe to the next page.

Here is my tweak list: 7-zip (POSIX): 16.02-1 A-Font: 1.5.2 Accelerated Home Button: 1.6 Activator Theme Fix: 1.0 Activator: 1.9.13~beta5 AdBlock for YouTube: 1.0.7 AllowTouchesOnPageDots: 1.0.1-1+debug AnimationsBeFast: 1.4.7 AppList: 1.5.15~beta1 Apps Manager: 1.5.0-12 AppStore++: 0.9.6-1 APT (apt-key): 1.4.9-2 APT 0.7 Transitional: 1:0-2 APT 1.4 Strict (libapt-pkg): 1.4.9-1 APT Command Line: 1:0-2 APT Strict (lib): 1.4.9-2 APT Strict: 1.4.9-1 Archero Cheats: 1.1.5+iOSGods.com Assuan: 2.5.1-1 Asteroid: 3.0.4 AutoTouch Cracked: 5.1.2-1k Barmoji: 1.9 Base Structure: 1-5 BatteryLife: 1.7.0 BegoneCIA (iOS 11 and 12): 0.2.1-2 Berkeley DB: 6.2.32-1 BetterCCIconsPro: 1.7.5k BetterCCXI (Weather Addon): 1.0.1 BetterCCXI: 1.4.8 betternet: 0.0.1 BetterSettings: 0.1.3 BigBoss Icon Set: 1.0 BinaryNumpad: 1.1 Bitcoin Billionaire Cheats: 4.8.1 Bourne-Again SHell: 5.0.3-1 bzip2: 1.0.6-1 CA Certs: 0.0.2 CamControls X: 1.0.2 Cappd: 1.0.3 CCLinker: 1.2.1 CCModules: 1.4-3 CCRinger: 2.1.0 CCSupport: 1.2-3 Cephei: 1.13.1-2 CircleSettings: 1.0.1 CocoaTop: 2.0.2 ColorBadges: 1.3.2-1 ColorFlow 4 (iOS 11 – 12): 1.3.0 Compactions CC: 1.1 CoolCC: 1:3.1 Core Utilities (/bin): 8.30-3 Core Utilities: 8.30-2 Cowbell: 1.2.1 CrashReporter: 1.16.0-1 Cuboid: 2.0.1 cURL: 7.65.0-1 Cydia Installer: 1.1.32~b16 Cydia Substrate: 0.9.7033 Cydia Translations: 1.1.32~b1 Cylinder: 1.0.6 CylinderFix: 0.0.2 DaDa-statusbar-1: 1.0 Darwin Tools: 1-6 Debian Packager: 1.18.25-11 Debian Utilities: 4.8.6-1 DeleteForever: 0.0.1-57 DetailedBatteryUsage: 1.1.1 Diff Utilities: 3.6-1 Disconnected: 1.0 diskdev-cmds: 593.221.1-1 DismissProgress: 1.0.4 DLGMemor Injected: 1.2.1 DoubleCut: 0.5 Dune: 1.2.1 DzMoha Icons: 9.8 Eclipse Dark Mode (iOS 12): 6.1.2 Episode - Choose Your Story Cheats: 10.40 Essential: 0-1 ExactTimePhone: 1.0-1+debug EZSwipe: 1.1 Fallout Shelter Cheats: 1.13.21 FastDel: 0.5 FDots: 1.0.1 file: 5.35-2 Filza File Manager 64-bit: 3.7.0-18 Find Utilities: 4.6.0-2 Fiona: 0.1 Flame: 1.3 Flat UI Theme: 1.2.4 FlipConvert: 0.0~beta5 Flipswitch: 1.0.16~beta5 FloatyDock: 1.5 FolderColor: 1.0-4 Free IAP: 0.0.1-7+debug gettext: 0.19.8-1 GNU Cryptography: 1.8.3-1 GNU Multiple Precision Arithmetic Library: 6.1.2-1 GnuPG Errors: 1.32-1 GnuPG: 2.2.11-2 GnuTLS: 3.5.19-1 grep: 3.1-1 Groovify: 1.2.1 Gushi Statusbar: 1.3 gzip: 1.9-1 HideDockLabels10: 0.0.1-7+debug HomeGesture: 2.1.4 Host AdBlocker: 1.6-3 hotspotvip: 4.7.0-1+debug HYI Repo Icons: 8.0.4 iCleaner Pro: 7.7.5 IconSupport: 1.11.1 Immortal: 1.2.1-1 IOKit Tools: 76-1 iOS Firmware: 12.2 iOSGods iAP Cracker: 1.0-2 iPhone Firmware (/sbin): 0-1 iThemer: 1.FuckYes Jailbreak Resources: 1.0~b23 Jumper: 1.5.0 KBPreferences: 0.0.7 Kiiimo Repo Icons: 12.5 KillX: 0.1.2 KSBA: 1.3.5-1 LeadMeHome: 1.0.1 LeaveMeAlone: 2.3.1 LetMeBlock: 0.0.6.8 LetMeKnow: 1.4.1 libbulletin: 0.1-145 libcolorpicker: 1.6.3-1 libcrashreport: 1.1.0-1 libCSColorPicker: 1.0.3 libCSPreferences: 1.2.0 Liberty Lite (Beta): 0.2.12 libfoxfortutils: 1.0.8 libidn2: 6.1.2-1 libimagepicker: 1.0.3 libnepeta: 0.1.1 libnghttp2-14: 1.38.0-1 libpackageinfo (cokepokes): 1.1.0.1-3 libpackageinfo: 1.1.0.1-1 libplist: 2.0.0-2 libSparkAppList: 1.0.3 libssh2: 1.8.0-2 libSubstitrate: 0.0.1-3 libswift (stable): 5.0 libswift4: 4.2.1-2 libsymbolicate: 1.9.0-1 libtasn1: 4.13-1 libunistring: 0.9.10-1 LightsOn: 1.0.0 Line StatusBar: 1.21 Lineal CC Theme: 1.0 Lineal Music Controls: 1.0 Lineal UI Theme: 1.2 Link Identity Editor: 2:2.1.1+elucubratus2 Locale Profiles in UTF-8: 1.0-1 LocalIAPStore: 1.4-2 Lotus Dark: 1.0.7 Lotus: 1.0 LowPowerMode: 1.0-3 LSPullToDismiss [Public]: 0.0.1-1 LZ4: 1.7.5-1 LZMA Utils: 2:4.32.7-2 Mega UHB IPv4+6 - iOS 9/10/11/12 - MUHB IPv4+6 (Mega Untrusted Hosts Blocker IPv4 and IPv6): 2.1.1 MessageColors: 1.5 MessageTypingIndicators: 1.0-1 Moonshine: 1.3 Moveable12: 1.0.0~beta29-32 Mune - Neon Edition: 1.1 Muze 4: 1.0 Muzik: 2.0 NCNoTitle: 1.0.1 Nettle: 3.4.1-1 New Curses: 5.9-1 New Curses: 6.1-1 New GNU Portable Threads: 1.6-1 NoCCGrabber12: 1.1 NoLowPowerAutoLock [Public]: 0.0.3 NoLSPadLock: 0.1 NoLSScreenshot: 0.0.1 NoSub (PalBreak w/ options): 1.3 Notchification Cracked: 1.4.2k Notifica: 0.3.0-4 NudeKeys (iOS 12): 1.0.0~b8 OpenSSL 1.0 Libraries: 1.0.2s-1 p11-kit: 0.23.12-1 PasscodeText: 0.1 Pebbli Status Bar for Xeon: 1.0 PencilChargingIndicator: 1.2~b6 PhotoManager (iOS 12): 1.0.7-1+debug pincrush: 0.9.2-1 PM, really?: 1.2 Portrait Lock: 1.8.4 PreferenceLoader: 2.2.4~beta1 PrefixUI: 1.2.2 Profile Directory: 0-1 readline: 8.0-1 RealCC: 1.0.2 Reddit No Ads: 0.0.2 ReProvision: 0.4.2 ReturnDismiss: 0.0.1-4 RocketBootstrap: 1.0.7~beta3 rsync: 3.1.3-2 Sareth: 1.0.3-1 sed: 4.5-1 Shadow Fight 2 Cheats: 1.9.38 shell-cmds: 118-8 shuffle: 1.0.4 Shy Labels: 1.1.1 Signing Certificate: 0.0.1 SilentScreenshot: 1.2 SmallVolumeStep: 1.1.0-2 SmartLight: 1.0.4 SmoothCursor: 1.1.3 SnowBoard Labels Extension: 1.0.0~Beta1 SnowBoard Settings Icons Extension: 1.0.4~Beta1 SnowBoard StatusBar Extension: 1.0.1~Beta1 SnowBoard: 1.2.14~Beta1 Soba: 1.2 Soda StatusBar(Gray灰色版): 1.3 Soul Knight Cheats: 2.2.1 Spotlightless11: 1.1.1 SSG3 Cheats: 1.0.0-4 StatusSwitcher: 1.1.1 Substitute Dummy for unc0ver: 1.0 Substrate Safe Mode: 0.9.6001.1 SugarCane: 1.0.0 System Memory Reset Fix: 1.0 system-cmds: 790.30.1-2 Tape Archive: 1.30-2 TapTapFlip: 1.5 TapVideoConfig: 0.0.4.1 TechSupport Framework (cokepokes): 1.5.0.1-2 TranslucentCydia: 0.9.0-1 Trust Cache Injector: 0.4~b5 Tweak Count 2: 1.0.1 tweakCompatible: 0.1.5 TypeReceipt: 0.0.2 UHB - iOS 9/10/11/12 (Untrusted Hosts Blocker): 1.7.1 UIKit Tools: 1.1.13-18 Ultrasound: 1.2.9 unrar: 5.6.4-1 unzip: 6.0+deb9u1-1 Viola: 1.5 Waze ++: 4.53 Whoops: 1.0.2 WiFi Passwords: 3.0.1 Xen HTML: 0.5.4 XenInfo: 2.2.6 XZ Utils: 5.2.4-4 zip: 2.32-1
Thanks in advance.
submitted by Benetzit to jailbreak [link] [comments]

Vertnode - An automated solution for installing Vertcoin node(s) on Single Board Computers

Hello Vertcoin Community,
Eager to contribute to the Vertcoin Community I began creating step by step walkthrough guides on how to get a Vertcoin node up and running on a Raspberry Pi, Raspberry Pi Zero and Intel NUC. Along with information to get a Vertcoin node up and running was also optional steps to install p2pool-vtc.
I decided that while this step by step guide might be helpful to a few, a setup script may prove to be useful to a wider range of people. I have this script to a point where I think it may be productive to share with a bigger audience, for those who are brave and have this hardware sitting around or like to tinker with projects; I invite you to test this setup script if you are interested, if you run into errors any sort of verbose console output of the error proves to be extremely helpful in troubleshooting.
The script was designed to produce a “headless” server... meaning we will not be using a GUI to configure Vertcoin or check to see how things are running. In fact, once the server is set up, you will only interact with it using command line calls over SSH. The idea is to have this full node be simple, low-power, with optimized memory usage and something that “just runs” in your basement, closet, etc.
Why run a headless node on a Single Board Computer?
The idea is to have this full node be simple, low-power, with optimized memory usage and something that “just runs” in your basement, closet, etc.
Required: USB Flash Drive 6GB - 32GB
Please note that the script was designed for Single Board Computers first and looks for an accessible USB Flash Drive to use for storing the blockchain and swap file, as constant writing to a microSD can degrade the health of the microSD.
Supports

Hardware

All of the hardware listed above is hardware that I have personally tested / am testing on myself. The plan is to continue expanding my arsenal of single board computers and continue to add support for more hardware to ensure as much compatibility as possible.
Functionality
It is worth noting that LIT can be ran with multiple configurations, the ones displayed in the Post Installation Report reflect values that run LIT with the Vertcoin Mainnet. Please be aware that the Vertcoin Testnet chain has not been mined 100% of the time in the past, if you make transactions on the Vertcoin testnet that do not go through it is likely because the chain has stopped being mined.
BE CAREFUL WITH YOUR COINS, ONLY TEST WITH WHAT YOU ARE OKAY WITH LOSING IF YOU USE THE MAINNET.

Vertcoin Testnet Coins

https://tvtc.blkidx.org/faucet/
I've included some documentation on LIT I created which includes information I found to be useful: https://github.com/e-corp-sam-sepiol/vertnode/blob/mastedocs/lit.md
Please visit the mit-dci/lit github repository for the most up to date information on lit: https://github.com/mit-dci/lit

Vertnode | Automated Vertcoin Node Installation Script

https://github.com/e-corp-sam-sepiol/vertnode

Recommended: Use Etcher to install the chosen OS to your microSD card / USB flash drive.

If you intend on installing Ubuntu Server 16.04 to your Intel NUC please use Etcher to install the .iso to your USB flash drive.
https://etcher.io/
PLEASE NOTE THIS SCRIPT MAY GIVE AN ERROR. THIS IS THE NATURE OF TESTING. PLEASE REPORT YOUR ERRORS IF YOU WANT THEM TO BE FIXED/RESOLVED. THANK YOU FOR BETTERING THE DEVELOPMENT OF THIS SCRIPT.

Ubuntu Server 16.04 Setup Details

You can use different clients to ssh into your node. One option is using PuTTY or Git Bash on Windows which is included in the desktop version of Git. If you are using Linux you can simply open a new terminal window and ssh to the IP address of your node (hardware you intend installing the Vertcoin node on).
You will need to know the IP address of your node, this can be found on your router page.
ssh 192.168.1.5 -l pi For example, this command uses ssh to login to 192.168.1.5 using the -l login name of pi. The IP address of your node will likely be different for you, in this example I am logging into a Raspberry Pi which has a default login name of pi.
A brief list of commands that can be used to check on the Vertcoin node status:
vertcoin-cli getblockchaininfo | Grab information about your blockchain
vertcoin-cli getblockcount | Grab the current count of blocks on your node
vertcoin-cli getconnectioncount | Grab the current count of connections to your node. A number of connections larger than 8 means that you have incoming connections to your node. The default settings are to make 8 outgoing connections. If you want incoming connections please port forward your Raspberry Pi in your Router settings page.
vertcoin-cli getpeerinfo | Grab the information about the peers you have connected to / are connected to
vertcoin-cli getnettotals | Grab network data, how much downloaded/upload displayed in bytes
tail -f ~/.vertcoin/debug.log | Output the latest lines in the Vertcoin debug.log to see verbose information about the Vertcoin daemon (ctrl+c to stop)
Thank you to all who have helped me and inspired me thus far, @b17z, @jamesl22, @vertcoinmarketingteam, @canen, @flakfired, @etang600, @BDF, @tucker178, @Xer0
This work is dedicated to the users of Vertcoin, thank you for making this possible.
7/20/2018 Thank you @CommodoreAmiga for the incredibly generous tip <3
You can reach me @Sam Sepiol#3396 on the Vertcoin Discord, here on reddit or @ [email protected]
submitted by ecorp-sam-sepiol to vertcoin [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]

A simple guide to financial sovereignty (set up your Bitcoin fullnode)

In 2009, a 9 pages white paper by satoshi Nakamoto described a protocol that made central banking obselete. It's a new paradigm where monney is no longer controlled by a few, but by the whole network.
The shift is already happening, as we speak, even if it's hard to see, especially if you lack the fundamental knowledege of cryptoghraphy, game theory and economics. It's just a matter of time before you realize that Bitcoin is hard money, and for the first time we have a framework to apply austrian economics, without permission. Time to reset the keynesian monopoly game.
I don't think people are inherently bad, it's just that in the actual system (which I call the legacy system) people are incentivised to make decisions that are good from their individual perspective, but unfortunately, the sum of those individual decisions are bad from the collective group perspective. That's just plain simple game theory. What makes Bitcoin so special is it's perfectly aligned set of incentives that makes individuals and collectives outcomes better. It switches the economic model from keynesian to austrian, inflation to deflation, spending to saving, modern slavery (throught debt) to financial sovereingty, de-evolution to evolution. We are currently shifting from fiat to Bitcoin.
What you think capitalism is has nothing to do with what Capitalism really is in a free market. Capitalism is beautiful, it's simply the act of evolution, saving and optimising for consumming only what's needed (don't forget with live in a world with limited ressources, yes we all forgot). Stop spending and start capitalising, that's what we should be doing. But it's near impossible in a world run by socialists imposing debt using violence. What do you think back the US dollar ? gold ? no no, only tanks, aircraft carriers, soldiers and corrupt politicians.
Our only way out of this madness with the minimum violence is Bitcoin.
To be clear, if you dont run a fullnode, then you don't validate the transactions yourself (which is one purpose of running a fullnode). If you don't do the job yourself, then you have no other choice then to trust someone else for it. That's not necesserely a bad thing, as long as you are aware of it. You have no say in what defines Bitcoin, you enforce no rules. You serve no purpose in the Bitcoin realm. Why not !
Now if you seek financial sovereignty and want to take part in the new money paradigm, you will need to operate a fullnode and get your hands a little dirty. This guide hopefuly will take you there while walking you through the steps of setting up your autonomous Bitcoin Core full node.
Why Bitcoin Core ? simply because the Bitcoin core client implement and enforce the set of rules that I myself define as being Bitcoin.

Prerequis

install

Choose & download the latest binaries for your platform directly from github: https://bitcoincore.org/bin/bitcoin-core-0.16.2
at the time of writing, the latest bitcoin core version is 0.16.2
wget https://bitcoincore.org/bin/bitcoin-core-0.16.2/bitcoin-0.16.2-x86_64-linux-gnu.tar.gz tar -zxvf bitcoin-0.16.2-x86_64-linux-gnu.tar.gz sudo mv bitcoin-0.16.2/bin/* /uslocal/bin/ rm -rf bitcoin-0.16.2-x86_64-linux-gnu.tar.gz bitcoin-0.16.2 # clean 

firewall

Make sure the needed ports (8333, 8332) are open on your server. If you don't know, you can & should use a firewall on your server. I use ufw, which stands for uncomplicated firewall.
sudo apt install ufw # install ufw 
configure default rules & enable firewall
sudo ufw default deny incoming sudo ufw default allow outgoing sudo ufw allow ssh # if you operate your server via ssh dont forget to allow ssh before enabling sudo ufw enable 
Once your firewall is ready, open the bitcoin ports :
sudo ufw allow 8333 # mainnet sudo ufw allow 8332 # mainnet rpc/http sudo ufw allow 7000 # netcat transfert (for trusted sync) 
check your firewall rules with sudo ufw status numbered

init

Start bitcoind so that it create the initial ~/.bitcoin folder structure.
bitcoind& # launch daemon (the & run the copmmand in the background) bitcoin-cli stop # stop the daemon once folder structure is created 

config

In my case, for a personnal fullnode, I want to run a full txindexed chain. We only live once and i want all options to be possible/available :) If you plan to interact with the lightning network in the future and want to stay 100% trustless, I encourage you txindexing the chain (because you'll need an indexed chain). it's not hard to txindex the chain later on, but the less you touch the data, the better. so always better to start with txindex=1 if you want to go for the long run. It only adds 26Go on top of the 200Go non indexed chain. So it's worth it !
Just to get an idea of the size of the bitcoin core chain (August 23, 2018) :
network folder txindexed height size
mainnet blocks + chainstate yes 538.094 209Go + 2.7Go = 221.7
mainnet blocks + chainstate no 538.094 193Go + 2.7Go = 195.7Go
testnet blocks + chainstate yes - -
testnet blocks + chainstate no 1.407.580 20Go + 982Mo = 21Go
Create a bitcoin.conf config file in the ~/.bitcoin folder. This is my default settings, feel free to adjust to your need. [ see full config Running Bitcoin - Bitcoin Wiki ]
# see full config here https://en.bitcoin.it/wiki/Running_Bitcoin # Global daemon=1 txindex=1 rpcallowip=0.0.0.0/0 # bind network interface to local only for now server=1 rest=1 # RPC rpcport=8332 rpcuser=admin rpcpassword=password # define a password rpcworkqueue=100 # zmq zmqpubrawblock=tcp://*:8331 zmqpubrawtx=tcp://*:8331 #zmqpubhashblock=tcp://*:8331 #zmqpubhashtx=tcp://*:8331 # numbers of peers. default to 125 maxconnections=10 # utxo cache. default to 300M dbcache=100 # Spam protection limitfreerelay=10 minrelaytxfee=0.0001 

Sync the blockchain

There are 2 ways you can donwload/sync the bitcoin blochain :

Network sync (default)

If this is the first time you are setting up a bitcoin full node, it's the only way to trust the data. It will take time, depending on your hardware and network speed, it could vary from hours to days. You have nothing to do but leave the bitcoind daemon running. check status with bitcoin-cli getblockchaininfo, kill daemon with bitcoin-cli stop.
Remember that this is the only procedure you should use in order to sync the blockchain for the first time, as you don't want to trust anyone with that data except the network itself.

Trusted sync

Skip this chapter if this is the first you're setting up a full node.
Once you operate a fully "network trusted" node, if you'd like to operate other nodes, syncing them from your trusted node(s) will go much faster, since you simply have to copy the trusted data from server to server directly, instead of going throught the bitcoin core network sync.
You will need to transfer the chainstate & blocks directory from the ~/.bitcoin folder of one of your trusted node to the new one. The way you achieve that transfer is up to you.
At the time of writing (August 23, 2018), the txindexed blockchain (chainstate + blocks up to height 538.094) is around 220Go. Moving that quantity of data over the network is not a trivial task, but if the transfer happens between 2 reliable servers, then netcat will be great for the job. (netcat sends raw tcp packets, there is no authentification or resume feature).
Note: with netcat, if one of the servers connection is not stable, and you lose connection, you will have to start again. that's a bummer. in that case you are better of with tools like rsync or rcp that let you resume a transfer.
In order to make the transfer a simple task, make sure you do the following on both of the receiver and the sender server :
Once both your servers (receiver & sender) are netcat ready, proceed as follow :
This is the transfer times for my last data sync between 2 servers hosted at time4vps.eu (not too bad) | folder | size | transfer time | - | - | - | blocks | 209Go | 5h20 | chainstate | 2.7Go | 4min

bitcoind as a service

For ease of use and 100% uptime, simply add bitcoind to your system service manager (in my case systemd) create the file /etc/systemd/system/bitcoind.service and add the following to it :
[Unit] Description=Bitcoin daemon After=network.target [Service] User=larafale RuntimeDirectory=bitcoind Type=forking ExecStart=/uslocal/bin/bitcoind -conf=/home/larafale/.bitcoin/bitcoin.conf ExecStop=/uslocal/bin/bitcoin-cli stop KillMode=process Restart=always RestartSec=120 TimeoutSec=240 # Hardening measures #################### # Provide a private /tmp and /vatmp. PrivateTmp=true # Mount /usr, /boot/ and /etc read-only for the process. ProtectSystem=full # Disallow the process and all of its children to gain # new privileges through execve(). NoNewPrivileges=true # Use a new /dev namespace only populated with API pseudo devices # such as /dev/null, /dev/zero and /dev/random. PrivateDevices=true # Deny the creation of writable and executable memory mappings. MemoryDenyWriteExecute=true [Install] WantedBy=multi-user.target 
Don't forget to correct the user name & the bitcoin.conf path. Once the systemd bitcoind config file is created, reload system services and start the bitcoind service:
sudo systemctl daemon-reload # reload new services sudo systemctl enable bitcoind # enable bitcoind sudo systemctl start bitcoind # start bitcoind sudo systemctl status bitcoind # check bitcoind status 
If everything worked, status should output the following:
● bitcoind.service - Bitcoin daemon Loaded: loaded (/etc/systemd/system/bitcoind.service; enabled; vendor preset: enabled) Active: active (running) since jeu. 2018-08-23 21:17:41 CEST; 5s ago Process: 5218 ExecStart=/uslocal/bin/bitcoind -conf=/home/larafale/.bitcoin/bitcoin.conf (code=exited, status=0/SUCCESS) Main PID: 5219 (bitcoind) CGroup: /system.slice/bitcoind.service └─5219 /uslocal/bin/bitcoind -conf=/home/larafale/.bitcoin/bitcoin.conf 
The bitcoind service is active and will automatically restart on statup/crash. Wait a couple minutes until the bitcoin-cli getblockchaininfo command returns the chain status. You can also query the rest interface by opening http://nodeIP:8332/rest/chaininfo.json in your browser.

Conclusion

You now have a full Bitcoin core node running on it's own. What's next ? Well I never blogged before, this is the first time I am outsourcing some of my work. I'm a passionnate enginner working on all kind of technologies. I've been dedicating half of my time to Bitcoin for the last 2 years already, so if this guide was usefull and want to go deeper , just let me know, depending on the feedback I get, i'll consider outsourcing more interesting work. For example next post could be about setting up an Electrum Server so you can safely use SPV wallets trusting your own fullnode.
Also I'm currently working on a trustless bitcoin payment processor called 8333, make sure you follow @_8333_ on twitter. I think I will release the project end of 2018. Ping me if interested.
The best way you can show support is via Bitcoin : 16FKGPiivpo3Z7FFPLdkoVRcV2ASBc7Ktu
submitted by larafale to Bitcoin [link] [comments]

Zeus/Gaw ASIC Setup Guide for Linux/Raspberry Pi

So I recently I became quite interested in mining and cyptocurrencies in general. So interested in fact that I bit the bullet and decided to buy myself a GAW Fury.
I then spent some time doing research on how to set up a GAW or Zeus ASIC on Linux, in particular on a Raspberry Pi, and have found most guides to be awful. The reason they are so bad IMHO is that they assume quite a bit of prior knowledge, either with Linux or mining, and give very little instructions. So I have tried to put together a guide that requires very little prior knowledge.
It is my aim that anyone could get their shiny new asic up and mining in no time using this guide. Anyway, I present...

The Complete Noobs Guide to Setting Up a Zeus or Gaw ASIC on Debian/Ubuntu/Raspberry Pi

Resources

About Cyrptocurrencies and Their Jargon

If you are new to cryptocurrencies and how they work I suggest taking a look at this series of KhanAcademy videos. They are for Bitcoin but the theory is the same. I found them very helpful when it came to understanding what mining actually does and the mechanics of cyrptocurrencies.
Also take a look at sircamm22 his info found here, is great and breaks down a large number of concepts. I slightly disagree with no. 21 regarding preordering. Just exercise common sense.

Linux

If you are new to Linux you could follow along by simply typing in the commands. However I highly recommend taking the time to learn what you are doing. This course is a great place to start.

Computer Setup

By the end of this section you will have your device turned on, fully setup and connected to the internet with.
Note: Commands to be typed into the command line will be displayed like this:
echo Hello World

Desktop/Laptop

For laptops and desktops already running Ubuntu or Debian I will assume you have setup your internet setup as part of the installation.
If not: There are plenty of guides out there and the installation/setup process is very easy. A good place to start for Ubuntu is here.
Now open up a terminal window. Ctrl + alt + t on a standard Ubuntu installation.
If you plan on using this PC without a monitor I would suggest installing an SSH Server.
These commands will be discussed later on in the guide.
sudo apt-get -y install openssh-server
sudo service openssh-server start

Raspberry Pi

The Raspberry Pi Foundation has put together a great guide in PDF format.
Use NOOBS it will save you a lot of trouble. NB: Some SD cards don't support NOOBs but will work fine if the image is put on using a different method.
Here is a great guide for setting up the Raspberry Pi SD card from Elinux.org. In fact it's a great place to start for anything RPi related. Raspberry Pi hub at Elinux.
Once the SD card is setup you will need to insert it into the Raspberry Pi and boot. Install Raspbian from the NOOBs menu and wait.
Follow this guide by Adafruit for first time setup. You will need to enable SSH Server.
I suggest not starting the desktop on boot. It can be easily run from the command line by typing startx.
Follow this guide by Adafruit to setup your network. Found here. No need to do this if you set up previously in the first time config.
We will also at this point want to setup ssh. Again I will point you to an Adafruit guide.
Once done exit back to a standard command line interface. This can be done in LXDE by using the power off menu located in the bottom right corner.

Miner Setup

Installing BFGMiner

If you want to the Raspberry Pi or PC without a monitor go ahead and SSH into your device.
So now you should be staring at a command line interface whether on the device with a monitor or via SSH.
First things first lets make sure we are all up to date. This will update our package list from the repositories and upgrade them to the newest version. "-y" Will simply say yes to any prompts.
sudo apt-get update && sudo apt-get -y upgrade
We are going to need to install some useful tools. Git-core is how we will clone and download BFGMiner from GitHub and Screen allows multiple command line instances and means if we exit out of ssh session or quit Terminal on Ubuntu, BFGMiner will continue to run.
sudo apt-get install git-core screen
We also need to download some other tools/dependencies to ensure that BFGMiner will compile successfully.
sudo apt-get -y install build-essential autoconf automake libtool pkg-config libcurl4-gnutls-dev libjansson-dev uthash-dev libncursesw5-dev libudev-dev libusb-1.0-0-dev libevent-dev libmicrohttpd-dev libc-bin
Ok now change into your home directory.
cd ~
And clone BFGMiner by Darkwinde.
git clone https://github.com/Darkwinde/bfgminer.git
Once the download has completed move into the bfgminer directory.
cd bfgminer
The following steps may take a while.
Now run autogen.sh
sudo ./autogen.sh
You will need to make the configure script execuitable.
sudo chmod +x ./configure
Now configure bfgminer
sudo ./configure CFLAGS="-O3" --enable-scrypt
Now lets make!
sudo make
Install BFGMiner
sudo make install
One more thing...
sudo ldconfig

Running BFGMiner

If you haven't already plug in your ASIC.
Just confirm your system is recognising the ASIC.
lsusb
Its output should look similar to this (no need to type this in):
Bus 001 Device 005: ID 10c4:ea60 Cygnal Integrated Products, Inc. CP210x UART Bridge / myAVR mySmartUSB light
Yep there it is our ASIC listed as device 005. There is no need to install any drivers, unlike in windows, as they come in the kernel.
Now lets actually start BFGMiner.
You will want to start a screen session to ensure BFGMiner doesn't quite when you exit.
"-S" is the option for starting a new screen session. You can replace "miner" with anything you like.
screen -S miner
Now you can run the commands below.
Here is a sample of what you should type. You will need to replace somethings with your own values.
sudo bfgminer --scrypt -o stratum+tcp://URL:PORT -u USERNAME -p PASSWORD --zeus-cc CHIPCOUNT --zeus-clk 328 -S zeus:/dev/ttyUSB0
Where:
URL:PORT is the address and port of the pool you wih to use. Now I won't suggest a pool. I will leave that decision up to you. If you do wish to mine DOGE take a look at this site for a list of pools and comparisons.
USERNAME this is the username you use on the pool. Every pool is different. Check your pool's website for details. PASSWORD same as above. Specific to your pool, not every pool requires one.
CHIPCOUNT this is specific to which ASIC you are using.
For GAWMiner ASIC's:
  • War Machine: 256
  • Falcon: 128
  • Black Widow: 64
  • Fury: 6
For ZeusMiner ASIC's:
  • Blizzard: 6
  • Cyclone: 96
  • Hurricane X2: 48
  • Hurricane X3: 64
  • Thunder X2: 96
  • Thunder X3: 128
Now to make sure you don't stop mining when you exit ssh or terminal. Press:
ctrl + a + d
To come back to the BFGMiner screen simply run:
screen -r miner
You're done!!

Start on Boot

First off you will want to make sure you have BFGMiner running correctly. Ensure you have the miners set up properly and your pool correctly configured.
Start a BFGMiner instance, detailed above.
Once the instance has started and you are happy with how everything is working press "s" on your keyboard to enter the settings menu.
Now press the "w" key. Don't press enter. We want to specify where our config will go. Type:
/home/USERNAME/bfgminer.conf
Substitute USERNAME for your user. On a standard RPI install its pi. On ubuntu it's what you set during the instillation.
Now press the enter key to return back to the main BFGMiner screen. Press "q" on your keyboard to exit BFGMiner. You should now be back in the command line.
Now we want to edit a file called rc.local. Any commands in this file will be executed on boot.
sudo nano /etc/rc.local
Depending on your system this file may already contain some commands. Be careful not to delete them.
After the last command and before "exit 0" type the following on one line:
sudo -u USERNAME screen -d -m sudo bfgminer --config /home/USERNAME/bfgminer.conf
Where USERNAME = your username
Hit ctrl + x then y to save and exit nano.
The above command will create a new screen session and run bfgminer using the config we created earlier. All while as our username so that we can easily reattach.
Lets reboot to ensure it is working correctly:
sudo reboot
Once rebooted and logged in, show all running screen sessions:
screen -ls
Reattach to the session. You only need to use the numbers before the first dot.
e.g Mine looks like: 2480..hostname (13/07/14 12:02:09) (Detached). So I type:
screen -r 2480
Verify everything worked as expected. Then ctrl + a + d to exit.
You have now setup BFGMiner to restart on reboot.

Power Failure

If you are using a Raspberry Pi and it loses power it will automatically reboot on receiving power again.
For standard desktop PCs there is an option in some BIOS/UEFI to turn the computer on when it receives power. Consult your motherboard's manual and manufacturer's website.

Sources

Here is where I got my info from.
And of course /dogemining

Wrap Up

Congrats you've done it. You have managed to successfully get your shiny new asic mining away.
I do plan to make another guide detailing how to setup and use StarMiner a ready to go RPi mining distro.
So I hope this is helpful for you guys. I have seen lots of posts asking the exact same questions again and again and I have tried to answer these as best I can. I am still learning about this stuff so if there is something I have missed or a mistake I have made please tell me.
Anyway good luck. And I'll see you at the moon.
Cheers Frogsiedoodle
Edit 1: Layout and formatting.
Edit 2: Added instructions for screen which I initially forgot.
Edit 3: Removed 1 unneeded dependency
Edit 4: Added section on start on reboot and power failure.
submitted by Frogsiedoodle to dogemining [link] [comments]

pyconfig.h: No such file or directory

Please help total noob?
I followed steps for my linux mint 18 system (DEBIAN / UBUNTU QUICK INSTALL FOR USERS). Seems ok until I get to:
[email protected] ~/Downloads/joinmarket-0.2.2 $ python wallet-tool.py generate
noncefunc.c:12:24: fatal error: pyconfig.h: No such file or directory compilation terminated. Traceback (most recent call last): File "wallet-tool.py", line 11, in from joinmarket import load_program_config, get_network, Wallet, encryptData, \ File "/home/x1/Downloads/joinmarket-0.2.2/joinmarket/init.py", line 11, in from .irc import IRCMessageChannel, B_PER_SEC File "/home/x1/Downloads/joinmarket-0.2.2/joinmarket/irc.py", line 11, in from joinmarket.configure import get_config_irc_channel, jm_single File "/home/x1/Downloads/joinmarket-0.2.2/joinmarket/configure.py", line 12, in import bitcoin as btc File "/home/x1/Downloads/joinmarket-0.2.2/bitcoin/init.py", line 4, in from bitcoin.secp256k1_main import * File "/home/x1/Downloads/joinmarket-0.2.2/bitcoin/secp256k1_main.py", line 45, in ffi.compile() File "/uslocal/lib/python2.7/dist-packages/cffi/api.py", line 672, in compile compiler_verbose=verbose, debug=debug, **kwds) File "/uslocal/lib/python2.7/dist-packages/cffi/recompiler.py", line 1471, in recompile compiler_verbose, debug) File "/uslocal/lib/python2.7/dist-packages/cffi/ffiplatform.py", line 29, in compile outputfilename = _build(tmpdir, ext, compiler_verbose, debug) File "/uslocal/lib/python2.7/dist-packages/cffi/ffiplatform.py", line 65, in _build raise VerificationError('%s: %s' % (e.class.name_, e)) cffi.ffiplatform.VerificationError: CompileError: command 'x86_64-linux-gnu-gcc'
submitted by newbyyyyyyyy to joinmarket [link] [comments]

Help with installing bitcoin-qt on ubuntu (booted from usb on a mac), from another usb

Hi everyone im quite new to bitcoin and this subreddit has been extremely helpful so thank you! Im trying to create an offline wallet and its so damn hard, since im not that good with computers... Anyways Ive been following the official guide on the bitcoin website (https://en.bitcoin.it/wiki/How_to_set_up_a_secure_offline_savings_wallet) and im on step 7 now which has been a difficult journey, (diretions on ubuntu is hard for the average user) I have downloaded bitcoin-0.8.6-linux and its on a seperate memory stick. On the read me file it says 'you need the Qt4 run-time libraries to run Bitcoin-Qt. On debian or ubuntu: 'sudo apt-get install libqtgui4'
Unpack the files into a directory and run:
-bin/32/bitcoin-qt (GUI, 32-bit) -bin/32/bitcoind (headless, 32-bit) -bin/64/bitcoin-qt (GUI, 64-bit) -bin/64/bitcoind (headless, 64-bit) '
K so typed sudo apt-get install libqtgui4 into terminal and it says 'libqtgui4 is already the newest version.' What do they mean by Unpack the files into a directory and run: ... ??
When I type -bin/64/bitcoin-qt (GUI, 64-bit) into terminal it says No such file or directory
When I double click on bitcoin-qt file it says 'Could not display "bitcoin-qt" There is no application installed for "executable" files. Do you want to search for an application to open this file? ' clicked yes then
It returns empty.
Thanks in advance for your help!
submitted by assthete to Bitcoin [link] [comments]

Installing software outside of the package manager

Hello all.
I've recently taken an interest in Bitcoins (/bitcoins), and so I've naturally decided to try them out using Bitcoin's own bitcoin-qt wallet software. Unfortunately, debian-qt only appears to be available in the sid (unstable) repositories and I'm running wheezy (stable), so I've had to download the binaries from bitcoin.org and work it out from there.
I've pretty much got everything working, but I'm not sure if there's a preferred standard way to do what I'm doing. I have done a fair bit of research, and it has lead me to believe that /opt or /uslocal is the best place to home user installed programs.
Pretty much, the steps I've taken so far are: 1. Download the tarball from bitcoin.org. 2. Verify it to make sure it's authentic and all that jazz. 3. Extract it (which leaves me with a directory called bitcoin-0.8.6-linux). 4. Find the 64 bit binaries in bitcoin-0.8.6-linux (which are located at bitcoin-0.8.6-linux/bin/64/) and copy them to /uslocal/bin.
That's what I've done as far as installation goes. I have, of course, set up a menu in the application menu for XFCE that leads to the bitcoin-qt executable that's in /uslocal/bin, but other than that, that's all. One issue that is remaining is that in the applications menu, the application for the bitcoin wallet has no icon. Now, I know how to implement icons, but I'm not sure where the standard place for housing icons/pngs is on debian/linux systems, so I haven't bothered yet.
So, my main question is: have I done this right? Is this the standard way to do things, as far as installing outside of the package manager goes?
All of the software I have previously installed has been through the package manager, so this is new territory to me. I'd love to hear your advice -- thank you for reading. :)
submitted by Mint_Apple_Pie to debian [link] [comments]

[WTS] 2 GPU Mining Rigs 1.53 mh/s and 650 kh/s (2.18 mh/s total)

Looking to sell off two mining rigs.
Rig 1 - 1.5 GH/s Bitcoin or 1.53 MH/s Litecoin
Similar setup sold on eBay for $879.99 plus shipping.
I would sell this one for $800 shipped in the continental USA.
Rig 2 - 660 MH/s Bitcoin or 650 KH/s Litecoin
  • AMD A4-5300 Trinity 3.4GHz (3.6GHz Turbo) Socket FM2 65W Dual-Core Desktop APU
  • ASUS F2A55-M LE FM2 AMD A55 (Hudson D2) HDMI Micro ATX AMD Motherboard with UEFI BIOS
  • CORSAIR XMS 4GB 240-Pin DDR3 SDRAM DDR3 1333 Desktop Memory Model CMX4GX3M1A1333C9
  • 2x SAPPHIRE 100355OCL Radeon HD 7850 2GB 256-bit GDDR5 PCI Express 3.0 x16 HDCP Ready CrossFireX Support Video Card
  • LG 24X DVD Burner
  • LOGISYS Computer CS368RB Red & Black Steel ATX Mid Tower Computer Case
  • CORSAIR CX Series CX750 750W ATX12V / EPS12V SLI Ready CrossFire Ready 80 PLUS BRONZE Certified Active PFC
  • Microsoft Windows 7 Professional 64-bit - OEM
  • Western Digital WD Blue WD5000AAKX 500GB 7200 RPM 16MB Cache SATA 6.0Gb/s
SOLD
Both rigs runs Windows and comes with the installation disc (Dell branded), but I was running a live Debian-based OS from a USB drive that will be included (4gb). It supports litecoin and bitcoin, and even the USB ASIC block erupters. It has remote monitoring support, which is mainly why I used it.
Will accept litecoin, bitcoin, Paypal, Dwolla, or Wells Fargo transfers. I would rather not ship outside the USA or part out. If no one is interested here, I will likely just list them on eBay.
submitted by wasabi12 to ltcmarket [link] [comments]

Bitcoin Core 0.10.0 released | Wladimir | Feb 16 2015

Wladimir on Feb 16 2015:
Bitcoin Core version 0.10.0 is now available from:
https://bitcoin.org/bin/0.10.0/
This is a new major version release, bringing both new features and
bug fixes.
Please report bugs using the issue tracker at github:
https://github.com/bitcoin/bitcoin/issues
The whole distribution is also available as torrent:
https://bitcoin.org/bin/0.10.0/bitcoin-0.10.0.torrent
magnet:?xt=urn:btih:170c61fe09dafecfbb97cb4dccd32173383f4e68&dn;=0.10.0&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%2Fopen.demonii.com%3A1337&ws;=https%3A%2F%2Fbitcoin.org%2Fbin%2F
Upgrading and downgrading

How to Upgrade
If you are running an older version, shut it down. Wait until it has completely
shut down (which might take a few minutes for older versions), then run the
installer (on Windows) or just copy over /Applications/Bitcoin-Qt (on Mac) or
bitcoind/bitcoin-qt (on Linux).
Downgrading warning
Because release 0.10.0 makes use of headers-first synchronization and parallel
block download (see further), the block files and databases are not
backwards-compatible with older versions of Bitcoin Core or other software:
  • Blocks will be stored on disk out of order (in the order they are
received, really), which makes it incompatible with some tools or
other programs. Reindexing using earlier versions will also not work
anymore as a result of this.
  • The block index database will now hold headers for which no block is
stored on disk, which earlier versions won't support.
If you want to be able to downgrade smoothly, make a backup of your entire data
directory. Without this your node will need start syncing (or importing from
bootstrap.dat) anew afterwards. It is possible that the data from a completely
synchronised 0.10 node may be usable in older versions as-is, but this is not
supported and may break as soon as the older version attempts to reindex.
This does not affect wallet forward or backward compatibility.
Notable changes

Faster synchronization
Bitcoin Core now uses 'headers-first synchronization'. This means that we first
ask peers for block headers (a total of 27 megabytes, as of December 2014) and
validate those. In a second stage, when the headers have been discovered, we
download the blocks. However, as we already know about the whole chain in
advance, the blocks can be downloaded in parallel from all available peers.
In practice, this means a much faster and more robust synchronization. On
recent hardware with a decent network link, it can be as little as 3 hours
for an initial full synchronization. You may notice a slower progress in the
very first few minutes, when headers are still being fetched and verified, but
it should gain speed afterwards.
A few RPCs were added/updated as a result of this:
  • getblockchaininfo now returns the number of validated headers in addition to
the number of validated blocks.
  • getpeerinfo lists both the number of blocks and headers we know we have in
common with each peer. While synchronizing, the heights of the blocks that we
have requested from peers (but haven't received yet) are also listed as
'inflight'.
  • A new RPC getchaintips lists all known branches of the block chain,
including those we only have headers for.
Transaction fee changes
This release automatically estimates how high a transaction fee (or how
high a priority) transactions require to be confirmed quickly. The default
settings will create transactions that confirm quickly; see the new
'txconfirmtarget' setting to control the tradeoff between fees and
confirmation times. Fees are added by default unless the 'sendfreetransactions'
setting is enabled.
Prior releases used hard-coded fees (and priorities), and would
sometimes create transactions that took a very long time to confirm.
Statistics used to estimate fees and priorities are saved in the
data directory in the fee_estimates.dat file just before
program shutdown, and are read in at startup.
New command line options for transaction fee changes:
  • -txconfirmtarget=n : create transactions that have enough fees (or priority)
so they are likely to begin confirmation within n blocks (default: 1). This setting
is over-ridden by the -paytxfee option.
  • -sendfreetransactions : Send transactions as zero-fee transactions if possible
(default: 0)
New RPC commands for fee estimation:
  • estimatefee nblocks : Returns approximate fee-per-1,000-bytes needed for
a transaction to begin confirmation within nblocks. Returns -1 if not enough
transactions have been observed to compute a good estimate.
  • estimatepriority nblocks : Returns approximate priority needed for
a zero-fee transaction to begin confirmation within nblocks. Returns -1 if not
enough free transactions have been observed to compute a good
estimate.
RPC access control changes
Subnet matching for the purpose of access control is now done
by matching the binary network address, instead of with string wildcard matching.
For the user this means that -rpcallowip takes a subnet specification, which can be
  • a single IP address (e.g. 1.2.3.4 or fe80::0012:3456:789a:bcde)
  • a network/CIDR (e.g. 1.2.3.0/24 or fe80::0000/64)
  • a network/netmask (e.g. 1.2.3.4/255.255.255.0 or fe80::0012:3456:789a:bcde/ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff)
An arbitrary number of -rpcallow arguments can be given. An incoming connection will be accepted if its origin address
matches one of them.
For example:
| 0.9.x and before | 0.10.x |
|--------------------------------------------|---------------------------------------|
| -rpcallowip=192.168.1.1 | -rpcallowip=192.168.1.1 (unchanged) |
| -rpcallowip=192.168.1.* | -rpcallowip=192.168.1.0/24 |
| -rpcallowip=192.168.* | -rpcallowip=192.168.0.0/16 |
| -rpcallowip=* (dangerous!) | -rpcallowip=::/0 (still dangerous!) |
Using wildcards will result in the rule being rejected with the following error in debug.log:
 Error: Invalid -rpcallowip subnet specification: *. Valid are a single IP (e.g. 1.2.3.4), a network/netmask (e.g. 1.2.3.4/255.255.255.0) or a network/CIDR (e.g. 1.2.3.4/24). 
REST interface
A new HTTP API is exposed when running with the -rest flag, which allows
unauthenticated access to public node data.
It is served on the same port as RPC, but does not need a password, and uses
plain HTTP instead of JSON-RPC.
Assuming a local RPC server running on port 8332, it is possible to request:
In every case, EXT can be bin (for raw binary data), hex (for hex-encoded
binary) or json.
For more details, see the doc/REST-interface.md document in the repository.
RPC Server "Warm-Up" Mode
The RPC server is started earlier now, before most of the expensive
intialisations like loading the block index. It is available now almost
immediately after starting the process. However, until all initialisations
are done, it always returns an immediate error with code -28 to all calls.
This new behaviour can be useful for clients to know that a server is already
started and will be available soon (for instance, so that they do not
have to start it themselves).
Improved signing security
For 0.10 the security of signing against unusual attacks has been
improved by making the signatures constant time and deterministic.
This change is a result of switching signing to use libsecp256k1
instead of OpenSSL. Libsecp256k1 is a cryptographic library
optimized for the curve Bitcoin uses which was created by Bitcoin
Core developer Pieter Wuille.
There exist attacks[1] against most ECC implementations where an
attacker on shared virtual machine hardware could extract a private
key if they could cause a target to sign using the same key hundreds
of times. While using shared hosts and reusing keys are inadvisable
for other reasons, it's a better practice to avoid the exposure.
OpenSSL has code in their source repository for derandomization
and reduction in timing leaks that we've eagerly wanted to use for a
long time, but this functionality has still not made its
way into a released version of OpenSSL. Libsecp256k1 achieves
significantly stronger protection: As far as we're aware this is
the only deployed implementation of constant time signing for
the curve Bitcoin uses and we have reason to believe that
libsecp256k1 is better tested and more thoroughly reviewed
than the implementation in OpenSSL.
[1] https://eprint.iacr.org/2014/161.pdf
Watch-only wallet support
The wallet can now track transactions to and from wallets for which you know
all addresses (or scripts), even without the private keys.
This can be used to track payments without needing the private keys online on a
possibly vulnerable system. In addition, it can help for (manual) construction
of multisig transactions where you are only one of the signers.
One new RPC, importaddress, is added which functions similarly to
importprivkey, but instead takes an address or script (in hexadecimal) as
argument. After using it, outputs credited to this address or script are
considered to be received, and transactions consuming these outputs will be
considered to be sent.
The following RPCs have optional support for watch-only:
getbalance, listreceivedbyaddress, listreceivedbyaccount,
listtransactions, listaccounts, listsinceblock, gettransaction. See the
RPC documentation for those methods for more information.
Compared to using getrawtransaction, this mechanism does not require
-txindex, scales better, integrates better with the wallet, and is compatible
with future block chain pruning functionality. It does mean that all relevant
addresses need to added to the wallet before the payment, though.
Consensus library
Starting from 0.10.0, the Bitcoin Core distribution includes a consensus library.
The purpose of this library is to make the verification functionality that is
critical to Bitcoin's consensus available to other applications, e.g. to language
bindings such as [python-bitcoinlib](https://pypi.python.org/pypi/python-bitcoinlib) or
alternative node implementations.
This library is called libbitcoinconsensus.so (or, .dll for Windows).
Its interface is defined in the C header [bitcoinconsensus.h](https://github.com/bitcoin/bitcoin/blob/0.10/src/script/bitcoinconsensus.h).
In its initial version the API includes two functions:
  • bitcoinconsensus_verify_script verifies a script. It returns whether the indicated input of the provided serialized transaction
correctly spends the passed scriptPubKey under additional constraints indicated by flags
  • bitcoinconsensus_version returns the API version, currently at an experimental 0
The functionality is planned to be extended to e.g. UTXO management in upcoming releases, but the interface
for existing methods should remain stable.
Standard script rules relaxed for P2SH addresses
The IsStandard() rules have been almost completely removed for P2SH
redemption scripts, allowing applications to make use of any valid
script type, such as "n-of-m OR y", hash-locked oracle addresses, etc.
While the Bitcoin protocol has always supported these types of script,
actually using them on mainnet has been previously inconvenient as
standard Bitcoin Core nodes wouldn't relay them to miners, nor would
most miners include them in blocks they mined.
bitcoin-tx
It has been observed that many of the RPC functions offered by bitcoind are
"pure functions", and operate independently of the bitcoind wallet. This
included many of the RPC "raw transaction" API functions, such as
createrawtransaction.
bitcoin-tx is a newly introduced command line utility designed to enable easy
manipulation of bitcoin transactions. A summary of its operation may be
obtained via "bitcoin-tx --help" Transactions may be created or signed in a
manner similar to the RPC raw tx API. Transactions may be updated, deleting
inputs or outputs, or appending new inputs and outputs. Custom scripts may be
easily composed using a simple text notation, borrowed from the bitcoin test
suite.
This tool may be used for experimenting with new transaction types, signing
multi-party transactions, and many other uses. Long term, the goal is to
deprecate and remove "pure function" RPC API calls, as those do not require a
server round-trip to execute.
Other utilities "bitcoin-key" and "bitcoin-script" have been proposed, making
key and script operations easily accessible via command line.
Mining and relay policy enhancements
Bitcoin Core's block templates are now for version 3 blocks only, and any mining
software relying on its getblocktemplate must be updated in parallel to use
libblkmaker either version 0.4.2 or any version from 0.5.1 onward.
If you are solo mining, this will affect you the moment you upgrade Bitcoin
Core, which must be done prior to BIP66 achieving its 951/1001 status.
If you are mining with the stratum mining protocol: this does not affect you.
If you are mining with the getblocktemplate protocol to a pool: this will affect
you at the pool operator's discretion, which must be no later than BIP66
achieving its 951/1001 status.
The prioritisetransaction RPC method has been added to enable miners to
manipulate the priority of transactions on an individual basis.
Bitcoin Core now supports BIP 22 long polling, so mining software can be
notified immediately of new templates rather than having to poll periodically.
Support for BIP 23 block proposals is now available in Bitcoin Core's
getblocktemplate method. This enables miners to check the basic validity of
their next block before expending work on it, reducing risks of accidental
hardforks or mining invalid blocks.
Two new options to control mining policy:
  • -datacarrier=0/1 : Relay and mine "data carrier" (OP_RETURN) transactions
if this is 1.
  • -datacarriersize=n : Maximum size, in bytes, we consider acceptable for
"data carrier" outputs.
The relay policy has changed to more properly implement the desired behavior of not
relaying free (or very low fee) transactions unless they have a priority above the
AllowFreeThreshold(), in which case they are relayed subject to the rate limiter.
BIP 66: strict DER encoding for signatures
Bitcoin Core 0.10 implements BIP 66, which introduces block version 3, and a new
consensus rule, which prohibits non-DER signatures. Such transactions have been
non-standard since Bitcoin v0.8.0 (released in February 2013), but were
technically still permitted inside blocks.
This change breaks the dependency on OpenSSL's signature parsing, and is
required if implementations would want to remove all of OpenSSL from the
consensus code.
The same miner-voting mechanism as in BIP 34 is used: when 751 out of a
sequence of 1001 blocks have version number 3 or higher, the new consensus
rule becomes active for those blocks. When 951 out of a sequence of 1001
blocks have version number 3 or higher, it becomes mandatory for all blocks.
Backward compatibility with current mining software is NOT provided, thus miners
should read the first paragraph of "Mining and relay policy enhancements" above.
0.10.0 Change log

Detailed release notes follow. This overview includes changes that affect external
behavior, not code moves, refactors or string updates.
RPC:
  • f923c07 Support IPv6 lookup in bitcoin-cli even when IPv6 only bound on localhost
  • b641c9c Fix addnode "onetry": Connect with OpenNetworkConnection
  • 171ca77 estimatefee / estimatepriority RPC methods
  • b750cf1 Remove cli functionality from bitcoind
  • f6984e8 Add "chain" to getmininginfo, improve help in getblockchaininfo
  • 99ddc6c Add nLocalServices info to RPC getinfo
  • cf0c47b Remove getwork() RPC call
  • 2a72d45 prioritisetransaction
  • e44fea5 Add an option -datacarrier to allow users to disable relaying/mining data carrier transactions
  • 2ec5a3d Prevent easy RPC memory exhaustion attack
  • d4640d7 Added argument to getbalance to include watchonly addresses and fixed errors in balance calculation
  • 83f3543 Added argument to listaccounts to include watchonly addresses
  • 952877e Showing 'involvesWatchonly' property for transactions returned by 'listtransactions' and 'listsinceblock'. It is only appended when the transaction involves a watchonly address
  • d7d5d23 Added argument to listtransactions and listsinceblock to include watchonly addresses
  • f87ba3d added includeWatchonly argument to 'gettransaction' because it affects balance calculation
  • 0fa2f88 added includedWatchonly argument to listreceivedbyaddress/...account
  • 6c37f7f getrawchangeaddress: fail when keypool exhausted and wallet locked
  • ff6a7af getblocktemplate: longpolling support
  • c4a321f Add peerid to getpeerinfo to allow correlation with the logs
  • 1b4568c Add vout to ListTransactions output
  • b33bd7a Implement "getchaintips" RPC command to monitor blockchain forks
  • 733177e Remove size limit in RPC client, keep it in server
  • 6b5b7cb Categorize rpc help overview
  • 6f2c26a Closely track mempool byte total. Add "getmempoolinfo" RPC
  • aa82795 Add detailed network info to getnetworkinfo RPC
  • 01094bd Don't reveal whether password is <20 or >20 characters in RPC
  • 57153d4 rpc: Compute number of confirmations of a block from block height
  • ff36cbe getnetworkinfo: export local node's client sub-version string
  • d14d7de SanitizeString: allow '(' and ')'
  • 31d6390 Fixed setaccount accepting foreign address
  • b5ec5fe update getnetworkinfo help with subversion
  • ad6e601 RPC additions after headers-first
  • 33dfbf5 rpc: Fix leveldb iterator leak, and flush before gettxoutsetinfo
  • 2aa6329 Enable customising node policy for datacarrier data size with a -datacarriersize option
  • f877aaa submitblock: Use a temporary CValidationState to determine accurately the outcome of ProcessBlock
  • e69a587 submitblock: Support for returning specific rejection reasons
  • af82884 Add "warmup mode" for RPC server
  • e2655e0 Add unauthenticated HTTP REST interface to public blockchain data
  • 683dc40 Disable SSLv3 (in favor of TLS) for the RPC client and server
  • 44b4c0d signrawtransaction: validate private key
  • 9765a50 Implement BIP 23 Block Proposal
  • f9de17e Add warning comment to getinfo
Command-line options:
  • ee21912 Use netmasks instead of wildcards for IP address matching
  • deb3572 Add -rpcbind option to allow binding RPC port on a specific interface
  • 96b733e Add -version option to get just the version
  • 1569353 Add -stopafterblockimport option
  • 77cbd46 Let -zapwallettxes recover transaction meta data
  • 1c750db remove -tor compatibility code (only allow -onion)
  • 4aaa017 rework help messages for fee-related options
  • 4278b1d Clarify error message when invalid -rpcallowip
  • 6b407e4 -datadir is now allowed in config files
  • bdd5b58 Add option -sysperms to disable 077 umask (create new files with system default umask)
  • cbe39a3 Add "bitcoin-tx" command line utility and supporting modules
  • dbca89b Trigger -alertnotify if network is upgrading without you
  • ad96e7c Make -reindex cope with out-of-order blocks
  • 16d5194 Skip reindexed blocks individually
  • ec01243 --tracerpc option for regression tests
  • f654f00 Change -genproclimit default to 1
  • 3c77714 Make -proxy set all network types, avoiding a connect leak
  • 57be955 Remove -printblock, -printblocktree, and -printblockindex
  • ad3d208 remove -maxorphanblocks config parameter since it is no longer functional
Block and transaction handling:
  • 7a0e84d ProcessGetData(): abort if a block file is missing from disk
  • 8c93bf4 LoadBlockIndexDB(): Require block db reindex if any blk*.dat files are missing
  • 77339e5 Get rid of the static chainMostWork (optimization)
  • 4e0eed8 Allow ActivateBestChain to release its lock on cs_main
  • 18e7216 Push cs_mains down in ProcessBlock
  • fa126ef Avoid undefined behavior using CFlatData in CScript serialization
  • 7f3b4e9 Relax IsStandard rules for pay-to-script-hash transactions
  • c9a0918 Add a skiplist to the CBlockIndex structure
  • bc42503 Use unordered_map for CCoinsViewCache with salted hash (optimization)
  • d4d3fbd Do not flush the cache after every block outside of IBD (optimization)
  • ad08d0b Bugfix: make CCoinsViewMemPool support pruned entries in underlying cache
  • 5734d4d Only remove actualy failed blocks from setBlockIndexValid
  • d70bc52 Rework block processing benchmark code
  • 714a3e6 Only keep setBlockIndexValid entries that are possible improvements
  • ea100c7 Reduce maximum coinscache size during verification (reduce memory usage)
  • 4fad8e6 Reject transactions with excessive numbers of sigops
  • b0875eb Allow BatchWrite to destroy its input, reducing copying (optimization)
  • 92bb6f2 Bypass reloading blocks from disk (optimization)
  • 2e28031 Perform CVerifyDB on pcoinsdbview instead of pcoinsTip (reduce memory usage)
  • ab15b2e Avoid copying undo data (optimization)
  • 341735e Headers-first synchronization
  • afc32c5 Fix rebuild-chainstate feature and improve its performance
  • e11b2ce Fix large reorgs
  • ed6d1a2 Keep information about all block files in memory
  • a48f2d6 Abstract context-dependent block checking from acceptance
  • 7e615f5 Fixed mempool sync after sending a transaction
  • 51ce901 Improve chainstate/blockindex disk writing policy
  • a206950 Introduce separate flushing modes
  • 9ec75c5 Add a locking mechanism to IsInitialBlockDownload to ensure it never goes from false to true
  • 868d041 Remove coinbase-dependant transactions during reorg
  • 723d12c Remove txn which are invalidated by coinbase maturity during reorg
  • 0cb8763 Check against MANDATORY flags prior to accepting to mempool
  • 8446262 Reject headers that build on an invalid parent
  • 008138c Bugfix: only track UTXO modification after lookup
P2P protocol and network code:
  • f80cffa Do not trigger a DoS ban if SCRIPT_VERIFY_NULLDUMMY fails
  • c30329a Add testnet DNS seed of Alex Kotenko
  • 45a4baf Add testnet DNS seed of Andreas Schildbach
  • f1920e8 Ping automatically every 2 minutes (unconditionally)
  • 806fd19 Allocate receive buffers in on the fly
  • 6ecf3ed Display unknown commands received
  • aa81564 Track peers' available blocks
  • caf6150 Use async name resolving to improve net thread responsiveness
  • 9f4da19 Use pong receive time rather than processing time
  • 0127a9b remove SOCKS4 support from core and GUI, use SOCKS5
  • 40f5cb8 Send rejects and apply DoS scoring for errors in direct block validation
  • dc942e6 Introduce whitelisted peers
  • c994d2e prevent SOCKET leak in BindListenPort()
  • a60120e Add built-in seeds for .onion
  • 60dc8e4 Allow -onlynet=onion to be used
  • 3a56de7 addrman: Do not propagate obviously poor addresses onto the network
  • 6050ab6 netbase: Make SOCKS5 negotiation interruptible
  • 604ee2a Remove tx from AlreadyAskedFor list once we receive it, not when we process it
  • efad808 Avoid reject message feedback loops
  • 71697f9 Separate protocol versioning from clientversion
  • 20a5f61 Don't relay alerts to peers before version negotiation
  • b4ee0bd Introduce preferred download peers
  • 845c86d Do not use third party services for IP detection
  • 12a49ca Limit the number of new addressses to accumulate
  • 35e408f Regard connection failures as attempt for addrman
  • a3a7317 Introduce 10 minute block download timeout
  • 3022e7d Require sufficent priority for relay of free transactions
  • 58fda4d Update seed IPs, based on bitcoin.sipa.be crawler data
  • 18021d0 Remove bitnodes.io from dnsseeds.
Validation:
  • 6fd7ef2 Also switch the (unused) verification code to low-s instead of even-s
  • 584a358 Do merkle root and txid duplicates check simultaneously
  • 217a5c9 When transaction outputs exceed inputs, show the offending amounts so as to aid debugging
  • f74fc9b Print input index when signature validation fails, to aid debugging
  • 6fd59ee script.h: set_vch() should shift a >32 bit value
  • d752ba8 Add SCRIPT_VERIFY_SIGPUSHONLY (BIP62 rule 2) (test only)
  • 698c6ab Add SCRIPT_VERIFY_MINIMALDATA (BIP62 rules 3 and 4) (test only)
  • ab9edbd script: create sane error return codes for script validation and remove logging
  • 219a147 script: check ScriptError values in script tests
  • 0391423 Discourage NOPs reserved for soft-fork upgrades
  • 98b135f Make STRICTENC invalid pubkeys fail the script rather than the opcode
  • 307f7d4 Report script evaluation failures in log and reject messages
  • ace39db consensus: guard against openssl's new strict DER checks
  • 12b7c44 Improve robustness of DER recoding code
  • 76ce5c8 fail immediately on an empty signature
Build system:
  • f25e3ad Fix build in OS X 10.9
  • 65e8ba4 build: Switch to non-recursive make
  • 460b32d build: fix broken boost chrono check on some platforms
  • 9ce0774 build: Fix windows configure when using --with-qt-libdir
  • ea96475 build: Add mention of --disable-wallet to bdb48 error messages
  • 1dec09b depends: add shared dependency builder
  • c101c76 build: Add --with-utils (bitcoin-cli and bitcoin-tx, default=yes). Help string consistency tweaks. Target sanity check fix
  • e432a5f build: add option for reducing exports (v2)
  • 6134b43 Fixing condition 'sabotaging' MSVC build
  • af0bd5e osx: fix signing to make Gatekeeper happy (again)
  • a7d1f03 build: fix dynamic boost check when --with-boost= is used
  • d5fd094 build: fix qt test build when libprotobuf is in a non-standard path
  • 2cf5f16 Add libbitcoinconsensus library
  • 914868a build: add a deterministic dmg signer
  • 2d375fe depends: bump openssl to 1.0.1k
  • b7a4ecc Build: Only check for boost when building code that requires it
Wallet:
  • b33d1f5 Use fee/priority estimates in wallet CreateTransaction
  • 4b7b1bb Sanity checks for estimates
  • c898846 Add support for watch-only addresses
  • d5087d1 Use script matching rather than destination matching for watch-only
  • d88af56 Fee fixes
  • a35b55b Dont run full check every time we decrypt wallet
  • 3a7c348 Fix make_change to not create half-satoshis
  • f606bb9 fix a possible memory leak in CWalletDB::Recover
  • 870da77 fix possible memory leaks in CWallet::EncryptWallet
  • ccca27a Watch-only fixes
  • 9b1627d [Wallet] Reduce minTxFee for transaction creation to 1000 satoshis
  • a53fd41 Deterministic signing
  • 15ad0b5 Apply AreSane() checks to the fees from the network
  • 11855c1 Enforce minRelayTxFee on wallet created tx and add a maxtxfee option
GUI:
  • c21c74b osx: Fix missing dock menu with qt5
  • b90711c Fix Transaction details shows wrong To:
  • 516053c Make links in 'About Bitcoin Core' clickable
  • bdc83e8 Ensure payment request network matches client network
  • 65f78a1 Add GUI view of peer information
  • 06a91d9 VerifyDB progress reporting
  • fe6bff2 Add BerkeleyDB version info to RPCConsole
  • b917555 PeerTableModel: Fix potential deadlock. #4296
  • dff0e3b Improve rpc console history behavior
  • 95a9383 Remove CENT-fee-rule from coin control completely
  • 56b07d2 Allow setting listen via GUI
  • d95ba75 Log messages with type>QtDebugMsg as non-debug
  • 8969828 New status bar Unit Display Control and related changes
  • 674c070 seed OpenSSL PNRG with Windows event data
  • 509f926 Payment request parsing on startup now only changes network if a valid network name is specified
  • acd432b Prevent balloon-spam after rescan
  • 7007402 Implement SI-style (thin space) thoudands separator
  • 91cce17 Use fixed-point arithmetic in amount spinbox
  • bdba2dd Remove an obscure option no-one cares about
  • bd0aa10 Replace the temporary file hack currently used to change Bitcoin-Qt's dock icon (OS X) with a buffer-based solution
  • 94e1b9e Re-work overviewpage UI
  • 8bfdc9a Better looking trayicon
  • b197bf3 disable tray interactions when client model set to 0
  • 1c5f0af Add column Watch-only to transactions list
  • 21f139b Fix tablet crash. closes #4854
  • e84843c Broken addresses on command line no longer trigger testnet
  • a49f11d Change splash screen to normal window
  • 1f9be98 Disable App Nap on OSX 10.9+
  • 27c3e91 Add proxy to options overridden if necessary
  • 4bd1185 Allow "emergency" shutdown during startup
  • d52f072 Don't show wallet options in the preferences menu when running with -disablewallet
  • 6093aa1 Qt: QProgressBar CPU-Issue workaround
  • 0ed9675 [Wallet] Add global boolean whether to send free transactions (default=true)
  • ed3e5e4 [Wallet] Add global boolean whether to pay at least the custom fee (default=true)
  • e7876b2 [Wallet] Prevent user from paying a non-sense fee
  • c1c9d5b Add Smartfee to GUI
  • e0a25c5 Make askpassphrase dialog behave more sanely
  • 94b362d On close of splashscreen interrupt verifyDB
  • b790d13 English translation update
  • 8543b0d Correct tooltip on address book page
Tests:
  • b41e594 Fix script test handling of empty scripts
  • d3a33fc Test CHECKMULTISIG with m == 0 and n == 0
  • 29c1749 Let tx (in)valid tests use any SCRIPT_VERIFY flag
  • 6380180 Add rejection of non-null CHECKMULTISIG dummy values
  • 21bf3d2 Add tests for BoostAsioToCNetAddr
  • b5ad5e7 Add Python test for -rpcbind and -rpcallowip
  • 9ec0306 Add CODESEPARATOFindAndDelete() tests
  • 75ebced Added many rpc wallet tests
  • 0193fb8 Allow multiple regression tests to run at once
  • 92a6220 Hook up sanity checks
  • 3820e01 Extend and move all crypto tests to crypto_tests.cpp
  • 3f9a019 added list/get received by address/ account tests
  • a90689f Remove timing-based signature cache unit test
  • 236982c Add skiplist unit tests
  • f4b00be Add CChain::GetLocator() unit test
  • b45a6e8 Add test for getblocktemplate longpolling
  • cdf305e Set -discover=0 in regtest framework
  • ed02282 additional test for OP_SIZE in script_valid.json
  • 0072d98 script tests: BOOLAND, BOOLOR decode to integer
  • 833ff16 script tests: values that overflow to 0 are true
  • 4cac5db script tests: value with trailing 0x00 is true
  • 89101c6 script test: test case for 5-byte bools
  • d2d9dc0 script tests: add tests for CHECKMULTISIG limits
  • d789386 Add "it works" test for bitcoin-tx
  • df4d61e Add bitcoin-tx tests
  • aa41ac2 Test IsPushOnly() with invalid push
  • 6022b5d Make script_{valid,invalid}.json validation flags configurable
  • 8138cbe Add automatic script test generation, and actual checksig tests
  • ed27e53 Add coins_tests with a large randomized CCoinViewCache test
  • 9df9cf5 Make SCRIPT_VERIFY_STRICTENC compatible with BIP62
  • dcb9846 Extend getchaintips RPC test
  • 554147a Ensure MINIMALDATA invalid tests can only fail one way
  • dfeec18 Test every numeric-accepting opcode for correct handling of the numeric minimal encoding rule
  • 2b62e17 Clearly separate PUSHDATA and numeric argument MINIMALDATA tests
  • 16d78bd Add valid invert of invalid every numeric opcode tests
  • f635269 tests: enable alertnotify test for Windows
  • 7a41614 tests: allow rpc-tests to get filenames for bitcoind and bitcoin-cli from the environment
  • 5122ea7 tests: fix forknotify.py on windows
  • fa7f8cd tests: remove old pull-tester scripts
  • 7667850 tests: replace the old (unused since Travis) tests with new rpc test scripts
  • f4e0aef Do signature-s negation inside the tests
  • 1837987 Optimize -regtest setgenerate block generation
  • 2db4c8a Fix node ranges in the test framework
  • a8b2ce5 regression test only setmocktime RPC call
  • daf03e7 RPC tests: create initial chain with specific timestamps
  • 8656dbb Port/fix txnmall.sh regression test
  • ca81587 Test the exact order of CHECKMULTISIG sig/pubkey evaluation
  • 7357893 Prioritize and display -testsafemode status in UI
  • f321d6b Add key generation/verification to ECC sanity check
  • 132ea9b miner_tests: Disable checkpoints so they don't fail the subsidy-change test
  • bc6cb41 QA RPC tests: Add tests block block proposals
  • f67a9ce Use deterministically generated script tests
  • 11d7a7d [RPC] add rpc-test for http keep-alive (persistent connections)
  • 34318d7 RPC-test based on invalidateblock for mempool coinbase spends
  • 76ec867 Use actually valid transactions for script tests
  • c8589bf Add actual signature tests
  • e2677d7 Fix smartfees test for change to relay policy
  • 263b65e tests: run sanity checks in tests too
Miscellaneous:
  • 122549f Fix incorrect checkpoint data for testnet3
  • 5bd02cf Log used config file to debug.log on startup
  • 68ba85f Updated Debian example bitcoin.conf with config from wiki + removed some cruft and updated comments
  • e5ee8f0 Remove -beta suffix
  • 38405ac Add comment regarding experimental-use service bits
  • be873f6 Issue warning if collecting RandSeed data failed
  • 8ae973c Allocate more space if necessary in RandSeedAddPerfMon
  • 675bcd5 Correct comment for 15-of-15 p2sh script size
  • fda3fed libsecp256k1 integration
  • 2e36866 Show nodeid instead of addresses in log (for anonymity) unless otherwise requested
  • cd01a5e Enable paranoid corruption checks in LevelDB >= 1.16
  • 9365937 Add comment about never updating nTimeOffset past 199 samples
  • 403c1bf contrib: remove getwork-based pyminer (as getwork API call has been removed)
  • 0c3e101 contrib: Added systemd .service file in order to help distributions integrate bitcoind
  • 0a0878d doc: Add new DNSseed policy
  • 2887bff Update coding style and add .clang-format
  • 5cbda4f Changed LevelDB cursors to use scoped pointers to ensure destruction when going out of scope
  • b4a72a7 contrib/linearize: split output files based on new-timestamp-year or max-file-size
  • e982b57 Use explicit fflush() instead of setvbuf()
  • 234bfbf contrib: Add init scripts and docs for Upstart and OpenRC
  • 01c2807 Add warning about the merkle-tree algorithm duplicate txid flaw
  • d6712db Also create pid file in non-daemon mode
  • 772ab0e contrib: use batched JSON-RPC in linarize-hashes (optimization)
  • 7ab4358 Update bash-completion for v0.10
  • 6e6a36c contrib: show pull # in prompt for github-merge script
  • 5b9f842 Upgrade leveldb to 1.18, make chainstate databases compatible between ARM and x86 (issue #2293)
  • 4e7c219 Catch UTXO set read errors and shutdown
  • 867c600 Catch LevelDB errors during flush
  • 06ca065 Fix CScriptID(const CScript& in) in empty script case
Credits

Thanks to everyone who contributed to this release:
  • 21E14
  • Adam Weiss
  • Aitor Pazos
  • Alexander Jeng
  • Alex Morcos
  • Alon Muroch
  • Andreas Schildbach
  • Andrew Poelstra
  • Andy Alness
  • Ashley Holman
  • Benedict Chan
  • Ben Holden-Crowther
  • Bryan Bishop
  • BtcDrak
  • Christian von Roques
  • Clinton Christian
  • Cory Fields
  • Cozz Lovan
  • daniel
  • Daniel Kraft
  • David Hill
  • Derek701
  • dexX7
  • dllud
  • Dominyk Tiller
  • Doug
  • elichai
  • elkingtowa
  • ENikS
  • Eric Shaw
  • Federico Bond
  • Francis GASCHET
  • Gavin Andresen
  • Giuseppe Mazzotta
  • Glenn Willen
  • Gregory Maxwell
  • gubatron
  • HarryWu
  • himynameismartin
  • Huang Le
  • Ian Carroll
  • imharrywu
  • Jameson Lopp
  • Janusz Lenar
  • JaSK
  • Jeff Garzik
  • JL2035
  • Johnathan Corgan
  • Jonas Schnelli
  • jtimon
  • Julian Haight
  • Kamil Domanski
  • kazcw
  • kevin
  • kiwigb
  • Kosta Zertsekel
  • LongShao007
  • Luke Dashjr
  • Mark Friedenbach
  • Mathy Vanvoorden
  • Matt Corallo
  • Matthew Bogosian
  • Micha
  • Michael Ford
  • Mike Hearn
  • mrbandrews
  • mruddy
  • ntrgn
  • Otto Allmendinger
  • paveljanik
  • Pavel Vasin
  • Peter Todd
  • phantomcircuit
  • Philip Kaufmann
  • Pieter Wuille
  • pryds
  • randy-waterhouse
  • R E Broadley
  • Rose Toomey
  • Ross Nicoll
  • Roy Badami
  • Ruben Dario Ponticelli
  • Rune K. Svendsen
  • Ryan X. Charles
  • Saivann
  • sandakersmann
  • SergioDemianLerner
  • shshshsh
  • sinetek
  • Stuart Cardall
  • Suhas Daftuar
  • Tawanda Kembo
  • Teran McKinney
  • tm314159
  • Tom Harding
  • Trevin Hofmann
  • Whit J
  • Wladimir J. van der Laan
  • Yoichi Hirai
  • Zak Wilcox
As well as everyone that helped translating on [Transifex](https://www.transifex.com/projects/p/bitcoin/).
Also lots of thanks to the bitcoin.org website team David A. Harding and Saivann Carignan.
Wladimir
original: http://lists.linuxfoundation.org/pipermail/bitcoin-dev/2015-February/007480.html
submitted by bitcoin-devlist-bot to bitcoin_devlist [link] [comments]

Install Debian Linux: Download and Install Debian on Your ... 4. Installing Bitcoin Core on Linux install bitcoin full node on debian How to Install Debian Linux on VirtualBox - YouTube How to install and run a 64 bit package on 32 bit on ...

How To Install Bitcoin-node On Debian 9 Stretch Linux. How to Install Bitcoin-node on Debian 9 Stretch Linux The objective is to install latest Bitcoin-node binaries on Debian 9 Stretch Linux. Privileged access to your Debian system will be required. # - requires given command to be executed with root privileges either directly as a root user or by use of sudo command $ - given command to be ... So, most of them are not included on open source operating systems like Debian. As these codecs are not included, you can’t play every type of audio and video files once you install a fresh copy of Debian. In this article, I am going to show you how to install multimedia codecs on Debian 10 Buster. So, let’s get started. Install Bitcoin Node To install Bitcoin node first extract the Bitcoin tarball: $ tar xzf bitcoin-0.14.1-x86_64-linux-gnu.tar.gz Next, run install command to install Bitcoin binaries: # install -m 0755 -o root -g root -t /usr/local/bin bitcoin-0.14.1/bin/* Start Bitcoin Daemon Lastly, start Bitcoin daemon: $ bitcoind -daemon Bitcoin server ... We are going to run a Bitcoin full node in a Debian system (Sid) ... $ tar xvzf bitcoin-0.14.2-x86_64-linux-gnu.tar.gz Install the binaries in /usr/local/bin directory $ sudo install -m 0755 -o root -g root -t /usr/local/bin bitcoin-0.14.2/bin/* Run Bitcoin node By now we are going to run only Bitcoin node with no graphical interface: I create a new user to run the Bitcoin node $ sudo adduser ... bitcoin wallet debian,We gather this here crypto Today Bitcoin – Bitcoin Core integration Ubuntu & Debian When the intention is to run only a P2P node without a wallet, bitcoin may be compiled in disable-wallet Minera is a complete web frontend to manage and monitor Bitcoin/Altcoins mining devices like Gridseed, Zeus Miner, Rockminer, Antminer, etc In one of our previous articles we’ve ...

[index] [35375] [37096] [28908] [23313] [23552] [30482] [39024] [22351] [35496] [6530]

Install Debian Linux: Download and Install Debian on Your ...

Wondering how to install Debian Linux on your computer? In this video I show how to setup the Debian Linux Distro on any computer. debian.org rufus.akeo.ie T... The VirtualBox Guest Additions version for Debian 9 is, as root: click link - http://www.codebind.com/linux-tutorials/install-virtualbox-guest-additions-debi... Java Project Tutorial - Make Login and Register Form Step by Step Using NetBeans And MySQL Database - Duration: 3:43:32. 1BestCsharp blog 7,662,402 views sudo add-apt-repository ppa:bitcoin/bitcoin sudo apt-get update sudo apt-get install bitcoin-qt bitcoind Linux terminal new stuff: clear, ll, cd, touch, echo, cat, shutdown www.bitcoinhackers.org Install and run 64-bit packages on a 32-bit system. Debian based. Commands: sudo dpkg --add-architecture i386 sudo apt-get update sudo apt-get install packag...

#