testnet-canonical

This repository is the starting point for anyone wanting to work on or test the bitcoin-hivemind project.

• Instructions for developers and testers
• Modified testnet seeder (syncs only to the last canonical block height)
• Script to generate canonical blockchain data using the hivemind-cli
• Backups of the canonical blockchain(s)

Starting development / testing (environment setup and building):

1. You may use the following guide to setup a remote node, or follow the instructions on a virtual machine / your local system: Fullnode setup guide

2. Edit your configuration file (~/.hivemind/hivemind.conf) and append the following line

testnet=1

3. Start the client of your choice (hivemindd & hivemind-cli or hivemind-qt) You should connect automatically to the testnet seeder node(s), if not run the following command through the debug window or hivemind-cli

addnode 162.243.37.30 onetry

Reseting your environment, how to start over with the canonical blockchain data for testing:

1. Make sure that all instances of hivemind (hivemindd, hivemind-cli and hivemind-qt) are completely shutdown

ps -aux | grep hivemind

The above command will list any process on the system with the name hivemind, look for any running daemons or hivemind-qt instances.

2. Remove hivemind's data directory Warning: be careful with the rm command, it will permanently delete files also note that this will remove all transactions, blocks, your configuration files and all of your private keys (coins) which you have created with hivemind.

rm -rf ~/.hivemind/

3. Remove the directory to which you have built hivemind.

4. Re-download the source code and build it fresh again using the Fullnode setup guide

Running the testnet seed node (modified to sync a certain number of blocks of data)

Testnet nodes for bitcoin-hivemind are modified to accept a certain number of blocks, up to nHeight of canonical blockchain data. This is to provide developers a testing environment with examples of hivemind's functions, which is always available in a clean state. Once a developer has synced with the seed node, they can create blocks and share blocks with other nodes that they connect to on the network. If for any reason however, the developer needs to reset the environment they need only erase the data they have added and restore the 'backup' by syncing with the seed node which has remained unchanged.

1. Download the source code and build it using the Fullnode setup guide

2. Edit your configuration file (~/.hivemind/hivemind.conf) and append the following line

testnet=1

3. Set the block sync limit by either:

• Copying the main.cpp file from this repository to replace the main.cpp in your local repository.
• Editing main.cpp in your code, adding the following to the AcceptBlock function after line 2754:

// Don't accept any blocks higher than last block of canonical blockchain data
if (nHeight > 300) {
    return false;
}

4. Copy the canonical blockchain data (blocks/blocks.tar.gz) from this repository into your ~/.hivemind/testnet folder

5. Extract the contents of the blocks archive inside of the testnet directory:

tar -xvzf blocks.tar.gz

5. Start the hivemindd daemon with the -rescan option

./src/hivemindd -rescan