NodeCore QuickStart
Revision as of 22:27, 9 December 2018 by VeriBlockTim (talk | contribs) (Created page with "See: HowTo_run_NodeCore, NodeCore_Operations __TOC__ NodeCore is the full node daemon for VeriBlock. Because many common tasks require NodeCore, it should be as easy...")
See: HowTo_run_NodeCore, NodeCore_Operations
NodeCore is the full node daemon for VeriBlock. Because many common tasks require NodeCore, it should be as easy to get started as possible.
You need NodeCore for | You do NOT need NodeCore for |
---|---|
|
|
NodeCore has basic hardware needs that most machines will have. It will require disk space to store the full node (say 10GB and growing). See exact details here: NodeCore_Operations
For LINUX, run this install script (thank you OverCookedPanda):
TODO_LINK____
Besides checking hardware requirements and ensuring necessary software is installed (lie Java 8), it will:
- Get the latest NodeCore software, reading from this url: https://testnet.explore.veriblock.org/api/stats/download
- Get the latest Bootstrap file, also reading from the above url (you could sync from scratch, but it will be *much* faster to download the bootstrap file)
- Unzip the bootstrap file and put the nodecore.dat in the bin\testnet folder
- Set NodeCore to have execute permissions
- Run NodeCore in a screen
For WINDOWS:
There is not yet a one-stop install script, so the above steps will need to be done manually. But it can be done fast:
- Ensure the correct software installed from here: NodeCore_Operations (this is standard software, and may already exist)
- Get the latest links: https://testnet.explore.veriblock.org/api/stats/download
- nodecore_all_zip --> 100mb. Unzip this.
- bootstrapfile_zip --> several GB. Unzip this, it creates a "nodecore.dat" file, place it in the nodecore\bin\testnet folder. If "testnet" doesn't exist in "bin", then create it. (See: NodeCore_Bootstrap_File for more details)
- Run nodecore-0.3.9\bin\nodecore.bat
- Note: you could also run "start.bat", which kicks off the NodeCore_CLI, and run the "startnodecore" command. Both ways do the same thing.
See: HowTo_run_NodeCore for more details