Difference between revisions of "HowTo run AlphaNet"
(typo on peers config)
|Line 33:||Line 33:|
Revision as of 16:04, 12 August 2019
When developing, it is helpful to run a local node with low difficulty and fast sync time. The AlphaNet allows this.
AlphaNet is separate from TestNet or MainNet... nodes do not talk across different networks, and coins cannot be sent from one network to the other. Alpha coins are intended for local development purposes.
AlphaNet uses port 7502 and 10502
How to run alpha locally
#NodeCore Configuration #set network to alpha and do not pull any bootstrap nodes network=alpha peer.bootstrap.enabled=false #Allow a CPU pool so that we can mine and get new blocks pool.stats.bind.address=0.0.0.0 ucp.mining.bind.address=0.0.0.0
If you wanted to set up a network of multiple nodes in alpha, you can still explicitly add nodes:
Have just these 3 files in the bin folder (delete any previous "alpha" folder if it existed)
This should create an "bin\alpha" folder (instead of a bin\testnet or bin\mainnet folder)
Connect via the NC_CLI
Alpha runs on port 10502 (instead of 10501 or 10500)
So connect to a local alpha instance via:
Run a CPU miner to get coins
In the NC_CLI, start a CPU pool
#Allow a CPU pool startpool CPU
Run the PoW CPU Miner (part of the nodecore suite). See: HowTo_run_PoW_CPU_Miner. This will require 3 inputs:
- Number of threads --> hit [ENTER] to accept default
- Address/Port --> hit [ENTER] to accept default of connecting to local host
- Address --> use any address, such as the result of getinfo in the NC_CLI
NOTE: If for some reason the CPU Miner gets stuck (block height is not increasing), then restart the CPU Miner.
If everything is successful, the following will all be running locally:
- NodeCore is running.
- Block height is increasing.
- A folder "bin\alpha" has been created
- NC_CLI is running, and run getinfo to see latest block and balance. Run any command from the NodeCore_CommandLine
- PoW CPU miner is running, submitting shares