-
Notifications
You must be signed in to change notification settings - Fork 10
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
Schedule Deneb on Chiado #26
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The time is also right after Sepolia, as we wanted to hard fork around the middle of the 3 testnet hard forks. This way we know if anything wrong happened with Goerli and stay in schedule with Ethereum.
In PR #9184 I confused slot with epoch. Refer to gnosischain/configs#26.
Hello, clients may need more info for implementation. Following constants should be the part of config too, could you clarify it's the same as in gnosis (or better add to this config too):
Also I cannot find gnosis deneb preset which should contain The last piece of puzzle is trusted setup, which one will be used? Also |
@zilm13 you can find the preset, and more specifically the deneb one here: https://github.com/gnosischain/specs/blob/master/consensus/preset/gnosis/deneb.yaml. The configuration for Chiado hasn't been specified yet, but all configuration variables will be the same as for Ethereum. The full file will be made available shortly. Regarding the size estimate, while on the CL side
I'm not sure where the discrepancy comes from, maybe I missed something in my formula, I'll check tomorrow. What variables do the numbers in your calculation represent? |
With target 1 it could be estimated as 35G (200G/6), right. |
Btw documentation on https://docs.gnosischain.com/about/networks/chiado leads to https://github.com/gnosischain/configs/ where there are no presets, that's why I asked for presets |
First, thank you for opening the issue on Teku's GitHub. Don't worry though, we'll open PRs on all CL clients in due time. To answer your questions:
I'm not exactly sure where the 200 GB estimation comes from, and I'm not sure if the size is dependent on the target or the maximum. Assuming the worst case and that the formula above is right, I get For Gnosis Chain, we only have 16 slots per epoch and a target of 2, so effectively 6x less required space in the worst case, which is 17.2 GB, or double of my earlier approximation with the target rather than the maximal amount. However, the bandwidth requirements would be closer to Ethereum, as that data would be "refreshed" on a more regular basis. @dapplion it would be nice if you could confirm those numbers.
The same one as Ethereum to stay as compatible as possible. |
|
You're totally right, So 4x more min epochs, 2x less slots per epoch and 3x less target / max blobs per block. So 2/3 of Ethereum, meaning 34.4 GB target and 68.7 GB max. Not sure which one actually ends up being required. |
|
EU friendly time after Ethereum's Goerli fork.