Maintenance & Version Control

  • Store your genesis file in a version-controlled repository (e.g GitHub) so changes are transparent and revertible.

  • If you decide to alter chain parameters after launch, you typically need a hard fork or a network-wide upgrade, which is subject to governance or validator consensus

Best Practices

  • Double-Check Allocations Ensure that all addresses and balances are correct before launch to avoid irreparable distribution issues.

  • Agree on the Chain ID All validators and participants must use the same chain ID; changing it post-launch can split or invalidate the network.

  • Document Any Custom Fields If you add custom fields for your PoS mechanism (e.g ExorPOS details), thoroughly document them so node operators and developers understand the meaning and effect.

  • Test Before Mainnet Always deploy a test network (testnet) to verify that your genesis file works with your node client, wallet integrations, and block explorers.

The Genesis File is the cornerstone of the Exorium Network defining the initial state, critical parameters, and overall β€œDNA” of the blockchain. Whether you are distributing tokens at launch, customizing block production, or enabling advanced features, the genesis file serves as the foundation upon which every subsequent block is built. Properly configuring and documenting this file is essential for a smooth, transparent network launch that all participants can trust.

Last updated