Update Solana genesis hash #678
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
After restarting the Solana Testnet, the new Genesis hash value was not updated, so I have adjusted it accordingly. (See references: Genesis Config, Gist link)
Unlike other blockchains, Solana’s Devnet and Testnet share the same RPC settings, which means the smart contracts deployed on Devnet are being used. Consequently, all current smart contracts are deployed on Devnet, and even if you configure it for Testnet, the RPC still operates through Devnet.
This setup can be confusing for developers.
However, before merging, it is necessary to deploy the smart contracts on the Testnet.