Skip to content

Blur v0.1.7.5.1 'Lustrous Nebula (CNv8)'
Compare
Choose a tag to compare
@blur-network blur-network released this 25 Oct 20:11
v0.1.7.5.1
f50e764

This update is mandatory for all nodes and is a point release for v0.1.7.5

sha256sums:
blur-v0.1.7.5.1-win-x86_64.zip:
94339456b02aaa163e1ba3051765898d6c9cfb46971e5efe4c3d225094d7fdef
blur-v0.1.7.5.1-mac-x86_64.zip:
0ad48502e906963459a87b2713e6c7237f4b7956ecba37c10e6ea7285174c032
blur--v0.1.7.5.1-ubuntu18-x86_64.tar.gz: a3a558a04c1be2a2c81e4a987831eae2a34d5f268a2236c93178fc1374262a38

Contents:


Seed Node Addresses:

  • Node 1: 178.128.191.245:14894
  • Node 2: 178.128.180.136:14894
  • Node 3: 178.128.186.101:14894

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 --seed-node 178.128.191.245:14894 --seed-node 178.128.180.136:14894 --seed-node 178.128.186.101:14894 --p2p-bind-port 14894 --rpc-bind-port 14895 --rpc-bind-ip 127.0.0.1

Alternatively, you may create a config file titled blurnet.conf in the directory located at ~/.blurnet on Linux. Add the following lines to that config file:

seed-node=178.128.191.245:14894
seed-node=178.128.186.101:14894
seed-node=178.128.180.136:14894

./blurd --seed-node 178.128.191.245:14894 --seed-node 159.203.48.201:14894 --seed-node 178.128.180.136:14894 --seed-node 178.128.186.101:14894 --config-file ~/.blurnet.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.7.5-win-x86_64 to switch to the directory you extracted the binaries into. Launch the daemon executable with the following options:

blurd.exe --seed-node 178.128.191.245:14894 --seed-node 178.128.180.136:14894 --seed-node 178.128.186.101:14894 --p2p-bind-port 14894 --rpc-bind-port 14895 --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, you may create a config file titled blurd.conf and place it in the same directory as the binaries. Add to that file the following lines:

seed-node=178.128.191.245:14894
seed-node=178.128.186.101:14894
seed-node=178.128.180.136:14894
p2p-bind-port=14894
rpc-bind-port=14895

Start the daemon file with the following command and flags:

blurd.exe --seed-node 178.128.191.245:14894 --seed-node 178.128.180.136:14894 --seed-node 178.128.186.101:14894 --p2p-bind-port 14894 --rpc-bind-port 14895 --rpc-bind-ip 127.0.0.1 --config-file=.\blurnet.conf

Blockchain Bootstrap Procedure

Download & extract the `blockchain_bootstrap.zip` archive. You should have a folder named `export`. Move the export folder into your `blurnet` data directory.

This should result in following structure:
[your user's data directory]/export/blockchain.raw

Linux/Mac: ~/.blurnet/export/blockchain.raw
Windows: %PROGRAMDATA%\blurnet\export\blockchain.raw or %APPDATA\Roaming\blurnet\export\blockchain.raw

Import the blockchain file with: ./blur-blockchain-import --batch-size=130000. You should be bootstrapped and immediately synced up to block 129,000 if the chain data was imported properly. Sometimes, batch transactions cause problems importing. If you still have problems, try disabling batch transactions with the --batch option and an argument of 0. For additional startup flags, start with ./blur-blockchain-import --help

How To Verify These Binaries:

At minimum, please verify these sha256sums to ensure you downloaded the correct file.

blur-v0.1.7.5-linux_x86_64.tar.gz: 28efaa4bd0bd2d99f6506c8d7c6d4b10a17cb89440d3e328bf08097ff8d09aac

blur-v0.1.7.5-mac-x86_64.zip: 0ad48502e906963459a87b2713e6c7237f4b7956ecba37c10e6ea7285174c032

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.7.5-linux-x86_64.zip.asc blur-v0.1.7.5-linux-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.

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.7.5-win-x86_64.zip.asc blur-v0.1.7.5-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.

Assets 7
Loading