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

Reminder: need to set VerifyGenesisSignatures to true on mainnet, #1104

Open
piux2 opened this issue Sep 6, 2023 · 2 comments
Open

Reminder: need to set VerifyGenesisSignatures to true on mainnet, #1104

piux2 opened this issue Sep 6, 2023 · 2 comments

Comments

@piux2
Copy link
Contributor

piux2 commented Sep 6, 2023

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

VerifyGenesisSignatures: false, // for development

@moul
Copy link
Member

moul commented Sep 6, 2023

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.

See #1050 and #1102 for more details.

@moul
Copy link
Member

moul commented Oct 15, 2024

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
No open projects
Development

No branches or pull requests

4 participants