Releases: blur-network/blur
Blur v0.1.7.6.1 'Lustrous Nebula (CNv8)'
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:
- Linux & Mac Instructions
- Windows Instructions
- Blockchain Bootstrap Procedure
- How to Verify These Binaries
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.
Blur v0.1.7.6 'Lustrous Nebula (CNv8)'
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:
- Linux & Mac Instructions
- Windows Instructions
- Blockchain Bootstrap Procedure
- How to Verify These Binaries
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 v0.1.7.5.1 'Lustrous Nebula (CNv8)'
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:
- Linux & Mac Instructions
- Windows Instructions
- Blockchain Bootstrap Procedure
- How to Verify These Binaries
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.
Blur v0.1.7 'Lustrous Nebula'
Contents:
- Linux & Mac Instructions
- Windows Instructions
- Blockchain Bootstrap Procedure
- How to Verify These Binaries
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 v0.1.7.5 'Lustrous Nebula (CNv8)'
redacted fix cn_variant omission if b.major_version is > 6
Blur v0.1.6.1 Amorphous Glare Updated'
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.
Blur v0.1.6 'Amorphous Glare'
This update includes new seed nodes for the network. It is a mandatory update; the previous nodes are no longer in operation. 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: 178.128.178.247:14894
Additionally, an API is now live at http://178.128.178.247:4949/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://178.128.180.136:8081.
For the fastest sync with the network run the daemon with the following command and options:
Linux:
./blurd --add-exclusive-node 178.128.191.245:14894 --add-exclusive-node 178.128.178.247:14894 --add-exclusive-node 178.128.180.136:14894 --add-exclusive-node 159.65.100.25:14894
Windows
blurd.exe --add-exclusive-node 178.128.191.245:14894 --add-exclusive-node 178.128.178.247:14894 --add-exclusive-node 178.128.180.136:14894 --add-exclusive-node 159.65.100.25: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.5-linux-x86_64.zip.asc blur-v0.1.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.5-win-x86_64.zip.asc blur-v0.1.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.
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=178.128.131.28:14894 seed-node=206.189.208.154:14894
Alternatively, open a terminal and launch the daemon executable with the following options:
./blurd --seed-node 178.128.191.245:14894 --seed-node 178.128.131.28:14894 --seed-node 206.189.208.154:14894
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:/Users/[your username]/AppData/Roaming/blurnet on Windows. Add to that file the following lines:
seed-node=178.128.191.245:14894 seed-node=178.128.131.28:14894 seed-node=206.189.208.154:14894
Alternatively, open Windows Powershell and type cd Downloads/blur-v0.1.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.131.28:14894 --seed-node 206.189.208.154:14894
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 blockchain-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: ~/.blurnet/export/blockchain.raw
Windows: %PROGRAMDATA%/blurnet/export/blockchain.raw
Blur v0.1.5 'Nebulous Glow' - Updated
This update is optional. These releases have only minor tweaks and maintenance. Checkpoints are updated for sync. If you have issues with either of these releases, use the previous release.
For the fastest sync with the network run the daemon with the following command and options:
Linux:
./blurd --add-exclusive-node 144.202.62.30:14894 --add-exclusive-node 45.76.29.176:14894 --add-exclusive-node 149.28.207.149:14894
Windows
blurd.exe --add-exclusive-node 144.202.62.30:14894 --add-exclusive-node 45.76.29.176:14894 --add-exclusive-node 149.28.207.149: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.5-linux-x86_64.zip.asc blur-v0.1.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.5-win-x86_64.zip.asc blur-v0.1.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.
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=149.28.207.149:14894 seed-node=144.202.62.30:14894 seed-node=45.76.29.176:14894
Alternatively, open a terminal and launch the daemon executable with the following options:
./blurd --seed-node 45.76.29.176:14894 --seed-node 144.202.62.30:14894 --seed-node 149.28.207.149:14894
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:/Users/[your username]/AppData/Roaming/blurnet on Windows. Add to that file the following lines:
seed-node=149.28.207.149:14894 seed-node=144.202.62.30:14894 seed-node=45.76.29.176:14894
Alternatively, open Windows Powershell and type cd Downloads/blur-v0.1.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 45.76.29.176:14894 --seed-node 144.202.62.30:14894 --seed-node 149.28.207.149:14894
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 blockchain-bootstrap-blur.tar.bz2 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: ~/.blurnet/export/blockchain.raw
Windows: %PROGRAMDATA%/blurnet/export/blockchain.raw
Now simply run the blur-blockchain-import executable. It will find the bootstrap in the export directory that you moved the blockchain.raw file into automatically, and you will be synced to block 20,000 immediately.
Blur v0.1.5 'Nebulous Glow'
This release will implement the v6 hardfork and is mandatory. The upgrade is scheduled for block 7500. A new, faster hashing algorithm will significantly increase mining rates.
Nodes that are updated will retain their full blockchain, with a hardfork at block 7500. If your binaries are not updated by the fork, your node will no longer be on the mainnet chain.
Note that the Windows executables will be blocked by your Anti-virus/Windows Defender. Add an exception or disable temporarily to download and run.
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.5-linux-x86_64.zip.asc blur-v0.1.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.5-win-x86_64.zip.asc blur-v0.1.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.
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=149.28.207.149:14894 seed-node=144.202.62.30:14894 seed-node=45.76.29.176:14894
Alternatively, open a terminal and launch the daemon executable with the following options:
./blurd --seed-node 45.76.29.176:14894 --seed-node 144.202.62.30:14894 --seed-node 149.28.207.149:14894
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:/Users/[your username]/AppData/Roaming/blurnet on Windows. Add to that file the following lines:
seed-node=149.28.207.149:14894 seed-node=144.202.62.30:14894 seed-node=45.76.29.176:14894
Alternatively, open Windows Powershell and type cd Downloads/blur-v0.1.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 45.76.29.176:14894 --seed-node 144.202.62.30:14894 --seed-node 149.28.207.149:14894
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 blockchain-bootstrap-blur.tar.bz2 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: ~/.blurnet/export/blockchain.raw
Windows: C:/Users/[your username]/AppData/Roaming/blurnet/export/blockchain.raw
Now simply run the blur-blockchain-import executable. It will find the bootstrap in the export directory that you moved the blockchain.raw file into automatically, and you will be synced to block 15,000 immediately.
Blur v0.1.2.1 'Luminous Primed'
Network has been primed for hardfork v6 (testing on testnet with this release). The next release will have the v6 hardfork hardcoded to take place at a predetermined block height
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=149.28.207.149:14894 seed-node=144.202.62.30:14894 seed-node=45.76.29.176:14894
Alternatively, open a terminal and launch the daemon executable with the following options:
./blurd --seed-node 45.76.29.176:14894 --seed-node 144.202.62.30:14894 --seed-node 149.28.207.149:14894
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 %APPDATA%/blurnet on Windows. Add to that file the following lines:
seed-node=149.28.207.149:14894 seed-node=144.202.62.30:14894 seed-node=45.76.29.176:14894
Alternatively, open Windows Powershell and type cd Downloads/blur-v0.1.2.1-win-x86_64 to switch to the directory you extracted the binaries into. Launch the daemon executable with the following options:
./blurd --seed-node 45.76.29.176:14894 --seed-node 144.202.62.30:14894 --seed-node 149.28.207.149:14894
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 bootstrap archive. You should have a folder named export. Move the export folder into your data directory, at either ~/.blurnet for Linux users, or %APPDATA%/blurnet for Windows.
This should result in following structure:
Linux: ~/.blurnet/export/blockchain.raw
Windows: %APPDATA%/blurnet/export/blockchain.raw
Now simply run the blur-blockchain-import executable. It will find the bootstrap automatically, and you will be synced immediately.