Skip to content

@who-biz who-biz released this Jul 30, 2020

Blur v0.1.9.9.5 '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 includes the following significant changes since v0.1.9.9.4, from rougly 22 commits:

  • Silences errors on unknown commands in protocol (90433bb)
  • Changes to openssl build options, in depends build system (f215455 & 6b5a086)
  • Upgrade boost to version 1.69 in depends build system (2ffd7ac)
  • Changes to workflow file for GitHub Actions CI (4a928c4)
  • Simplification (and slight speed-up) of code for dynamic portion of proof-of-work algorithm (6b64964)
  • Removal of ldns as optional dependency, as all DNS-related functionality was removed quite some time ago (a457426)
  • Addition of note to README.md about macOS cross-compilation (a457426)
  • Revert performance timer files back to original state at initialization of blur repo, to fix an AOCC/clang compiler error (3bec88a)
  • Fix readline library linking, and detection (9a4f0e8)
  • Change public linkage to private in wallet (6a849da)
  • Switch from memcpy to memset in critical portion of proof-of-work algorithm (59a2a71)
  • Update snapcraft build for v0.1.9.9.4 (8ab93f7)
  • Standardize notation for command-line options in README.md (cfed164)
  • Implementation of new DB resizing mechanics, reduce initial mapsize, and always enable auto-resizing (ba05bbc, 8fa9b93, & 456f21b
  • Removes a strange behavior inherited from Monero in protocol, where data directory would change if blurd was communicating on a non-standard port (fe85b45)
  • Quicker connection with network, due to adding seed nodes on daemon init (b60a4f6)
  • Updates version for v0.1.9.9.5 release (0b836f8)
  • Fix for cross-compilation Makefile entry for Windows, compiled on Linux host (a45f2d0)
  • Removes problematic detection & linking of ICU_LIBRARIES in wallet (019aa08)

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

blur-v0.1.9.9.5-linux-x86_64.tar.gz:
a7f582489495d00e47cc7c9fb00cdc06ca1210cf565f8265c6b9f2cbf9137663

blur-v0.1.9.9.5-win-x86_64.zip
27084a74e30ad47140e5f088b2c978f035670199ef6bbdb89db592347bc325c7

blur-v0.1.9.9.5-mac-x86_64.zip:
a8dfe1ce5cbe3d376f074c2e61a05aa1f743e4ac25eec949682e121cc18964eb


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:

./blurd --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.

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

@who-biz who-biz released this Jun 5, 2020 · 1 commit to v0.1.9.9.4 since this release

Blur v0.1.9.9.4 '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.

This release fixes a bug in DB map resizing, and removes fluffy blocks from protocol.

Please note, binaries were compiled for this commit, rather than the tagged commit.

Changelog

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

  • Fixes a memory map resizing error in LMDB
  • Remove fluffy blocks
  • TBD

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

blur-v0.1.9.9.4-linux-x86_64.tar.gz:
e7d0b5dbc393cbc639ba3c09be3abd10a0ef194ee37c23d5d74e647b18e888be

blur-v0.1.9.9.4-win-x86_64.zip
7f6c7221e573175049775ed536c12ebca8e75f86c1a41725cf8e0112a6e3d0f2

blur-v0.1.9.9.4-mac-x86_64.zip:
46d9562e358d072e47f47130bb70e5ff963d587e3121cab3e4e9da4ecb91b287


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

@who-biz who-biz released this May 18, 2020

This is an intermediary release within v0.1.9.9.3.

This release differs from v0.1.9.9.3 in:

  • Removal of fluffy_blocks from protocol.
  • Fix chain-forking issue by calling m_hardfork->reorganize_from_block_height() during each call of m_blockchain.prepare_handle_incoming_blocks().

Due to the removal of fluffy_blocks, this release will show the following message, fairly frequently:

[P2P2]  ERROR   cn.block_queue  src/cryptonote_protocol/cryptonote_protocol_handler.h:91        Unknown command:2008
[P2P2]  ERROR   net     src/p2p/net_node.h:142  Unknown command:2008  

Simply diregard this. It should not affect network connectivity adversely.


Please check the following sha256 sums, against your downloaded files:

blur-v0.1.9.9.3e-linux-x86_64.tar.gz:
ce9ce544a0158799cfdd2d4617c0988e8e9e95b157f271fd3743facc2aec06ca

Assets 4

@who-biz who-biz released this Mar 6, 2020

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

@who-biz who-biz released this Nov 28, 2019

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) <admin@blur.cash>
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) <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.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

@who-biz who-biz released this Sep 14, 2019 · 2 commits to v0.1.9.9.1 since this release

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
Pre-release

@who-biz who-biz released this Sep 2, 2019

Blur v0.1.9.9 'Radiance' Release Brief

This point release for Blur v0.1.9 'Radiance' is optional, and for the primary purpose of silencing a warning message that incorrectly claimed that an update was necessary.

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

blur-v0.1.9.9-linux-x86_64.tar.gz:
1147090254dadcdff75775af978ca9d03ef11b0772a43175b21d3a9930e03ca0

blur-v0.1.9.9-ubuntu-debian-x86_64.tar.gz:
2594f0f71d48d7ed18aadf4decdcca6d84af5162ca342f0addb04a68ca8951b0

blur-v0.1.9.9-mac-x86_64.zip:
2a28b278d2894cf51920e524538c65800e84f77adf55684cb5cf7cb20c6f2667

blur-v0.1.9.9-win-x86_64.zip:
198d449a1af3b70e1b07ee706b1e5996403241fd755beb66a45ff5a53ea292e7

Assets 10

@who-biz who-biz released this Jul 12, 2019 · 163 commits to master since this release

Blur v0.1.9.8.1 'Radiance' Release Brief

This update is STRONGLY RECOMMENDED for all nodes, as it includes a bugfix for the Monero wallet vulnerability (disclosed July 2nd, 2019), that could result in fake transaction amounts (controlled by an attacker) being displayed, within an incoming transfer.

This release also fixes a bug in the previously released v0.1.9.8 that caused a failure when trying to open wallet files created prior to v0.1.9.8.

This release did not port XMR's patch directly. Therefore, if you are a virtual service provider, it is critical that you ignore (or continue to ignore) coinbase tx's when scanning outputs.

This is precautionary, and can be achieved with the command set refresh-type no-coinbase issued to blur-wallet-cli for each wallet that is receiving transfers. This only needs done once, and is a persistent setting. If you are unsure of your wallets' settings, you can view them by issuing the command set with no parameters. In the list that displays, you will see the following:

[wallet bL3nhB]: set		
seed = English
always-confirm-transfers = 1
print-ring-members = 0
store-tx-info = 1
auto-refresh = 1
refresh-type = full
priority = 0
confirm-missing-payment-id = 1
ask-password = 1
unit = blur
min-outputs-count = 0
min-outputs-value = 0.000000000000
merge-destinations = 0
confirm-backlog = 1
confirm-backlog-threshold = 0
confirm-export-overwrite = 1
refresh-from-block-height = 511095
auto-low-priority = 1
segregate-pre-fork-outputs = 0
key-reuse-mitigation2 = 0
subaddress-lookahead = 50:200
segregation-height = 0

Your value for refresh-type should read full or no-coinbase. If it says full, you have not disabled coinbase scanning.

Due to past issues with miner transactions, we strongly recommend that any exchange, custodial service, etc. (which receives BLUR at centralized wallets) does not allow their users to mine BLUR to custodial wallet addresses. This will ensure that your wallets do not receive fake transfer amounts from the XMR vulnerability (even if this patch does not fully address the issue). This may also prevent future bugs, if other similar bugs are found within miner transactions, from impacting your wallets.

Please see the changelog below for a record of other relevant changes/improvements.

Changelog

  • RPC methods for previously removed save_graph commands have now also been removed (3f3ac3c)
  • Updated snapcraft build to use ubuntu18 core (fc1aebc)
  • Removed unsafe use of std namespace from wallet2.cpp to use safely scoped types, instead (8844314)
  • Fixed inconsistency in non-const operator within tx_pool & sortting (d52daa3)
  • Removed an unused lambda capture from net_node.inl (ea7e7f0)
  • Added libhydrogen as a submodule for future use (1e66139)
  • Removed the last remnants of ZeroMQ dependency & associated macros (5c84e0c)
  • Fixed static linking of libncurses on macOS (10832b8)
  • Removed the last remnants from Unbound and MiniUPnP dependencies (10832b8)
  • Fixed a failure to retrieve HF version 1 from a non-existent database (6571eac)
  • Bugfix for wallet output scanning & removal of optimize-coinbase refresh type (81bdea5)
  • Removal of light_wallet-specific functions and API endpoints (81bdea5)
  • Fixed a mathematical omission in block verification, that caused the wrong PoW hash to be computed for blocks prior to hardfork v7. Verification now properly computes the PoW hash for each block, at every hardfork & algorithm variant (92748d5)

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

blur-v0.1.9.8.1-linux-x86_64.tar.gz:
7d6e72eb0d75cc353a5cb0b220427a88aaf5e1b8696f738f3b7455a35b9bac9d

blur-v0.1.9.8.1-mac-x86_64.zip:
85e077b63f9414ad3540abd2001321c786b8a68187aaa54f2aad2110a6efaa43

blur-v0.1.9.8.1-win-x86_64.zip:
f2237d0c72ee2f239f41d94d3dd36f898d441a01f28e69d400c47aa9eb4e056b

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

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.8.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: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

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.8.1-linux-x86_64.tar.gz.asc blur-v0.1.9.8.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.8.1-win-x86_64.zip.asc blur-v0.1.9.8.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 8
Pre-release

@who-biz who-biz released this Jul 10, 2019 · 166 commits to master since this release

This tagged release has a bug within slow-hash that caused wallets not to open. Please use v0.1.9.8.1 instead.

Assets 2

@who-biz who-biz released this Jun 19, 2019 · 1 commit to v0.1.9.7 since this release

This is a point release the fix sync-related issues for users who are having connectivity issues on v0.1.9.6.

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

blur-v0.1.9.7-linux-x86_64.tar.gz:
29c9a72126fe1bae3908bb05c32d4c3294b45b654221d37e7113a6a9713df103

blur-v0.1.9.7-mac-x86_64.zip:
58a4092ef2bb8e89d6e5af9f1f57b46104f1c84708ed874aafd3774eea53f57b

blur-v0.1.9.7-win-x86_64.zip:
dd02cdb9abdb8106e713ac219bbd1656a8b9ea0c575e91c18ca6df8c4f4fbc89

Assets 7