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

Native SDK Local Network State Export #1422

Closed
gzukel opened this issue Nov 30, 2023 · 2 comments · Fixed by #1979
Closed

Native SDK Local Network State Export #1422

gzukel opened this issue Nov 30, 2023 · 2 comments · Fixed by #1979
Assignees
Milestone

Comments

@gzukel
Copy link
Contributor

gzukel commented Nov 30, 2023

The way generating a state export for upgrade path testing works currently is a bit flawed. We take a state export then we use python to manipulate a json file to try and prepare a state for starting a single node network. This isn't exactly reliable or efficient.

What makes more sense is giving the cli a function that can prepare a mainnet state export using the native CosmosSDK for starting local single node testing networks derived from the mainnet state.

That way the SDK can manipulate the genesis as it writes it to be able to start a local network with a provided account address as the validator address to assign the power to start the network too.

Also, we should examine the state export code when doing this to try and reduce or limit its speed to reduce resources required to take a state export instead of trying to do it as fast as possible limit the memory usage and keep the export within a set of bounds to have it be more predictable.

@CharlieMc0
Copy link
Member

@kingpinXD
Copy link
Contributor

kingpinXD commented Apr 8, 2024

The following are already added when we create a new genesis,

  • Observer List
  • Validators
    This happens through the zetacored add-observer-list observers.json command

The same command takes an additional option input for tss-pubkey
Example :

zetacored add-observer-list observers.json --keygen-block=0 --tss-pubkey="zetapub1addwnpepq28c57cvcs0a2htsem5zxr6qnlvq9mzhmm76z3jncsnzz32rclangr2g35p"

Which can be used to add the following details

  • TSS Address
  • TSS Nonce

Connector and token contracts are set through chain params,which can be updated via MsgUpdateChainParams

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

Successfully merging a pull request may close this issue.

4 participants