Skip to content

Blur v0.1.6.1 Amorphous Glare Updated'
Compare
Choose a tag to compare
@blur-network blur-network released this 11 Jul 05:40
· 663 commits to master since this release
v0.1.6.1
0cdd3c0

This update is mandatory for all nodes in the network. This update includes various bugfixes and improvements from upstream, including monero #3985, sync improvements, and finalized node updates. Those nodes are as follows:

Node 1: 178.128.191.245:14894
Node 2: 178.128.180.136:14894
Node 3: 178.128.186.101:14894
Node 4: 159.203.48.201:14894

Additionally, an API is now live at http://explorer.blur.cash/api/ (for example, the word 'transactions' at the end of that address will return a list of the 25 most recent transactions. It is a JSON-API and docs can be found on the blur-explorer repository page. It is tied directly to the block explorer which is also now live at http://explorer.blur.cash

For the fastest sync with the network run the daemon with the following command and options:

Linux:
./blurd --seed-node 178.128.191.245:14894 --seed-node 159.203.48.201.55:14894 --seed-node 178.128.180.136:14894 --seed-node 178.128.186.101:14894

Windows
blurd.exe --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

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.6.1-linux-x86_64.zip.asc blur-v0.1.6.1-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.6.1-win-x86_64.zip.asc blur-v0.1.6.1-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.

Linux Binaries & Instruction

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. To do so, 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=159.203.48.201:14894
seed-node=178.128.186.101:14894
seed-node=178.128.180.136:14894

Alternatively, open a terminal and launch the daemon executable with the following options:

./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/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 Binaries & Instruction

Download and unzip the compressed binaries. Double click the file named blurd.exe. Your daemon will then begin to sync with the network.

Please add the seed nodes if you have trouble syncing. To do so, you may create a config file titled blurnet.conf in the directory located at C:\Program Data\blurnet on Windows. Add to that file the following lines:

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

Alternatively, open Windows Powershell and type cd Downloads/blur-v0.1.6.1-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 159.203.48.201:14894 --seed-node 178.128.180.136:14894 --seed-node 178.128.186.101:14894 --config-file C:\Program Data\blurnet\blurnet.conf

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).

Blockchain Bootstrap Procedure

Download & extract the export.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

You should immediately be bootstrapped and synced up to block 65,000, if the chain data was imported properly.

Assets 9
Loading