Blur v0.1.9 'Radiant Flux'
This update is MANDATORY for all nodes. This release upgrades the network at block 342,000 to version 10. All nodes must update by the upgrade block, or you will no longer be mining on the main chain. This upgrade brings with it a PoW algorithm upgrade to CryptoNight Dynamic v2. Please upgrade as soon as possible. Any daemons still on version v0.1.8.x at the fork block will cease to be relevant to the network.
Changes since the last release (v0.1.8.3) include:
- 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 block difficulty as an arbitrary value in the calculation of iterations (at various points during the slow-hash calculation).
- Addition of different functions for discernment of pre-v10 PoW hashes and post-v10 PoW.
- 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-linux-x86_64.tar.gz:
b6832c5eab1b0a909ff30b7206e0e84cb8bacce914a841a7c19917a1f0bfdab1
blur-v0.1.9-mac-x86_64.zip:
dbbbe163fbe54377ae361741a257e892e6f5a040f4ad73fc144457d6cd0565cd
blur-v0.1.9-win-x86_64.zip:
6cdb42217c1b6ffda71c9e77680b9281b76d98b77240051598696d38aea5c3a0
blur-blockchain-bootstrap.zip:
fb7e00a5cfd19951c3db0283f716991e53657aa39e8fe834033c348f3efc4194
Contents:
- Linux & Mac Instructions
- Windows Instructions
- How to Verify These Binaries
- Blockchain Bootstrap Procedure
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.9-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) <[email protected]>
sub rsa4096 2018-06-07 [E]
Then, verify the files you've downloaded with: gpg --verify blur-v0.1.9-linux-x86_64.tar.gz.asc blur-v0.1.9-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-win-x86_64.zip.asc blur-v0.1.9-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
Import the blockchain file with: ./blur-blockchain-import
. You should be bootstrapped and immediately synced up to block ~335,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