who-biz released this Feb 2, 2019 · 1 commit to v0.1.8.3 since this release

This update is MANDATORY for all nodes. This release fixes a number of bugs (some of which would be critical if exploited correctly). Nodes that do not update will be able to keep mining on their current version, but v0.1.8.3 brings with it performance improvements, apart from the bug fixes, so you will want to update. This will be the final release before a hardfork to update our PoW algorithm. This mandatory update is necessary to ensure the safety of the chain prior to the release of v0.1.9. Please upgrade as soon as possible.

Changes since the last release (v0.1.8.2) include:

Upgrades Qt package from 5.7 -> 5.9.7 in depends build system.

build system. Upgrades OpenSSL package from 1.0.1k -> 1.0.2q in depends build system.

build system. Remove unused packages from depends build system (bdb, miniupnpc)

build system (bdb, miniupnpc) Fixes compilation errors for GCC 8.1 & MSYS.

Remove old seed node IPs for mainnet & testnet from hardcoded nodelist.

Updates the snapcraft script for building of snaps with correct format (previous method has been deprecated).

Updates Docker build script to function properly with our current codebase.

Adds checkpoints at heights (0, 250000, and 265000) as well as checksum for checkpoints.dat file.

file. Addition of const keyword within hash-relevant files to ensure uniformity of parameter interpretation within slow-hash function.

keyword within hash-relevant files to ensure uniformity of parameter interpretation within slow-hash function. Properly renames scope within translation files for wallet API.

Properly renames systemd service.

Updates crypto library with a 32-byte equality function using constant time (Monero #3999)

Fixes a bug with json serialization (Monero #4831)

Optimizes some of the operations within the slow-hash function for a bit higher hashrates across the board.

Updates easylogging++ library (rebase to Monero)

Updates epee library (with bugfixes from Monero)

Updates relevant files within blur/src/common to accomodate the above bugfixes and rebase.

to accomodate the above bugfixes and rebase. Fixes a critical vulnerability that could be catastrophic if source code is changed to increase the premine amount, or if transaction version is incremented. Please see 5398d18 for details on this vulnerability and the fix.

for details on this vulnerability and the fix. Fixes a vulnerability present in hardcoded seed node definitions, that could result in an attacker communicating with the network, in place of proper seed nodes. This bug was also due to an omission within our upstream. Please see commit aad8177 for the relevant fix.

for the relevant fix. Fixes the wrongful display of red warning messages about incoming connections, despite incoming connections being allowed (introduced in v0.1.8.2).

Please verify the following sha256sums against those of the files you download:

blur-v0.1.8.3-linux-x86_64.tar.gz: 5c9340245e50f94a081cc7e30cc4f005dc3a494958e7f8a4ea55e3b1fce01012

blur-v0.1.8.3-mac-x86_64.zip:

2b882bc361dae1c6cc4d9948ba6332c0cb6c031bfefe628313342f15632fa23b

blur-v0.1.8.3-win-x86_64.zip:

7d26db1404810eb214dc4db6fe639205b1c7a58c79fb585f2e678df309c2b91b

blur-blockchain-bootstrap.zip:

Contents:

Seed Node Addresses:

Mainnet Nodes

Node 1: 66.70.189.131:13894

Node 2: 66.70.189.183:13894

Node 3: 66.70.188.178:13894

Linux & Mac Instructions

Download and unzip the compressed binaries. Start the daemon with the command ./blurd Your daemon will then begin to sync with the network.

Please add the seed node addresses below if you have trouble syncing.

Open a terminal and launch the daemon executable with the following options:

./blurd --add-priority-node 66.70.189.131:13894 --seed-node 66.70.189.183:13894 --add-priority-node 66.70.188.178:13894 --p2p-bind-port 13894 --rpc-bind-port 13895 --rpc-bind-ip 127.0.0.1

Alternatively, you may use the file named blurd.conf located at blur/util/conf/blurd.conf in source code, and copy that file into your binary directory.

Launch the daemon with the option --config-file ~/blur/util/conf/blurd.conf

Once you're fully synced, start the wallet with the command: ./blur-wallet-cli

Follow the prompts to create a wallet file & password, then enter the command:

start_mining [# of threads]

Where [# of threads] is the number of threads within your CPU that you wish to dedicate to mining BLUR.

Example: start_mining 4

The wallet should output the message Mining started in daemon . You can track your progress in the daemon output. There is a slight delay between mined blocks shown in the daemon, and the reflection in your wallet's balance. Type help into either command line interface for a list of commands and their function(s).

Windows Instructions

Download and unzip the compressed binaries. Double click the file named blurd.exe. Your daemon will then begin to sync with the network. Once it is fully synced, double click the blur-wallet-cli.exe to open the wallet.

For Sync issues on Windows:

Open Windows Powershell (Windows Key + X, then click powershell (non-admin) and type cd Downloads/blur-v0.1.8.3-win-x86_64 to switch to the directory you extracted the binaries into. Launch the daemon executable with the following options:

blurd.exe --add-priority-node=66.70.189.131:13894 --seed-node=66.70.189.183:13894 --add-priority-node=66.70.188.178:13894 --p2p-bind-port 13894 --rpc-bind-port 13895 --rpc-bind-ip 127.0.0.1

Once you're fully synced, start the wallet by double clicking the file named blur-wallet-cli.exe

Follow the prompts to create a wallet file & password, then enter the command:

start_mining [# of threads]

Where [# of threads] is the number of threads within your CPU that you wish to dedicate to mining BLUR.

Example: start_mining 4

The wallet should output the message Mining started in daemon . You can track your progress in the daemon output. There is a slight delay between mined blocks shown in the daemon, and the reflection in your wallet's balance. Type help into either command line interface for a list of commands and their function(s).

Please add the seed nodes if you have trouble syncing. To do so, locate the file named blurd.conf (located at: blur/util/conf/blurd.conf ) and copy/move it into the same directory as your binaries. Add to that file the following lines:

seed-node=66.70.189.131:13894

seed-node=66.70.188.178:13894

seed-node=66.70.189.183:13894

p2p-bind-port=13894

rpc-bind-port=13895

Start the daemon file with the following command and flags:

blurd.exe --seed-node 66.70.189.131:13894 --seed-node 66.70.189.183:13894 --seed-node 66.70.188.178:13894 --p2p-bind-port 13894 --rpc-bind-port 13895 --rpc-bind-ip 127.0.0.1 --config-file=.\blurd.conf

How To Verify These Binaries:

Download the zip archive of your choice and the accompanying '.asc' file. If you haven't already, download and install GnuPG.

Linux

Type the following command into a terminal: gpg --keyserver sks-keyservers.net --recv-keys D5C9054050576902

After downloading they public keys, check their fingerprint: gpg --fingerprint D5C9054050576902

You should see the output:

pub rsa4096 2018-06-07 [SC]

F3FE DCCF A90C 5683 1318 3C33 D5C9 0540 5057 6902

uid [ unknown] Blur Network (Blur: The Private Cryptocurrency) <admin@blur.cash>

sub rsa4096 2018-06-07 [E]

Then, verify the files you've downloaded with: gpg --verify blur-v0.1.8.3-linux-x86_64.tar.gz.asc blur-v0.1.8.3-linux-x86_64.tar.gz The output should say "Good Signature." The warning message is due to no trust index being assigned to the signature, simply ignore it.

Windows

Open cmd.exe and type: "C:\Program Files\Gnu\GnuPg\gpg.exe" --keyserver sks-keyservers.net --recv-keys D5C9054050576902

After downloading they public keys, check their fingerprint: "C:\Program Files\Gnu\GnuPg\gpg.exe" --fingerprint D5C9054050576902

You should see the output:

pub rsa4096 2018-06-07 [SC]

F3FE DCCF A90C 5683 1318 3C33 D5C9 0540 5057 6902

uid [ unknown] Blur Network (Blur: The Private Cryptocurrency) <admin@blur.cash>

sub rsa4096 2018-06-07 [E]

Move into your downloads folder with cd C:\Users\[your username]\Downloads Then, verify the files you've downloaded with: "C:\Program Files\Gnu\GnuPg\gpg.exe" --verify blur-v0.1.8.3-win-x86_64.zip.asc blur-v0.1.8.3-win-x86_64.zip The output should say "Good Signature." The warning message is due to no trust index being assigned to the signature, simply ignore it.

Blockchain Bootstrap Procedure

Download & extract the `blur-blockchain-bootstrap.zip` archive. Upon extraction, you should be left with a folder named `export`. Move the export folder into your `blur-net` data directory.

This should result in following structure:

[your user's data directory]/export/blockchain.raw

On Linux/Mac: ~/.blur-net/export/blockchain.raw

On Windows: %PROGRAMDATA%\blur-net\export\blockchain.raw or %APPDATA\Roaming\blur-net\export\blockchain.raw