Closed ralexstokes closed 5 months ago
Kurtosis team plans to open source their entire project. (https://x.com/KurtosisTech/status/1800258729289355763) There is currently a plan to migrate the ethereum-package from their repo to the ethpandaops organization on 13th of June.
From their announcement channel:
We will be transferring the Ethereum Package to ethPandaOps this Thursday 2024-06-14
From then on to access the Kurtosis package you will have to do
kurtosis run github.com/ethpandaops/ethereum-package
...
This is a pretty big breaking change, as it will break literally everyone's workflow until they don't change the url. Would like to discuss what this will mean for us/client teams in the coming days/weeks.
I'd nudge on getting the finality of the F-star naming again this week.
The ChatGPT-generated proposals: https://hackmd.io/oVQCHuOdT-q2KN9YrD-r7w
In the last call, iirc "Fulu" and "Felis" received a lot of support in the zoom chat. It seems people like shorter names. I'd add that "Foramen" is cool because of the Ramen x Osaka theme (🍜 x🏯)!
p.s. I think Felis looks like a typo of Felix (@fjl 😂)
I'm totally up for having a fork named after me.
Draft PR to include PeerDAS in the Pectra Meta EIP once we've clarified how it will be reflected in the CL specs.
Transaction
StableContainer
structure (but not the various Profile
), in order to know how to merkleize transactions and compute hash_tree_root
ByteList
of opaque, serialized transactions. But in this case, we need two lists, one containing the serialized transactions (as today), and an additional one containing the transaction roots. Essentially leading to double the hashes on the EL side to compute both roots.I'd like to confirm if it's okay to merge https://github.com/ethereum/consensus-specs/pull/3768 in the call.
Review request for the PFI
/CFI
/SFI
EIP: https://github.com/ethereum/EIPs/pull/8662
We don't have to discuss on the call, but client team reviews of the proposal would be appreciated 😄
Biggest open question: do we want CFI to have an explicit "gate", i.e. 1 (+?) client team thinks an EIP should be in an upgrade?
I'd nudge on getting the finality of the F-star naming again this week.
@hwwhww I dug my F-star name discussion post out of drafts on Eth Magicians. (I had been waiting for Pectra scope to be finalized). It is a wiki post so feel free to edit. https://ethereum-magicians.org/t/f-star-name-for-consensus-layer-upgrade-after-electra/20285
Review request for the
PFI
/CFI
/SFI
EIP: ethereum/EIPs#8662We don't have to discuss on the call, but client team reviews of the proposal would be appreciated 😄
Biggest open question: do we want CFI to have an explicit "gate", i.e. 1 (+?) client team thinks an EIP should be in an upgrade?
ref. explicit "gate" : The current version of https://github.com/ethereum/EIPs/pull/8662 (based on @abcoathup 's EthMag feedback on the way for the Upgrade Meta EIP author to avoid spam proposals) seems fairer than adding an explicit gate.
closing in lieu of #1084
Consensus-layer Call 135
prev: call 134
Meeting Date/Time: Thursday 2024/6/13 at 14:00 UTC Meeting Duration: 1.5 hours stream
ethereum-package
kurtosis modulev1.5.0-alpha.3
PEERDAS_ACTIVATION_EPOCH
recap