You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We need to verifying the signatures of txs in genesis file upon mainnet launch. We might want to set default to true before the release. This could be a backdoor for production
I'm considering changing gnoland start to gnoland dev to facilitate users in crafting custom genesis files for experimentation. Meanwhile, gnoland start will be tailored for production use, having fixed parameters and incorporating VerifyGenesisSignatures.
This is a simple fix, but we actually want to revert it to continue development.
I suggest making this either a configuration file option that can be changed without patching the codebase or a fuse variable that can be set with a transaction. This way, we can expect a chain to start as false and then, from a specific transaction, change to true, without the ability to revert.
We need to verifying the signatures of txs in genesis file upon mainnet launch. We might want to set default to true before the release. This could be a backdoor for production
gno/gno.land/pkg/gnoland/app.go
Line 54 in 4bd1789
The text was updated successfully, but these errors were encountered: