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

Jump to bottom

Tracking issue: Prague Hardfork #7363

Closed
10 tasks done
Rjected opened this issue Mar 27, 2024 · 3 comments
Closed
10 tasks done

Tracking issue: Prague Hardfork #7363

Rjected opened this issue Mar 27, 2024 · 3 comments
Labels
C-tracking-issue An issue that collects information about a broad development initiative E-prague Related to the prague network upgrade M-prevent-stale Prevents old inactive issues/PRs from being closed due to inactivity

Comments

@Rjected
Copy link
Member

Rjected commented Mar 27, 2024 •
edited
Loading

This is a tracking issue for the changes we need to make for the prague hardfork.

The current meta EIP: https://eips.ethereum.org/EIPS/eip-7600
The discussion thread: https://ethereum-magicians.org/t/pectra-network-upgrade-meta-thread/16809

Devnet-0: https://notes.ethereum.org/@ethpandaops/pectra-devnet-0

Tasks
Beta Give feedback
  10. Add Header fields while maintaining backwards compatibility #7820
    A-db E-prague M-prevent-stale S-needs-investigation
@Rjected Rjected added C-tracking-issue An issue that collects information about a broad development initiative E-prague Related to the prague network upgrade labels Mar 27, 2024
@DaniPopes DaniPopes added the M-prevent-stale Prevents old inactive issues/PRs from being closed due to inactivity label Apr 15, 2024
@gakonst gakonst mentioned this issue Apr 16, 2024
Closed
This was referenced Apr 17, 2024
Merged
Merged
@onbjerg onbjerg mentioned this issue Apr 23, 2024
Merged
@joshieDo joshieDo mentioned this issue Apr 23, 2024
Closed
@onbjerg onbjerg pinned this issue Apr 24, 2024
@rakita
Copy link
Collaborator

rakita commented Apr 29, 2024

Revm tracking issue: bluealloy/revm#1268

@ralexstokes ralexstokes mentioned this issue May 7, 2024
Closed
@gakonst
Copy link
Member

gakonst commented May 11, 2024

I vote we use devnet-0 branch main...devnet-0 given EIP-3074 integration and I don't want to pull in that EIP into Revm (cc @rakita) given it's likely we'll go with EIP-7702.

@shekhirin shekhirin mentioned this issue May 12, 2024
Closed
@onbjerg onbjerg mentioned this issue Jun 4, 2024
Closed
@shekhirin shekhirin unpinned this issue Jun 11, 2024
@Rjected
Copy link
Member Author

Rjected commented Jun 12, 2024

Going to close this as we're planning for devnet-1 now: #8788

@Rjected Rjected closed this as completed Jun 12, 2024
@github-project-automation github-project-automation bot moved this from Todo to Done in Reth Tracker Jun 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
C-tracking-issue An issue that collects information about a broad development initiative E-prague Related to the prague network upgrade M-prevent-stale Prevents old inactive issues/PRs from being closed due to inactivity
Projects
Reth Tracker
Archived in project
Milestone
No milestone
Development

No branches or pull requests
4 participants
@Rjected @rakita @gakonst @DaniPopes