Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature: reset node states #1195

Open
piux2 opened this issue Oct 4, 2023 · 0 comments
Open

Feature: reset node states #1195

piux2 opened this issue Oct 4, 2023 · 0 comments

Comments

@piux2
Copy link
Contributor

piux2 commented Oct 4, 2023

Description

To run a gno.land node in both production and local testnet environments, the node must have the capability to reset to its original state during migration, upgrades, and testing.

Currently, to achieve this, we delete the "testdir" which is created by default when starting gno.land. However, this action also deletes testdir/config/config.toml, leading to the loss of any configuration changes.

There are two primary methods to reset the network:

  • Hard Reset (Unsafe): This method involves removing the data and resetting the validator state back to its genesis. It is typically used in testnet environments. There is no coordinated upgrade and reset needed.

  • Soft Reset (Safer): In this approach, only the data is removed while retaining the validator state from the time of the reset. This method is favored in production environments to prevent issues like double signing and network forking. After a soft reset, the node must synchronize transactions and states from other nodes until it reaches the height where the soft reset occurred.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: 🌟 Wanted for Launch
Development

No branches or pull requests

1 participant