Blur v0.1.8.2 'Shift'
This update is strongly recommended for all nodes. While the update is non-mandatory, there are quite a few changes that have taken place since the last release. Most notably, you will find that the release v0.1.8.1 will not sync if it is being run for the first time. This is due to the seed node addresses changing, and will not affect nodes that are already running. If you use this release instead, the switch is automatic.
Changes since the last release (v0.1.8.1) include:
- Fixes for snapcraft.io build system.
- Fixes for depends build system located in
blur/contrib/depends
- Fixes a memory leaking issue on Windows 64-bit
- Command line interface now uses ANSI Colors for Windows 10.
- Fixes scope for wallet locking in Windows 10 (boost)
- Wallet refresh text is changed from
blocks received
toblocks refreshed
for disambiguation - Fixes double counting of outs in wallet if more than one pubkey (monero)
- Implements a block for the
merge_mining
tag in tx extra fields starting at v10. - Brings most of the
blur/src/crypto
library current with Monero. - Brings most of the
blur/src/common
library current with Monero. - Fixes for Cmake build system (linking of Readline)
- Fixes password handling bug from #24 for Windows platform
- Hides certain values when daemon is launched using
restricted-rpc
option. - Updates seed node addresses for mainnet.
- Updates network type (
nettype
) handling for wallet and daemon. - Updates incoming and outgoing connection limits for daemon.
Please verify your download by comparing the file's sha256sum with these posted below:
blur-v0.1.8.2-linux-x86_64.tar.gz:
41808e8a6a7db6145ccf260e6e054f41aa384f0df4479e664e90c56260be5449
blur-v0.1.8.2-win-x86_64.zip:
25361d1229f01e37871d292a6b5dcb9aa0ad6f1c7eefc6ad7bd6cab9a8789efd
blur-v0.1.8.2-mac-x86_64.zip:
d72b2e2f8bf6b02af507fd03966f49b316dd6a770eddc3fa10a6eb28187e5392
blur-blockchain-bootstrap.zip:
153214c1701d594eb03c530d9e6ed256d20e31d59b08dccf1eef287553ffa560
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.8.2-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.8.2-linux-x86_64.tar.gz.asc blur-v0.1.8.2-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.8.2-win-x86_64.zip.asc blur-v0.1.8.2-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 --batch-size=186000
. You should be bootstrapped and immediately synced up to block ~295,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