Adopt EIP-7688: Forward compatible consensus data structures #3844
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Only last commit is relevant, the rest is part of #3777.
|
|
The circleci errors ( make clean
make install_test
make build_wheel
caffeinate -ims make -j generate_tests
find ../consensus-spec-tests/tests -depth -type d -empty -delete |
etan-status
force-pushed
the
ef-eip7688
branch
2 times, most recently
from
90c01f3
to
38ab5c4
Compare
etan-status
force-pushed
the
ef-eip7688
branch
2 times, most recently
from
0abb4b6
to
4a15496
Compare
This was referenced Jul 22, 2024
etan-status
force-pushed
the
ef-eip7688
branch
from
2bb7dbb
to
fd9398a
Compare
etan-status
force-pushed
the
ef-eip7688
branch
4 times, most recently
from
15a049b
to
b647114
Compare
EIP-4788 exposes the beacon root to smart contracts, but smart contracts using it need to be redeployed / upgraded whenever the indexing changes during a fork, even if that fork does not touch any used functionality. This problem expands further to bridges on other blockchains, or even into wallet apps on a phone that verify data from the beacon chain instead of trusting the server. It is quite unrealistic to expect such projects to all align their release cadence with Ethereum's forks. EIP-7688 fixes this by defining forward compatibility for beacon chain data structures. Electra `Profile` retain their Merkleization even when rebased to `StableContainer` definitions from future forks, enabling decentralized protocols to drop the requirement for trusted parties to periodically upgrade beacon state proof verifiers.
etan-status
force-pushed
the
ef-eip7688
branch
from
b647114
to
50cbc00
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
EIP-4788 exposes the beacon root to smart contracts, but smart contracts using it need to be redeployed / upgraded whenever the indexing changes during a fork, even if that fork does not touch any used functionality.
This problem expands further to bridges on other blockchains, or even into wallet apps on a phone that verify data from the beacon chain instead of trusting the server. It is quite unrealistic to expect such projects to all align their release cadence with Ethereum's forks.
EIP-7688 fixes this by defining forward compatibility for beacon chain data structures. Electra
Profileretain their Merkleization even when rebased toStableContainerdefinitions from future forks, enabling decentralized protocols to drop the requirement for trusted parties to periodically upgrade beacon state proof verifiers.v1.5.0-alpha.8)