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

chore: bump chain id for testnet 73 #4274

Merged
merged 1 commit into from
Apr 26, 2024
Merged

Conversation

conorsch
Copy link
Contributor

@conorsch conorsch commented Apr 26, 2024

Describe your changes

We mistakenly broke testnet 72 on chain upgrade, by leaving a forked network running that caused tombstoning. To resolve, we're going to reset chain state and use a new chain id. This commit ensures that the chain id is bumped penumbra-testnet-deimos-6 ->
penumbra-testnet-deimos-7. Not strictly necessary, but for posterity, copied over the same configs for the intervening 71 & 72 testnets.

Issue ticket number and link

Checklist before requesting a review

  • If this code contains consensus-breaking changes, I have added the "consensus-breaking" label. Otherwise, I declare my belief that there are not consensus-breaking changes, for the following reason:

    This PR updates the chain id and will result in a new network, so it's definitely consensus-breaking.

Testing and review

Run cargo run --release --bin pd -- testnet generate locally and confirm that you see penumbra-testnet-deimos-7, not -6, in the output.

We mistakenly broke testnet 72 on chain upgrade, by leaving a forked
network running that caused tombstoning. To resolve, we're going to
reset chain state and use a new chain id. This commit ensures that the
chain id is bumped `penumbra-testnet-deimos-6` ->
`penumbra-testnet-deimos-7`. Not strictly necessary, but for posterity,
copied over the same configs for the intervening 71 & 72 testnets.
@conorsch conorsch added consensus-breaking breaking change to execution of on-chain data state-breaking breaking change to on-chain data labels Apr 26, 2024
@conorsch
Copy link
Contributor Author

Self-merging to get this out the door.

@conorsch conorsch merged commit 2d259ac into release/v0.73.x Apr 26, 2024
5 checks passed
@conorsch conorsch deleted the prep-for-testnet-73 branch April 26, 2024 01:00
conorsch added a commit that referenced this pull request Apr 26, 2024
Bumps the usual version spec for the docs, so it's clear what version
should be downloaded. Given that 73 has a fresh chain, remove the
archive-url from the join instructions, because it's no longer correct.

Refs #4274
conorsch added a commit that referenced this pull request Apr 26, 2024
Bumps the usual version spec for the docs, so it's clear what version
should be downloaded. Given that 73 has a fresh chain, remove the
archive-url from the join instructions, because it's no longer correct.

Refs #4274
conorsch added a commit that referenced this pull request Apr 26, 2024
Bumps the usual version spec for the docs, so it's clear what version
should be downloaded. Given that 73 has a fresh chain, remove the
archive-url from the join instructions, because it's no longer correct.

Refs #4274
@cratelyn cratelyn added this to the Sprint 5 milestone May 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
consensus-breaking breaking change to execution of on-chain data state-breaking breaking change to on-chain data
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

2 participants