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

Use the correct values for the fork config #15094

Merged
merged 18 commits into from
Feb 14, 2024
Merged

Conversation

mrmr1993
Copy link
Member

In particular:

  • we want to use the best tip's hash
  • the genesis block already has blockchain length set to the fork's blockchain length, so we're double counting if we manually attempt to do it here.

This change makes these so. It works out actually simpler than the code that was written.

emberian and others added 2 commits February 12, 2024 14:48
In particular:
* we want to use the best tip's hash
* the genesis block already has blockchain length set to the fork's
  blockchain length, so we're double counting if we manually attempt to
  do it here.

This change makes these so. It works out actually simpler than the code
that was written.
@mrmr1993 mrmr1993 requested review from a team as code owners February 13, 2024 19:33
@mrmr1993
Copy link
Member Author

!ci-build-me

@mrmr1993
Copy link
Member Author

!ci-build-me

@mrmr1993
Copy link
Member Author

The scope of this is now reduced after the merge of #15079. Between the 2 PRs, this fixes

  • the state hash, which is now for the given block instead of its parent,
  • the blockchain length, where the offset calculation doubles up the calculation done in the genesis ledger setup,
  • the export of the genesis configuration, where we actually want to use the configuration specified by the mainnet or devnet compile configurations, and so we remove it entirely.

mrmr1993 and others added 4 commits February 13, 2024 21:24
In particular:
* we want to use the best tip's hash
* the genesis block already has blockchain length set to the fork's
  blockchain length, so we're double counting if we manually attempt to
  do it here.

This change makes these so. It works out actually simpler than the code
that was written.# Please enter the commit message for your changes. Lines starting
@mrmr1993 mrmr1993 requested a review from a team as a code owner February 13, 2024 21:42
@mrmr1993
Copy link
Member Author

This PR now represents the merge-back of #15109.

@mrmr1993
Copy link
Member Author

!ci-build-me

Remove merges-cleanly job for rampup, now that it is retired
@mrmr1993
Copy link
Member Author

!approved-for-mainnet

@mrmr1993
Copy link
Member Author

!ci-build-me

mrmr1993 and others added 4 commits February 14, 2024 09:34
Problem: compiled parameters are explicitly listed in the fork config
exported with the Graphql. This may leas to bugs when using the fork
config in laucnhing a fork network.

Solution: do not include runtime config into fork config.
@mrmr1993
Copy link
Member Author

!ci-build-me

@mrmr1993
Copy link
Member Author

!approved-for-mainnet

@mrmr1993 mrmr1993 merged commit 85fc613 into berkeley Feb 14, 2024
39 checks passed
@mrmr1993 mrmr1993 deleted the fix/state-dump-graphql branch February 14, 2024 11:44
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