Running A Full Node - Bitcoin

BCH Unlimited Ubuntu PPA repo updated to version 1.9.0

The BCH Unlimited Ubuntu PPA repository has been updated to serve version 1.9.0 is available at:
 
https://launchpad.net/~bitcoin-unlimited/+archive/ubuntu/bucash
 
This release is compatible the Bitcoin Cash protocol. To update already installed packages:
 
sudo apt update sudo apt upgrade 
 
To install
 
sudo add-apt-repository ppa:bitcoin-unlimited/bucash sudo apt-get update sudo apt install bitcoind bitcoin-qt 
 
starting from this update the repository is serving also ElectrsCash(**) v2.0.0, for now just for the amd64 architecture. To install it just execute this command:
sudo apt install electrscash 
 
See the official announcement and the release notes for more details:
https://old.reddit.com/btc/comments/ih2eyt/bch_unlimited_190_has_just_been_released/
https://github.com/BitcoinUnlimited/BitcoinUnlimited/blob/release/doc/release-notes/release-notes-1.9.0.md
 
Known issues:
On Ubuntu 18.04 (bionic) you'll probably get an error while trying to install bitcoind. The error message is the following:
The following packages have unmet dependencies. bitcoind : Depends: libgcc-s1 (>= 3.4) but it is not installable E: Unable to correct problems, you have held broken packages. Package libgcc-s1 is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source 
To solve the problem please do:
sudo add-apt-repository ppa:ubuntu-toolchain-test sudo apt update sudo apt dist-upgrade sudo apt install bitcoind 
 
(**) ElectrsCash is an efficient re-implementation of Electrum Server written in Rust.
submitted by s1ckpig to btc [link] [comments]

What is the stable version?

I just compiled bitcoin cash from source, version 0.21.11, and it when I do getblockchaininfo I get the warning:
"warnings": "This is a pre-release test build - use at your own risk - do not use for mining or merchant applications"
So I tried with 0.21.10, 0.21.9, and even 0.21.8. They all give the same warning!
Here's what I did (on Ubuntu 20.04):
apt-get update
apt-get upgrade -y
apt-get install libboost-system-dev libboost-filesystem-dev libboost-chrono-dev libboost-test-dev libboost-thread-dev git bsdmainutils build-essential libssl-dev libevent-dev ninja-build python3 cmake libjemalloc-dev libminiupnpc-dev libdb-dev libdb++-dev libzmq3-dev -y
git clone https://github.com/Bitcoin-ABC/bitcoin-abc --branch v0.21.11 --single-branch
(cd bitcoin-abc && mkdir build && cd build && cmake -GNinja -DBUILD_BITCOIN_QT=OFF .. && ninja && strip src/bitcoind && strip src/bitcoin-cli && strip src/bitcoin-tx && ninja install)
What am I doing wrong? I am planning on mining so I am concerned by this warning.
submitted by bithire to Bitcoincash [link] [comments]

BCH Unlimited Ubuntu PPA repo updated to version 1.9.0

The BCH Unlimited Ubuntu PPA repository has been updated to serve version 1.9.0 is available at:
 
https://launchpad.net/~bitcoin-unlimited/+archive/ubuntu/bucash
 
This release is compatible the Bitcoin Cash protocol. To update already installed packages:
 
sudo apt update sudo apt upgrade 
 
To install
 
sudo add-apt-repository ppa:bitcoin-unlimited/bucash sudo apt-get update sudo apt install bitcoind bitcoin-qt 
 
starting from this update the repository is serving also ElectrsCash(**) v2.0.0, for now just for the amd64 architecture. To install it just execute this command:
sudo apt install electrscash 
 
See the official announcement and the release notes for more details:
https://old.reddit.com/btc/comments/ih2eyt/bch_unlimited_190_has_just_been_released/
https://github.com/BitcoinUnlimited/BitcoinUnlimited/blob/release/doc/release-notes/release-notes-1.9.0.md
 
Known issues:
On Ubuntu 18.04 (bionic) you'll probably get an error while trying to install bitcoind. The error message is the following:
The following packages have unmet dependencies. bitcoind : Depends: libgcc-s1 (>= 3.4) but it is not installable E: Unable to correct problems, you have held broken packages. Package libgcc-s1 is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source 
To solve the problem please do:
sudo add-apt-repository ppa:ubuntu-toolchain-test sudo apt update sudo apt dist-upgrade sudo apt install bitcoind 
 
(**) ElectrsCash is an efficient re-implementation of Electrum Server written in Rust.
submitted by s1ckpig to Bitcoincash [link] [comments]

BCH Unlimited Ubuntu PPA repo updated to version 1.8.0

The BCH Unlimited Ubuntu PPA repository has been updated to serve version 1.8.0 is available at:
 
https://launchpad.net/~bitcoin-unlimited/+archive/ubuntu/bucash
 
This release is compatible the Bitcoin Cash protocol. To update already installed packages (*):
 
sudo apt update sudo apt upgrade 
 
To install
 
sudo add-apt-repository ppa:bitcoin-unlimited/bucash sudo apt-get update sudo apt install bitcoind bitcoin-qt 
 
starting from this update the repository is serving also ElectrsCash(**) v.1.1.1, for now just for the amd64 architecture. To install it just execute this command:
sudo apt install electrscash 
 
See the official announcement and the release notes for more details:
https://np.reddit.com/btc/comments/g3k4mbch_unlimited_180_has_just_been_released/
https://github.com/BitcoinUnlimited/BitcoinUnlimited/blob/release/doc/release-notes/release-notes-1.8.0.md
 
Known issues:
On Ubuntu 18.04 (bionic) you'll probably get an error while trying to install bitcoind. The error message is the following:
The following packages have unmet dependencies. bitcoind : Depends: libgcc-s1 (>= 3.4) but it is not installable E: Unable to correct problems, you have held broken packages. Package libgcc-s1 is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source 
It seems like libgcc-s1 which is a focal (ubuntu 20.04, still in beta) package that has somehow crept in the bionic "food-chain", I'm working on a fix right now. Thanks to xd1gital for the initial report.
Edit: to solve the problem please do:
sudo add-apt-repository ppa:ubuntu-toolchain-test sudo apt update sudo apt dist-upgrade sudo apt install bitcoind 
 
(*) due to fact we rebranded Ubuntua PPA name along with the name of the clients, you will be displayed with this warning and question to which you could safely reply "Yes":
E: Repository 'http://ppa.launchpad.net/bitcoin-unlimited/bucash/ubuntu bionic InRelease' changed its 'Label' value from 'BU Cash' to 'BCH Unlimited' N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details. Do you want to accept these changes and continue updating from this repository? [y/N] 
  (**) ElectrsCash is an efficient re-implementation of Electrum Server written in Rust.
submitted by s1ckpig to bitcoin_unlimited [link] [comments]

BCH Unlimited Ubuntu PPA repo updated to version 1.8.0

The BCH Unlimited Ubuntu PPA repository has been updated to serve version 1.8.0 is available at:
 
https://launchpad.net/~bitcoin-unlimited/+archive/ubuntu/bucash
 
This release is compatible the Bitcoin Cash protocol. To update already installed packages (*):
 
sudo apt update sudo apt upgrade 
 
To install
 
sudo add-apt-repository ppa:bitcoin-unlimited/bucash sudo apt-get update sudo apt install bitcoind bitcoin-qt 
 
starting from this update the repository is serving also ElectrsCash(**) v.1.1.1, for now just for the amd64 architecture. To install it just execute this command:
sudo apt install electrscash 
 
See the official announcement and the release notes for more details:
https://np.reddit.com/btc/comments/g3k4mbch_unlimited_180_has_just_been_released/
https://github.com/BitcoinUnlimited/BitcoinUnlimited/blob/release/doc/release-notes/release-notes-1.8.0.md
 
Known issues:
On Ubuntu 18.04 (bionic) you'll probably get an error while trying to install bitcoind. The error message is the following:
The following packages have unmet dependencies. bitcoind : Depends: libgcc-s1 (>= 3.4) but it is not installable E: Unable to correct problems, you have held broken packages. Package libgcc-s1 is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source 
It seems like libgcc-s1 which is a focal (ubuntu 20.04, still in beta) package that has somehow crept in the bionic "food-chain", I'm working on a fix right now. Thanks to xd1gital for the initial report.
Edit: to solve the problem please do:
sudo add-apt-repository ppa:ubuntu-toolchain-test sudo apt update sudo apt dist-upgrade sudo apt install bitcoind 
 
(*) due to fact we rebranded Ubuntua PPA name along with the name of the clients, you will be displayed with this warning and question to which you could safely reply "Yes":
E: Repository 'http://ppa.launchpad.net/bitcoin-unlimited/bucash/ubuntu bionic InRelease' changed its 'Label' value from 'BU Cash' to 'BCH Unlimited' N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details. Do you want to accept these changes and continue updating from this repository? [y/N] 
  (**) ElectrsCash is an efficient re-implementation of Electrum Server written in Rust.
submitted by s1ckpig to btc [link] [comments]

BCH Unlimited Ubuntu PPA repo updated to version 1.8.0

The BCH Unlimited Ubuntu PPA repository has been updated to serve version 1.8.0 is available at:

 

https://launchpad.net/~bitcoin-unlimited/+archive/ubuntu/bucash

 

This release is compatible the Bitcoin Cash protocol. To update already installed packages (*):

 

sudo apt update
sudo apt upgrade

 

To install

 

sudo add-apt-repository ppa:bitcoin-unlimited/bucash
sudo apt-get update
sudo apt install bitcoind bitcoin-qt

 

starting from this update the repository is serving also ElectrsCash(**) v.1.1.1, for now just for the `amd64` architecture. To install it just execute this command:

sudo apt install electrscash

 

See the official announcement and the release notes for more details:

https://np.reddit.com/btc/comments/g3k4mbch_unlimited_180_has_just_been_released/

https://github.com/BitcoinUnlimited/BitcoinUnlimited/blob/release/doc/release-notes/release-notes-1.8.0.md

 

Known issues:

On Ubuntu 18.04 (bionic) you'll probably get an error while trying to install `bitcoind`. The error message is the following:

The following packages have unmet dependencies.
bitcoind : Depends: libgcc-s1 (>= 3.4) but it is not installable
E: Unable to correct problems, you have held broken packages.

Package libgcc-s1 is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

It seems like [libgcc-s1](https://packages.ubuntu.com/focal/libgcc-s1) which is a focal (ubuntu 20.04, still in beta) package that has somehow crept in the bionic "food-chain", I'm working on a fix right now. Thanks to xd1gital for the initial report.

 

(*) due to fact we rebranded Ubuntua PPA name along with the name of the clients, you will be displayed with this warning and question to which you could safely reply "Yes":

E: Repository 'http://ppa.launchpad.net/bitcoin-unlimited/bucash/ubuntu bionic InRelease' changed its 'Label' value from 'BU Cash' to 'BCH Unlimited'
N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details.
Do you want to accept these changes and continue updating from this repository? [y/N]

 
(**) ElectrsCash is an efficient re-implementation of Electrum Server written in Rust.
submitted by s1ckpig to Bitcoincash [link] [comments]

BTCPay Server + EPS + RTL - how?

I am trying to build a box with: - Linux Ubuntu 18.04 - BTCPay Server, using docker - EPS (Electrum Personal Server) - RTL (Ride the lightning)
I have the full bitcoin data synced in a folder already, from a previous bitcoin-qt/bitcoind instance.
  1. Can I install BTCPay Server with docker and then run beside another docker with EPS?
  2. I understand that RTL is already integrated into BTCPay, so I just have to update the server and activate it?
  3. Is possible to integrate also EPS into the BTCPay docker file, after the installation? Or is it in "works" to be integrated in the same docker installation/update server by BTCPay ?
  4. Is possible to run EPS without docker, but using the bitcoind from BTCPay docker instance?
  5. Is possible to connect a mobile wallet (ex. Samourai) to that bitcoind instance from BTCPay Server ?
  6. One last question: is there a procedure to backup all the BTCPay server settings, for in case of disaster recovery moment? So to restore all data at once after reinstall OS ?
This is very important thing, if I start to put a BTCPay server at work in production and the machine gets fucked, how easy is to restore it?
Please somebody can respond to these questions, not in a super technical manner so many others can understand it?
Maybe u/belcher_ and u/CardCollector1 or u/NicolasDorier can help with some answers here, please?
EDIT: I hope I don't have to add a meme to this post to bring more attention... seems that lately only memes are "important" here, subjects like this are ignored. EDIT2: 21 hours and still not any answer... fuck, nobody uses BTCPay ?
submitted by Mr--Robot to Bitcoin [link] [comments]

Lost most of my Doge late 2013. There may be one last solution to getting some back. Does anyone have a copy of "DogeCoin version v0.6.4.0-unk-beta" or know which release it is directly linked to?

My keys corrupted and i didn't have a recent backup, after the upgrade lost all the doges.

I think there might be one more hope of finding some, and would appreciate if anyone knows which version " v0.6.4.0-unk-beta" which is on the debug.log output.

Noticed after all this time after digging through Bitcoin release notes that before bip32/hd wallets came in or as a matter of fact As they came in too (thanks devs). Most if not everyone i asked thought backing up the wallet.dat file is good enough, or the old --salvagewallet nor -zapwalletxes. They either aggressively scrambled the wallet making it more likely destroy even more keys, sure saved a few coins but most of the addresses in the keypool which has a size of 100 didn't have a corresponding private key anywhere in the wallet AFAIKT,
Sorry before i rant, i just need some info on if this wallet if linked to a specific Dogecoin version and just happens to say v0.6.4.0 in the debug log file.

I can't update directly to any other version without the wallet breaking up. Apparently i need the exact version that was last used, and turn it off extra safely so the log files which hold some parts of the keys go back to the Wallet.dat or something.

I tried all solutions, this might just work. from the "Bitcoin version 0.7.1 Readme file."
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).
If you were running on Linux with a version that might have been compiled with a different version of Berkeley DB (for example, if you were using an Ubuntu PPA version), then run the old version again with the -detachdb argument and shut it down; if you do not, then the new version will not be able to read the database files and will exit with an error.
Explanation of -detachdb (and the new “stop true” RPC command): The Berkeley DB database library stores data in both “.dat” and “log” files, so the database is always in a consistent state, even in case of power failure or other sudden shutdown. The format of the “.dat” files is portable between different versions of Berkeley DB, but the “log” files are not– even minor version differences may have incompatible “log” files. The -detachdb option moves any pending changes from the “log” files to the “blkindex.dat” file for maximum compatibility, but makes shutdown much slower. Note that the “wallet.dat” file is always detached, and versions prior to 0.6.0 detached all databases at shutdown.
or on shut down the coin client using the -detatchdb comas coins use both log and dat files with berkeley.

Thanks,

D_M


submitted by doge_messiah to dogecoin [link] [comments]

Interested in contributing to the BTC network? Here is the steps to get a full node up and running in Linux.

These instructions will work both on a VPS cloud server or a personal computer. You may find cheap VPS somewhere online for rent.
What Is A Full Node?
A full node is a program that fully validates transactions and blocks. Almost all full nodes also help the network by accepting transactions and blocks from other full nodes, validating those transactions and blocks, and then relaying them to further full nodes.
Most full nodes also serve lightweight clients by allowing them to transmit their transactions to the network and by notifying them when a transaction affects their wallet. If not enough nodes perform this function, clients won’t be able to connect through the peer-to-peer network—they’ll have to use centralized services instead.
Many people and organizations volunteer to run full nodes using spare computing and bandwidth resources—but more volunteers are needed to allow Bitcoin to continue to grow. This document describes how you can help and what helping will cost you.
Costs And Warnings
Running a Bitcoin full node comes with certain costs and can expose you to certain risks. This section will explain those costs and risks so you can decide whether you’re able to help the network.
Special Cases
Miners, businesses, and privacy-conscious users rely on particular behavior from the full nodes they use, so they will often run their own full nodes and take special safety precautions. This document does not cover those precautions—it only describes running a full node to help support the Bitcoin network in general.
Please consult an expert if you need help setting up your full node correctly to handle high-value and privacy-sensitive tasks.
Secure Your Wallet
It’s possible and safe to run a full node to support the network and use its wallet to store your bitcoins, but you must take the same precautions you would when using any Bitcoin wallet. Please see the securing your wallet page for more information.
Minimum Requirements
Bitcoin Core full nodes have certain requirements. If you try running a node on weak hardware, it may work—but you’ll likely spend more time dealing with issues. If you can meet the following requirements, you’ll have an easy-to-use node.
Note: many operating systems today (Windows, Mac, and Linux) enter a low-power mode after the screensaver activates, slowing or halting network traffic. This is often the default setting on laptops and on all Mac OS X laptops and desktops. Check your screensaver settings and disable automatic “sleep” or “suspend” options to ensure you support the network whenever your computer is running.
Possible Problems
Legal: Bitcoin use is prohibited or restricted in some areas.
Bandwidth limits: Some Internet plans will charge an additional amount for any excess upload bandwidth used that isn’t included in the plan. Worse, some providers may terminate your connection without warning because of overuse. We advise that you check whether your Internet connection is subjected to such limitations and monitor your bandwidth use so that you can stop Bitcoin Core before you reach your upload limit.
Anti-virus: Several people have placed parts of known computer viruses in the Bitcoin block chain. This block chain data can’t infect your computer, but some anti-virus programs quarantine the data anyway, making it more difficult to run a full node. This problem mostly affects computers running Windows.
Attack target: People who want to disrupt the Bitcoin network may attack full nodes in ways that will affect other things you do with your computer, such as an attack that limits your available download bandwidth or an attack that prevents you from using your full node’s wallet for sending transactions.
Linux Instructions
The following instructions describe installing Bitcoin Core on Linux systems.
Ubuntu 14.10 Instructions for Bitcoin Core 0.10.0.
If you use Ubuntu Desktop, click the Ubuntu swirl icon to start the Dash and type “term” into the input box. Choose any one of the terminals listed:
Alternatively, access a console or terminal emulator using another method, such as SSH on Ubuntu Server or a terminal launcher in an alternative desktop environment.
Type the following line to add the Bitcoin Personal Package Archive (PPA) to your system:
sudo apt-add-repository ppa:bitcoin/bitcoin
You will be prompted for your user password. Provide it to continue. Afterwards, the following text will be displayed:
Stable Channel of bitcoin-qt and bitcoind for Ubuntu, and their dependencies
More info: https://launchpad.net/~bitcoin/+archive/ubuntu/bitcoin
Press [ENTER] to continue or ctrl-c to cancel adding it
Press enter to continue. The following text (with some variations) will be displayed and you will be returned to the command line prompt:
gpg: keyring /tmp/tmpixuqu73x/secring.gpg' created gpg: keyring/tmp/tmpixuqu73x/pubring.gpg' created gpg: requesting key 8842CE5E from hkp server > > > >keyserver.ubuntu.com gpg: /tmp/tmpixuqu73x/trustdb.gpg: trustdb created gpg: key 8842CE5E: public key "Launchpad PPA for Bitcoin" imported gpg: no ultimately trusted keys found gpg: Total number processed: 1 pg: imported: 1 (RSA: 1) OK
Type the following line to get the most recent list of packages:
sudo apt-get update
A large number of lines will be displayed as different update files are downloaded. This step may take several minutes on a slow Internet connection.
To continue, choose one of the following options
sudo apt-get install bitcoin-qt
sudo apt-get install bitcoind
sudo apt-get install bitcoin-qt bitcoind
After choosing what packages to install, you will be asked whether you want to proceed. Press enter to continue.
If you’re logged in as an administrative user with sudo access, you may log out. The steps in this section should be performed as the user you want to run Bitcoin Core. (If you’re an expert administrator, you can make this a locked account used only by Bitcoin Core.)
Before using the Bitcoin Core daemon, bitcoind, you need to create its configuration file with a user name and password. First create the .bitcoin directory, create (touch) the file, and set the file’s permissions so that only your user account can read it. From the terminal, type:
mkdir ~/.bitcoin touch ~/.bitcoin/bitcoin.conf chmod 600 ~/.bitcoin/bitcoin.conf
Then you can run the command bitcoind. It will print output similar to this:
bitcoind Error: To use the "-server" option, you must set a rpcpassword in the configuration file: /home/bitcoinorg/.bitcoin/bitcoin.conf It is recommended you use the following random password: rpcuser=bitcoinrpc rpcpassword=XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX (you do not need to remember this password)
The username and password MUST NOT be the same.
If the file does not exist, create it with owner-readable-only file permissions. It is also recommended to set alertnotify so you are notified of problems; for example: alertnotify=echo %s | mail -s "Bitcoin Alert" [email protected] The “rpcpassword” displayed will be unique for your system. You can copy the rpcuser and rpcpassword lines into your configuration file using the following commands. Note that in most Ubuntu terminals, you need to press Ctrl-Shift-C to copy and Ctrl-Shift-V to paste because Ctrl-C and Ctrl-V have different meanings in a Unix-style terminal.
echo rpcuser=bitcoinrpc >> ~/.bitcoin/bitcoin.conf echo rpcpassword=XXXXXX >> ~/.bitcoin/bitcoin.conf (Warning: Don’t use XXXXXX as your RPC password. Copy the rpcpassword displayed by bitcoind for your system.)
Now you can start Bitcoin Core daemon for real. Type the following command:
bitcoind -daemon
It will print a message that Bitcoin Core is starting. To interact with Bitcoin Core daemon, you will use the command bitcoin-cli (Bitcoin command line interface). Note: it may take up to several minutes for Bitcoin Core to start, during which it will display the following message whenever you use bitcoin-cli:
error: {"code":-28,"message":"Verifying blocks..."}
After it starts, you may find the following commands useful for basic interaction with your node:
to safely stop your node, run the following command:
bitcoin-cli stop
A complete list of commands is available in the Bitcoin.org developer reference.
When Bitcoin Core daemon first starts, it will begin to download the block chain. This step will take at least several hours, and it may take a day or more on a slow Internet connection or with a slow computer. During the download, Bitcoin Core will use a significant part of your connection bandwidth. You can stop Bitcoin Core at any time using the stop command; it will resume from the point where it stopped the next time you start it.
Optional: Start Your Node At Boot
Starting your node automatically each time your computer boots makes it easy for you to contribute to the network. The easiest way to do this is to start Bitcoin Core daemon from your crontab. To edit your crontab, run the following command:
crontab -e
@reboot bitcoind -daemon Save the file and exit; the updated crontab file will be installed for you. Now Bitcoin Core daemon will be automatically started each time your reboot your computer.
If you’re an Ubuntu expert and want to use an init script instead, see this Upstart script.
You have now completed installing Bitcoin Core. If you have any questions, please ask in one of Bitcoin’s many communities, such as Bitcoin StackExchange, BitcoinTalk technical support, or the #bitcoin IRC chatroom on Freenode.
To support the Bitcoin network, you also need to allow incoming connections. Please read the Network Configuration section for details.
Network Configuration
If you want to support the Bitcoin network, you must allow inbound connections.
When Bitcoin Core starts, it establishes 8 outbound connections to other full nodes so it can download the latest blocks and transactions. If you just want to use your full node as a wallet, you don’t need more than these 8 connections—but if you want to support lightweight clients and other full nodes on the network, you must allow inbound connections.
Servers connected directly to the Internet usually don’t require any special configuration. You can use the testing instructions below to confirm your server-based node accepts inbound connections.
Home connections are usually filtered by a router or modem. Bitcoin Core will request your router automatically configure itself to allow inbound connections to Bitcoin’s port, port 8333. Unfortunately many routers don’t allow automatic configuration, so you must manually configure your router. You may also need to configure your firewall to allow inbound connections to port 8333. Please see the following subsections for details.
Testing Connections
The BitNodes project provides an online tool to let you test whether your node accepts inbound connections. To use it, start Bitcoin Core (either the GUI or the daemon), wait 10 minutes, and then visit the GetAddr page (https://getaddr.bitnodes.io/). The tool will attempt to guess your IP address—if the address is wrong (or blank), you will need to enter your address manually.
For more instruction and reviews based off BTC please follow my subreddit /BTC_Reviews
all material from this post was found here --> https://bitcoin.org/en/full-node
submitted by Mattjhagen to Bitcoin [link] [comments]

Bitcoin ABC Ubuntu repo has been updated to serve 0.14.6

Bitcoin ABC Ubuntu repo has been updated to provide the latest stable version 0.14.6
See the release notes for more details.
Notice for the Yakkety/16.10 users: this ubuntu release has been discontinued and is not supported anymore by Ubuntu PPA services. So if you want to upgrade you have to upgrade to Zesty/17.04 or update ABC manually.
Repo home page:
https://launchpad.net/~bitcoin-abc/+archive/ubuntu/ppa
If you are installing for the first time just execute these commands(*):
sudo apt-get install software-properties-common sudo add-apt-repository ppa:bitcoin-abc/ppa sudo apt-get update sudo apt-get install bitcoind bitcoin-qt 
(*) if you already have a prev version of Bitcoin ABC just run:
sudo apt-get update sudo apt-get upgrade 
submitted by s1ckpig to btc [link] [comments]

Bitcoin ABC Ubuntu repo has been updated to serve 0.14.5

Bitcoin ABC Ubuntu repo has been updated to provide the latest stable version 0.14.5.
Notice for the Yakkety/16.10 users: this ubuntu release has been discontinued and is not supported anymore by Ubuntu PPA services. So if you want to upgrade you have to upgrade to Zesty/17.04 or update ABC manually.
Repo home page:
https://launchpad.net/~bitcoin-abc/+archive/ubuntu/ppa
If you are installing for the first time just execute these commands(*):
sudo apt-get install software-properties-common sudo add-apt-repository ppa:bitcoin-abc/ppa sudo apt-get update sudo apt-get install bitcoind bitcoin-qt 
(*) if you already have a prev version of Bitcoin ABC just run:
sudo apt-get update sudo apt-get upgrade 
submitted by s1ckpig to btc [link] [comments]

Bitcoin ABC Ubuntu repo has been updated to serve 0.15.0

Bitcoin ABC Ubuntu repo has been updated to provide the latest stable version 0.15.0
See the release notes for more details.
Notice for the Yakkety/16.10 users: this ubuntu release has been discontinued and is not supported anymore by Ubuntu PPA services. So if you want to upgrade you have to upgrade to Zesty/17.04 or update ABC manually.
Repo home page:
https://launchpad.net/~bitcoin-abc/+archive/ubuntu/ppa
If you are installing for the first time just execute these commands(*):
sudo apt-get install software-properties-common sudo add-apt-repository ppa:bitcoin-abc/ppa sudo apt-get update sudo apt-get install bitcoind bitcoin-qt 
(*) if you already have a prev version of Bitcoin ABC just run:
sudo apt-get update sudo apt-get upgrade 
submitted by s1ckpig to BitcoinABC [link] [comments]

Bitcoin ABC Ubuntu repo has been updated to serve 0.14.6

Bitcoin ABC Ubuntu repo has been updated to provide the latest stable version 0.14.6
See the release notes for more details.
Notice for the Yakkety/16.10 users: this ubuntu release has been discontinued and is not supported anymore by Ubuntu PPA services. So if you want to upgrade you have to upgrade to Zesty/17.04 or update ABC manually.
Repo home page:
https://launchpad.net/~bitcoin-abc/+archive/ubuntu/ppa
If you are installing for the first time just execute these commands(*):
sudo apt-get install software-properties-common sudo add-apt-repository ppa:bitcoin-abc/ppa sudo apt-get update sudo apt-get install bitcoind bitcoin-qt 
(*) if you already have a prev version of Bitcoin ABC just run:
sudo apt-get update sudo apt-get upgrade 
submitted by s1ckpig to BitcoinABC [link] [comments]

Bitcoin ABC Ubuntu repo has been updated to serve 0.15.0

Bitcoin ABC Ubuntu repo has been updated to provide the latest stable version 0.15.0
See the release notes for more details.
Notice for the Yakkety/16.10 users: this ubuntu release has been discontinued and is not supported anymore by Ubuntu PPA services. So if you want to upgrade you have to upgrade to Zesty/17.04 or update ABC manually.
Repo home page:
https://launchpad.net/~bitcoin-abc/+archive/ubuntu/ppa
If you are installing for the first time just execute these commands(*):
sudo apt-get install software-properties-common sudo add-apt-repository ppa:bitcoin-abc/ppa sudo apt-get update sudo apt-get install bitcoind bitcoin-qt 
(*) if you already have a prev version of Bitcoin ABC just run:
sudo apt-get update sudo apt-get upgrade 
submitted by s1ckpig to btc [link] [comments]

Getting bitcoin off a broken computer

I don't know if I should post this here or in a Linux subreddit. I have a barely functional laptop that no longer recognizes any drives or network devices except the hard drive, due to the OS (Ubuntu 13.1) being hosed. So it can't get online or transfer files to another medium. All I can do is display stuff on the screen. I used it for bitcoin before it crashed and I believe there is a tenth of a bitcoin on the hard drive. It has bitcoind and bitcoin-qt 0.8.5 installed.
I remember hearing about bitcoin on paper, but I can't print with this computer. Is there an old school way I can do that by writing what I see on the screen?
submitted by k9jeep to Bitcoin [link] [comments]

Help getting ABC node on MY Ubuntu 12 VPS?

Edit: Ubuntu 12 too old to use this repository. Upgrading to 14 fixed it!
Note that now Bitcoin Unlimited has a BCC version up at adoptanode.com its probably unnecessary to set up a BCC node on a VPS.

My hosting provider offers VPS hosting so thought I'd try it as first month is half price.
I can choose from various versions of Linux, and for the moment am on Ubuntu 12.
After some fiddling, I was able to add the PPA, but when trying to install bitcoind and bitcoin-qt I get this error :
[email protected]:~# apt-get install bitcoind bitcoin-qt
Reading package lists... 0%
Reading package lists... 100%
Reading package lists... Done
Building dependency tree... 0%
Building dependency tree... 0%
Building dependency tree... 50%
Building dependency tree... 50%
Building dependency tree
Reading state information... 0%
Reading state information... 2%
Reading state information... Done
E: Unable to locate package bitcoin-qt
[email protected]:~#
I don't think it's reading the PPA or it's picking up another bitcoind because if I just apt-get install bitcoind then get to run it, it says it's very old and discontinued.
I am a Unix novice. And in doing this from a phone.
Trying to use instructions from https://amp.reddit.com/btc/comments/6poavx/bitcoin_abc_ubuntu_repo_has_been_updated_to_serve/
submitted by cccmikey to btc [link] [comments]

Question re RPC interface

I have an idea for an app/website that could need to query the blockchain, and was wondering how to integrate BItcoin-QT client into my dev workflow...
I FINALLY got the entire blockchain downloaded. Took a bit, but it's finally here. That's hosted on my Mac.
Now, I develop using Virtual Box to do the hosting, with a NAT Network connection. Would I guess I'd need to set up the bitcoin.conf file to accept connections from whichever IP address the VB Nat Network appears as?
Can I mount the bitcoin data directory in Ubuntu, and just fire up bitcoind and have it use the blocks my Mac already downloaded, or will it corrupt that directory and force me to download it all over again?
Be nice to me! :) I probably should have sought a little guidance before I even downloaded the blockchain, but it's here now and I'm just trying to figure out the best way forward. Figure more than one of you have already gone down this path :)
Thanks!
submitted by identicalBadger to Bitcoin [link] [comments]

Really like the watch only functionality in bitcoin core!

First of all: thanks core developers for all the efforts!
Reason: if you run a full bitcoin node, to see your total balance without exposing your addresses to others.
Did it like this on my full node (ubuntu linux, no pruning):
Backup your wallet.dat
Start: bitcoind
Execute in a script (or on the command line):
bitcoin-cli importaddress "address1" Label false
bitcoin-cli importaddress "address2" Label false
bitcoin-cli importaddress "address3" Label false
Etc.
Stop: bitcoind
Start: bitcoin-qt -rescan
bitcoin-qt will rescan the wallet and you can see the progress. When finished you will see the balance of all addresses (watch and non watch)
When running bitcoind you can get the total balance of the wallet:
bitcoin-cli getbalance "*" 0 true
To get the total balance without the watch only addresses
bitcoin-cli getbalance "*" 0 false
Combine this with an Apache server and you can watch your balance completely safe anywhere and without exposing your (HD) addresses.
Side note: you can use bitcoin-qt as a wallet without too much hinder like this:
/usbin/taskset -c 0 /usbin/ionice -c 3 /usbin/nice -n 19 /home/usebitcoin-0.11.0/src/qt/bitcoin-qt
taskset: use only one cpu
ionice: low i/o priority
nice: low cpu priority
I hope this is useful for someone.
submitted by sumBTC to Bitcoin [link] [comments]

Bitcoin ABC Ubuntu repo has been updated to serve 0.14.5

Bitcoin ABC Ubuntu repo has been updated to provide the latest stable version 0.14.5.
Notice for the Yakkety/16.10 users: this ubuntu release has been discontinued and is not supported anymore by Ubuntu PPA services. So if you want to upgrade you have to upgrade to Zesty/17.04 or update ABC manually.
Repo home page:
https://launchpad.net/~bitcoin-abc/+archive/ubuntu/ppa
If you are installing for the first time just execute these commands(*):
sudo apt-get install software-properties-common sudo add-apt-repository ppa:bitcoin-abc/ppa sudo apt-get update sudo apt-get install bitcoind bitcoin-qt 
(*) if you already have a prev version of Bitcoin ABC just run:
sudo apt-get update sudo apt-get upgrade 
submitted by s1ckpig to BitcoinABC [link] [comments]

(1) Is it true that encrypting an *existing* bitcoin-qt wallet.dat file will "invalidate" any existing backups? (2) Can I use unicode characters - eg ♥ - in the bitcoin-qt wallet passphrase?

I have an existing bitcoin-qt wallet.dat file which I want to encrypt - using the command in the bitcoin-qt Settings menu, involving creating a passphrase.
I have 2 (possibly somewhat related) questions:
TL;DR
(1) If you encrypt an existing wallet.dat file, will the backups of the old wallet.dat file still work?
(2) Can you include unicode characters - eg ♥ - in the passphrase used to encrypt a bitcoin-qt wallet.dat file?
Worst-case scenario: The answers to (1) and (2) are both "no" - and I attempt to encrypt an existing wallet using unicode, and my backups no longer work (due to a new pool of addresses somehow being created?) and the passphrase isn't what I think it is (due to the unicode characters somehow being misinterpreted?) - and then I could lose all my coins??
Details
(1) The following (old, short) thread claims that after you encrypt an existing wallet, any previous backups of that wallet will no longer work:
https://pay.reddit.com/Bitcoin/comments/1ccfdk/encrypting_walletdat_in_bitcoinqt/
Obviously, the the first response in that thread was slightly wrong, for saying that the "server" creates a new pool of 100 addresses to draw on. So using word "server" here was certainly incorrect - but maybe the gist of what they were saying might still be correct? (if you simply change "server" to "client").
I can actually understand that there might be reasons why encrypting a wallet.dat file could cause a new pool of 100 addresses to be generated.
But it does not make sense to me that this would make any older (unencrypted) backups instantly useless.
It seems to me that these older, unencrypted backups would still have their private keys intact, and could thus be used in certain (perhaps limited?) ways - such as:

(2) It seems that including a few unicode characters in the bitcoin-qt wallet passphrase would make it a lot stronger (since unicode is a much larger set of characters than ascii), so I would like to include a few.
But it would be more reassuring if it could be explicitly stated that this is indeed supported.

Possible catastrophic interaction between (1) and (2)?
If the answers to (1) and (2) were both "no" (ie, if you encrypt an existing bitcoin-qt wallet.dat file then any existing backups will not work, and unicode characters do not work in bitcoin-qt passphrases), then I'm worried there could be some kind of catastrophic interaction between (1) and (2) where I lose all my coins, as follows:
(1) I encrypt my existing wallet - making my old, unencrypted wallet.dat file now invalidated (due to something involving a new pool of addresses being generated?)
and
(2) I use a passphrase which includes unicode characters which bitcoin-qt appears to accept at the time of creation, but which doesn't work at the time of trying to decrypt the wallet.dat file (due to something going wring with how the supposed unicode characters are actually interpreted while being entered or copied-and-pasted?).
In this possible worst-case scenario, my old backups of wallet.dat no longer work, and my newly encrypted wallet.dat has some password which I'm not able to correctly enter anymore.
Sorry to be so paranoid about this!
Other remarks:
(a) I did do a (limited) test of unicode capability for bitcoin-qt wallet.dat passphrases: simply by creating a new (empty) wallet.dat file, and creating a passphrase for it involving unicode characters, and then attempting to change the passphrase (which requires entering the old passphrase that contained unicode characters).
This did seem to work ok: it let me re-enter the old passphrase (which included unicode characters) to create a new passphrase.
However, since this is an empty wallet (and since bitcoin-qt would ask for the passphrase only when attempting to actually spend from an encrypted wallet), I did not see a way to fully test whether the passphrase actually worked to decrypt a unicode-passphrase-encrypted wallet for the purpose of spending from it.
(I'm still downloading the rest of the blockchain and it's going to take at least another week on my slow connection, so don't see how I could send a small amount to the new wallet to test it either. My existing wallet.dat file was originally created on an internet-connected machine a long time ago, but it's been offline ever since, so in some sense it's kinda-sorta been in somewhat "cold" storage all this time, and I would prefer to avoid putting it online on a "hot" internet-connected machine until absolutely necessary.)
(b) Long-term, I am actually also in the process of setting up a proper cold storage system based on Armory, which I have installed on 2 Ubuntu machines (one offline and one online).
But I have a slow internet connection, and the backups of this old wallet.dat file have been sitting around unencrypted for ages (I've been relying simply on then being physically inaccessible).
Now some "things" are coming up over the next few days where I some better security right away, and it's probably going to take over a week for Armory/bitcoind to update my local copy of the blockchain.
So in the meantime, I also need some basic additional security right now - so encrypting the existing bitcoin-qt wallet.dat file using a strong passphrase (and making some new backups) seems like it could be a reasonable initial approach.
Thanks for any help!
submitted by encrypt_throwaway to Bitcoin [link] [comments]

Colored coin client preview #1 (based on Bitcoin Armory)

I think it's already good enough for people to play with it. (Although certainly it's not ready for anything serious.)
For people who are not familiar with concept, colored coins is a technology which allows people to represent arbitrary tokens (e.g. issue private currencies, stocks, bonds, etc.) using small quantities of bitcoins. It is interesting because it would allow us to create decentralized and secure markets. (As decentralized and secure as Bitcoin itself, at least in theory.) See here.
Notes about current release:
Windows binaries: http://killerstorm.xen.prgmr.com/alex/ArmoryX-0.2.5.zip
There are no Linux binaries, but it's really easy to build it on Ubuntu or Debian:
(Note: if you're already using Armory, it is a good idea to hide you ~/.armory so it won't be seen by this experimental Armory mod. Or, perhaps, just don't run this experimental mod.)
Before you run it, make sure that bitcoind or Bitcoin-Qt is running and fully sync'ed. Armory takes up to 10 minutes to start (this version is slower because it additionally scans for colored transactions) and requires ~ 1 GB of RAM.
At start it will offer to create a wallet, do not enable encryption, otherwise issuing colored coins won't work.
Send some bitcoins to this new wallet, 0.02 BTC is probably enough to issue some colored coins and to pay for tx fees.
There is a drop down to choose color. Balance is displayed for a currently chosen color (i.e. if you chose TESTcc it will show how many TESTcc units this wallet owns), and when you send coins you send coins of that color.
Initially 'uncolored' is selected, it means normal BTC. This drop down also has TESTcc ("test colored coins") and "All colors" (this mode is just for debugging, you cannot send coins in this mode).
Here's what you can do now:
  1. Ask somebody to send you TESTcc. (We want to make it automatic, Satoshi Dice style, but unfortunately that code isn't quite ready.)
  2. Find and install other color definitions.
  3. Issue your own colored coins and send them to somebody who wants them. (LOL.)
Let's start from option #3. There is 'Hallucinate' menu. (It is called 'hallucinate' because colors do not exist on blockchain level, it is a client-side convention.) Choose 'Issue colored coins'. Likely all you need to change is name, but you can tweak satoshi-per-unit and number of units if you want.
When you click Issue it will create a new transaction (using your uncolored BTC) and will create a color definition. Optionally it will also upload your color definition to color definition registry. (This registry runs on my server, it might be down.)
You should note ColorID, this is how other people can refer to these coins (name is ambiguous).
You can now choose this new color in drop down and it will show your balance. (E.g. 1000 units.)
Now you'll perhaps want to send these coins to somebody. That person would need to install your color definition first. If you send colored coins without warning they might be lost, i.e. mixed with uncolored ones. For same reason it makes no sense to send them to wallet which isn't color aware.
For example, you can post on some forum:
I've issued LOLwut coins (ColorID: 36738fe78a443656535503efb585fee140a37d54), each unit represents a bond with face value of 0.1 BTC payable by me, Trololo, via buy back. I promise to buy back all bonds in a month.
Now people who are interested in this LOLwut coin issue will copy ColorID, paste it into Hallucinate > Download color definition dialog, and if this color definition is published it will be downloaded and installed. Armory restart is required to complete installation.
After installation that person will be able to see these LOLwut coins.
Note that if you do not trust my registration server, you can publish color definition yourself: go to ~/.armory/colordefs, find 36738fe78a443656535503efb585fee140a37d54.colordef and upload it to your web server. Then you can give people URL like http://example.com/36738fe78a443656535503efb585fee140a37d54.colordef and they can download it by URL.
Or they can just obtain this file by any means and copy it to ~/.armory/colordefs directory. It is decentralized, nobody can prevent you from issuing colored coins.
I think that's all. There is also Hallucinate > Manage color definitions dialog, but I hope it's easy to figure out how it works.
We are working on improved version, particularly on p2p exchange feature.
I've set up an IRC channel for people to talk about trying out colored coins: #colored-coins-otc on Freenode.
submitted by killerstorm to Bitcoin [link] [comments]

Linux noob needs help getting a Bitcoin Classic node running on Lubuntu

I've installed Lubuntu 15.10 on an old laptop that used to be Windows XP. Seems to run fine. I tried Ubuntu but the laptop struggled to run it.
I've downloaded bitcoin-0.11.2-linux32.tar.gz as my Lubuntu installation is 32 bit.
I've extracted the contents but don't have a clue how to install - dont laugh, I've only ever used Windows before.
The bitcoin-0.11.2 folder contains the following folders:
Bin Include Lib
I assume the file I want to run to install is in bin?
The options are:
Bitcoin-cli Bitcoind Bitcoin-qt Bitcoin-tx
And two others starting 'test'
Which of the above do I run to install Classic?
And how do I run, is it a matter of simply double clicking, or do I use the Terminal? If so, what is the terminal command?
Thanks for your help.
submitted by vyhvdrujnbdryu to Bitcoin_Classic [link] [comments]

Programming Bitcoin-qt using the RPC api (1 of 6) How to Install Bitcoin Core Wallet on Ubuntu 16 How to install Bitcoin on Ubuntu 16.04 How To Install BitCoin On Ubuntu 16.04 6. bitcoin-qt

Bitcoin software has both a graphical interface called bitcoin-qt and a console interface, bitcoind. If the first is convenient for human use, then without a text it is quite difficult to make an online store or any other service that accepts bitcoins as a payment. About it and speech will go. To work you need to run one instance of bitcoin as a daemon, so he worked as a full-fledged host on ... Bitcoin ist eine Währung, die nur virtuell existiert, die aber für die Bezahlung von Dienstleistungen und Waren benutzt werden kann. Interessant ist sie, weil sie von keiner Regierung herausgegeben und kontrolliert wird, und weil der Transfer von Bitcoins kaum etwas kostet. Um Bitcoin einsetzen zu können, benötigt man einen Geldbeutel für Bitcoins, ein Wallet. Bitcoin-QT enthält dieses ... In this article, I will talk about what Bitcoin is, what a Bitcoin wallet is, how to install Bitcoin core on Ubuntu and how to use it. Let’s get started. About Bitcoin. Bitcoin is a crypto-currency. You can also call it a virtual currency as well. It was created by Satoshi Nakamoto. The advantage of bitcoin is that you don’t need to rely on ... Next, update Ubuntu’s software package lists: $ sudo apt-get update Finally, install Bitcoin core itself. Enter “Y” when asked asked for permission to continue: $ sudo apt-get install bitcoin-qt This last command may take some time, during which both Bitcoin Core and all of its dependencies will be installed. Run Bitcoin Core After struggeling with the dependencies for a while, I finally managed to compile Bitcoin-Qt on my Ubuntu machine. I used the following commandos for compiling: ./autogen.sh ./configure -with-gui make sudo make install Now when I write bitcoin-qt in the terminal, the wallet will succesfully start. However, I am not able to locate bitcoin-qt.exe on my computer. I want to be able to get the .exe ...

[index] [26493] [34103] [5891] [1825] [16644] [37135] [5069] [20436] [12390] [6002]

Programming Bitcoin-qt using the RPC api (1 of 6)

Ubuntu -1 Setting up Bitcoin Commands, sudo add-apt-repository ppa:bitcoin/bitcoin sudo apt-get update sudo apt-get install bitcoin-qt sudo apt-get install bitcoind sudo blkid sudo nano /etc/fstab ... How to install Bitcoin on Ubuntu 16.04 On this video, I will show you how to install Bitcoin on Ubuntu 16.04 Commands sudo apt-add-repository ppa:bitcoin/bi... This video covers the method to install BitCoins on Ubuntu 16.04 Bitcoin is a virtual and crypto-currency created by Satoshi Nakamoto. For more explanation o... This short video shows how to compile the bitcoin source code on linux (ubunu). an easy task to do but it take some time (around 15 min) please read the instruction in the official github https ... How to run Bitcoin-qt as a server with a configuration file (3 of 6) - Duration: 5:48. Lars Holdgaard 11,060 views. 5:48 . How To Build Raw Bitcoin Transactions in NodeJS - Duration: 16:57 ...

#