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

Binary testnet holocene timestamp added #749

Open
wants to merge 18 commits into
base: main
Choose a base branch
from

Conversation

priyanshuthapliyal55
Copy link
Contributor

@priyanshuthapliyal55 priyanshuthapliyal55 commented Dec 6, 2024

Adding a New Chain

This PR adds [Chain Name Here] to the registry.

Checklist

  • I have declared the chain at the appropriate Superchain Level.
  • I have run just validate <chain-id> locally to ensure all local validation checks pass.
  • I have run just codegen to ensure that the chainlist and other generated files are up-to-date and include my chain.

@priyanshuthapliyal55 priyanshuthapliyal55 requested a review from a team as a code owner December 6, 2024 05:22
@@ -8,8 +8,9 @@ batch_inbox_addr = "0xFf00000000000000000000000000000000042069"
canyon_time = 0 # Thu 1 Jan 1970 00:00:00 UTC
delta_time = 0 # Thu 1 Jan 1970 00:00:00 UTC
ecotone_time = 0 # Thu 1 Jan 1970 00:00:00 UTC
fjord_time = 1723204838 #Saturday June 8 2024 10:47:18 AM UTC
Copy link
Collaborator

Choose a reason for hiding this comment

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

Strange that these timestamp comments incorrect before -- @bitwiseguy do we know why?

Copy link
Member

Choose a reason for hiding this comment

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

The old ones look like they were created manually, not with date -u -r.

granite_time = 1723545055 #Monday June 12 2024 1:57:35 PM UTC
fjord_time = 1723204838 # Fri Aug 09 2024 12:00:38 UTC
granite_time = 1723545055 # Tue Aug 13 2024 10:30:55 UTC
holocene_time = 1732633200 # Tue Nov 26 15:00:00 UTC 2024
Copy link
Collaborator

Choose a reason for hiding this comment

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

Do you intend for this chain to receive all future hardforks in sync with the rest of the superchain? If so, I recommend following these instructions https://github.com/ethereum-optimism/superchain-registry/?tab=readme-ov-file#hardfork-activations

Comment on lines +11 to +12
fjord_time = 1723204838 # Fri Aug 09 2024 12:00:38 UTC
granite_time = 1723545055 # Tue Aug 13 2024 10:30:55 UTC
Copy link
Member

Choose a reason for hiding this comment

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

verified that the timestamps in the corrected comments are ✅

granite_time = 1723545055 #Monday June 12 2024 1:57:35 PM UTC
fjord_time = 1723204838 # Fri Aug 09 2024 12:00:38 UTC
granite_time = 1723545055 # Tue Aug 13 2024 10:30:55 UTC
holocene_time = 1732633200 # Tue Nov 26 15:00:00 UTC 2024
Copy link
Member

Choose a reason for hiding this comment

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

Note that the Sepolia activation has already passed over a week ago. Did you locally set this with an override on all your nodes?

If that's intentional, you probably want to receive all future hardfork from Holocene onwards, so better just set the superchain_time.

Suggested change
holocene_time = 1732633200 # Tue Nov 26 15:00:00 UTC 2024
superchain_time = 1732633200 # Holocene - Tue Nov 26 15:00:00 UTC 2024

Copy link
Contributor Author

Choose a reason for hiding this comment

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

This is a Custom Gas token Chain do you suggest that we can use superchain_time and it will not cause any issue ?

Copy link
Member

Choose a reason for hiding this comment

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

Setting superchain_time simply means that you inherit the activation times that are set for the superchain automatically. That also works for CGT chains.

Copy link
Member

Choose a reason for hiding this comment

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

But again, the Sepolia activation has already passed. Do you intentionally retroactively set the Sepolia Holocene activation time because you locally activated last week with overrides?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

yes i locally activated Holocene last week using overrides.

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.

4 participants