Skip to content
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

Execution Layer Meeting 179 #939

Closed
timbeiko opened this issue Jan 15, 2024 · 13 comments
Closed

Execution Layer Meeting 179 #939

timbeiko opened this issue Jan 15, 2024 · 13 comments

Comments

@timbeiko
Copy link
Collaborator

timbeiko commented Jan 15, 2024

Meeting Info

Agenda

@yperbasis
Copy link
Member

Can we please deploy the beacon roots contract on Sepolia, Holesky, mainnet.

@gakonst
Copy link

gakonst commented Jan 17, 2024

Here's the Reth team view on post-Cancun planning, keen to discuss if there's time!

@timbeiko
Copy link
Collaborator Author

@yperbasis, @marioevz is quick: sepolia, holesky 🔥

@0xfoobar
Copy link

Would love to share a quick perspective on EIP-3074 on behalf of apps and end users

@timbeiko
Copy link
Collaborator Author

@0xfoobar, let's do it! The zoom link for the call is shared in the R&D discord, in the #allcoredevs channel.

@gakonst
Copy link

gakonst commented Jan 17, 2024

@0xfoobar in order to keep scope tight, do you mind sharing some bullets / guidelines on what the app / end user view is?

I think as a community we should improve the information density and conciseness in ACD. One way to work towards that is to have more 'bulletpointed' communication, to avoid discussions going too long and w/o clear action items / next steps.

So for 3074 would love for a written pre-read with some proposed action items so we can have a productive discussion with high context and next steps, WDYT @0xfoobar?

@0xfoobar
Copy link

0xfoobar commented Jan 17, 2024

@gakonst Definitely. Longform rationale is here: https://0xfoobar.substack.com/p/batch-transactions-for-eoas

TLDR:

  • stale approvals are a huge security risk, have already drained 100s of millions from retail. EOA batch txs fix this
  • batch txs are a 'free lunch' for state growth, by removing unnecessary overhead of sequential txs can fit more actions into same state size
  • batch txs eliminate unbundling risk and make the private relaying world more competitive
  • EOAs are >90% of current addresses, should continue improving the default experience while working on more complex smart contract wallets

@michaelneuder
Copy link

if there is time i'd like to discuss the following two EIPs as candidates for prague! they both have EL & CL implications :-)

@wjmelements
Copy link

I want to discuss alternative designs for SETCODE to evaluate core developer preferences. While there was some resistance to the belongs-to specification, I suspect it will be favored when the rationale is explained.

  • match-SSTORE specificiation, original
  • belongs-to specification, proposed by yoav, current
  • CODE_ADDRESS specification, proposed by Vitalik

You can preview this presentation here

@timbeiko
Copy link
Collaborator Author

timbeiko commented Jan 17, 2024

@0xfoobar @wjmelements thanks for the prepared materials! I think what makes the most sense is for you both, and @michaelneuder, to go over your proposals before we hear from all the client teams (in case it shifts their views!).

That said, I want to make sure we do leave time for that at the end. So, depending on how long the Dencun conversation takes, I may timebox each specific EIP conversation. Ideally, we can do 10ish minutes each!

@hwwhww
Copy link
Collaborator

hwwhww commented Jan 18, 2024

We will cut CL spec release v1.4.0-beta.6 immediately after ADCD today. The only consensus change is a fork choice one: ethereum/consensus-specs#3431

If some CL devs are here, I want to double check if we will use v1.4.0-beta.6 for Sepolia & the future releases for Goerli.

IMO it's okay to mix versions in Goerli since it's unlikely to cause consensus failure.

@g11tech
Copy link

g11tech commented Jan 18, 2024

If some CL devs are here, I want to double check if we will use v1.4.0-beta.6 for Sepolia & the future releases for Goerli.

Lodestar could push this change into sepolia builds, also isn't goerli future = dead?

@timbeiko
Copy link
Collaborator Author

Closed in favor of #943

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants