Tim Beiko’s recap of all core devs – execution (ACDE):

• The Prysm team gave an overview of the missed slots situation over the past few days. It seems to have been caused by an issue in the bloxroute relay. The conversation will continue on the mev-boost community call and hopefully a postmortem will be shared.

• The Reth/Paradigm team presented their state growth research (https://www.paradigm.xyz/2024/03/how-to-raise-the-gas-limit-1), and emphasized the relative importance of history growth. General agreement that we should continue the work on 4444 & out-of-network historical data serving. You can follow the conversation in #history-expiry

• We agreed to move forward with the two retroactive EIPs (7523 & 7610). I'll draft a Meta EIP to document our growing list of retro EIPs. If anyone from Gnosis Chain is reading this, you should review 7523!

• Dencun EIPs need to be moved to Final. This PR tracks all of the individual EIPs: https://github.com/ethereum/EIPs/pull/8334 --- @ansgar.eth @dankrad @lightclient @proto there is still an open PR for 4844. Aside from that, everything looks ready to merge!

• Pectra EIP updates: re: 2537 gas costs, Marius shared a doc above with benchmarks. Reth team said they will also run benchmarks soon, and the EIP champions will look into the necessity of subgroup checks for non-pairing operations.

• Pectra Candidates updates: we spent most of the call going over updates for potential Pectra EIPs. I won't recap each one here, but we covered nearly everything and agreed to make decisions about the Pectra scope next call.

• Client teams: please review the list of candidate EIPs before the next ACDE (https://ethereum-magicians.org/t/pectra-network-upgrade-meta-thread/16809#other-pectra-proposals-2) and be ready to voice your preferences for what to include alongside what's already in.

• EIP Champions: if you have more updates, please share them in writing ahead of the call so client teams can review.

Notes

Tim Beiko’s tweet thread notes of ACDE:

https://twitter.com/TimBeiko/status/1773421360112635964

Video Recording

Tim Beiko’s recap of all core devs – execution (ACDE):

• Dencun: The Sepolia fork went very well overall! Prysm is investigating a proposal delay issue that may be due to relays. That said, the Nethermind team managed to break devnet-12 using a blob spammer. Over the next week, we'll dig into both of these issues, see blobs expire on Goerli, and have Holesky fork. Assuming everything looks by then, we'll pick a mainnet fork time on next week's ACDC. By then, we'll also try and gather testing feedback from L2s.

• Most of the call went into details for Verkle, EOF, and EIP-4444/Portal. I won't recap all the conversations here, but here are a few notable links:

  • Verkle status update: https://docs.google.com/presentation/d/1R_UkS0WyGN1FK3qYxSBK5zZxBbN8Cx2mFHQj6rQ0jRA/edit?usp=sharing

• Portal FAQ: https://notes.ethereum.org/@Kolby-ML/HJ-9D5aYp

• We agreed to prioritize Verkle and make it the core feature of the Osaka upgrade, which will follow Prague. I've opened a PR to reflect this: https://github.com/ethereum/EIPs/pull/8159

• With that decided, we'll focus the next ACDE on finalizing the scope for Prague: https://github.com/ethereum/EIPs/pull/8121

• No objections to reserving a precompile range for L2s, so https://github.com/ethereum/EIPs/pull/8074 will move forward.

• Lastly, two things we didn't get to cover on the call but want to flag:

• Adding client versions in the Engine API: https://github.com/ethereum/execution-apis/pull/517

• EIP-7523, see: ⁠allcoredevs⁠

Notes

Tim Beiko’s tweet thread notes of ACDE:

https://twitter.com/TimBeiko/status/1753125753020137890

Video Recording

Tim Beiko’s recap of all core devs – execution (ACDE):

ACDE Recap - this was a big one, so brace yourselves! Dencun

• Teams are satisfied with how Goerli went: issues have already been triaged, fixed, and new releases shipped. We are therefore keeping our Sepolia/Holesky schedule. Client teams should have a release out with activation set for both testnets by early next week. See EIP-7569 for epochs/timestamps. CL spec was just released, too (see ⁠announcements)

• We tentatively agreed to move forward with this JSON RPC PR (https://github.com/ethereum/execution-apis/pull/486) once (1) we've merged the 4844 naming changes (https://github.com/ethereum/EIPs/pull/8095) and updated the PR to reflect those, and (2) ideally have @RyanSchneider (or another future user!) confirm that the JSON RPC PR looks good

• We're good to deploy the 4788 contract to mainnet. First one to do this and post a txn hash here gets their gas refunded

Prague/Electra

• Lots of conversation on the call, won't summarize everything here. If you care about what's going in the fork, make sure you watch the recording!

• EL teams agreed that we should aim to do a fork in 2024, which likely means excluding Verkle and having it in the next fork. That said, there is likely bandwidth for one "harder thing" in that fork.

• All EL teams agreed that 2537, 6110 and 7002 should be prioritized in the next fork. I've drafted a Meta EIP to reflect this, and given 2/3rd of these EIPs also involve the CL and we didn't get a formal +1 from them, I've put all 3 in the "CFI" bucket for now: https://github.com/ethereum/EIPs/pull/8121

• On the next ACDE, we'll discuss the 3 potential "big things": Verkle, EOF and 4444. If you have specific questions/points you'd like to cover about those, please raise them on either the call agenda (https://github.com/ethereum/pm/issues/943), here, or with the champions for those initiatives.

Hopefully, after that we have a feel for where Verkle should go, and what space is left in Prague!

Notes

Tim Beiko’s tweet thread notes of ACDE:

https://twitter.com/TimBeiko/status/1748064586023239900

Video Recording

lightclients recap of all core devs – execution (ACDE):

Pectra EIPs:

https://ethereum-magicians.org/t/prague-electra-network-upgrade-meta-thread/16809

Notes

lightclients tweet thread notes of ACDE:

https://twitter.com/lightclients/status/1742963481618289061

Video Recording

Tim Beiko’s recap of all core devs – execution (ACDE):

Goerli shadow fork analysis:

https://notes.ethereum.org/@ethpandaops/dencun-gsf-1-analysis

Prague/Electra proposed EIPs:

https://ethereum-magicians.org/t/prague-electra-network-upgrade-meta-thread/16809

Notes

Tim Beiko’s tweet thread notes of ACDE:

https://twitter.com/TimBeiko/status/1737834960881680800

Video Recording

Tim Beiko’s recap of all core devs – execution (ACDE):

Notes

Tim Beiko’s tweet thread notes of ACDE:

https://twitter.com/TimBeiko/status/1732813652536009115

Video Recording

Tim Beiko’s recap of all core devs – execution (ACDE):

Notes

Tim Beiko’s tweet thread notes of ACDE:

https://twitter.com/TimBeiko/status/1727810699295113339

Video Recording

Tim Beiko’s recap of all core devs – execution (ACDE):

Notes

Tim Beiko’s tweet thread notes of ACDE:

https://twitter.com/TimBeiko/status/1722635956719866015

Video Recording

Tim Beiko’s recap of all core devs – execution (ACDE) 172

Notes

Tim Beiko’s tweet thread notes of ACDE 172:

https://twitter.com/TimBeiko/status/1712534201042612514

Video Recording

Tim Beiko’s recap of all core devs – execution (ACDE) 171

Notes

Tim Beiko’s tweet thread notes of ACDE 171:

https://twitter.com/TimBeiko/status/1707464366629781768

Video Recording

I’m the editor at Week in Ethereum News and Tweet the most/much clicked items each week in the newsletter. This means four times a week I am trying to find a Twitter handle for each most/much clicked news item. In all of my previous web3 roles (software lead & community manager) I also regularly needed to find people.

Use the following recommendations to make yourself findable, so people (like me) can share your work and contact you.

Display name

Use a display name that you want to represent your identity. It can be associated with your anon identity or real name.

You should use the same display name everywhere.

My parents gave me the initials ABC (thanks parents). I started using Andrew B Coathup (following Michael J Fox) in my teens, though have been moving to my ENS name abcoathup.eth.

For team Ethereum, I suggest using your ENS name. It also helps when receiving cold DMs to see who has done the most basic research so they can use your actual first name.

Emojis in your display name on Twitter can help identify which subgroups you are part of, though they are a little naff. I use 🐡 (EIP4844), 🛡️ (Coinbase stand with crypto) and 🦇🔊 (ultrasound meme). They also can be used as your last name if you use your ENS as your first name.

Username/handle

Use a handle that is ideally relatable to your display name. Your identity is a brand after all, and each component should build on the other.

You should make every possible effort to use the same handle everywhere. Change your handles to match if you have to. You are much more findable if you share the same handle between Twitter and GitHub. If I don’t see a link from your GitHub to Twitter I will try using the same handle.

Avoid underscores and hyphens as not all services support these, meaning you will have different handles across services. Notions copy and paste is particularly unhelpful with underscores, and treats copied handles as markdown and removes the underscores.

PFP

Use a PFP (profile pic) that represents your identity. Ideally people could recognize you by your PFP (if you are not anon).

Use the same pfp everywhere, unless you have a really good reason.

I use a black & white selfie I took in my hall wearing a tuxedo jacket over my t-shirt. I use my TexturePunx on Twitter (because Texture created it for me back before they were NFTs).

Don’t change your pfp without a really good reason. Flipping NFTs isn’t a good reason. Slight mods for major events/seasons/holidays are ok. I have a version of my pfp with a Santa hat.

Twitter

Twitter is unfortunately the primary place to connect with people online, especially for crypto twitter, so you should point everyone to your Twitter account.

I recommend adding your Twitter handle to your GitHub profile, Medium about page and every other service.

Conclusion

Make yourself easy to find by using the same display name, username/handle & pfp across sites and add links to major accounts in your profile.

Find me

You can find me on Twitter, GitHub and pretty much everywhere else using my handle: abcoathup.