Skip to content

Blur v0.1.9.9.3 'Radiance'
Compare
Choose a tag to compare
@who-biz who-biz released this 06 Mar 22:35
v0.1.9.9.3
7eb142c

Blur v0.1.9.9.3 'Radiance' Release Brief

This point release for Blur v0.1.9 'Radiance' is optional. However, users will notice significant synchronization speedups, potentially improved privacy w.r.t node identification over peer communication, slightly improved miner speed on (at least) linux, and improved network connectivity.

Please note, due to compilation difficulty, the binaries for macOS have various non-reproducible modifications to CMake/build environment. The nearest commit to the code used, can be found here: 54b839d.

Changelog

This point release includes the following significant changes since v0.1.9.9.2:

  • Switched to C99 standard-compliant function timespec_get in src/crypto/oaes_lib.c for linux. Note: due to issues with lacking compliance w.r.t. to C standard in Windows and Mac builds, the deprecated ftime function is still used on these platforms. (7eb142c)
  • Fixed an implicit-copy compilation error on GCC 9+, in epee library, and associated connection_contexts (fb135d7)
  • Removed deprecated mmitigate_rop compiler option (fb135d7)
  • Load peers_state.bin from file onp2p init. This had previously been removed, due to concerns with security/privacy. However, its removal adversely impacted network connectivity fairly dramatically. (fb135d7)
  • Fixed stack tracing using backward-cpp library.
  • Added workflows for GitHub actions. (Run on all branches prefixed with dev-, and master on push)
  • Fixes fee-split issue from #24, in wallet (3a08268)
  • Fixes for testing suite (424671d)
  • Removes libunwind linking in common library (dcff0c2)
  • Removes CMAKE_DL_LIBRARIES linking in OpenSSL, due to concerns with dynamic loading and paths (82e4516).
  • Block synchronizing count increased from 20 to 100, so that messages are only printed to stdout every 100 blocks. (f385034)
  • Removes compatible_version tests from DB, and associated VERSION macro (2f4cc1f)
  • Add failure for rct::identity and crypto::null_key scenarios to devicelibrary (f640346)
  • Adds a separate testnet genesis transaction, so that cross-chain communication will not occur. For some reason, nettype was not being checked properly by daemons, resulting in communication across network types. This commit fixes that issue, as the genesis tx will not validate on the incorrect network (ca4ae10)
  • Untangles dependencies, and properly compiles libraries as shared or static. Previously, some libraries always compiled as static, while others always compiled as shared libraries.

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

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

blur-v0.1.9.9.3-linux-x86_64.tar.gz:
d3cbe61724c34035daad9bc2ee638b08953fda014030f6ceda18d6923ce08cc7

blur-v0.1.9.9.3-win-x86_64.zip
e53901913a746f508302106545af2f9400d5bdb637fab6c501957a77fc777039

blur-v0.1.9.9.3-mac-x86_64.zip:
f0eb328b1daca4850b3f0fcc4cecdbdd831ec48b277f2cc61b8060347d05beb8

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
  • Node 4: 51.79.66.123:52541
  • Node 5: 51.79.64.164:52541
  • Node 6: 51.79.66.36: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.3-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) <admin@blur.cash>
sub rsa4096 2018-06-07 [E]

Then, verify the files you've downloaded with: gpg --verify blur-v0.1.9.9.3-linux-x86_64.tar.gz.asc blur-v0.1.9.9.3-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) <admin@blur.cash>
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.3-win-x86_64.zip.asc blur-v0.1.9.9.3-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 8
Loading