Difference between revisions of "NodeCore QuickStart"
VeriBlockTim (talk | contribs) |
Crunchycat (talk | contribs) m (Removed 'testnet' from testnet.explore.veriblock.org/api/stats/download, changed 'test' to 'main' throughout, changed port 10501 to 10500) |
||
Line 29: | Line 29: | ||
# Ensure the correct software installed from here: [[NodeCore_Operations]] (this is standard software, and may already exist) | # Ensure the correct software installed from here: [[NodeCore_Operations]] (this is standard software, and may already exist) | ||
− | # Get the latest links: https:// | + | # Get the latest links: https://explore.veriblock.org/api/stats/download |
# '''nodecore_all_zip''' --> 100mb. Unzip this. | # '''nodecore_all_zip''' --> 100mb. Unzip this. | ||
## The download file looks something like https://github.com/VeriBlock/nodecore-releases/releases/download/v0.XX/veriblock-nodecore-all-0.XX.zip | ## The download file looks something like https://github.com/VeriBlock/nodecore-releases/releases/download/v0.XX/veriblock-nodecore-all-0.XX.zip | ||
# '''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) | # '''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) | ||
## The download file looks something like: http://mirror1.veriblock.org/nodecore-bootstrap-XXXXXX.zip | ## The download file looks something like: http://mirror1.veriblock.org/nodecore-bootstrap-XXXXXX.zip | ||
− | ## The end result, there will be a file like "nodecore\bin\ | + | ## The end result, there will be a file like "nodecore\bin\mainnet\nodecore.dat" |
## Reminder that the bootstrap file is not needed - you could sync from scratch - but it will be much faster to sync using the latest bootstrap file | ## Reminder that the bootstrap file is not needed - you could sync from scratch - but it will be much faster to sync using the latest bootstrap file | ||
# Run the startup script (such as "nodecore-0.X.X\bin\'''nodecore.bat'''" for Windows) | # Run the startup script (such as "nodecore-0.X.X\bin\'''nodecore.bat'''" for Windows) | ||
Line 48: | Line 48: | ||
Besides checking hardware requirements and ensuring necessary software is installed (lie Java 8), the script will automatically: | Besides checking hardware requirements and ensuring necessary software is installed (lie Java 8), the script will automatically: | ||
− | # Get the latest NodeCore software, reading from this url: https:// | + | # Get the latest NodeCore software, reading from this url: https://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) | # 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\ | + | # Unzip the bootstrap file and put the nodecore.dat in the bin\mainnet folder |
# Set file "nodecore" to have execute permissions | # Set file "nodecore" to have execute permissions | ||
# Run "nodecore" in a screen | # Run "nodecore" in a screen | ||
Line 63: | Line 63: | ||
# Ensure the correct software installed from here: [[NodeCore_Operations]] (this is standard software, and may already exist) | # Ensure the correct software installed from here: [[NodeCore_Operations]] (this is standard software, and may already exist) | ||
− | # Get the latest links: https:// | + | # Get the latest links: https://explore.veriblock.org/api/stats/download |
# '''nodecore_all_zip''' --> 100mb. Unzip this. | # '''nodecore_all_zip''' --> 100mb. Unzip this. | ||
## The download file looks something like https://github.com/VeriBlock/nodecore-releases/releases/download/v0.XX/veriblock-nodecore-all-0.XX.zip | ## The download file looks something like https://github.com/VeriBlock/nodecore-releases/releases/download/v0.XX/veriblock-nodecore-all-0.XX.zip | ||
− | # '''bootstrapfile_zip''' --> several GB. Unzip this, it creates a "nodecore.dat" file, place it in the nodecore\bin\ | + | # '''bootstrapfile_zip''' --> several GB. Unzip this, it creates a "nodecore.dat" file, place it in the nodecore\bin\mainnet folder. If "mainnet" doesn't exist in "bin", then create it. (See: [[NodeCore_Bootstrap_File]] for more details) |
## The download file looks something like: http://mirror1.veriblock.org/nodecore-bootstrap-XXXXXX.zip | ## The download file looks something like: http://mirror1.veriblock.org/nodecore-bootstrap-XXXXXX.zip | ||
− | ## The end result, there will be a file like "nodecore\bin\ | + | ## The end result, there will be a file like "nodecore\bin\mainnet\nodecore.dat" |
## Reminder that the bootstrap file is not needed - you could sync from scratch - but it will be much faster to sync using the latest bootstrap file | ## Reminder that the bootstrap file is not needed - you could sync from scratch - but it will be much faster to sync using the latest bootstrap file | ||
# Run nodecore-0.X.X\bin\'''nodecore.bat''' | # Run nodecore-0.X.X\bin\'''nodecore.bat''' | ||
Line 93: | Line 93: | ||
You could run either the NC_CLI or GUI Wallet and connect. For example, click "start.bat" (windows) or "start" (linux) to run the NC_CLI: | You could run either the NC_CLI or GUI Wallet and connect. For example, click "start.bat" (windows) or "start" (linux) to run the NC_CLI: | ||
− | # connect "connect 127.0.0.1: | + | # connect "connect 127.0.0.1:10500" |
# run getstateinfo | # run getstateinfo | ||
Line 107: | Line 107: | ||
# In the NodeCore suite: "veriblock-nodecore-all-0.X.XX", run "start" (linux) or "start.bat" (windows) | # In the NodeCore suite: "veriblock-nodecore-all-0.X.XX", run "start" (linux) or "start.bat" (windows) | ||
− | # connect to your running instance of NodeCore, such as typing "connect 127.0.0.1: | + | # connect to your running instance of NodeCore, such as typing "connect 127.0.0.1:10500" |
# type "getinfo" | # type "getinfo" | ||
# By default, a new wallet address is created, and it will have zero balance | # By default, a new wallet address is created, and it will have zero balance | ||
− | If this is a new install (bin\ | + | If this is a new install (bin\mainnet folder is empty), then the NC_CLI should be able to connect to NodeCore within about 10 seconds - i.e. it does not need to fully sync. |
− | If restarting NodeCore (bin\ | + | If restarting NodeCore (bin\mainnet folder has a nodecore.dat file), then it must sync before NC_CLI can connect. |
<pre> | <pre> |
Revision as of 03:21, 19 April 2019
See: HowTo_run_NodeCore, NodeCore_Operations, NodeCore_Bootstrap_File
Contents
How to Install
NodeCore should run on any OS that supports Java 1.8 (Linux, Windows, Mac...)
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
General Process
- Ensure the correct software installed from here: NodeCore_Operations (this is standard software, and may already exist)
- Get the latest links: https://explore.veriblock.org/api/stats/download
- nodecore_all_zip --> 100mb. Unzip this.
- The download file looks something like https://github.com/VeriBlock/nodecore-releases/releases/download/v0.XX/veriblock-nodecore-all-0.XX.zip
- 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)
- The download file looks something like: http://mirror1.veriblock.org/nodecore-bootstrap-XXXXXX.zip
- The end result, there will be a file like "nodecore\bin\mainnet\nodecore.dat"
- Reminder that the bootstrap file is not needed - you could sync from scratch - but it will be much faster to sync using the latest bootstrap file
- Run the startup script (such as "nodecore-0.X.X\bin\nodecore.bat" for Windows)
- Note: you could also run "start" or "start.bat", which kicks off the NodeCore_CLI, and run the "startnodecore" command. Both ways do the same thing.
For LINUX
A community member committed this script (thank you OverCookedPanda) [DISCLAIMER: this is a community script]:
https://github.com/overcookedpanda/veriblock-scripts/blob/master/vbkinstall.sh
Besides checking hardware requirements and ensuring necessary software is installed (lie Java 8), the script will automatically:
- Get the latest NodeCore software, reading from this url: https://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\mainnet folder
- Set file "nodecore" to have execute permissions
- Run "nodecore" in a screen
For WINDOWS
A community member committed this powershell script (thank you KernelPanick) [DISCLAIMER: this is a community script]:
https://gist.github.com/gsxryan/20795e55d1e8ef079e42062656cc7eea
Manual Windows steps:
- Ensure the correct software installed from here: NodeCore_Operations (this is standard software, and may already exist)
- Get the latest links: https://explore.veriblock.org/api/stats/download
- nodecore_all_zip --> 100mb. Unzip this.
- The download file looks something like https://github.com/VeriBlock/nodecore-releases/releases/download/v0.XX/veriblock-nodecore-all-0.XX.zip
- bootstrapfile_zip --> several GB. Unzip this, it creates a "nodecore.dat" file, place it in the nodecore\bin\mainnet folder. If "mainnet" doesn't exist in "bin", then create it. (See: NodeCore_Bootstrap_File for more details)
- The download file looks something like: http://mirror1.veriblock.org/nodecore-bootstrap-XXXXXX.zip
- The end result, there will be a file like "nodecore\bin\mainnet\nodecore.dat"
- Reminder that the bootstrap file is not needed - you could sync from scratch - but it will be much faster to sync using the latest bootstrap file
- Run nodecore-0.X.X\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.
For Mac
There is not yet a one-stop install script, so the above steps will need to be done manually.
Basically, follow the install steps listed above for Windows, namely ensure your system has the software specs (Java), download NodeCore (and optionally the bootstrap file), and execute the bin\nodecore script.
See: HowTo_run_NodeCore for more details
What Success Looks like
A "nodecore" process should be running,
Your NodeCore instance should have created files:
You could run either the NC_CLI or GUI Wallet and connect. For example, click "start.bat" (windows) or "start" (linux) to run the NC_CLI:
- connect "connect 127.0.0.1:10500"
- run getstateinfo
You should see something like so, i.e. a JSON response showing relevant info like the local height and network height:
What Next?
View your wallet
Note that NodeCore creates a new wallet/address by default. If you run getinfo in the NC_CLI, you'll see the default address (NodeCore_CommandLine#getinfo).
- In the NodeCore suite: "veriblock-nodecore-all-0.X.XX", run "start" (linux) or "start.bat" (windows)
- connect to your running instance of NodeCore, such as typing "connect 127.0.0.1:10500"
- type "getinfo"
- By default, a new wallet address is created, and it will have zero balance
If this is a new install (bin\mainnet folder is empty), then the NC_CLI should be able to connect to NodeCore within about 10 seconds - i.e. it does not need to fully sync.
If restarting NodeCore (bin\mainnet folder has a nodecore.dat file), then it must sync before NC_CLI can connect.
getinfo #returns info for a specific command rpc (77.46.106.162:10500) > { "payload": { "default_address": { "address": "VazUQm9TaPmbhTWEi6FYUUPp28Eynq", "amount": 187457753607875 },
Get more involved
- Run the GUI Wallet (GUI Wallet)
- Start PoW Mining with a GPU (HowTo_run_PoW_GPU_Miner)
- Start PoP Mining (HowTo_run_PoP_Miner)
- Start a Community Pool (HowTo_run_and_connect_to_PoW_Miner_pool)
- Join the community and help others! https://discord.gg/wJZEjry