Skip to content

Blur v0.1.9.9.1 'Radiance'
Compare
Choose a tag to compare
@who-biz who-biz released this 14 Sep 03:06
· 2 commits to v0.1.9.9.1 since this release
v0.1.9.9.1
c67acb5

Blur v0.1.9.9.1 'Radiance' Release Brief

This point release for Blur v0.1.9 'Radiance' is optional, and for the primary purpose of fixing the adversely affected hashrates within the previous release, as well as a bug that slowed blockchain sync significantly. All binaries released after block 342000 should still be operational, as there has not been a hardfork since that height. However, sync issues may be encountered when syncing from scratch with other versions. As such, it is recommended to use v0.1.9.9.1 for all users.

Changelog

The full list of changes since Blur v0.1.9.8.1 can be found here. These include 34 commits, within which are the following significant changes/improvements:

  • Fixes an operator precedence error in simplewallet, which would cause wallets to register as Stagenet wallets erroneously (cdb5cf2)
  • Silences a warning seen when compiling with clang, which indicated a null dereference within the mempool, potentially causing undefined behavior (3ab0bd4 - taken from XMR#3619)
  • Removes a seemingly incorrect condition for transaction evaluation in core, that would treat transactions over an arbitrary size of 100 differently than those that were of normal size. When this occurred, the transaction was swapped with the previous transaction seen with BAD_SEMANTICS_SIZE in a separate container, and that previous transaction was cleared (80a7341)
  • Adds an RPC method for extracting a block's merkle root. The method takes an array of transaction hashes (b.miner_tx + tx_hashes), or a block hash as parameters (3ff97bf)
  • Properly initializes libsodium with a call to sodium_init(). Prior to this, libsodium was not initialized properly, which could compromise any components of the library that were used in code. This issue appears to remain unresolved in Monero (4ce7f5d)
  • Removes batch resizing in the database, which would previously occur every 1000 blocks. Resizing the memory map in LMDB is never needed for 64-bit architectures (32-bit builds are not officially supported in BLUR), so it has been removed due to a perceived possibility of causing issues with an excess function (49de156)
  • Added more informative logging messages for when peers are added to the blocked nodes list automatically (9f8a0a4)
  • Fixes linking of lrelease-qt5 when building from source on Fedora/Red Hat (e7a8561)
  • Adds an RPC method for base64 encoding. The method takes a c-style unsigned char array as a bytes parameter, and prints those bytes as a string, encoded in base64, using the epee library.(4cd30f5)
  • Switches precedence of preferred peers when connecting to other nodes from peerlist. Prior to this change, anchorlist peers were preferred over whitelisted ones. (cf98530)
  • Fixes an error in max_outgoing_connections that would erroneously cap the maximum outgoing connections at the default value of 8, specifically if a user disabled the limit by passing a startup flag of --out-peers=-1 (cf98530)
  • Adds backward-cpp from Google to enable safe and informative stack traces in the event of abnormal exit codes such as segmentation faults on Debug builds. (412b9fa) code repository for backward-cpp: https://github.com/bombela/backward-cpp
  • Partially fixes an issue within blockchain syncing (5f5f886, 5d46d62, and 681d28d)

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

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

blur-v0.1.9.9.1-ubuntu-debian-x86_64.tar.gz:
(Use this if you distro has an older glibc version, such as Ubuntu 16.04, or Debian 9)
3b350bd845fb49992e6e19edacd62c751df3877b8dc065f07e878e4aea257efb

blur-v0.1.9.9.1-win-x86_64.zip
5a578e357e4d998b73b3b0e95c5e8d926ed47d7078029cab29d9bd92c3d3e669

blur-v0.1.9.9.1-mac-x86_64.zip:
284751003c70031fb2443342db5c8e68f2d59820d17abbfea64bc384fe18a0bf

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.1-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.1-linux-x86_64.tar.gz.asc blur-v0.1.9.9.1-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.1-win-x86_64.zip.asc blur-v0.1.9.9.1-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