Complete guide to configure and run a BoostChain masternode
1 core (minimum)
2+ cores (recommended)
2 GB (minimum)
4 GB (recommended)
40 GB SSD
(with room for growth)
100 Mbps
Static public IPv4
Send exactly 1,000.00000000 BOOST to a new address in your wallet. It's crucial that it's exactly 1,000 BOOST in a single transaction.
Wait for at least 5 confirmations (approximately 5 minutes) before proceeding to the next step.
In your wallet console, run:
Consolemasternode outputs
You'll get something like:
{
"fdab9dff1ff9caf5d291905ad43b9f7d69775189d4d22cb085d7fedd94ea1c6a": "0"
}
The first value is your collateralHash and the second is your collateralIndex (usually "0" or "1"). Save both values.
In the wallet console, run:
Consolebls generate
You'll get something like:
{
"secret": "64f6f0e27be5d171b23f91803e9ad8fa1a92cb6a1f857eb664d5ab1ac35e514b",
"public": "0b961a0679d231f2837515b4e7952792fae047143089fc7bc160ec5946496a61485993e358fad5342be32e3ce239fe8f",
"scheme": "legacy"
}
Save both keys securely. The secret will be used on the VPS and the public in the ProTx registration.
Generate three addresses for different purposes. Run this command three times in the console:
Consolegetnewaddress
Label each address as follows:
In Core wallet:
This will be your feeSourceAddress. You need a small amount (~ 0.01 BOOST) for registration fees.
Now you'll use the protx register command to register your masternode on the network.
protx register "collateralHash" "collateralIndex" "ipAndPort" "ownerAddress" "operatorPubKey" "votingAddress" "operatorReward" "payoutAddress" "feeSourceAddress"
Fill in all the fields below to generate your protx register command:
masternode outputs
getnewaddress
bls generate (public key)
Bashssh root@YOUR_VPS_IP
Bashapt update && apt upgrade -y
Bashadduser boostchain usermod -aG sudo boostchain su - boostchain
Download the latest version from the official repository:
Bash# Create directory for binary mkdir -p ~/boostchain cd ~/boostchain # Download (replace X.X.X with current version) wget https://github.com/boostchain/boostchain/releases/download/vX.X.X/boostchain-X.X.X-x86_64-linux-gnu.tar.gz # Extract tar -xvzf boostchain-X.X.X-x86_64-linux-gnu.tar.gz # Copy binaries to PATH sudo cp boostchain-X.X.X/bin/* /usr/local/bin/ # Verify installation boostchaind --version
First, create the data directory:
Bashmkdir -p ~/.boostchaincore nano ~/.boostchaincore/boostchain.conf
Fill in the required fields to generate your boostchain.conf file with secure random RPC credentials:
bls generate (secret key from step 2.4)
Bashboostchaind
The node will start syncing with the blockchain. This may take several hours.
To check progress:
boostchain-cli getblockcount
boostchain-cli mnsync status
After successfully running the protx register command, you'll receive a ProTx Hash (transaction ID). This is your masternode's unique identifier on the network.
The output will look something like:
7da2e1187202a1a497beca05e0e53a6e4df0dc06046f72fbf8b61c942db2982a
This is your ProTx Hash. Keep it safe - you'll need it to check your masternode status.
On the VPS, run:
boostchain-cli mnsync status
It should show "AssetName": "MASTERNODE_SYNC_FINISHED"
After completing the ProTx registration and once your VPS is fully synced, your masternode will automatically start and appear in the masternode list.
On the VPS, check masternode status:
boostchain-cli masternode status
You should see:
{
"outpoint": "fdab9dff1ff9caf5d291905ad43b9f7d69775189d4d22cb085d7fedd94ea1c6a-0",
"service": "1.2.3.4:9939",
"proTxHash": "7da2e1187202a1a497beca05e0e53a6e4df0dc06046f72fbf8b61c942db2982a",
"status": "Ready"
}
You can also check from your wallet console:
protx info "YOUR_PROTX_HASH"
boostchain-cli masternode status
boostchain-cli masternode list
boostchain-cli getinfo
boostchain-cli getbalance
| Problem | Solution |
|---|---|
| Masternode not showing as ENABLED | Verify the collateral has at least 15 confirmations and the masternode.conf file is correct. |
| Error "Not capable masternode" | Verify the VPS has port 9999 open and externalip is configured correctly. |
| Node not syncing | Check network connectivity, make sure you're using the latest software version. |
| Masternode in POSE_BANNED state | Your node has had too much downtime. Verify the service is running and wait for automatic restoration. |