Skip to content

fix: Pectra activation #448

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

Merged
merged 1 commit into from
Jul 30, 2025
Merged

fix: Pectra activation #448

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
7 changes: 4 additions & 3 deletions docs/wiki/pectra-faq.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@
# Pectra FAQ

**What is Pectra?**
Pectra, (Prague - Electra), is the next network upgrade scheduled for Ethereum. The full list of EIPs as well as an introduction to the features can be found [here](https://notes.ethereum.org/@ethpandaops/mekong#What-is-in-the-Mekong-testnet).
ectra, (Prague - Electra), is an Ethereum network upgrade that activated on Ethereum mainnet at epoch `364032`, on **07-May-2025 at 10:05 (UTC)**.. The full list of EIPs as well as an introduction to the features can be found [here](https://notes.ethereum.org/@ethpandaops/mekong#What-is-in-the-Mekong-testnet).

**Who is this guide for?**
For App developers, Stakers and Node operators who are interested in the upcoming Pectra upgrade.
Expand Down Expand Up @@ -148,7 +148,8 @@
The consolidation will fail as the validators must be active on the beacon chain at the time of consolidation execution.

#### **Q:** Whats the ABI of the consolidation system contract?
The EIP-7251 consolidations contract is deployed here `0x0000BBdDc7CE488642fb579F8B00f3a590007251`, source here: https://github.com/ethereum/sys-asm/blob/main/src/consolidations/main.eas.

The EIP-7251 consolidations contract is deployed here `0x0000BBdDc7CE488642fb579F8B00f3a590007251`, source here: https://github.com/ethereum/sys-asm/blob/main/src/consolidations/main.eas.

Check failure on line 152 in docs/wiki/pectra-faq.md

View workflow job for this annotation

GitHub Actions / lint

Bare URL used 

docs/wiki/pectra-faq.md:152:114 MD034/no-bare-urls Bare URL used [Context: "https://github.com/ethereum/sy..."] https://github.com/DavidAnson/markdownlint/blob/v0.33.0/doc/md034.md
The consolidations are put in a queue and dequeued at a rate of 2 per block.
The contract is not written in solidity, nor do they have a typical solidity ABI in order to not enshrine the API.

Expand Down Expand Up @@ -195,7 +196,7 @@

#### **Q:** Whats the ABI of the withdrawal system contract?

The EIP-7002 contract is deployed here `0x00000961Ef480Eb55e80D19ad83579A64c00700` source here: https://github.com/ethereum/sys-asm/blob/main/src/withdrawals/main.eas.
The EIP-7002 contract is deployed here `0x00000961Ef480Eb55e80D19ad83579A64c00700` source here: https://github.com/ethereum/sys-asm/blob/main/src/withdrawals/main.eas.

Check failure on line 199 in docs/wiki/pectra-faq.md

View workflow job for this annotation

GitHub Actions / lint

Bare URL used 

docs/wiki/pectra-faq.md:199:97 MD034/no-bare-urls Bare URL used [Context: "https://github.com/ethereum/sy..."] https://github.com/DavidAnson/markdownlint/blob/v0.33.0/doc/md034.md
The withdrawals are put in a queue and at maximum 16 are dequeued per block.
The contract is not written in solidity, nor do they have a typical solidity ABI in order to not enshrine the API.
The functionality of the withdrawal contract in pseudo code:
Expand Down
Loading