10 Jul 15:16

who-biz

e536593

Blur v0.1.9.8 'Radiance' Pre-release

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

19 Jun 21:13

who-biz

v0.1.9.7

645a735

Blur v0.1.9.7 'Radiance'

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

24 May 19:21

who-biz

v0.1.9.6

bac38c0

Blur v0.1.9.6 'Radiance'

Blur v0.1.9.6 'Radiance' Release Brief

This update is STRONGLY RECOMMENDED for all nodes, as it includes very significant improvements to security and privacy. You may continue mining on the older versions, but hashrate should be improved noticeably with these changes.

This point release greatly lessens the potential for misuse of the network, so we strongly encourage everyone to update as soon as possible. Most of these updates are improvements upon our parent codebase, and are seen nowhere else in CryptoNote. If you are part of another CN community, please consider informing others about these changes, as they may reduce the likelihood that the network(s) are misused maliciously. Disclosures about relevant vulnerabilities were made where reasonably possible. Ultimately, we feel that patching these issues are the only way they will get fixed, and as a result, have included citations where the changes took place in each commit, as diligently as we could.

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

Changelog

Changes since the last release (v0.1.9.5) include the following, from roughly 75 significant commits:

Removal of ALLOW_DEBUG_COMMANDS conditional which could make timing attacks a lot easier. (Technically from v0.1.9.5, but did not go into to detail until other projects were notified)
Removal of proof_of_trust function that caused every daemon who performed a handshake to hash a zeroed pubkey with keccak, as well as transmitting the host computer's operating system each time, in its response to a proof_of_trust p2p request.
- The zeroed pubkey was removed from src/cryptonote_config.h. Within the global scope,P2P_REMOTE_DEBUG_PUB_KEY was defined as a string of zeroes.
- This behavior facilitates a type of attack proven effective by Dan Bernstein in his paper on cache-timing attacks. The attack in the paper linked to, has a victim host computer hash a zeroed string repeatedly, so that the attacker can determine the victim's AES private keys. In CryptoNight, keccak is used to initialize the scratchpad, and within key expansion for the "AES" pseudo-rounds.
- Additional known information about the host, improves efficacy of this attack further. This is the same vulnerability from the Spectre and Meltdown bugs. These changes (removal of code) prove that those aspects of the p2p protocol are entirely irrelevant to the network's primary functionalities.
Removal of SMTP-related code in epee library, as well as munin plugins (ca4cae4).
- Note that these were entirely unutilized, but due to the epee library being a source of at least one large issue in the past (DoS bug - disclosed by Cisco Talos) this library will see further removal of unused code in an effort to prevent misuse.
- SMTP-related functions were of particular concern, due to the fact that this library was employed in the past as part of a spam botnet. We will be moving away from this library as soon as practicable. (You can follow progress here: #51)
P2P no longer restores its state from peers_state.bin on each restart. Each time nodes are restarted, they will load a default (new) configuration. You may safely remove peers_state.bin. Full removal of the file has been held off until the de-initialization functions can be safely patched away from storing their state within that file (2f3d38a#diff-c02157891426370c008d7076b723128cL88)
Fix accounting for additional_tx_pubkeys or R' in scenarios where we have additional keys, but don't "need" to account for them. (https://github.com/blur-network/blur/blob/master/src/cryptonote_core/cryptonote_tx_utils.cpp#L320)
All DNS-related code has been removed, as well as all instances of the function get_address_from_str_or_url. The latter has been patched over with the get_address_from_str function seen elsewhere in code. (ab4f780). URI-endcoded addresses for QR-code generation, and etc. remain intact and functional.
Together with OpenAlias, the URL handling and DNS-specific code could lead to misuse of the network. As a result, the OpenAlias functions have also been excavated (9e96a69)
Without any need for DNS records or DNSSEC, the dependency in libunbound has been removed. (ab4f780)
Clean up of some p2p code for node communication. Sync speed is further improved.
Removal of extra parameters in start_mining command (i.e. allow_background_mining and ignore_battery). Prior to these changes, the miner would treat anything it was pointed at as a URL if it was not one of: testnet, stagenet, or mainnet addresses. This is no longer the case. (36e03a6#diff-ac8dafe790c54bf6385932af74b47a56R283)
Mining algorithm speed improved by optimizing for powers of two. (a6f4244)
Thread stack size was erroneously allocating over 5MB to each thread minimum, which was adversely impacting hashrates. This has been fixed to now allocate 524kB (0x80000), as should have been the case.
Hardfork height for version 11 has been delayed, pending investigation of possible issues found within the cryptonote-specific implementation of the ChaCha20 stream cipher and accompanying Poly1305 for MAC. A Similar issue is present within CVE 2019-1543.
Messages for PRNG from previous block and mining iterations have been moved to log level 2.
Removal of graphviz dependency and associated save_graph commands (p2p graphs).
Removal of functions determining whether the host computer is running on a rotating disk drive (we don't need to know this & user already knows).
Removal of a dangerous macro for LONG_PAYMENT_ID that had a return statement in it. (70f2236)
Removal of unsafe stack trace files (see: 5449839#diff-185b76a2878d92e392ebd20786466293L63)
Removal of unnecessary dependency packages from depends build system.
Addition of Makefile entries for cross-compiling on linux for non-native linux and windows, to chain build depends packages with the source build.
Fix for display of print_cn commands to be cleaner and thinner. (7888a68)
Removal of a macro for the name of a Windows service, that was not made a conditional (present on all platforms), and was taken as a argument on the command line. (212f1cb)
Removal of ZeroMQ dependency and associated files (f24aef0)
Removal of remote update notifications as well as any functions dealing with remote downloads.
Fix for pow_hash being used in incorrect places within RPC commands, due to changing from it being an optional inclusion in the header, to a mandatory one. (8cff01e).
Improvement to p2p protocol by making sure nettypes & seed nodes are handled better, and sync is a bit quicker (b056e90).
ANSI colors are made more appealing (66f85c7)
Package upgrades for OpenSSL and Readline within depends build system. The openssl upgrade to 1.0.2r addresses CVE 2019-1559.
MiniUPNP is no longer a dependency and universal plug and play functionality has been removed, as well as the --no-igd startup flag.
Seed node addresses have been changed.
Wallet API and Simplewallet were also updated to bring their code in line with the overall state of the codebase (Simplewallet: 500b262 & API: 23f9811).

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

blur-v0.1.9.6-linux-x86_64.tar.gz:
558fa78da73c66072908484eab67aadf0f466cc53706668f1093b6ad97564a36

blur-v0.1.9.6-mac-x86_64.zip:
92ce0b04624431696c93b258621d22fb09a3d2ec694e5db6adbdd3110e754d2b

blur-v0.1.9.6-win-x86_64.zip:
1ea79ef1ffaf6310acea85a0931bffd61d0efa2dbede9d1b7b43a70070aeafd3

Seed Node Addre...

Assets 8

22 Mar 06:22

who-biz

v0.1.9.5

1954846

Blur v0.1.9.5 'Radiant Flux Primed'

This update is very strongly recommended for all nodes. Blur v0.1.9.5 'Radiant Flux Primed' primes the network for a change in difficulty adjustment algorithm, and includes the the v11 hardfork on the testnet to commence testing prior to v0.2.0.0. This release also begins the purging of unused code. If code is not utilized, it will be dropped. The beginning of what has been cut out is listed below in the changelog. Hardfork block height for v11 TBD on Mainnet.

This release contains important bugfixes, so please update your nodes ASAP, to ensure your security and privacy.

Changes since the last release (v0.1.9.1) include:

Guards against zero-case, in CryptoNight-Dynamic calculations. Where the previous block's hash is used in the calculation, there was a small chance of segfaulting if that hash began with six zeroes. Previously, this would have caused a divide-by-zero scenario.
The GUI wallet API now includes a fallback value for the creation height estimate. This should solve the issue where the wallet would report a zero balance until the creation height was changed to 0, manually.
Adds a check for RCTTypeNull in prevalidation of miner transactions, failing if one is present.
Cleans up some of the P2P protocol code, moving away from all Monero forks with P2P for the future.
Updates blurd.conf & similar files to hold new values for ports on mainnet & seed nodes.
Fixes coinbase handling bug, in ringct from (Monero #5217)
Fixes adding new pre-h-o-h block when a tx is already in the pool (Monero #4920)
Cleanup of protocol file: removing of "wedged_sync_restarter", unformity of returning 1/0 vs true/false for uniformity, also fixes fluffly block serialization bug.
Wallet now accounts for BLUR sent to a change address that the sender owns. previously, this was included on a the tx received/incoming list.
Reverts some upstream changes to epee/logging from XMR, as well as some changes to rapidjson, cmake & fuzz testing.
Removes annoying spam warning from the daemon communications about allowing incoming ports.
Changes the default priority level in transactions so that the "fee too low" issue doesn't happen where transactions would not send if the amount sent was of a certain amount. Default priority is now 'medium' with a negligible increase in fees.
Fixes handling of additional_tx_keys that make it past the boolean check that does accounting for them.
Adds a makefile entry release-cross-gui-win64 for cross-compiling GUI deps on Linux for Windows host system.
Removes updates.cpp and header file from common directory.
Removes spawn and notify files from common directory.
Adds a gpg key for biz to relevant directory.
Removes download.cpp and associated header file since it is not used, and we don't want anything downloading, similarly to updates files.
Remove DNS checkpoint options and functions. Again, not liking the idea of these being present, as it could result in some unforeseen behaviours.
Removes some of the optional dependencies from the depends build system, and downgrades Qt.
Store hex string instead of binary to tx_blob (Monero #4635)
Primes the testnet for v11 testing, and the mainnet (minus a block height designation) should testing go swimmingly.
Replaces DAA with Monero DAA for v11
Removes the zeroed trusted pubkey and related "debug" commands...

Please verify the following sha256sums against those of the files you download:
blur-v0.1.9.5-linux-x86_64.tar.gz:
34f27629e6a34e062392e8e9b557946e89187b652685ed81607674e01911ccd1

blur-v0.1.9.5-mac-x86_64.zip:
f1797b33f32ea083185e6221a79bf7722b074eefe8baeef35585e26c436c5100

blur-v0.1.9.5-win-x86_64.zip:
0a69be5129182ae87a41c6327fa5be36086ec0521bc38da0d70decf6be35d63c

blur-blockchain-bootstrap.zip:
ac6ddd8500f59bedc547bb6f123246177ec2ce789f64543df84f6c176e752fa2

Seed Node Addresses:

Mainnet Nodes

Node 1: 45.33.92.232:52541
Node 2: 45.79.85.65:52541
Node 3: 212.71.234.44: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=45.33.92.232:52541 --add-priority-node=212.71.234.44:52541 --add-priority-node=45.79.85.65:52541 --p2p-bind-port 52541 --rpc-bind-port 52542 --rpc-bind-ip 127.0.0.1

Alternatively, you may use the file named blurd.conf located at blur/util/conf/blurd.conf in source code, and copy that file into your binary directory.

Launch the daemon with the option --config-file ~/blur/util/conf/blurd.conf

Once you're fully synced, start the wallet with the command: ./blur-wallet-cli

Follow the prompts to create a wallet file & password, then enter the command:

start_mining [# of threads]

Where [# of threads] is the number of threads within your CPU that you wish to dedicate to mining BLUR.

Example: start_mining 4

The wallet should output the message Mining started in daemon. You can track your progress in the daemon output. There is a slight delay between mined blocks shown in the daemon, and the reflection in your wallet's balance. Type help into either command line interface for a list of commands and their function(s).

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.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=45.33.92.232:52541 --add-priority-node=212.71.234.44:52541 --add-priority-node=45.79.85.65:52541 --p2p-bind-port 52541 --rpc-bind-port 52542 --rpc-bind-ip 127.0.0.1

Once you're fully synced, start the wallet by double clicking the file named blur-wallet-cli.exe

Follow the prompts to create a wallet file & password, then enter the command:

start_mining [# of threads]

Where [# of threads] is the number of threads within your CPU that you wish to dedicate to mining BLUR.

Example: start_mining 4

Please add the seed nodes if you have trouble syncing. To do so, locate the file named blurd.conf (located at: blur/util/conf/blurd.conf) and copy/move it into the same directory as your binaries. Add to that file the following lines:

seed-node=45.33.92.232:52541
seed-node=45.79.85.65:52541
seed-node=212.71.234.44:52541
p2p-bind-port=52541
rpc-bind-port=52542

Start the daemon file with the following command and flags:

blurd.exe --seed-node 45.33.92.232:52541 --seed-node 212.71.234.44:52541 --seed-node 45.79.85.65:52541 --p2p-bind-port 52541 --rpc-bind-port 52542 --rpc-bind-ip 127.0.0.1 --config-file=.\blurd.conf

How To Verify These Binaries:

Download the zip archive of your choice and the accompanying '.asc' file. If you haven't already, download and install GnuPG.

Linux
Type the following command into a terminal: gpg --keyserver sks-keyservers.net --recv-keys D5C9054050576902

After downloading they public keys, check their fingerprint: gpg --fingerprint D5C9054050576902

You should see the output:

pub rsa4096 2018-06-07 [SC]
F3FE DCCF A90C 5683 1318 3C33 D5C9 0540 5057 6902
uid [ unknown] Blur Network (Blur: The Private Cryptocurrency) <[email protected]>
sub rsa4096 2018-06-07 [E]

Then, verify the files you've downloaded with: gpg --verify blur-v0.1.9.5-linux-x86_64.tar.gz.asc blur-v0.1.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) <[email protected]>
sub rsa4096 2018-06-07 [E]

Move into your downloads folder with cd C:\Users\[your username]\Downloads Then, verify the files you've downloaded with: "C:\Program Files\Gnu\GnuPg\gpg.exe" --verify blur-v0.1.9.5-win-x86_64.zip.asc blur-v0.1.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 ig...

Assets 10

01 Mar 02:01

who-biz

v0.1.9.1

e893575

Blur v0.1.9.1 'Radiant Flux'

This update is MANDATORY for all nodes. This release fixes the sync issues that started at the fork, and upgrades the network to version 10. The port numbers have been changed for P2P/RPC/0MQ communication due to the fork issues, and malicious traffic from another project. The new ports are P2P: 52541, RPC: 52542, 0MQ: 52543. This upgrade brings with it a PoW algorithm change to CryptoNight Dynamic v2. Please upgrade as soon as possible. You may delete your old data directory, as files will now be stored in a different directory.

Changes since the last release (v0.1.8.3) include:

Port changes for all protocols (P2P, RPC, 0MQ)'
Updates the seed nodes list for v10 hardfork
Changes the name of the data directory from blur-net to blurnetwork
Fixes the fork issues that were present, starting at block 342,000.
Adds a checkpoint for the valid fork block at 342,000.
Updates the testing suite.
PoW hash is now displayed by default in RPC calls such as get_block.
Changes the address prefixes for mainnet to decimal format rather than hexidecimal (for clarity)
Removes the mm_tag blocking previously scheduled for v10. This is not yet necessary.
Sets fork height for v10 at block 342,000.
Implements a new PoW, which uses the previous blocks hash (taken from the block header), truncated after the sixth character, and converted to an unsigned integer from hexidecimal. That number is then used as an arbitrary value in the calculation of iterations (at various points during the slow-hash calculation).
Users can now see the PRNG value generated by the method detailed above, as well as the per-block iterations by typing set_log 1 into their daemon.
Variable iterations window for longhash algorithm increased from 4,096 to 32,768.

Please verify the following sha256sums against those of the files you download:
blur-v0.1.9.1-linux-x86_64.tar.gz:
36b335de47e4a4f9948ffc9619517d7ce5ec624fe534fe170b216047f3fc16bd

blur-v0.1.9.1-mac-x86_64.zip:
7dd930ada937356978fe2b3afb63022db32a95bd8b12e078e72ebb86ccad3781

blur-v0.1.9.1-win-x86_64.zip:
b2dab2a96d2432572556bbf23f872628fab6938d07fbab79468e75044c63503a

blur-blockchain-bootstrap.zip:
eb336d07818df247e446fe315ff2c469eb92393ffc07d2b4d1d038cf35ff0929

Seed Node Addresses:

Mainnet Nodes

Node 1: 45.33.92.232:52541
Node 2: 45.79.85.65:52541
Node 3: 212.71.234.44: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-exclusive-node=45.33.92.232:52541 --add-exclusive-node=212.71.234.44:52541 --add-exclusive-node=45.79.85.65:52541 --p2p-bind-port 52541 --rpc-bind-port 52542 --rpc-bind-ip 127.0.0.1

Alternatively, you may use the file named blurd.conf located at blur/util/conf/blurd.conf in source code, and copy that file into your binary directory.

Launch the daemon with the option --config-file ~/blur/util/conf/blurd.conf

Once you're fully synced, start the wallet with the command: ./blur-wallet-cli

Follow the prompts to create a wallet file & password, then enter the command:

start_mining [# of threads]

Where [# of threads] is the number of threads within your CPU that you wish to dedicate to mining BLUR.

Example: start_mining 4

Windows Instructions

For Sync issues on Windows:

Open Windows Powershell (Windows Key + X, then click powershell (non-admin) and type cd Downloads/blur-v0.1.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-exclusive-node=45.33.92.232:52541 --add-exclusive-node=212.71.234.44:52541 --add-exclusive-node=45.79.85.65:52541 --p2p-bind-port 52541 --rpc-bind-port 52542 --rpc-bind-ip 127.0.0.1

Once you're fully synced, start the wallet by double clicking the file named blur-wallet-cli.exe

Follow the prompts to create a wallet file & password, then enter the command:

start_mining [# of threads]

Where [# of threads] is the number of threads within your CPU that you wish to dedicate to mining BLUR.

Example: start_mining 4

seed-node=45.33.92.232:52541
seed-node=45.79.85.65:52541
seed-node=212.71.234.44:52541
p2p-bind-port=52541
rpc-bind-port=52542

Start the daemon file with the following command and flags:

blurd.exe --seed-node 45.33.92.232:52541 --seed-node 212.71.234.44:52541 --seed-node 45.79.85.65:52541 --p2p-bind-port 52541 --rpc-bind-port 52542 --rpc-bind-ip 127.0.0.1 --config-file=.\blurd.conf

How To Verify These Binaries:

Download the zip archive of your choice and the accompanying '.asc' file. If you haven't already, download and install GnuPG.

Linux
Type the following command into a terminal: gpg --keyserver sks-keyservers.net --recv-keys D5C9054050576902

After downloading they public keys, check their fingerprint: gpg --fingerprint D5C9054050576902

You should see the output:

pub rsa4096 2018-06-07 [SC]
F3FE DCCF A90C 5683 1318 3C33 D5C9 0540 5057 6902
uid [ unknown] Blur Network (Blur: The Private Cryptocurrency) <[email protected]>
sub rsa4096 2018-06-07 [E]

Then, verify the files you've downloaded with: gpg --verify blur-v0.1.9.1-linux-x86_64.tar.gz.asc blur-v0.1.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) <[email protected]>
sub rsa4096 2018-06-07 [E]

Move into your downloads folder with cd C:\Users\[your username]\Downloads Then, verify the files you've downloaded with: "C:\Program Files\Gnu\GnuPg\gpg.exe" --verify blur-v0.1.9.1-win-x86_64.zip.asc blur-v0.1.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.

Blockchain Bootstrap Procedure

Download & extract the `blur-blockchain-bootstrap.zip` archive. Upon extraction, you should be left with a folder named `export`. Move the export folder into your `blurnetwork` data directory.

This should result in following structure:
[your user's data directory]/export/blockchain.raw

On Linux/Mac: ~/.blurnetwork/export/blockchain.raw
On Windows: %PROGRAMDATA%\blurnetwork\export\blockchain.raw

Import the blockchain file with: ./blur-blockchain-import. You should be bootstrapped and immediately synced up to block ~342,000 if the chain data was imported properly. Sometimes, batch transactions cause problems importing. If you still have problems, try disabling batch transactions with the --batch option and an argument of 0. For additional startup flags, start with ./blur-blockchain-import --help

Assets 10

19 Feb 15:09

who-biz

v0.1.9

7b93224

Blur v0.1.9 'Radiant Flux'

This update is MANDATORY for all nodes. This release upgrades the network at block 342,000 to version 10. All nodes must update by the upgrade block, or you will no longer be mining on the main chain. This upgrade brings with it a PoW algorithm upgrade to CryptoNight Dynamic v2. Please upgrade as soon as possible. Any daemons still on version v0.1.8.x at the fork block will cease to be relevant to the network.

Changes since the last release (v0.1.8.3) include:

Updates the testing suite.
PoW hash is now displayed by default in RPC calls such as get_block.
Changes the address prefixes for mainnet to decimal format rather than hexidecimal (for clarity)
Removes the mm_tag blocking previously scheduled for v10. This is not yet necessary.
Sets fork height for v10 at block 342,000.
Implements a new PoW, which uses block difficulty as an arbitrary value in the calculation of iterations (at various points during the slow-hash calculation).
Addition of different functions for discernment of pre-v10 PoW hashes and post-v10 PoW.
Variable iterations window for longhash algorithm increased from 4,096 to 32,768.

Please verify the following sha256sums against those of the files you download:
blur-v0.1.9-linux-x86_64.tar.gz:
b6832c5eab1b0a909ff30b7206e0e84cb8bacce914a841a7c19917a1f0bfdab1

blur-v0.1.9-mac-x86_64.zip:
dbbbe163fbe54377ae361741a257e892e6f5a040f4ad73fc144457d6cd0565cd

blur-v0.1.9-win-x86_64.zip:
6cdb42217c1b6ffda71c9e77680b9281b76d98b77240051598696d38aea5c3a0

blur-blockchain-bootstrap.zip:
fb7e00a5cfd19951c3db0283f716991e53657aa39e8fe834033c348f3efc4194

Seed Node Addresses:

Mainnet Nodes

Node 1: 66.70.189.131:13894
Node 2: 66.70.189.183:13894
Node 3: 66.70.188.178:13894

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.189.131:13894 --seed-node 66.70.189.183:13894 --add-priority-node 66.70.188.178:13894 --p2p-bind-port 13894 --rpc-bind-port 13895 --rpc-bind-ip 127.0.0.1

Alternatively, you may use the file named blurd.conf located at blur/util/conf/blurd.conf in source code, and copy that file into your binary directory.

Launch the daemon with the option --config-file ~/blur/util/conf/blurd.conf

Once you're fully synced, start the wallet with the command: ./blur-wallet-cli

Follow the prompts to create a wallet file & password, then enter the command:

start_mining [# of threads]

Where [# of threads] is the number of threads within your CPU that you wish to dedicate to mining BLUR.

Example: start_mining 4

Windows Instructions

For Sync issues on Windows:

Open Windows Powershell (Windows Key + X, then click powershell (non-admin) and type cd Downloads/blur-v0.1.9-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.189.131:13894 --seed-node=66.70.189.183:13894 --add-priority-node=66.70.188.178:13894 --p2p-bind-port 13894 --rpc-bind-port 13895 --rpc-bind-ip 127.0.0.1

Once you're fully synced, start the wallet by double clicking the file named blur-wallet-cli.exe

Follow the prompts to create a wallet file & password, then enter the command:

start_mining [# of threads]

Where [# of threads] is the number of threads within your CPU that you wish to dedicate to mining BLUR.

Example: start_mining 4

seed-node=66.70.189.131:13894
seed-node=66.70.188.178:13894
seed-node=66.70.189.183:13894
p2p-bind-port=13894
rpc-bind-port=13895

Start the daemon file with the following command and flags:

blurd.exe --seed-node 66.70.189.131:13894 --seed-node 66.70.189.183:13894 --seed-node 66.70.188.178:13894 --p2p-bind-port 13894 --rpc-bind-port 13895 --rpc-bind-ip 127.0.0.1 --config-file=.\blurd.conf

How To Verify These Binaries:

Download the zip archive of your choice and the accompanying '.asc' file. If you haven't already, download and install GnuPG.

Linux
Type the following command into a terminal: gpg --keyserver sks-keyservers.net --recv-keys D5C9054050576902

After downloading they public keys, check their fingerprint: gpg --fingerprint D5C9054050576902

You should see the output:

pub rsa4096 2018-06-07 [SC]
F3FE DCCF A90C 5683 1318 3C33 D5C9 0540 5057 6902
uid [ unknown] Blur Network (Blur: The Private Cryptocurrency) <[email protected]>
sub rsa4096 2018-06-07 [E]

Then, verify the files you've downloaded with: gpg --verify blur-v0.1.9-linux-x86_64.tar.gz.asc blur-v0.1.9-linux-x86_64.tar.gz The output should say "Good Signature." The warning message is due to no trust index being assigned to the signature, simply ignore it.

Windows
Open cmd.exe and type: "C:\Program Files\Gnu\GnuPg\gpg.exe" --keyserver sks-keyservers.net --recv-keys D5C9054050576902

After downloading they public keys, check their fingerprint: "C:\Program Files\Gnu\GnuPg\gpg.exe" --fingerprint D5C9054050576902

You should see the output:

pub rsa4096 2018-06-07 [SC]
F3FE DCCF A90C 5683 1318 3C33 D5C9 0540 5057 6902
uid [ unknown] Blur Network (Blur: The Private Cryptocurrency) <[email protected]>
sub rsa4096 2018-06-07 [E]

Move into your downloads folder with cd C:\Users\[your username]\Downloads Then, verify the files you've downloaded with: "C:\Program Files\Gnu\GnuPg\gpg.exe" --verify blur-v0.1.9-win-x86_64.zip.asc blur-v0.1.9-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.

Blockchain Bootstrap Procedure

Download & extract the `blur-blockchain-bootstrap.zip` archive. Upon extraction, you should be left with a folder named `export`. Move the export folder into your `blur-net` data directory.

This should result in following structure:
[your user's data directory]/export/blockchain.raw

On Linux/Mac: ~/.blur-net/export/blockchain.raw
On Windows: %PROGRAMDATA%\blur-net\export\blockchain.raw or %APPDATA\Roaming\blur-net\export\blockchain.raw

Import the blockchain file with: ./blur-blockchain-import. You should be bootstrapped and immediately synced up to block ~335,000 if the chain data was imported properly. Sometimes, batch transactions cause problems importing. If you still have problems, try disabling batch transactions with the --batch option and an argument of 0. For additional startup flags, start with ./blur-blockchain-import --help

Assets 10

02 Feb 09:45

who-biz

v0.1.8.3

29c3223

Blur v0.1.8.3 'Shift'

This update is MANDATORY for all nodes. This release fixes a number of bugs (some of which would be critical if exploited correctly). Nodes that do not update will be able to keep mining on their current version, but v0.1.8.3 brings with it performance improvements, apart from the bug fixes, so you will want to update. This will be the final release before a hardfork to update our PoW algorithm. This mandatory update is necessary to ensure the safety of the chain prior to the release of v0.1.9. Please upgrade as soon as possible.

Changes since the last release (v0.1.8.2) include:

Upgrades Qt package from 5.7 -> 5.9.7 in depends build system.
Upgrades OpenSSL package from 1.0.1k -> 1.0.2q in depends build system.
Remove unused packages from depends build system (bdb, miniupnpc)
Fixes compilation errors for GCC 8.1 & MSYS.
Remove old seed node IPs for mainnet & testnet from hardcoded nodelist.
Updates the snapcraft script for building of snaps with correct format (previous method has been deprecated).
Updates Docker build script to function properly with our current codebase.
Adds checkpoints at heights (0, 250000, and 265000) as well as checksum for checkpoints.dat file.
Addition of const keyword within hash-relevant files to ensure uniformity of parameter interpretation within slow-hash function.
Properly renames scope within translation files for wallet API.
Properly renames systemd service.
Updates crypto library with a 32-byte equality function using constant time (Monero #3999)
Fixes a bug with json serialization (Monero #4831)
Optimizes some of the operations within the slow-hash function for a bit higher hashrates across the board.
Updates easylogging++ library (rebase to Monero)
Updates epee library (with bugfixes from Monero)
Updates relevant files within blur/src/common to accomodate the above bugfixes and rebase.
Fixes a critical vulnerability that could be catastrophic if source code is changed to increase the premine amount, or if transaction version is incremented. Please see 5398d18 for details on this vulnerability and the fix.
Fixes a vulnerability present in hardcoded seed node definitions, that could result in an attacker communicating with the network, in place of proper seed nodes. This bug was also due to an omission within our upstream. Please see commit aad8177 for the relevant fix.
Fixes the wrongful display of red warning messages about incoming connections, despite incoming connections being allowed (introduced in v0.1.8.2).

Please verify the following sha256sums against those of the files you download:
blur-v0.1.8.3-linux-x86_64.tar.gz: 5c9340245e50f94a081cc7e30cc4f005dc3a494958e7f8a4ea55e3b1fce01012
blur-v0.1.8.3-mac-x86_64.zip:
2b882bc361dae1c6cc4d9948ba6332c0cb6c031bfefe628313342f15632fa23b
blur-v0.1.8.3-win-x86_64.zip:
7d26db1404810eb214dc4db6fe639205b1c7a58c79fb585f2e678df309c2b91b
blur-blockchain-bootstrap.zip:

Seed Node Addresses:

Mainnet Nodes

Node 1: 66.70.189.131:13894
Node 2: 66.70.189.183:13894
Node 3: 66.70.188.178:13894

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.189.131:13894 --seed-node 66.70.189.183:13894 --add-priority-node 66.70.188.178:13894 --p2p-bind-port 13894 --rpc-bind-port 13895 --rpc-bind-ip 127.0.0.1

Alternatively, you may use the file named blurd.conf located at blur/util/conf/blurd.conf in source code, and copy that file into your binary directory.

Launch the daemon with the option --config-file ~/blur/util/conf/blurd.conf

Once you're fully synced, start the wallet with the command: ./blur-wallet-cli

Follow the prompts to create a wallet file & password, then enter the command:

start_mining [# of threads]

Where [# of threads] is the number of threads within your CPU that you wish to dedicate to mining BLUR.

Example: start_mining 4

Windows Instructions

For Sync issues on Windows:

Open Windows Powershell (Windows Key + X, then click powershell (non-admin) and type cd Downloads/blur-v0.1.8.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.189.131:13894 --seed-node=66.70.189.183:13894 --add-priority-node=66.70.188.178:13894 --p2p-bind-port 13894 --rpc-bind-port 13895 --rpc-bind-ip 127.0.0.1

Once you're fully synced, start the wallet by double clicking the file named blur-wallet-cli.exe

Follow the prompts to create a wallet file & password, then enter the command:

start_mining [# of threads]

Where [# of threads] is the number of threads within your CPU that you wish to dedicate to mining BLUR.

Example: start_mining 4

seed-node=66.70.189.131:13894
seed-node=66.70.188.178:13894
seed-node=66.70.189.183:13894
p2p-bind-port=13894
rpc-bind-port=13895

Start the daemon file with the following command and flags:

How To Verify These Binaries:

Download the zip archive of your choice and the accompanying '.asc' file. If you haven't already, download and install GnuPG.

Linux
Type the following command into a terminal: gpg --keyserver sks-keyservers.net --recv-keys D5C9054050576902

After downloading they public keys, check their fingerprint: gpg --fingerprint D5C9054050576902

You should see the output:

pub rsa4096 2018-06-07 [SC]
F3FE DCCF A90C 5683 1318 3C33 D5C9 0540 5057 6902
uid [ unknown] Blur Network (Blur: The Private Cryptocurrency) <[email protected]>
sub rsa4096 2018-06-07 [E]

Then, verify the files you've downloaded with: gpg --verify blur-v0.1.8.3-linux-x86_64.tar.gz.asc blur-v0.1.8.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) <[email protected]>
sub rsa4096 2018-06-07 [E]

Move into your downloads folder with cd C:\Users\[your username]\Downloads Then, verify the files you've downloaded with: "C:\Program Files\Gnu\GnuPg\gpg.exe" --verify blur-v0.1.8.3-win-x86_64.zip.asc blur-v0.1.8.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.

Blockchain Bootstrap Procedure

Download & extract the `blur-blockchain-bootstrap.zip` archive. Upon extraction, you should be left with a folder named `export`. Move the export folder into your `blur-net` data directory.

This should result in following structure:
[your user's data directory]/export/blockchain.raw

On Linux/Mac: ~/.blur-net/export/blockchain.raw
On Windows: %PROGRAMDATA%\blur-net\export\blockchain.raw or %APPDATA\Roaming\blur-net\export\blockchain.raw

Import the blockchain file with: ./blur-blockchain-import. You should be bootstrapped and immediately synced up to block ~311,000 if the chain data was imported properly. Sometimes, batch transactions cause problems importing. If you still have problems, try disabling batch transactions with the --batch op...

Assets 8

21 Dec 21:31

who-biz

v0.1.8.2

5b4088f

Blur v0.1.8.2 'Shift'

This update is strongly recommended for all nodes. While the update is non-mandatory, there are quite a few changes that have taken place since the last release. Most notably, you will find that the release v0.1.8.1 will not sync if it is being run for the first time. This is due to the seed node addresses changing, and will not affect nodes that are already running. If you use this release instead, the switch is automatic.

Changes since the last release (v0.1.8.1) include:

Fixes for snapcraft.io build system.
Fixes for depends build system located in blur/contrib/depends
Fixes a memory leaking issue on Windows 64-bit
Command line interface now uses ANSI Colors for Windows 10.
Fixes scope for wallet locking in Windows 10 (boost)
Wallet refresh text is changed from blocks received to blocks refreshed for disambiguation
Fixes double counting of outs in wallet if more than one pubkey (monero)
Implements a block for the merge_mining tag in tx extra fields starting at v10.
Brings most of the blur/src/crypto library current with Monero.
Brings most of the blur/src/common library current with Monero.
Fixes for Cmake build system (linking of Readline)
Fixes password handling bug from #24 for Windows platform
Hides certain values when daemon is launched using restricted-rpc option.
Updates seed node addresses for mainnet.
Updates network type (nettype) handling for wallet and daemon.
Updates incoming and outgoing connection limits for daemon.

Please verify your download by comparing the file's sha256sum with these posted below:

blur-v0.1.8.2-linux-x86_64.tar.gz:
41808e8a6a7db6145ccf260e6e054f41aa384f0df4479e664e90c56260be5449

blur-v0.1.8.2-win-x86_64.zip:
25361d1229f01e37871d292a6b5dcb9aa0ad6f1c7eefc6ad7bd6cab9a8789efd

blur-v0.1.8.2-mac-x86_64.zip:
d72b2e2f8bf6b02af507fd03966f49b316dd6a770eddc3fa10a6eb28187e5392

blur-blockchain-bootstrap.zip:
153214c1701d594eb03c530d9e6ed256d20e31d59b08dccf1eef287553ffa560

Seed Node Addresses:

Mainnet Nodes

Node 1: 66.70.189.131:13894
Node 2: 66.70.189.183:13894
Node 3: 66.70.188.178:13894

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.189.131:13894 --seed-node 66.70.189.183:13894 --add-priority-node 66.70.188.178:13894 --p2p-bind-port 13894 --rpc-bind-port 13895 --rpc-bind-ip 127.0.0.1

Alternatively, you may use the file named blurd.conf located at blur/util/conf/blurd.conf in source code, and copy that file into your binary directory.

Launch the daemon with the option --config-file ~/blur/util/conf/blurd.conf

Once you're fully synced, start the wallet with the command: ./blur-wallet-cli

Follow the prompts to create a wallet file & password, then enter the command:

start_mining [# of threads]

Where [# of threads] is the number of threads within your CPU that you wish to dedicate to mining BLUR.

Example: start_mining 4

Windows Instructions

For Sync issues on Windows:

Open Windows Powershell (Windows Key + X, then click powershell (non-admin) and type cd Downloads/blur-v0.1.8.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.189.131:13894 --seed-node=66.70.189.183:13894 --add-priority-node=66.70.188.178:13894 --p2p-bind-port 13894 --rpc-bind-port 13895 --rpc-bind-ip 127.0.0.1

Once you're fully synced, start the wallet by double clicking the file named blur-wallet-cli.exe

Follow the prompts to create a wallet file & password, then enter the command:

start_mining [# of threads]

Where [# of threads] is the number of threads within your CPU that you wish to dedicate to mining BLUR.

Example: start_mining 4

seed-node=66.70.189.131:13894
seed-node=66.70.188.178:13894
seed-node=66.70.189.183:13894
p2p-bind-port=13894
rpc-bind-port=13895

Start the daemon file with the following command and flags:

How To Verify These Binaries:

Download the zip archive of your choice and the accompanying '.asc' file. If you haven't already, download and install GnuPG.

Linux
Type the following command into a terminal: gpg --keyserver sks-keyservers.net --recv-keys D5C9054050576902

After downloading they public keys, check their fingerprint: gpg --fingerprint D5C9054050576902

You should see the output:

pub rsa4096 2018-06-07 [SC]
F3FE DCCF A90C 5683 1318 3C33 D5C9 0540 5057 6902
uid [ unknown] Blur Network (Blur: The Private Cryptocurrency) <[email protected]>
sub rsa4096 2018-06-07 [E]

Then, verify the files you've downloaded with: gpg --verify blur-v0.1.8.2-linux-x86_64.tar.gz.asc blur-v0.1.8.2-linux-x86_64.tar.gz The output should say "Good Signature." The warning message is due to no trust index being assigned to the signature, simply ignore it.

Windows
Open cmd.exe and type: "C:\Program Files\Gnu\GnuPg\gpg.exe" --keyserver sks-keyservers.net --recv-keys D5C9054050576902

After downloading they public keys, check their fingerprint: "C:\Program Files\Gnu\GnuPg\gpg.exe" --fingerprint D5C9054050576902

You should see the output:

pub rsa4096 2018-06-07 [SC]
F3FE DCCF A90C 5683 1318 3C33 D5C9 0540 5057 6902
uid [ unknown] Blur Network (Blur: The Private Cryptocurrency) <[email protected]>
sub rsa4096 2018-06-07 [E]

Move into your downloads folder with cd C:\Users\[your username]\Downloads Then, verify the files you've downloaded with: "C:\Program Files\Gnu\GnuPg\gpg.exe" --verify blur-v0.1.8.2-win-x86_64.zip.asc blur-v0.1.8.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.

Blockchain Bootstrap Procedure

Download & extract the `blur-blockchain-bootstrap.zip` archive. Upon extraction, you should be left with a folder named `export`. Move the export folder into your `blur-net` data directory.

This should result in following structure:
[your user's data directory]/export/blockchain.raw

On Linux/Mac: ~/.blur-net/export/blockchain.raw
On Windows: %PROGRAMDATA%\blur-net\export\blockchain.raw or %APPDATA\Roaming\blur-net\export\blockchain.raw

Import the blockchain file with: ./blur-blockchain-import --batch-size=186000. You should be bootstrapped and immediately synced up to block ~295,000 if the chain data was imported properly. Sometimes, batch transactions cause problems importing. If you still have problems, try disabling batch transactions with the --batch option and an argument of 0. For additional startup flags, start with ./blur-blockchain-import --help

Assets 9

24 Nov 17:31

blur-network

v0.1.8.1

8230253

Blur v0.1.8.1 'Shift'

Blur Network now has an official snap for Linux. If you prefer to use snaps over portable binaries, you can find the CLI tools by searching "Blur Network" in the Ubuntu Software Store, or clicking below:

This is a mandatory update, which fixes the v9 hardfork segfault that was occurring, incorporating the latest improvements to the network.

This major release will upgrade the network to v0.1.8.1 'Shift'. Hardfork v9 occurred at block 211000. As always with hardforks, you must update your node to remain on the main chain Changes since the last minor release include (technically from v0.1.7.6.1, but leaving here for clarity):

Set height for Hardfork v9 at 211,000
Update checkpoints to ~block 206,000
Update CMakeLists.txt to remove submodule checks, BerkeleyDB, and to link boost locale library properly
locale library in correct place
Update Makefile for Windows 64-bit build with MSYS2
Removal of git submodule for unbound dependency, to get rid of gratuitous warnings on Windows static compile
Fixes a bug where sending coins to yourself would result in an inability to rescan the blockchain or display any new transactions
Rework of new algorithm for upcoming v9 hardfork

Please verify your download by comparing the file's sha256sum with these posted below:

blur-v0.1.8.1-linux-x86_64.tar.gz:
a26c7f474947c6013c1469492e06e08461714b6acd3c9f774aa5761d46a8e616

blur-v0.1.8.1-mac-x86_64.zip:
b54bfa777c29f10133276071f035e1e79675cf45fc23d240436d679b0f778664

blur-v0.1.8.1-win-x86_64.zip:
324115fc0618fcb1845a0d4cc36466ea9e00ac699338e0e76abd048f25cdfb30

Seed Node Addresses:

Mainnet Nodes

Node 1: 178.128.191.245:13894
Node 2: 178.128.180.136:13894
Node 3: 178.128.186.101:13894

Testnet Nodes

Node 1: 206.189.163.61:11111
Node 2: 104.248.69.152:11111
Node 3: 104.248.182.234:11111

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 178.128.191.245:13894 --seed-node 178.128.180.136:13894 --add-priority-node 178.128.186.101:13894 --p2p-bind-port 13894 --rpc-bind-port 13895 --rpc-bind-ip 127.0.0.1

Alternatively, you may use the file named blurd.conf located at blur/util/conf/blurd.conf in source code, and copy that file into your binary directory.

Launch the daemon with the option --config-file ~/blur/util/conf/blurd.conf

Once you're fully synced, start the wallet with the command: ./blur-wallet-cli

Follow the prompts to create a wallet file & password, then enter the command:

start_mining [# of threads]

Where [# of threads] is the number of threads within your CPU that you wish to dedicate to mining BLUR.

Example: start_mining 4

Windows Instructions

For Sync issues on Windows:

Open Windows Powershell (Windows Key + X, then click powershell (non-admin) and type cd Downloads/blur-v0.1.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=178.128.191.245:13894 --seed-node=178.128.180.136:13894 --add-priority-node=178.128.186.101:13894 --p2p-bind-port 13894 --rpc-bind-port 13895 --rpc-bind-ip 127.0.0.1

Once you're fully synced, start the wallet by double clicking the file named blur-wallet-cli.exe

Follow the prompts to create a wallet file & password, then enter the command:

start_mining [# of threads]

Where [# of threads] is the number of threads within your CPU that you wish to dedicate to mining BLUR.

Example: start_mining 4

seed-node=178.128.191.245:13894
seed-node=178.128.186.101:13894
seed-node=178.128.180.136:13894
p2p-bind-port=13894
rpc-bind-port=13895

Start the daemon file with the following command and flags:

blurd.exe --seed-node 178.128.191.245:13894 --seed-node 178.128.180.136:13894 --seed-node 178.128.186.101:13894 --p2p-bind-port 13894 --rpc-bind-port 13895 --rpc-bind-ip 127.0.0.1 --config-file=.\blurd.conf

How To Verify These Binaries:

Download the zip archive of your choice and the accompanying '.asc' file. If you haven't already, download and install GnuPG.

Linux
Type the following command into a terminal: gpg --keyserver sks-keyservers.net --recv-keys D5C9054050576902

After downloading they public keys, check their fingerprint: gpg --fingerprint D5C9054050576902

You should see the output:

pub rsa4096 2018-06-07 [SC]
F3FE DCCF A90C 5683 1318 3C33 D5C9 0540 5057 6902
uid [ unknown] Blur Network (Blur: The Private Cryptocurrency) <[email protected]>
sub rsa4096 2018-06-07 [E]

Then, verify the files you've downloaded with: gpg --verify blur-v0.1.8.1-linux-x86_64.tar.gz.asc blur-v0.1.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) <[email protected]>
sub rsa4096 2018-06-07 [E]

Move into your downloads folder with cd C:\Users\[your username]\Downloads Then, verify the files you've downloaded with: "C:\Program Files\Gnu\GnuPg\gpg.exe" --verify blur-v0.1.8.1-win-x86_64.zip.asc blur-v0.1.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

20 Nov 23:37

blur-network

v0.1.8

2e7c21e

Blur v0.1.8 'Shift'

This is a mandatory update, which primes the testnet & mainnet for v9 hardfork, and integrates the latest improvements to the network.

This major release will upgrade the network to v0.1.8 'Shift'. Hardfork v9 is set for block 211,000, you must update your node by then to remain on the mainchain Changes since the last minor release include:

Set height for Hardfork v9 at 211,000
Update checkpoints to ~block 206,000
Update CMakeLists.txt to remove submodule checks, BerkeleyDB, and to link boost locale library properly
locale library in correct place
Update Makefile for Windows 64-bit build with MSYS2
Removal of git submodule for unbound dependency, to get rid of gratuitous warnings on Windows static compile
Fixes a bug where sending coins to yourself would result in an inability to rescan the blockchain or display any new transactions
Rework of new algorithm for upcoming v9 hardfork

Please take even a small portion of your hashpower and direct it toward our testnet so that we may effectively test the new mining algorithm. To do so, start up the daemon with the option --testnet. You will also need to start blur-wallet-cli with the same --testnet flag, to generate a testnet address for mining.

Please verify your download by comparing the file's sha256sum with these posted below:

blur-v0.1.8-linux-x86_64.tar.gz:
1812d3a36db8d4472d473b75e46ee580800df534e3a6e98e1e63547934bc8824

blur-v0.1.8-ubuntu-18.04.1-x86_64.tar.xz:
54a719efff01c7be80e4cee8928f522cbdf51a092edb2e70ffb4b74aeba1dc94

blur-v0.1.8-mac-x86_64.tar.xz:
3e761bb5bec81882d88289ce8e09e2c1e62ca9ba5ce08f5e7fdb83867622b698

blur-v0.1.8-win-x86_64.tar.gz:
fa56167c490ca3d7c7006d19b100e3343ec5656502c6673b0f26d5e5d0049904

blockchain-bootstrap.zip:
bf6cfa42d808b67695366472d6784404270933dd0f45acd7e1d178672f7f098e

Seed Node Addresses:

Mainnet Nodes

Node 1: 178.128.191.245:13894
Node 2: 178.128.180.136:13894
Node 3: 178.128.186.101:13894

Testnet Nodes

Node 1: 206.189.163.61:11111
Node 2: 104.248.69.152:11111
Node 3: 104.248.182.234:11111

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 178.128.191.245:13894 --seed-node 178.128.180.136:13894 --add-priority-node 178.128.186.101:13894 --p2p-bind-port 13894 --rpc-bind-port 13895 --rpc-bind-ip 127.0.0.1

Alternatively, you may use the file named blurd.conf located at blur/util/conf/blurd.conf in source code, and copy that file into your binary directory.

Launch the daemon with the option --config-file ~/blur/util/conf/blurd.conf

Once you're fully synced, start the wallet with the command: ./blur-wallet-cli

Follow the prompts to create a wallet file & password, then enter the command:

start_mining [# of threads]

Where [# of threads] is the number of threads within your CPU that you wish to dedicate to mining BLUR.

Example: start_mining 4

Windows Instructions

For Sync issues on Windows:

Open Windows Powershell (Windows Key + X, then click powershell (non-admin) and type cd Downloads/blur-v0.1.8-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=178.128.191.245:13894 --seed-node=178.128.180.136:13894 --add-priority-node=178.128.186.101:13894 --p2p-bind-port 13894 --rpc-bind-port 13895 --rpc-bind-ip 127.0.0.1

Once you're fully synced, start the wallet by double clicking the file named blur-wallet-cli.exe

Follow the prompts to create a wallet file & password, then enter the command:

start_mining [# of threads]

Where [# of threads] is the number of threads within your CPU that you wish to dedicate to mining BLUR.

Example: start_mining 4

seed-node=178.128.191.245:13894
seed-node=178.128.186.101:13894
seed-node=178.128.180.136:13894
p2p-bind-port=13894
rpc-bind-port=13895

Start the daemon file with the following command and flags:

How To Verify These Binaries:

Download the zip archive of your choice and the accompanying '.asc' file. If you haven't already, download and install GnuPG.

Linux
Type the following command into a terminal: gpg --keyserver sks-keyservers.net --recv-keys D5C9054050576902

After downloading they public keys, check their fingerprint: gpg --fingerprint D5C9054050576902

You should see the output:

pub rsa4096 2018-06-07 [SC]
F3FE DCCF A90C 5683 1318 3C33 D5C9 0540 5057 6902
uid [ unknown] Blur Network (Blur: The Private Cryptocurrency) <[email protected]>
sub rsa4096 2018-06-07 [E]

Then, verify the files you've downloaded with: gpg --verify blur-v0.1.8-linux-x86_64.zip.asc blur-v0.1.8-linux-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.

Windows
Open cmd.exe and type: "C:\Program Files\Gnu\GnuPg\gpg.exe" --keyserver sks-keyservers.net --recv-keys D5C9054050576902

After downloading they public keys, check their fingerprint: "C:\Program Files\Gnu\GnuPg\gpg.exe" --fingerprint D5C9054050576902

You should see the output:

pub rsa4096 2018-06-07 [SC]
F3FE DCCF A90C 5683 1318 3C33 D5C9 0540 5057 6902
uid [ unknown] Blur Network (Blur: The Private Cryptocurrency) <[email protected]>
sub rsa4096 2018-06-07 [E]

Move into your downloads folder with cd C:\Users\[your username]\Downloads Then, verify the files you've downloaded with: "C:\Program Files\Gnu\GnuPg\gpg.exe" --verify blur-v0.1.8-win-x86_64.zip.asc blur-v0.1.8-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 12

Releases: blur-network/blur

Blur v0.1.9.8 'Radiance'

Blur v0.1.9.7 'Radiance'