-
Notifications
You must be signed in to change notification settings - Fork 325
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
EIP-4844 Implementers' Call #1 #647
Comments
We should expose the modulus to the EVM in some way. This is necessary if we want rollups that work with the point evaluation precompile to be forward-compatible with future changes that change the EVM. In particular, I expect a significant chance that we'll change the commitment scheme over to STARKed Merkle roots over a 64-bit modulus (!!) as hashes and STARKs are very fast in that context. If the modulus is available in the EVM, rollups would be able to write their proof-of-equivalence circuits to work with whatever modulus is provided, and would be forward-compatible. A few possible options include:
The last option probably requires the fewest client changes. But whatever we want to do regarding this, it's probably worth agreeing on the exact approach and adding it to the EIP soon. |
I won't be able to make this due to a conflict, but here are prysm updates:
Spec updates, I opened the following. Thanks everyone for the feedback so far! 2mb testing, I opened this branch to be able to capture attestation arrival latency: |
There's also: ethereum/consensus-specs#3038 |
Closed in favour of #650 |
Meeting Info
#4844-testing
prior to the call📆 Subscribe to the Ethereum Protocol Call calendar for calendar invites
Agenda
MIN_EPOCHS_FOR_BLOBS_SIDECARS_REQUESTS
to 18 days consensus-specs#3047The text was updated successfully, but these errors were encountered: