Blur v0.1.8 'Shift'
This is a mandatory update, which primes the testnet & mainnet for v9 hardfork, and integrates the latest improvements to the network.
This major release will upgrade the network to v0.1.8 'Shift'. Hardfork v9 is set for block 211,000, you must update your node by then to remain on the mainchain Changes since the last minor release include:
- Set height for Hardfork v9 at 211,000
- Update checkpoints to ~block 206,000
- Update CMakeLists.txt to remove submodule checks, BerkeleyDB, and to link boost locale library properly
locale library in correct place - Update Makefile for Windows 64-bit build with MSYS2
- Removal of git submodule for unbound dependency, to get rid of gratuitous warnings on Windows static compile
- Fixes a bug where sending coins to yourself would result in an inability to rescan the blockchain or display any new transactions
- Rework of new algorithm for upcoming v9 hardfork
Please take even a small portion of your hashpower and direct it toward our testnet so that we may effectively test the new mining algorithm. To do so, start up the daemon with the option --testnet
. You will also need to start blur-wallet-cli
with the same --testnet
flag, to generate a testnet address for mining.
Please verify your download by comparing the file's sha256sum with these posted below:
blur-v0.1.8-linux-x86_64.tar.gz:
1812d3a36db8d4472d473b75e46ee580800df534e3a6e98e1e63547934bc8824
blur-v0.1.8-ubuntu-18.04.1-x86_64.tar.xz:
54a719efff01c7be80e4cee8928f522cbdf51a092edb2e70ffb4b74aeba1dc94
blur-v0.1.8-mac-x86_64.tar.xz:
3e761bb5bec81882d88289ce8e09e2c1e62ca9ba5ce08f5e7fdb83867622b698
blur-v0.1.8-win-x86_64.tar.gz:
fa56167c490ca3d7c7006d19b100e3343ec5656502c6673b0f26d5e5d0049904
blockchain-bootstrap.zip:
bf6cfa42d808b67695366472d6784404270933dd0f45acd7e1d178672f7f098e
Contents:
- Linux & Mac Instructions
- Windows Instructions
- Blockchain Bootstrap Procedure
- How to Verify These Binaries
Seed Node Addresses:
Mainnet Nodes
- Node 1: 178.128.191.245:13894
- Node 2: 178.128.180.136:13894
- Node 3: 178.128.186.101:13894
Testnet Nodes
- Node 1: 206.189.163.61:11111
- Node 2: 104.248.69.152:11111
- Node 3: 104.248.182.234:11111
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 178.128.191.245:13894 --seed-node 178.128.180.136:13894 --add-priority-node 178.128.186.101: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-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=178.128.191.245:13894 --seed-node=178.128.180.136:13894 --add-priority-node=178.128.186.101: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=178.128.191.245:13894
seed-node=178.128.186.101:13894
seed-node=178.128.180.136:13894
p2p-bind-port=13894
rpc-bind-port=13895
Start the daemon file with the following command and flags:
blurd.exe --seed-node 178.128.191.245:13894 --seed-node 178.128.180.136:13894 --seed-node 178.128.186.101: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.8-linux-x86_64.zip.asc blur-v0.1.8-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) <[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.8-win-x86_64.zip.asc blur-v0.1.8-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.