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

Update for Berkeley upgrade details. #996

Merged
merged 2 commits into from
Jun 5, 2024
Merged

Conversation

shimkiv
Copy link
Member

@shimkiv shimkiv commented Jun 4, 2024

Leftover from the #995.

@shimkiv shimkiv self-assigned this Jun 4, 2024
Copy link

vercel bot commented Jun 4, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
docs2 ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jun 4, 2024 11:11pm
1 Ignored Deployment
Name Status Preview Comments Updated (UTC)
07-oracles ⬜️ Ignored (Inspect) Visit Preview Jun 4, 2024 11:11pm

@@ -143,19 +143,19 @@ where:

:warning: Running a replayer from scratch on a Devnet/Mainnet database can take up to a couple of days. The recommended best practice is to break the replayer into smaller parts by using the checkpoint capabilities of the replayer.

:warning: You must run the replayer using the Mainnet version. You can run it from the Docker image at `gcr.io/o1labs-192920/mina-archive:2.0.0-039296a-bullseye`.
:warning: You must run the replayer using the Mainnet version. You can run it from the Docker image at `minaprotocol/mina-archive:3.0.0-93e0279-bullseye`.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this should still be 2.0.0-039296a since this is patching the pre-fork DB

@ymekuria ymekuria marked this pull request as ready for review June 5, 2024 02:05
@ymekuria ymekuria requested a review from a team as a code owner June 5, 2024 02:05
@ymekuria ymekuria merged commit 786a620 into main Jun 5, 2024
4 checks passed
@ymekuria ymekuria deleted the fix/berkeley-upgrade-details branch June 5, 2024 02:11
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 this pull request may close these issues.

3 participants