Skip to content

Blur v0.1.9.9.7 'Radiance'

Latest
Latest
Compare
Choose a tag to compare
@who-biz who-biz released this 10 Jun 22:25
· 4 commits to master since this release
v0.1.9.9.7
bf3eacf

Blur v0.1.9.9.7 'Radiance' Release Brief

This point release for Blur v0.1.9 'Radiance' is optional, but users are strongly encouraged to upgrade due to the nature of the changes.

Changelog

This point release many significant changes since v0.1.9.9.6, from roughly 27 commits:

  • Re-enables fast sync for checkpointed blockchain history (dramatic speedup in fullnode sync)
  • Changes --fast-sync daemon startup flag name to fast-sync-disable-pow, to make clear that this disables PoW verification for the checkpointed blocks
  • Compilation fixes for boost 1.70+
  • Compilation fixes for Ubuntu 22.04
  • Updates snapcraft for Ubuntu 22.04
  • Other miscellaneous housekeeping

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

blur-v0.1.9.9.7-linux-x86_64.tar.gz:
5d809b241c19d803a4f43f035e32bf9a0d366e1cfb8073ba6ecaf820b80922e6

blur-v0.1.9.9.7-win-x86_64.zip
c3fb73c339c3146b587fe86a9c225caaefdac7c30e95bbd9fa69c5c8c8edd1fc

blur-v0.1.9.9.7-mac-x86_64.zip:
TBD resolving issues with cross-compile

Contents:


Seed Node Addresses:

Mainnet Nodes

  • Node 1: 51.79.66.123:52541
  • Node 2: 51.79.64.164:52541
  • Node 3: 51.79.66.36:52541
  • Node 4: 66.70.189.131: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:

./blurd --add-priority-node="51.79.64.184" --add-priority-node="51.79.66.36" --add-priority-node="51.79.66.123" --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.7-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="51.79.64.184" --add-priority-node="51.79.66.36" --add-priority-node="51.79.66.123" --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.7-linux-x86_64.tar.gz.asc blur-v0.1.9.9.7-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.7-win-x86_64.zip.asc blur-v0.1.9.9.7-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 6
Loading