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

Implement sudo mode tooling for testing #4265

Open
aubrika opened this issue Apr 24, 2024 · 1 comment
Open

Implement sudo mode tooling for testing #4265

aubrika opened this issue Apr 24, 2024 · 1 comment
Labels
A-testing Area: Relates to testing of Penumbra A-tooling Area: developer tooling for building Penumbra itself _P-V2 Priority: after mainnet

Comments

@aubrika
Copy link
Contributor

aubrika commented Apr 24, 2024

We should have the ability for a Penumbra node to fork and then simulate the as close to the exact state of a given network as possible.

Penumbra's support for consensus key rotation makes this possible: we can implement tooling in a pd subcommand, e.g., pd sudo-fork, that:

  • does a custom migration-like (not an actual migration but implemented using the same in-place edit functionality) operation editing all of the validator definitions to have new consensus keys
  • this should also overwrite the cometbft data describing the validator set, which may or may not require surgery
  • copies the resulting data to make a clone of all active validators
  • generates Docker config data for running all those clones in a single docker-compose operation
@aubrika aubrika added A-tooling Area: developer tooling for building Penumbra itself A-testing Area: Relates to testing of Penumbra needs-refinement unclear, incomplete, or stub issue that needs work labels Apr 24, 2024
@github-project-automation github-project-automation bot moved this to Backlog in Penumbra Apr 24, 2024
@hdevalence
Copy link
Member

hdevalence commented May 6, 2024

We should implement a basic upgrade smoke-test first, and aim to do this more complex simulation capability post-mainnet.

@cratelyn cratelyn added the _P-V2 Priority: after mainnet label May 6, 2024
@aubrika aubrika removed the needs-refinement unclear, incomplete, or stub issue that needs work label May 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-testing Area: Relates to testing of Penumbra A-tooling Area: developer tooling for building Penumbra itself _P-V2 Priority: after mainnet
Projects
Status: Backlog
Development

No branches or pull requests

3 participants