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.

Sign up for GitHub

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 EIP-6122: Fix typo in EIP-6122 #8170

Merged
merged 2 commits into from
Feb 8, 2024
Merged

Update EIP-6122: Fix typo in EIP-6122 #8170

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
ce4e733
Update eip-6122.md
gfukushima Feb 7, 2024
803319d
Merge branch 'master' into patch-2
lightclient Feb 8, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion EIPS/eip-6122.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -34,7 +34,7 @@ Each node maintains the following values:
- Block timestamps are regarded as `uint64` integers, encoded in big endian format when checksumming.
- If a chain is configured to start with a non-Frontier ruleset already in its genesis, that is NOT considered a fork.
- **`FORK_NEXT`**: Block number or timestamp (`uint64`) of the next upcoming fork, or `0` if no next fork is known.
- Note that it is not important to distinguish between a timestamp or a block for `FROK_NEXT`.
- Note that it is not important to distinguish between a timestamp or a block for `FORK_NEXT`.

A `FORK_HASH` for a timestamp based fork at `1668000000` on top of homestead would be:

Expand Down
Loading