Skip to content

Blur v0.1.9.9.2 'Radiance'
Compare
Choose a tag to compare
@who-biz who-biz released this 28 Nov 09:26
v0.1.9.9.2
468e463

Blur v0.1.9.9.2 'Radiance' Release Brief

This point release for Blur v0.1.9 'Radiance' is optional, and for the primary purpose of fixing a DoS vector within protocol communication, as well as hashrate improvement over v0.1.9.9.1 for most devices (much more pronounced on AMD cpus).

Changelog

This point release includes the following significant changes since v0.1.9.9.1, from 22 commits:

  • Addition of inline function helpers, employing bitwise operators (in place of + operators) in longhash calculation (e3f9b00)
  • Modification to hardfork function parameters, to make proper use of const directive, and reference types (72ff766, OBOE is reverted in later commit - c1f89b5)
  • Modifies the CMake build system, such that p2p and protocol libraries are no longer compiled as plugins. They are now compiled uniformly in the cmake build, as libraries (b027fc1)
  • Overhaul of git and Monero-style versioning systems (b027fc1)
  • Removes remnants of optimize-coinbase wallet scanning behavior, which no longer exists (bf134d8)
  • Modifies estimate_blockchain_height function in wallet to actually grab height from daemon RPC interface, rather than doing guesswork based of difficulty (a733e52)
  • Mining algorithm's speed-critical dynamic iteration function is rewritten for better speed, and annotated for comprehension (f274087, ec4856a, and 1bfc819)
  • Fixes some parts of parallel build hanging when building with GCC (cef3176)
  • Hardcodes checkpoints for blocks 400,000 - 700,000 (f2a1b8a)
  • Removes buggy check against parent hash (that does not exist) that was allowing DoS of peers (0f148c6)
  • Fixes a broken libsodium link in depends build system (16dae5f)

The full list of changes since Blur v0.1.9.9.1 can be found here.

Please verify the following sha256sums against those of the files you download:

blur-v0.1.9.9.2-linux-x86_64.tar.gz:
(Use this if you distro has a more recent glibc version, such as Ubuntu 18.04, Debian 10, Arch)
16e42bd8b0c4e2ce8eebed5a54e981177b925b7e4706f954fc238d3a6aedb813

blur-v0.1.9.9.2-ubuntu-debian-x86_64.tar.gz:
(Use for older glibc versions, distros like Debian 9 and Ubuntu 16)
d44af8f76c6b9210a915ae882e985db3ce5a125c616401ae779b5f2fecdca21f

blur-v0.1.9.9.2-mac-x86_64.zip:
6ed214f913b815d74628a6560003b6c83e48477474c5952a9c13ba1215cda12c

blur-v0.1.9.9.2-win-x86_64.zip
0c85d5a128d832fcd1f30060bae81c2a5711e3f8f86f12c3553c397a14c576cd

Contents:


Seed Node Addresses:

Mainnet Nodes

  • Node 1: 66.70.188.178:52541
  • Node 2: 66.70.189.131:52541
  • Node 3: 66.70.189.183: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-priority-node=66.70.188.178:52541 --add-priority-node=66.70.189.183:52541 --add-priority-node=66.70.189.131:52541 --p2p-bind-port 52541 --rpc-bind-port 52542 --rpc-bind-ip 127.0.0.1

If you are connecting to nodes on your local LAN, you will need to add those nodes with their local IPs, and append the flag --allow-local-ip to the startup flags above.

Wait for sync to complete, open a new tab or terminal window, and then start the wallet with:

./blur-wallet-cli

Follow the prompts to setup a new wallet. When prompted for the password, the CLI will not show a password as you type, as echo has been turned off for password entry.

Record the information for your wallet.

You can mine from your wallet, using the start_mining <threads> command -- but using that method directly from the wallet is NOT recommended.

Secure way to mine: Once you've generated a wallet address, issue the following command to a running daemon:

start_mining <address> <# of threads>

Example: start_mining bL4PdWFk3VVgEGYezGTXigHrsoJ3JGKgxKDi1gHXT7GKTLawFu3WMhu53Gc2KCmxxmCHbR4VEYMQ93PRv8vWgJ8j2mMHVEzLu 4

Or: Use the following startup flags when launching the daemon:

./blurd --start-mining"<BLUR address>" --mining-threads="<num. threads>"

Example: ./blurd --start-mining=bL4PdWFk3VVgEGYezGTXigHrsoJ3JGKgxKDi1gHXT7GKTLawFu3WMhu53Gc2KCmxxmCHbR4VEYMQ93PRv8vWgJ8j2mMHVEzLu --mining-threads 4

You should see a message for each thread that reads: Mining started for thread[0] or something similar.

To view your hashrate in real-time, use the command show_hr.

Whenever you find a block, your daemon will show a bold message with the block # found. It is normal to experience a slight delay between that message and the balance reflecting in your wallet.

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.9.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.188.178" --add-priority-node="66.70.189.183" --add-priority-node="66.70.189.131" --p2p-bind-port="52541" --rpc-bind-port="52542" --rpc-bind-ip="127.0.0.1"

If you are connecting to nodes on your local LAN, you will need to add those nodes with their local IPs, and append the flag --allow-local-ip to the startup flags above.

Alternatively, you may start the daemon by double-clicking the blurd.exe file.

You will see a pop-up from your firewall. Be sure to check the box next to "Private Networks" if you are on a private network, or your daemon will not be able to sync with the network. If you daemon stalls while syncing, close and restart the program. You will not lose any blocks you have already synced with. Once your daemon is synced with the network...

Start the wallet by double-clicking the blur-wallet-cli file.

Follow the prompts to setup a new wallet. When prompted for the password, please note that the CLI will not show a password or indicate your keystrokes as you type.

Follow the prompts to setup a new wallet. When prompted for the password, the CLI will not show a password as you type, as echo has been turned off for password entry.

Record the information for your wallet.

You can mine from your wallet, using the start_mining <threads> command -- but using that method directly from the wallet is NOT recommended.

Secure way to mine: Once you've generated a wallet address, issue the following command to a running daemon:

start_mining <address> <# of threads>

Example: start_mining bL4PdWFk3VVgEGYezGTXigHrsoJ3JGKgxKDi1gHXT7GKTLawFu3WMhu53Gc2KCmxxmCHbR4VEYMQ93PRv8vWgJ8j2mMHVEzLu 4

Or: Use the following startup flags when launching the daemon, from Powershell:

.\blurd.exe --start-mining"<BLUR address>" --mining-threads"<num. threads>"

Example: .\blurd.exe --start-mining="bL4PdWFk3VVgEGYezGTXigHrsoJ3JGKgxKDi1gHXT7GKTLawFu3WMhu53Gc2KCmxxmCHbR4VEYMQ93PRv8vWgJ8j2mMHVEzLu" --mining-threads="4"

You should see a message for each thread that reads: Mining started for thread[0] or something similar.

To view your hashrate in real-time, use the command show_hr.

Whenever you find a block, your daemon will show a bold message with the block # found. It is normal to experience a slight delay between that message and the balance reflecting in your wallet.

You should see the message: Mining started in daemon

Switch back to the terminal or tab in which your daemon is running, and type show_hr for real-time hashrate monitoring. For further commands in either the wallet or the daemon, type help into either CLI. Note that the commands for the daemon and wallet are different.

Whenever you find a block, your daemon will show a bold message with the block # found. There is a slight delay between that message and the balance reflecting in your wallet.

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.9.2-linux-x86_64.tar.gz.asc blur-v0.1.9.9.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.9.9.2-win-x86_64.zip.asc blur-v0.1.9.9.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.

Assets 10
Loading