Install Bitcoind Windows CryptoCoins Info Club

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]

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]

Bitcoin Cash Node Ubuntu PPA repository is available

The Bitcoin Cash Node Ubuntu PPA repository has been set up to serve version 0.21.0 and is available at:
 
https://launchpad.net/~bitcoin-cash-node/+archive/ubuntu/ppa
 
To install
 
sudo add-apt-repository ppa:bitcoin-cash-node/ppa sudo apt-get update sudo apt install bitcoind bitcoin-qt 
 
NB if you have installed other Bitcoin Cash clients via PPA, it would be better to uninstall those binaries and remove their repository, eg:
 
sudo apt-get remove bitcoind bitcoin-qt bitcoin-tx sudo add-apt-repository --remove ppa:bitcoin-abc/ppa 
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 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]

#Reddcoin ($RDD) Core Wallet Release 3.0.1 - PosV v2 SuperMajority Consensus Upgrade at 45.6% - Required Upgrade

Reddcoin (RDD) Core Wallet v3.0.1 - January 09, 2020
Version 3.0.1 is the official release version of Reddcoin Core. It is available for download at Reddcoin Core's Github repository here: https://github.com/reddcoin-project/reddcoin/releases/tag/v3.0.1
This release features PoSV v2.supermajority activation and new staking ruleset (and minor misc fixes). v3.0.1 is still not yet MacOS Catalina compatible. We are still working and should have that fix issued very soon. Sincere apologies to our Mac-using ReddHeads.
It is particularly important that all users upgrade, as once PoSV v2 is enforced, version 4 blocks will be rejected from the network entirely.
Therefore v3.0.1 is a "strongly recommended" update for all users. Note: If you have already installed v3.0.0, this upgrade is not required. If you have not yet upgraded from v2.0.x or earlier, this is a REQUIRED upgrade. Please install the newest version v3.0.1 to avoid losing functionality during supermajority activation of PoSV v2.
Reddcoin Core version 3.0.1 is now available from: https://github.com/reddcoin-project/reddcoin/releases Release Notes are available here and replicated below in this announcement: https://github.com/reddcoin-project/reddcoin/blob/mastedoc/release-notes.md
This is a new major version release of Reddcoin.
Previously, the original and subsequent versions of Reddcoin were taken from a fork of the Litecoin code base.
With the release of Reddcoin V2.0.0, the code was based directly from a fork of Bitcoin. This allows for better source control and feature implementation from upstream changes into the future
With the release of Reddcoin V3.0.0, the PoSV stake reward has been improved to allow for a target 5% network growth, in process re-incentivizing individual network stakers and providing for integrated dev support.
Upgrading to this release is strongly recommended and required for continued operation. Once a supermajority of 90% is reached, old wallets will no longer accept the new v5 blocks.
Please report bugs using the issue tracker at github:
https://github.com/reddcoin-project/reddcoin/issues
How to Upgrade
If you are running an older version of Reddcoin, shut it down. Wait until it has completely shut down (which may take a few minutes for older versions). Run the installer (on Windows) or just copy over /Applications/Reddcoin-Qt (on Mac) or reddcoind/reddcoin-qt (on Linux).
Start wallet. All done!
Reddcoin v3.0.0 introduced an updated PoSV method to better distribute staking rewards and target a overall 5% network growth. Staking and relay policy enhancements 
To implement PoSV v2, Reddcoin Core's block templates are now for version 5 blocks only. When PoSV v2 consensus (Supermajority 9000/10000) is reached, only v5 blocks will be accepted by the network.This equates to approximately 90% of blocks being generated over 1 week period. Status at any time may be viewed in node debug.log
Blockchain Download:
Blockchain data for both testnet and mainnet along with instructions can be downloaded from github. https://github.com/reddcoin-project/bootstrap_files
3.0.1 changelog
*83e212838 - John Nash, 2020-01-09 : really delete these files *3a1458ecd - Oliver Webb, 2020-01-08 : Added missing dependency libminiupnpc-dev for Jessie *d21915431 - Tiago Peralta, 2019-06-21 : Add vout to listtransactions/gettransaction *8d58ea7cf - Oliver Webb, 2020-01-08 : Script for downloading pre compiled binaries for Raspbian Jessie, Stretch or Buster *d4eced1bc - Oliver Webb, 2020-01-08 : Delete reddcoin_core_download_raspbian_stretch.sh *c5e9f91cf - Oliver Webb, 2020-01-08 : Delete reddcoin_core_download_raspbian_jessie.sh *5d5771b00 - Oliver Webb, 2020-01-08 : Delete reddcoin_core_download_raspbian_buster.sh *75c6ae91b - Oliver Webb, 2020-01-05 : add reddcoin-qt and remove starting daemon process *54c501787 - Oliver Webb, 2020-01-05 : add reddcoin-qt and remove starting daemon process *acb30a2b6 - Oliver Webb, 2020-01-05 : script files for Raspbian Jessie (also Stakebox) *cfddbe594 - John Nash, 2020-01-05 : Update copyright year and version *e46e5e7de - John Nash, 2020-01-05 : download script for pre compiled wallet *37386790a - John Nash, 2020-01-05 : change libssl deb packages links to github *9dbc772e6 - Oliver Webb, 2020-01-03 : download script for pre compiled wallet *857d697fd - Oliver Webb, 2020-01-03 : change libssl deb packages links to github *2cb74b9a8 - John Nash, 2019-12-31 : update copyright year *c641a1ab3 - Oliver Webb, 2019-12-30 : Raspberry Pi build script files for v3 wallet *a3f21a4a4 - John Nash, 2019-12-30 : add install script for building db4 update instructions for unix, osx, arm building using the db4 install script *5f6299b2a - John Nash, 2019-12-28 : docs: Update build notes for arm processors *465716c01 - John Nash, 2019-12-28 : test for arm devices *3fec3a535 - John Nash, 2018-02-02 : build: update source paths *5f6031ab4 - John Nash, 2019-12-28 : Scrypt n=1024 Pow hash based upon Colin Percival's Tarnsnap (2009) Modified by Artforz, coblee, pooler, wtogami, Nikolay Belikov, reddink *2fd4d91a0 - John Nash, 2019-12-24 : update copyright year *326828b36 - John Nash, 2019-12-24 : set release state true *8ebede0a6 - John Nash, 2019-12-24 : release notes *36df6fdfb - John Nash, 2019-12-23 : add check explictly for v5 blocks or greater *874dc1f0c - John Nash, 2019-12-17 : remove hardcoded global variable rearrange debug log output *763b25db8 - John Nash, 2019-12-17 : move copyright to new line *536baf635 - John Nash, 2019-12-17 : update version and set release state to false *cde9009f3 - John Nash, 2019-12-17 : update copyright year *ae41b7ed3 - John Nash, 2019-12-17 : set isSuperMajority to 90% for mainnet *e43e1c8ed - John Nash, 2019-12-10 : additional logging to verify isSuperMajority in the debug.log output *e31783cac - John Nash, 2019-12-05 : add/update public key for mainnet *405c6f002 - John Nash, 2019-12-05 : add log output for current inflation rate *9cc43c3f7 - John Nash, 2019-12-02 : determine calculated stake based on posv version *7baa3bf75 - John Nash, 2019-11-25 : check the posv transaction for correct pubkey *9ffa7ca38 - John Nash, 2019-11-21 : check for posv v1 or posv v2 blocks when calculating stake reward *39f7aad68 - John Nash, 2019-11-14 : add logging *0e283e6c3 - John Nash, 2019-11-13 : correct maths *74cbdeffd - John Nash, 2019-11-11 : use new posv v2 functions addidtional logging *35d7413b5 - John Nash, 2019-11-11 : add new proofofstakereward *3d917216c - John Nash, 2019-11-11 : get inflation adjustment *f63d17443 - John Nash, 2019-11-08 : add the developer output split fund output *ca263c9c9 - John Nash, 2019-11-05 : add dev key to chainparams *df6996ab0 - John Nash, 2019-11-05 : add block version checking *14b663479 - John Nash, 2019-11-05 : increase block version
Credits
Thanks to everyone who contributed to coding, testing and feedback for this release, notably:
@cryptognasher @techadept @chris @cryptobuze @harmonyq @mindredder @paxtech @Tiago Peralta 
Stake on!!
-Reddcoin (RDD) Core Development Team
submitted by TechAdept to reddCoin [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]

Bitcoin Unlimited 1.7.0 has just been released

Download the latest Bitcoin Cash compatible release of Bitcoin Unlimited (1.7.0, October 11th, 2019) from:
 
https://www.bitcoinunlimited.info/download
https://github.com/BitcoinUnlimited/BitcoinUnlimited/releases/tag/bucash1.7.0.0
 
This is a major release of Bitcoin Unlimited compatible with the upcoming protocol upgrade of the Bitcoin Cash network. You could find November 15th, 2019 upgrade specifications here:
This is list of the main changes that have been merged in this release:
 
Release notes: https://github.com/BitcoinUnlimited/BitcoinUnlimited/blob/dev/doc/release-notes/release-notes-bucash1.7.0.md
 
PS Ubuntu PPA repository is currently being updated to serve for 1.7.0
(*) if you were using BU with -txindex, after the fist session after the upgrade the database where the index are stored will be upgraded to a new format. During this migration RPC command will return an error message saying the txindex is syncing. The lasting of the migration process depends on the machine where BU is installed.
submitted by s1ckpig to btc [link] [comments]

[IDEA] [PROPOSAL] Monero Debian (deb) packages / Debian package repository deb.getmonero.org (I can do)

I have the skills to implement this if wanted.
Possible User Experience
This is a proposal, i.e. not implemented yet. Instructions for users, simplified.
How to install monero using apt-get
Download the repository signing key.
wget https://www.getmonero.org/monero.asc
Add the signing key.
sudo apt-key --keyring /etc/apt/trusted.gpg.d/monero.gpg add ~/monero.asc
Add APT repository.
echo "deb https://deb.getmonero.org buster main" | sudo tee /etc/apt/sources.list.d/monero.list
Update your package lists.
sudo apt-get update
Install monero.
sudo apt-get install monero
A few technical implementation details
I would simply grab the binaries provided by getmonero.org, download them, check software (gpg) signatures, put these into deb packages, add these to a repository, and upload the repository.
What I would not do is creating the binaries during package creation. While this is nice to have, it doesn't help user experience and blocks the progress on reaching this goal. See next chapter.
Why simply put the pre-build Monero binaries into a deb package?
1) After bitcoin existing for more than 10 years, being popular and being in Debian unstable (sid) it still never made its way into Debian testing, let alone stable. Reason being explained that a difference in underlying libraries (even just security fixes) during compilation may result in a network split. Binaries compiled during packaging on different versions of Linux distributions might have different libraries that might cause a network fork / chain split.
References:
(Note: above website saying Tags: fixed-upstream is probably a mistake as discussion at bottom says.)
2) The github issue of packaging monero stalled.
3) By shipping the same binaries as provided by getmonero.org reduces the chances of introducing a backdoor.
Many Options
Timeline
Doable quickly. The electrum (bitcoin) AppImage was recently added to a Debian package (binaries-freedom) by me and is now easily installable in Whonix. Pre-installed in testers version of Whonix already.
About Me
I am the founder of Whonix, which I am maintaining at present for more than 7 years.
Whonix (formerly TorBOX) is a Debian GNU/Linux–based security-focused Linux distribution. It aims to provide privacy, security and anonymity on the internet.
You can see an overview of packages I am maintaining on my github profile.
To proof that this forum account adrelanos corresponds the same person maintaining whonix.org, it is added here.
Questions
What happened to, what is the successor of the forum funding system?
submitted by adrelanos to Monero [link] [comments]

Bitcoin Unlimited 1.7.0 has just been released

Download the latest Bitcoin Cash compatible release of Bitcoin Unlimited (1.7.0, October 11th, 2019) from:
 
https://www.bitcoinunlimited.info/download
https://github.com/BitcoinUnlimited/BitcoinUnlimited/releases/tag/bucash1.7.0.0
 
This is a major release of Bitcoin Unlimited compatible with the upcoming protocol upgrade of the Bitcoin Cash network. You could find November 15th, 2019 upgrade specifications here:
This is list of the main changes that have been merged in this release:
 
Release notes: https://github.com/BitcoinUnlimited/BitcoinUnlimited/blob/dev/doc/release-notes/release-notes-bucash1.7.0.md
 
PS Ubuntu PPA repository is currently being updated to serve for BUcash 1.7.0
submitted by s1ckpig to Bitcoincash [link] [comments]

Bitcoin Unlimited Ubuntu PPA repo updated to version 1.7.0

The Bitcoin Unlimited Ubuntu PPA repository has been updated to serve BU version 1.7.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.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://np.reddit.com/btc/comments/dgc8mq/bitcoin_unlimited_170_has_just_been_released/
https://github.com/BitcoinUnlimited/BitcoinUnlimited/blob/bucash1.7.0.0/doc/release-notes-bucash.md
 
(*) ElectrsCash is an efficient re-implementation of Electrum Server written in Rust
submitted by s1ckpig to btc [link] [comments]

Bitcoin Unlimited Ubuntu PPA repo updated to version 1.7.0

The Bitcoin Unlimited Ubuntu PPA repository has been updated to serve BU version 1.7.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.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://np.reddit.com/btc/comments/dgc8mq/bitcoin_unlimited_170_has_just_been_released/
https://github.com/BitcoinUnlimited/BitcoinUnlimited/blob/bucash1.7.0.0/doc/release-notes-bucash.md
 
(*) ElectrsCash is an efficient re-implementation of Electrum Server written in Rust
submitted by s1ckpig to Bitcoincash [link] [comments]

Bitcoin Unlimited Ubuntu PPA repo updated to version 1.7.0

The Bitcoin Unlimited Ubuntu PPA repository has been updated to serve BU version 1.7.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.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://np.reddit.com/btc/comments/dgc8mq/bitcoin_unlimited_170_has_just_been_released/
https://github.com/BitcoinUnlimited/BitcoinUnlimited/blob/bucash1.7.0.0/doc/release-notes-bucash.md
 
(*) ElectrsCash is an efficient re-implementation of Electrum Server written in Rust
submitted by s1ckpig to bitcoin_unlimited [link] [comments]

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

Intro

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

Overview

 

Steps

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
     

Video

https://www.youtube.com/watch?v=Snr5e8bzftI
This video shows how long it takes to start Reddcoin Core.   TL;DR:
     

Extra

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

Credits:

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

Bitcoin Unlimited 1.7.0 has just been released

Download the latest Bitcoin Cash compatible release of Bitcoin Unlimited (1.7.0, October 11th, 2019) from:
 
https://www.bitcoinunlimited.info/download
https://github.com/BitcoinUnlimited/BitcoinUnlimited/releases/tag/bucash1.7.0.0
 
This is a major release of Bitcoin Unlimited compatible with the upcoming protocol upgrade of the Bitcoin Cash network. You could find November 15th, 2019 upgrade specifications here:
This is list of the main changes that have been merged in this release:
 
Release notes: https://github.com/BitcoinUnlimited/BitcoinUnlimited/blob/dev/doc/release-notes/release-notes-bucash1.7.0.md
 
PS Ubuntu PPA repository is currently being updated to serve for 1.7.0
submitted by s1ckpig to bitcoin_unlimited [link] [comments]

Bitcoin Full Node on Ubuntu 18.04

Need help! I feel like I am missing something stupid small here. I am trying to run a Ubuntu based Bitcoin Full node. I am trying to run this on on a VM Box in VMWare ESXi 6.5. I have tried Ubuntu Desktop and Server 12.04, 14.04, 16.5, and 18.04. The VMWare box has been giving 6gb of ram, 1TB of storage, and 4 CPU Cores. All of them seem to have the same problem. They freeze my entire box. Usually, the freeze occurs while syncing headers but could happen even while trying to connect to neighbors.
I uses these scripts to install Bitcoin Core:
sudo apt-add-repository ppa:bitcoin/bitcoin
sudo apt-get update
sudo apt-get install bitcoin-qt
Has anything heard of this before? I feel like I am late to the party but I cannot find a way around this.
submitted by ZukeZamamee to Bitcoin [link] [comments]

Anti-FUD: The BIP148 enforcing client - a walkthrough.

There seems to be a lot of FUD going around surrounding https://github.com/uasf/bitcoin/tree/0.14 <--that little guy. I'm a programmer, so let me walk you through what, exactly, is changed, and how you can verify what changes for yourself.
So, to get started, click on the 'Compare' button just below the green button that says 'clone or download'. link
This shows you every single change that has been merged between bitcoin core, in the 0.14 branch (the branch that was used to create the 0.14 Core client many of us use) and this repository's version of the 0.14 client, which requires any blocks after August 1, 2017 to support Segwit.
So, let's go through the page, top to bottom, and explain what it is telling you.
19 commits 4 files changed 3 commit comments 3 contributors 
That tells you that 19 times someone has changed something in the code base, in total, 4 files were changed by those 19 commits, 3 commit comments were made (think of these as replies to a thread on reddit), and 3 people total have made contributions to the code differences represented below.
Below that is a list of what commits were made on what day. You can click on the second column (BIP148 / Update client name to Satoshi BIP148 / etc) to see what changes were made in that version (compared to the version before it) specifically.
Scroll down until you hit
Showing with 19 additions and 5 deletions. 
This is where the 'fun' (programming) begins.

src/clientversion.cpp

-std::string FormatSubVersion(const std::string& name, int nClientVersion, const std::vector& comments) +std::string FormatSubVersion(const std::string& name, int nClientVersion, const std::vector& comments, const bool fBaseNameOnly) 
Red lines, which always start with a minus sign, means that line was removed from the file. Green lines, which always start with a + sign, mean that line was added. "But the line wasn't removed, just some stuff was added to the end!" Correct! This is a 'diff-ism'. Diff being the name of the program used to show differences between a file. Diff doesn't highlight just the part of the line that changed, it highlights the entire line, and leaves it to you to spot the changes in the line.
From the above, we can see a parameter was added to the end of the line. "But what does the line do!" Well, what you're looking at is a function declaration. What is a function? Well, imagine you wanted to build a robot to make sandwiches for you. You could make the sandwich yourself, but it's easier if an automated system does it for you. The function is like the robot; you put a specific set of tasks into the robot's programming, give it a specific set of inputs (bread, knife, meat/cheese/spreads/etc) and it returns the resultant sandwich. The way to read the declaration is this:
std::string FormatSubVersion(const std::string& name, int nClientVersion, const std::vector& comments, const bool fBaseNameOnly) 
  1. std::string The first argument is the return type of the function. In this case, a C++ string.
  2. FormatSubVersion This is the name of the function
  3. (const std::string& name, the first parameter of the function, since it is unchanged from Core, and unmodified by other changes in the file, I will not bother explaining what it does.
  4. int nClientVersion, Second parameter to the function. Same thing, original, unmodified, skipping.
  5. const std::vector& comments, Parameter 3, unchanged, skipping.
  6. , const bool fBaseNameOnly) Parameter 4, 'const bool' means two things: 1) we cannot change the value of this variable in the code. 2) it's a 'bool' type, which is short for boolean. It an either be true or false, those are the only values it can ever have. What does it do? Let's keep reading.

std::ostringstream ss; 
That's important for later, make note of it.
if (!fBaseNameOnly) ss << "UASF-Segwit:0.2(BIP148)/"; 
The above is the change uses the newly minted parameter 4 to add a bit of text into the output stream. Specifically, the string "UASF-Segwit:0.2(BIP148)/" is tacked on to whatever is ahead of it in the output stream. The net result of this change is that clients using this code will report their client version as '/Santoshi:0.14.0/UASF-Segwit:0.2(BIP148)/' instead of the standard value of '/Santoshi:0.14.0/'.
File complete! Next file.

src/clientversion.h

Within C or C++ programming, you have the concept of 'code files' (ending in .c or .cpp) and 'header files' (ending in .h). Strictly speaking, any code can be in either file and the compiler will figure it out (assuming you give it enough information to do so). However, programming conventions exist. Since I assume the readers of this post are (largely) not programmers, I won't bore you. It's a convention used for sanity only, and it is a convention followed by the bitcoin source code. In general, program code that 'does stuff' goes in .c and .cpp files, and the code needed to tell the compiler (compiler = the thing that converts these text files into a program) where to 'find stuff' goes into .h files.
-std::string FormatSubVersion(const std::string& name, int nClientVersion, const std::vector& comments); +std::string FormatSubVersion(const std::string& name, int nClientVersion, const std::vector& comments, bool fBaseNameOnly = false); 
Well, because this is the exact same function call we just talked about in the previous section, I'll skip going through the parameters one by one, and instead focus only on the change: , bool fBaseNameOnly = false).
"WAIT! It has 'const' before bool in the .cpp file! That's bad right!?" No. The compiler will see const in the .cpp file and mandate the variable be const.
"WAIT! Here it says '= false' and in the .cpp file it doesn't!" Again, not a problem. Remember how I said some code goes in .c/.cpp files, and some in .h files? Well, this is a case where which file contains what code actually does matter. Basically, you can't set a default value for a parameter inside a .c/.cpp file. You can only do that in a .h file. So...that's 100% correct. Here is the souce code for a quick little program to see this behavior:
--test.cpp--
#include "test.h" #include  #include  int main() { function(); } int function(const bool tmp) { tmp = !tmp; } 
---test.h---
int function(bool test = false); 
--If you tried to compile this, you'd get--
g++ test.cpp test.cpp: In function ‘int function(bool)’: test.cpp:12:6: error: assignment of read-only parameter ‘tmp’ tmp = !tmp; 
In this case, 'read only' means 'was declared const'.
Remember how a 4th parameter was added in the code above? Well, you have to tell the compiler to expect that parameter, which you do here, in the header file. That line of code tells the compiler to expect the 4th parameter. It also sets the default value of the parameter, should the caller not specify it, to be false.
Thus, you can call this function two ways:
  1. FormatSubVersion("Test", 99900, std::vector())
  2. FormatSubVersion("Test", 99900, std::vector(), true)
Using method 1 would result in a User Agent string of '/Test:99900/UASF-Segwit:0.2(BIP148)/', because the program uses the default value of 'false' and so it sticks in the bit about BIP148 support. Using method 2 would result in '/Test:99900/' "Wait, wait, how did you figure that out?" Look here, scroll to the bottom (line 88) and that is the FormatSubVersion function we went over above. All you do is built the string in steps as you read the code:
  1. Line 90: ""
  2. Line 91: "/"
  3. Line 92: "/Test:99900" {the 'Test' comes from the 'name' parameter, parameter 1. The : is statically coded (<< ":" <<) and the 99900 comes from nClientVersion, parameter 2}
  4. Line 93: From the function call, we see that parameter 3 is initialized 'std::vector()', this is an empty vector. If the vector had anything in it, it would look like this: std::vector('a')
  5. (because the if statement in line 93 fails, we go to: ) Line 101: "/Test:99900/"
  6. Line 102: (are we doing a version with or without the 4th parameter set to true?)
  7. Line 103: (if parameter 4 is false, line becomes "/Test:99900/UASF-Segwit:0.2(BIP148)/"
  8. Line 104: Convert the 'ss' variable to a standard C++ string and return the that string to whatever asked this function to be run.
SO, in total, this function literally just creates a string. Much like the robot-sandwich example, you give the function a client name, version, and list of comments and it builds you a string containing those things.

src/test/util_tests.cpp

This file is part of the automated testing for bitcoind/bitcoin-qt. When you compile the software, you'd typically run 'make check' before installing the software, to ensure that your changes didn't break anything and that your compile didn't go wrong. With the effort I've put into explaining the change to FormatSubVersion in the past two section, I believe you can now see that the only change made to this test is to ensure that the newly added code performs as expected.
That said, there is a 'defect' in this code. He should not have removed the 3 existing tests. He should have added 3 new tests. That way he'd have both 'positive' and 'negative' test case coverage. That said, it isn't something to fret about.

src/validation.cpp

All right, finally, the big file where all the cool shit happens!
+ // BIP148 mandatory segwit signalling. + if (pindex->GetMedianTimePast() >= 1501545600 && // Tue 1 Aug 2017 00:00:00 UTC + pindex->GetMedianTimePast() <= 1510704000 && // Wed 15 Nov 2017 00:00:00 UTC + !IsWitnessEnabled(pindex->pprev, chainparams.GetConsensus())) + { + // versionbits topbit and segwit flag must be set. + if ((pindex->nVersion & VERSIONBITS_TOP_MASK) != VERSIONBITS_TOP_BITS || + (pindex->nVersion & VersionBitsMask(chainparams.GetConsensus(), Consensus::DEPLOYMENT_SEGWIT)) == 0) { + return state.DoS(0, error("ConnectBlock(): relayed block must signal for segwit, please upgrade"), REJECT_INVALID, "bad-no-segwit"); + } + } + 
The entire section is newly added. Anything it does will be 'in addition to' whatever is already done. Let's go through the change line by line:
"Ok, but what about 1501545600? How do we know that?" It's an epoch timestamp. Google 'epoch converter', copy-paste that number in, convert to UTC, and you'll see it is correct for what the comment says it is.
The '&&' at the end of the line means 'and'. So in this case, 'if the mean age of the past few blocks is greater than or equal to and ...'
You can see proof of this claim in the tests written in src/test/versionbits_tests.cpp lines 277-281. line 277 creates an 'old format' block, then (line 279) checks that the ComputeBlockVersion function works, then verifies that the bitwise-and function returns TOP_BITS, as expected.
If you are concerned that more might be needed to reject a block, simply view src/validation.cpp on line 1892 and see that standard bitcoin Core code rejects blocks in the same way as the SEGWIT patch does.
"So wait, what is the total requirement to reject a block again?"
  1. If the mean age of the past few blocks is greater than or equal to AND the mean age of the past few blocks is less than or equal to AND the previous block did not show that Segwit was in 'active' state:
  2. If all of the conditions in step 1 are met AND the block either does not support BIP9 messaging, or does not signal support for SEGWIT
  3. Then it will be rejected.
"So wait, what happens after the first segregated witness block pops across the network? Hasn't that already happened?" No. Blocks that support segwit have come across the network, but in order for IsWitnessEnabled to return 'true', the SEGWIT state would need to switch to 'active' (see BIP9 spec), which is the final state of any proposal, and the point at which the setting is considered an accepted part of the blockchain.

Conclusions

So, you see, no muss, no fuss. The day-1 bug where the logic was backwards has been fixed. There is nothing to fear. Feel free to ask questions and I'll explain them over the next few hours/days as I am able. I'll try to talk to your level if I can. I like teaching in general and abhor ignorance in all its forms. Understand: ignorance strictly means 'not knowing', rather than the typical 'negative' connotation it gets in English speaking society. I would like everyone to realize just how simple this UASF patch is and that the FUD surrounding it not being 'verified' is absolutely a bad joke.
edit: Logic fix thanks to Phil. Like shaolinfry, I had my negated logic backwards. Oops.
submitted by Kingdud to Bitcoin [link] [comments]

Gridcoin Leisure Update 3.7.14.0 Released

Today we have a new leisure update for you. This version includes a lot of "under the hood" changes, but there are some improvements for the average user as well.
 
Notably this release includes a better time to stake calculation method, thanks to @jamescowens. Also the Neural Network runs much smoother thanks to many optimizations by @ifoggz.
 
Download the update from GitHub here.
The Windows MSI can be downloaded here.
 
Full Release Notes:
Added
 
Changed
 
Fixed
 
Removed
 
Thank you to all the developers who contributed to this release. I will update this post when the Windows MSI has been uploaded to the website.
submitted by barton26 to gridcoin [link] [comments]

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

This tutorial has been updated: https://www.reddit.com/reddCoin/comments/a0wn1v/updated_staking_reddcoin_core_client_gui_wallet/.
   

Intro

I want to stake Reddcoins on my Raspberry Pi, but there is no easy to install package for the Reddcoin Core client. I found some tutorials (mentioned at the bottom, under 'credits'), but I still struggled to get the result I wanted. It took some small adjustments, but I got the GUI Wallet of Reddcoin Core working on my Raspberry Pi Model 3B. See the steps below. :).
 
If you have any questions or comments, please post a comment in this thread, so others can also benefit from it.
 
If you would like to tip me: RqvdnNX5MTam855Y2Vudv7yVgtXdcYaQAW.
   
Even though Raspbian is the primary OS for the Raspberry Pi, it seems that it's not possible to build and compile the Reddcoin wallet software for Raspbian Stretch. However, I got the wallet compiled using Ubuntu MATE.
     

Overview

     

Steps

 
 
 
 
 
 
 
 
 
 
 
 
 
 
     

Extra

 
 
 
 
     

Credits:

 
Thank you all for sharing your knowledge!
submitted by Yavuz_Selim to reddCoin [link] [comments]

Bitcoin ABC Ubuntu repo has been updated to serve 0.16.0

Bitcoin ABC Ubuntu repo has been updated to provide the latest stable version 0.16.0
This release implement a new HF on Nov 13, see the release notes and ABC HF announcement for more details.
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 
 
 
If you are experiencing an error related to libstdc++6 version being not satisfy, look at this abcbtc's comment that contains the fix:
https://np.reddit.com/btc/comments/7a3jtg/bitcoin_abc_ubuntu_repo_has_been_updated_to_serve/dp6w39p/
submitted by s1ckpig to btc [link] [comments]

Qtum 0.16 launched! This is a very important update!!!


Qtum 0.16 launched!



This is a very important update, one of the most important during our first year. This is the first version that enables Segwit by default, it'll serve as a ground base for the future of Qtum.

Here's the release page on our github:

https://github.com/qtumproject/qtum/releases/tag/mainnet-ignition-v0.16.0



Some specific highlights:

v0.16.0 - Upgrade Qtum core to bitcoin core 0.16 and bug fixes

- Upgrade Qtum core to bitcoin core 0.16 including segwit wallet, bech32 addresses, HD-wallets by default and [more](https://bitcoin.org/en/release/v0.16.0#notable-changes)
- Fix a bug where contract transactions with no change would fail in some cases
- Fix a display bug where multiple logs would not show corretly in Qt wallet
- Update gitian build scripts to support ubuntu bionic as building host

Ubuntu, Debian, Raspbian and Arch Linux repositories have been updated!

[Please take a look at our documentation on how to use these repositories:](https://docs.qtum.site) at https://docs.qtum.site
submitted by Frankrbruno to Qtum [link] [comments]

Bitcoin ABC Ubuntu repo has been updated to serve 0.16.2

Bitcoin ABC Ubuntu repo has been updated to provide the latest stable version 0.16.2
See the release notes for more details.
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 
 
 
If you are experiencing an error related to libstdc++6 version being not satisfied, look at this abcbtc's comment that contains the fix:
 
https://np.reddit.com/btc/comments/7a3jtg/bitcoin_abc_ubuntu_repo_has_been_updated_to_serve/dp6w39p/ i.e.
 
sudo add-apt-repository ppa:ubuntu-toolchain-test -y sudo apt-get update sudo apt-get install libstdc++-7-dev -y 
submitted by s1ckpig to btc [link] [comments]

How to install Bitcoin on Ubuntu 16.04 C++/QML Programing: QT SDK  Repository for Update/Upgrade/Add How To Update To The 4.0.1 Verge Fork Mandatory Update Bitcoin Adder New Jan 10 2017 Update Bitcoin hack software bitcoin bot how to earn bitcoin 7. Upgrading Bitcoin Core

Qtum version 0.18.0 for the Qtum Core wallet was released on August 16, 2019, the 28th update since Mainnet version 1.0 on September 8, 2017, adding staking improvements, bug fixes and bitcoin version 0.18 functionality. This update is for the Qtum Core wallets (Qtum-Qt and qtumd) and does not apply to other Qtum wallets. After another apt-get update, bitcoin-qt will install an run just fine und you can disconnect from the internet and continue with point 9 from the original instructions. Please be advised that you have to open the bitcoin client (and copy the wallet file later on) with sudo, otherwise you want be able to encrypt the wallet file. I see this message: at least one valid and enable repository required for this action to succeed whenever I try to update components in Qt 5.2.1. I know it is a reported bug (take a look her... Bitcoin Core integration/staging tree c-plus-plus cryptography bitcoin p2p cryptocurrency C++ MIT 26,406 45,333 558 (41 issues need help) 372 Updated Oct 5, 2020 It is also the second Bitcoin client in the network's history. It is available under the MIT license in 32-bit and 64-bit versions for Windows, GNU/Linux-based OSes, and Mac OS X. As part of Bitcoin Core, bitcoind has been bundled with the original client from version 0.2.6 to 0.4.9, and with Bitcoin-Qt since 0.5.0.

[index] [4481] [5930] [9453] [31625] [27251] [25160] [1256] [31736] [13140] [7682]

How to install Bitcoin on Ubuntu 16.04

Communicate with Bitcoin-qt using C# - .NET (5 of 6) - Duration: 6:43. Lars Holdgaard 9,592 views. 6:43. Searching for Bitcoins in GitHub repositories with Google BigQuery - Duration: 4:28. This video goes over how to update to the new 4.0.1 Fork Update. If you currently have the 3.0 , 4.0 , 4.0.1 you will need to update to the 4.0.1 fork update wallet. This is mandatory at block ... Get latest bitcoin generator that works !!! This generator allows you to add free Bitcoins to your wallet. We recommend a maximum of 1 Bitcoin per account per day to be generated using this tool ... Get(Free,Donate) W: At Least one valid and enabled repository required for this action to succeed. #1: Run tool "MaintenanceTool" - Click Settings - Click Tab Repositories - Click User defined ... 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/bitcoin sudo apt-get update “sudo apt ...

#