@blur-network blur-network released this Nov 24, 2018 · 21 commits to master since this release

Assets 8

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:

Get it from the Snap Store

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

Contents:


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

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

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).

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

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

Contents:


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

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

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).

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

@blur-network blur-network released this Nov 8, 2018

Assets 10

This is an optional update, which primes the testnet for v9 hardfork, and integrates the latest improvements to the network.

This is a point release for v0.1.7 'Lustrous Nebula'. The following are changes since the last major release:

  • Renaming of config file 'blurd.conf' and inclusion of default configuration variables for Blur. (located in: blur/utils/conf)
  • Fixes easylogging errors on Windows Daemon
  • Begin supporting foreign languages on Windows platform w/ proper utf-16 handling (courtesy of code from RYO)
  • Addition of hardcoded testnet seed node IPs
  • Tightening 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.7.6.1-linux-x86_64.tar.gz: b2cb2be413d7e5e45802de8557fbf0c32da5867a07643c944577a9ea66be2a2e

blur-v0.1.7.6.1-ubuntu-18.04.1-x86_64.tar.gz:
c3063bba080dc8a9c575e6413bfd08a70de016c944999e0e2b876177b833af47

blur-v0.1.7.6.1-win-x86_64.tar.gz:
6e8391f7f9c7dfd00720756bf188c06e942ff47ae42b65afe2fb364216c99a14

blur-v0.1.7.6.1-mac-x86_64.tar.gz:
fd41aa855ce47a0f833e79e3691008cc32a847b8d13fec0ab6b3f940a7df4919

Contents:


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

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.7.6.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

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).

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=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) <admin@blur.cash>
sub rsa4096 2018-06-07 [E]

Then, verify the files you've downloaded with: gpg --verify blur-v0.1.7.6.1-linux-x86_64.zip.asc blur-v0.1.7.6-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) <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.7.6-win-x86_64.zip.asc blur-v0.1.7.6-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 11

Windows Wallets are now working as of 11/06... If you downloaded this release with a non-working wallet for Windows, please re-download and use the proper version wallet.

This update is mandatory for all nodes You will need to sync from scratch due to the rollback. This update primes the testnet for v9, in preparation for the v0.1.8 release 'Shift'. Version 0.1.8 will feature a new algorithm for mining. The prototype of that algorithm is live on the testnet now.

Port numbers have changed to 13894 and 13895 for p2p and rpc respectively. ERASE YOUR PREVIOUS DATA DIRECTORY or you run the risk of mining on a chain that will result in a 24 hour ban. Hashrates have doubled in this release, allowing for larger and more distinguishable differences between types of CPUs and their effective network impact.

sha256sums:
blur-v0.1.7.6-win-x86_64.zip:
ad780dc29072b688eb7a7ecfeafe6a3e74158761916db8edc1e6f3bd6b30a137

blur-v0.1.7.6-linux-x86_64.tar.xz:
061c43afaec304bc8977442b0d038b9469504629b7ae1b2755fabad72ef1609b

blur-v0.1.7.6-ubuntu-16.04-x86_64.tar.xz:
1bf772bcbc3ad3811bf8851957fc08de97dd511947fb9cf68eb2bc473438ced6

blur-v0.1.7.6-mac-x86_64.zip:
324a784ee6c7dd2a80298e33c1fc975c7838b9323459973600d1312ce2168803

blockchain-bootstrap.zip: 8e2fc8a7740ebbebe858f28ad49202bf278a340302856354326866764dde39b5

Contents:


Seed Node Addresses:

  • Node 1: 178.128.191.245:13894
  • Node 2: 178.128.180.136:13894
  • Node 3: 178.128.186.101: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 --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

Alternatively, you may create a config file titled blur-net.conf in the directory located at ~/.blur-net on Linux. Add the following lines to that config file:

seed-node=178.128.191.245:13894
seed-node=178.128.186.101:13894
seed-node=178.128.180.136:13894

./blurd --seed-node 178.128.191.245:13894 --seed-node 159.203.48.201:13894 --seed-node 178.128.180.136:13894 --seed-node 178.128.186.101:13894 --config-file ~/.blur-net.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.7.6-win-x86_64 to switch to the directory you extracted the binaries into. Launch the daemon executable with the following options:

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

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

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).

Please add the seed nodes if you have trouble syncing. To do so, you may create a config file titled blurnet.conf and place it in the same directory as the binaries. Add to that file the following lines:

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=.\blurnet.conf

Blockchain Bootstrap Procedure

Download & extract the `blockchain_bootstrap.zip` archive. You should have 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

Linux/Mac: ~/.blur-net/export/blockchain.raw
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 129,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

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.7.6-linux-x86_64.zip.asc blur-v0.1.7.6-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) <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.7.6-win-x86_64.zip.asc blur-v0.1.7.6-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.

@blur-network blur-network released this Oct 25, 2018

Assets 7

This update is mandatory for all nodes and is a point release for v0.1.7.5

sha256sums:
blur-v0.1.7.5.1-win-x86_64.zip:
94339456b02aaa163e1ba3051765898d6c9cfb46971e5efe4c3d225094d7fdef
blur-v0.1.7.5.1-mac-x86_64.zip:
0ad48502e906963459a87b2713e6c7237f4b7956ecba37c10e6ea7285174c032
blur--v0.1.7.5.1-ubuntu18-x86_64.tar.gz: a3a558a04c1be2a2c81e4a987831eae2a34d5f268a2236c93178fc1374262a38

Contents:


Seed Node Addresses:

  • Node 1: 178.128.191.245:14894
  • Node 2: 178.128.180.136:14894
  • Node 3: 178.128.186.101:14894

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 --seed-node 178.128.191.245:14894 --seed-node 178.128.180.136:14894 --seed-node 178.128.186.101:14894 --p2p-bind-port 14894 --rpc-bind-port 14895 --rpc-bind-ip 127.0.0.1

Alternatively, you may create a config file titled blurnet.conf in the directory located at ~/.blurnet on Linux. Add the following lines to that config file:

seed-node=178.128.191.245:14894
seed-node=178.128.186.101:14894
seed-node=178.128.180.136:14894

./blurd --seed-node 178.128.191.245:14894 --seed-node 159.203.48.201:14894 --seed-node 178.128.180.136:14894 --seed-node 178.128.186.101:14894 --config-file ~/.blurnet.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.7.5-win-x86_64 to switch to the directory you extracted the binaries into. Launch the daemon executable with the following options:

blurd.exe --seed-node 178.128.191.245:14894 --seed-node 178.128.180.136:14894 --seed-node 178.128.186.101:14894 --p2p-bind-port 14894 --rpc-bind-port 14895 --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

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).

Please add the seed nodes if you have trouble syncing. To do so, you may create a config file titled blurd.conf and place it in the same directory as the binaries. Add to that file the following lines:

seed-node=178.128.191.245:14894
seed-node=178.128.186.101:14894
seed-node=178.128.180.136:14894
p2p-bind-port=14894
rpc-bind-port=14895

Start the daemon file with the following command and flags:

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

Blockchain Bootstrap Procedure

Download & extract the `blockchain_bootstrap.zip` archive. You should have a folder named `export`. Move the export folder into your `blurnet` data directory.

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

Linux/Mac: ~/.blurnet/export/blockchain.raw
Windows: %PROGRAMDATA%\blurnet\export\blockchain.raw or %APPDATA\Roaming\blurnet\export\blockchain.raw

Import the blockchain file with: ./blur-blockchain-import --batch-size=130000. You should be bootstrapped and immediately synced up to block 129,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

How To Verify These Binaries:

At minimum, please verify these sha256sums to ensure you downloaded the correct file.

blur-v0.1.7.5-linux_x86_64.tar.gz: 28efaa4bd0bd2d99f6506c8d7c6d4b10a17cb89440d3e328bf08097ff8d09aac

blur-v0.1.7.5-mac-x86_64.zip: 0ad48502e906963459a87b2713e6c7237f4b7956ecba37c10e6ea7285174c032

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.7.5-linux-x86_64.zip.asc blur-v0.1.7.5-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) <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.7.5-win-x86_64.zip.asc blur-v0.1.7.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.

Oct 25, 2018
Fix Windows portion of Makefile
Oct 21, 2018
Set hardfork v8 height for 177100, add cnv8 changes, push back BPs

@blur-network blur-network released this Aug 11, 2018 · 109 commits to master since this release

Assets 11

Contents:


Seed Node Addresses:

  • Node 1: 178.128.191.245:14894
  • Node 2: 178.128.180.136:14894
  • Node 3: 178.128.186.101:14894

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 --seed-node 178.128.191.245:14894 --seed-node 178.128.180.136:14894 --seed-node 178.128.186.101:14894 --p2p-bind-port 14894 --rpc-bind-port 14895 --rpc-bind-ip 127.0.0.1

Alternatively, you may create a config file titled blurnet.conf in the directory located at ~/.blurnet on Linux. Add the following lines to that config file:

seed-node=178.128.191.245:14894
seed-node=178.128.186.101:14894
seed-node=178.128.180.136:14894

./blurd --seed-node 178.128.191.245:14894 --seed-node 159.203.48.201:14894 --seed-node 178.128.180.136:14894 --seed-node 178.128.186.101:14894 --config-file ~/.blurnet.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.7-win-x86_64 to switch to the directory you extracted the binaries into. Launch the daemon executable with the following options:

blurd.exe --seed-node 178.128.191.245:14894 --seed-node 178.128.180.136:14894 --seed-node 178.128.186.101:14894 --p2p-bind-port 14894 --rpc-bind-port 14895 --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

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).

Please add the seed nodes if you have trouble syncing. To do so, you may create a config file titled blurd.conf and place it in the same directory as the binaries. Add to that file the following lines:

seed-node=178.128.191.245:14894
seed-node=178.128.186.101:14894
seed-node=178.128.180.136:14894
p2p-bind-port=14894
rpc-bind-port=14895

Start the daemon file with the following command and flags:

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

Blockchain Bootstrap Procedure

Download & extract the `blockchain_bootstrap.zip` archive. You should have a folder named `export`. Move the export folder into your `blurnet` data directory.

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

Linux/Mac: ~/.blurnet/export/blockchain.raw
Windows: %PROGRAMDATA%\blurnet\export\blockchain.raw or %APPDATA\Roaming\blurnet\export\blockchain.raw

Import the blockchain file with: ./blur-blockchain-import --batch-size=120000. You should be bootstrapped and immediately synced up to block 129,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

How To Verify These Binaries:

At minimum, please verify these sha256sums to ensure you downloaded the correct file.

blur-v0.1.7-linux_x86_64.tar.gz: d9b600921752227ab8a1b087ab89d7227b7ef52025d87f46e6757963db872c56

blur-v0.1.7-mac-x86_64.tar.gz: fc174999c20ee9fca8dd419874c3e7ea1a219d7d983844c47945b7232cb305d0

blur-v0.1.7-win-x86_64.tar.gz: 05f0bcb52d384dd672e60ecc539bfd5fd074d14f993769661b4e5ca4ef578be5

blur-v0.1.7-ubuntu-16.04-x86_64.tar.gz: 47f235f08ecf3b7f0b0f16ac7b7557d6462b4c5895b3ef60a5a0a08227df0a8f

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.7-linux-x86_64.zip.asc blur-v0.1.7-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) <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.7-win-x86_64.zip.asc blur-v0.1.7-win-x86_64.zip The output should say "Good Signature." The warning message is due to no trust index being assigned to the signature, simply ignore it.

@blur-network blur-network released this Oct 21, 2018 · 38 commits to v0.1.7.5 since this release

Assets 2
redacted

fix cn_variant omission if b.major_version is > 6

@blur-network blur-network released this Jul 11, 2018 · 124 commits to master since this release

Assets 9

This update is mandatory for all nodes in the network. This update includes various bugfixes and improvements from upstream, including monero #3985, sync improvements, and finalized node updates. Those nodes are as follows:

Node 1: 178.128.191.245:14894
Node 2: 178.128.180.136:14894
Node 3: 178.128.186.101:14894
Node 4: 159.203.48.201:14894

Additionally, an API is now live at http://explorer.blur.cash/api/ (for example, the word 'transactions' at the end of that address will return a list of the 25 most recent transactions. It is a JSON-API and docs can be found on the blur-explorer repository page. It is tied directly to the block explorer which is also now live at http://explorer.blur.cash

For the fastest sync with the network run the daemon with the following command and options:

Linux:
./blurd --seed-node 178.128.191.245:14894 --seed-node 159.203.48.201.55:14894 --seed-node 178.128.180.136:14894 --seed-node 178.128.186.101:14894

Windows
blurd.exe --seed-node 178.128.191.245:14894 --seed-node 159.203.48.201:14894 --seed-node 178.128.180.136:14894 --seed-node 178.128.186.101:14894

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.6.1-linux-x86_64.zip.asc blur-v0.1.6.1-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) <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.6.1-win-x86_64.zip.asc blur-v0.1.6.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.

Linux Binaries & Instruction

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. To do so, you may create a config file titled blurnet.conf in the directory located at ~/.blurnet on Linux. Add the following lines to that config file:

seed-node=178.128.191.245:14894
seed-node=159.203.48.201:14894
seed-node=178.128.186.101:14894
seed-node=178.128.180.136:14894

Alternatively, open a terminal and launch the daemon executable with the following options:

./blurd --seed-node 178.128.191.245:14894 --seed-node 159.203.48.201:14894 --seed-node 178.128.180.136:14894 --seed-node 178.128.186.101:14894 --config-file ~/.blurnet/blurnet.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 Binaries & Instruction

Download and unzip the compressed binaries. Double click the file named blurd.exe. Your daemon will then begin to sync with the network.

Please add the seed nodes if you have trouble syncing. To do so, you may create a config file titled blurnet.conf in the directory located at C:\Program Data\blurnet on Windows. Add to that file the following lines:

seed-node=178.128.191.245:14894
seed-node=159.203.48.201:14894
seed-node=178.128.186.101:14894
seed-node=178.128.180.136:14894

Alternatively, open Windows Powershell and type cd Downloads/blur-v0.1.6.1-win-x86_64 to switch to the directory you extracted the binaries into. Launch the daemon executable with the following options:

./blurd.exe --seed-node 178.128.191.245:14894 --seed-node 159.203.48.201:14894 --seed-node 178.128.180.136:14894 --seed-node 178.128.186.101:14894 --config-file C:\Program Data\blurnet\blurnet.conf

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

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).

Blockchain Bootstrap Procedure

Download & extract the export.zip archive. You should have a folder named export. Move the export folder into your blurnet data directory.

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

Linux/Mac: ~/.blurnet/export/blockchain.raw
Windows: %PROGRAMDATA%/blurnet/export/blockchain.raw

You should immediately be bootstrapped and synced up to block 65,000, if the chain data was imported properly.