Run a node
Decide what the node is for
Section titled “Decide what the node is for”| Role | Primary job | Planning considerations |
|---|---|---|
| Validator | Participate in consensus | Membership authorization, keys, availability and bounded retention |
| Full | Serve and follow chain data | Peer connectivity, historical bootstrap and configured retention |
| Archive | Serve historical state | Storage growth, snapshots, deltas and expensive-query limits |
Do not size production hardware from an unqualified TPS figure. Use the workload and topology in the throughput test methodology, then measure your own environment.
Build and configure
Section titled “Build and configure”Request the official V2 release or source access and its configuration examples from Tolar. The repository is not publicly accessible at present. The project’s C++ toolchain is Clang 22; follow the supplied release’s build instructions rather than a historical V1 guide.
Verify the network configuration, genesis, role, peers, RPC exposure and data directories. Never publish validator keys or copy production secrets into a website configuration.
Bootstrap and retention
Section titled “Bootstrap and retention”Historical bootstrap requires a compatible, authenticated data source and the correct network/checkpoint. Validate snapshot or archive commitments using the supported tooling. Retention settings determine which later queries the node can answer.
A successful startup does not by itself prove that every historical query is available. Test the exact RPC paths your application needs.
Validator membership
Section titled “Validator membership”Live membership follows Tolar’s V1 designated-update-key model. It is not permissionless self-registration or a public staking flow. Changes require the authorized process and coordinated operational checks documented in source.
Upgrade deliberately
Section titled “Upgrade deliberately”Review release notes, activation requirements, database compatibility and recovery procedures. Back up the required state, test the upgrade on a representative environment, and verify network health and RPC behavior afterward.
Version-specific commands, bootstrap locations and production configuration must come with the official release. This overview is not a complete deployment runbook.