Skip to content

Blur v0.1.9.1 'Radiant Flux'
Compare
Choose a tag to compare
@who-biz who-biz released this 01 Mar 02:01
· 465 commits to master since this release
v0.1.9.1
e893575

This update is MANDATORY for all nodes. This release fixes the sync issues that started at the fork, and upgrades the network to version 10. The port numbers have been changed for P2P/RPC/0MQ communication due to the fork issues, and malicious traffic from another project. The new ports are P2P: 52541, RPC: 52542, 0MQ: 52543. This upgrade brings with it a PoW algorithm change to CryptoNight Dynamic v2. Please upgrade as soon as possible. You may delete your old data directory, as files will now be stored in a different directory.

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

  • Port changes for all protocols (P2P, RPC, 0MQ)'
  • Updates the seed nodes list for v10 hardfork
  • Changes the name of the data directory from blur-net to blurnetwork
  • Fixes the fork issues that were present, starting at block 342,000.
  • Adds a checkpoint for the valid fork block at 342,000.
  • Updates the testing suite.
  • PoW hash is now displayed by default in RPC calls such as get_block.
  • Changes the address prefixes for mainnet to decimal format rather than hexidecimal (for clarity)
  • Removes the mm_tag blocking previously scheduled for v10. This is not yet necessary.
  • Sets fork height for v10 at block 342,000.
  • Implements a new PoW, which uses the previous blocks hash (taken from the block header), truncated after the sixth character, and converted to an unsigned integer from hexidecimal. That number is then used as an arbitrary value in the calculation of iterations (at various points during the slow-hash calculation).
  • Users can now see the PRNG value generated by the method detailed above, as well as the per-block iterations by typing set_log 1 into their daemon.
  • Variable iterations window for longhash algorithm increased from 4,096 to 32,768.

Please verify the following sha256sums against those of the files you download:
blur-v0.1.9.1-linux-x86_64.tar.gz:
36b335de47e4a4f9948ffc9619517d7ce5ec624fe534fe170b216047f3fc16bd

blur-v0.1.9.1-mac-x86_64.zip:
7dd930ada937356978fe2b3afb63022db32a95bd8b12e078e72ebb86ccad3781

blur-v0.1.9.1-win-x86_64.zip:
b2dab2a96d2432572556bbf23f872628fab6938d07fbab79468e75044c63503a

blur-blockchain-bootstrap.zip:
eb336d07818df247e446fe315ff2c469eb92393ffc07d2b4d1d038cf35ff0929

Contents:


Seed Node Addresses:

Mainnet Nodes

  • Node 1: 45.33.92.232:52541
  • Node 2: 45.79.85.65:52541
  • Node 3: 212.71.234.44:52541

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-exclusive-node=45.33.92.232:52541 --add-exclusive-node=212.71.234.44:52541 --add-exclusive-node=45.79.85.65:52541 --p2p-bind-port 52541 --rpc-bind-port 52542 --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.9.1-win-x86_64 to switch to the directory you extracted the binaries into. Launch the daemon executable with the following options:

blurd.exe --add-exclusive-node=45.33.92.232:52541 --add-exclusive-node=212.71.234.44:52541 --add-exclusive-node=45.79.85.65:52541 --p2p-bind-port 52541 --rpc-bind-port 52542 --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=45.33.92.232:52541
seed-node=45.79.85.65:52541
seed-node=212.71.234.44:52541
p2p-bind-port=52541
rpc-bind-port=52542

Start the daemon file with the following command and flags:

blurd.exe --seed-node 45.33.92.232:52541 --seed-node 212.71.234.44:52541 --seed-node 45.79.85.65:52541 --p2p-bind-port 52541 --rpc-bind-port 52542 --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) <[email protected]>
sub rsa4096 2018-06-07 [E]

Then, verify the files you've downloaded with: gpg --verify blur-v0.1.9.1-linux-x86_64.tar.gz.asc blur-v0.1.9.1-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) <[email protected]>
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.9.1-win-x86_64.zip.asc blur-v0.1.9.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.

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 `blurnetwork` data directory.

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

On Linux/Mac: ~/.blurnetwork/export/blockchain.raw
On Windows: %PROGRAMDATA%\blurnetwork\export\blockchain.raw

Import the blockchain file with: ./blur-blockchain-import. You should be bootstrapped and immediately synced up to block ~342,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

Assets 10
Loading