NodeCore File Structure
- 1 Overview
- 2 By File Type
- 3 By File
- 4 By Function
- 5 Other Notes
The NodeCore package has two main folders:
- bin - The scripts and data files. This page will discuss the files here.
- lib - All the jar files. This could be about 50 files and 30MB.
NodeCore starts with two script files:
- nodecore --> execute on linux/mac
- nodecore.bat --> execute on windows
Running NodeCore creates several additional local files. These store data (like the blockchain, wallet, pool, etc...) and configuration.
Note that NodeCore has a startup "-d" parameter to write the data files to a specific folder:
#Linux Example ./nodecore -d ~/data/ #Windows Example nodecore.bat -d E:\Data
By File Type
Standard log files, generated by slf4j.
Plaintext files, user can modify these config values.
Contains data written by NodeCore. These are SQLite files.
The nodecore.dat file can be viewed with a SQLite browser: http://sqlitebrowser.org, however it is an internal file intended to be written to solely by the NodeCore instance.
The others have their own special formats and are not SQLite databases.
- tcache.csh - A cache file of nodecore.dat such that NodeCore can reload the blockchain much faster upon restart.
- poolshares.txt - A plaintext file that stores the history of submitted shares to the pool operated by the local NodeCore instance (will not be present if pool has never been run).
The blockchain data itself, as well as additional operational information (blacklisting IPs, caching broadcast blocks, etc...). This is the distributed ledger shared among all nodes.
To view the public blockchain, check out the dashboard: https://testnet.explore.veriblock.org
See: nodecore.properties for exact reference on each property value.
If this file does not exist, then NodeCore will create it.
If this file is changed, then NodeCore may need to be restarted to use the new value.
Rolling log file. Older logs will have the date in them, such as veriblock.nodecore-2018-04-04.0.log.
veriblock.nodecore.log is always the most recent log.
Contains just errors, ideally this is always empty.
The results of the pool. See: HowTo_run_and_connect_to_PoW_Miner_pool
ROUND,1 VGdQFeskH63Wk8Xk3bJM8hLDG8CLV1,1 ROUND,2 VGdQFeskH63Wk8Xk3bJM8hLDG8CLV1,1
The dedicated wallet for the pool. This is an internal file.
A backup file for the pool. This is an internal file.
A configuration file for the pool's wallet. This is an internal file.
A cache file for the blockchain, built upon first load, such that subsequent restarts of NodeCore are much faster.
Your wallet, with addresses and balances. The NodeCore_CommandLine provides several wallet-features:
- getbalance - see the available balances
- backupwallet - copies the wallet.dat (and related files) to a specific backup location.
A configuration file for the wallet. This is an internal file.
NodeCore Executable (affects all)
The wallet stores a list of public-private keypairs. The wallet does not contain any information regarding transactions or balances.
To backup the wallet, one can run the backupwallet command from NodeCore_CommandLine, and this would copy their files to the given location.
Under the bin folder, there is a separate TestNet subfolder for various data files for testnet.