Diegorb1329/eth_magicians_forum huggingface dataset:
Title: All_Core_Devs___Execution__ACDE___189__June_6_2024
Category: Protocol_Calls___happenings

Author: abcoathup
Date: 2024-06-02T00:33:28.896Z

Agenda
https://github.com/ethereum/pm/issues/1052
Moderator: @timbeiko
Summary
Recap by @timbeiko

After a lot of back and forth, we finalized the Pectra scope ! EOF and EIP-7702 are both included (PR: Update EIP-7600: Add Included EIPs by timbeiko · Pull Request #8627 · ethereum/EIPs · GitHub). To give teams time to work on their EOF implementations and do cross-client testing on everything else in the fork, devnet-1 will not include EOF, but will include all other Pectra EIPs. Notably, we’ll include 7702 even though the spec may still be changed.
We’re tentatively planning to include the following changes in devnet-1, but will leave a few more days for people to review them prior to merging the PRs:

Update EIP-7251: Add EL triggered consolidations by mkalinin · Pull Request #8625 · ethereum/EIPs · GitHub

engine: Add EL triggered consolidations by mkalinin · Pull Request #554 · ethereum/execution-apis · GitHub
engine: align WithdrawalRequestV1 with EIP-7002 and consensus spec by nflaig · Pull Request #549 · ethereum/execution-apis · GitHub
engine: Extend payload bodies with deposit and withdrawal requests by mkalinin · Pull Request #545 · ethereum/execution-apis · GitHub (already merged)




We discussed deactivating EIP-158, as it would cause issues similar to SELFDESTRUCT in a post-Verkle world and EIP-7702 as currently specified could create accounts with 0 nonce/balance/codehash but storage. @gballet will draft a proposal to formally consider the change. If 7702 is tweaked in a way that does not cause this issue, we’d consider it for the Verkle fork.
@pipermerriam came on to get a status update on EIP-4444 & portal support by client teams. A few client teams have begun working on this, but flagged that they currently have many competing priorities. The Portal team will keep monitoring ⁠history-expiry to offer help to any client team needing it!
We briefly discussed my proposed ACD/Network Upgrade Process/EthMag change doc (AllCoreDevs, Network Upgrade & EthMagicians Process Improvements) and agreed to try the “EIP Review Request” proposal. There weren’t any objections to PFI/CFI/SFI, but given the scope I’ll open a PR for us to discuss before agreeing to the change.
Testing teams proposed a new channel layout for discord (see above)

And, lastly, we flagged the upcoming EPBS (tomorrow) and PeerDAS (June 11) breakouts:

ePBS breakout room #2 · Issue #1060 · ethereum/pm · GitHub
PeerDAS Breakout Room #1 · Issue #1059 · ethereum/pm · GitHub

From Eth R&D Discord
Recording
https://www.youtube.com/live/A5EaPLLRsoQ?t=180s
Additional info
Notes by @timbeiko: Tweet thread
Notes by @Christine_dkim:  https://www.galaxy.com/insights/research/ethereum-all-core-developers-execution-call-189-writeup/
Title: EOF_Implementers_call__61__October_30_2024
Category: Protocol_Calls___happenings

Author: abcoathup
Date: 2024-10-17T01:27:19.182Z

Agenda
EOF Implementers Call #61 · Issue #1184 · ethereum/pm · GitHub
Notes
Notes by @shemnon (Copied from ethereum/pm)

Clients

Nethermind -

merged osaka fixes,
based off of prague / main


reth

has osaka wired in,
Fixed one bug with precompiles and EXTDELEGAGECALL


evmone transition to osaka is larger than expected

Migrated all ethereum/tests state tests over to EEST
EOF validation tests are not moved over yet
Some evmone tests are not ported yet - EVMONE v13 tests


Besu

osaka ready in main
prague-3/4 - based on where main besu gets to




Spec Changes

EXT*CALL

discuss after devcon


EOFCREATE hashing

multiple initcode contexts are creaed
Using container address only works for first level, not nested creates
create transaction - sender has no code so container address won’t work
Not always possible to point to a “physical address” of the container holding the initcode
Maybe omit address, and still hash subcontainer when it cannot be proved, but computation time is different in two scenarios
Goal is to reduce extra hashing
Useful property is to prove code came from a specific code (not just address)
Is it possible to defeat polymorphic code?
Should auxdata be included?


Change max stack height - to be stack needed in addition to inputs

makes the two fields (inputs / max stack) unrelated, rather than max >= inputs
rename the field from max_stack_height to… max_stack_increase
EEST has some auto-calculations we could leverage, client unit tests would incur ~4h work
Quality of Life fix, can miss if we are shipping Q1, but if we had 6 more months would be worth looking into for devnet-1


Re-order EOFCREATE to match EVMCALL

same QoL level of effort. Can miss, but if we have time worth adding.
Feels “small”
Valuable for tooling and developers manually debugging code, to not have to swap elements


Rename RETURNCONTRACT to RETURNCODE
Zero client impact, opcode stays the same
Documentation changes only
QoL for devnet-1
Please comment on EXTCODE* after devcon (//TODO add link)
EXTDATACOPY and EXTDATASIZE (//TODO add bug link)

Target memory? SSTORE2 will use return buffer
When SSTORE2 is used in this context really we are talking about just the read side, not write
Question now is smart contract read methods equivelantly good.
How does it handle legacy and delegate contracts? Read like EXTCODECOPY? Zeros? fault?
Would EXTDATALOAD be needed too? (no EXTCODELOAD…)


DELEGATECALL to legacy

If we fail we need to be able to detect legacy contracts safely and easily
Could we further tweak SELFDESTRUCT to behave differently when a delegate of EOF?





Recording
Title: SoulBound_Donations___A_Call_to_help_people_that_s
Category: Protocol_Calls___happenings

Author: DonMartin3z
Date: 2023-02-22T08:20:06.672Z

Dear Magicians
As you may have seen in the news, the world is deeply chaotic, and while the globe turns its attention to Turkey or Ukraine, bad things are also happening to the people of Brazil > Brazil: flooding and landslides kill dozens in São Paulo state | Brazil | The Guardian
My name is Don Martinez, I am an Ethereum developer, currently responsible for research in the area of zero knowledge proofs and the SoulBound token. You can follow all my social media here ( don_martinez.eth | Instagram, Facebook | Linktree ) I come to ask for everyone’s help to assist several families affected by the floods and landslides caused by the heavy rains that have hit the state of São Paulo in recent weeks and have been devastating. Many people have lost their homes and belongings, as well as suffering emotional and physical traumas.
At this moment, it is crucial that we come together in solidarity with the people affected by this catastrophe. That is why we are asking for your help. Any donation, no matter how small, can make a difference in the life of someone who is going through difficulties at this time. I will conduct a Mint using EIP4973 for non-transferable tokens to register donations in our Ethereum ecosystem in Brazil, and all donor addresses, photos, or any data that they wish to share, can be exposed at our Ethereum Rio 2023 event, next month.  please check > https://www.ethereumbrasil.com/ .
I will film the receipt of donations and post the results for all donors who interact on this topic.
Donations can be made to these addresses:
$BTC : 3EJUusuPEm52GbxpEbDz3ncr6HUV58KgHv
$ETH :  0xDCF6104179E1fA730c3f7D1871832CA264fE7305
Some of the organizations that are working in this region include the Brazilian Red Cross, the Archdiocesan Caritas of São Paulo, and the Movement of People Affected by Dams. All these organizations are receiving few donations and still working tirelessly to provide assistance to victims. Donations will be converted and sent to these organizations, generating a receipt that I will share with you.
We ask that everyone who can contribute does so to help alleviate the suffering of the people who have been affected by this catastrophe. Together, we can make a difference. We are Ethereum.
Thank you in advance for any help you can offer.
Sincerely,
The entire Ethereum Nordeste team.
Title: EIPIP_Meeting_116___May_21__2025
Category: Protocol_Calls___happenings

Author: system
Date: 2025-04-17T01:34:26.526Z

EIPIP Meeting #116, May 21, 2025

Date and time in UTC in format May 21, 2025, 14:00 UTC

Agenda
1. Discuss Open Issues/PRs, and other topics
TBA
Edit to Final Proposals
TBA
Edit to Stagnant Proposals
TBA
Call for Input




Call For Input
Status
Inclination/Result
Deadline



2. Other discussions and updates
TBA
3. EIPs Insight - Monthly EIPs status reporting.

 May 2025

4. EIP Editing Office Hour

Agenda 59 Video 58

5. Review action items from earlier meetings

Notes

Next Meeting date & time - June 18, 2025 (3rd Wed of the Month) at 14:00 UTC
Other comments and resources

- Zoom shared on the [Ethereum Protocol Calls Calendar](https://calendar.google.com/calendar/u/0?cid=Y191cGFvZm9uZzhtZ3JtcmtlZ243aWM3aGs1c0Bncm91cC5jYWxlbmRhci5nb29nbGUuY29t)
- [EIPIP Meeting Playlist](https://www.youtube.com/playlist?list=PL4cwHXAawZxpLrRIkDlBjDUUrGgF91pQw)
- Discussion - [ECH Discord #eip-editing](https://discord.gg/MFSunmfGxu) channel

 🤖 config

Duration in minutes : 60
Recurring meeting : true
Call series : EIPIP
Occurrence rate : monthly
Already a Zoom meeting ID : true
Already on Ethereum Calendar : true
Need YouTube stream links : false


GitHub Issue
Title: Client_testing_call__19__January_6__2025
Category: Protocol_Calls___happenings

Author: parithosh
Date: 2025-01-06T14:34:25.605Z

Pectra

Final call for EIP-7840, Details here.
EIP-2935 updates have been made over the holidays, the current status can be found here. The aim is to conclude the topic this wee.
EELS and test releases went out over the holidays, please use pectra-devnet-5@v1.1.0 for testing your EL.
There was a test regarding empty bytes that requires some discussion, please find it happening in this thread.
Hive instance for pectra-devnet-5 can be found here. The devnet goes live once hive showcases most tests passing on most clients.
On the CL front, there seems to be some issues with the minimal preset for the latest devnet. Information can be found in the interop channel.
In order to make mev-workflow testing easier, Pawan has written a mock builder found here. This mock builder is almost fully integrated into kurtosis, once done, all clients should be able to locally test the mev-workflow.

Progress/Open PRs for pectra-devnet-5
PeerDAS

Rebase work is ongoing. Local kurtosis configs will be provided over the next days.
There are some open topics such as activation and v3 req/resp for blob sidecars found here. Please join the peerDAS breakout session to discuss the topic.

EOF

Rebase work is ongoing, should go better now that pectra specs are fixed.
Fuzzers from Danno and a few others are being used to find bugs.
EOF aims to have a devnet once the rebase work has made some headway.
Title: Verkle_implementers_call__24__September_9_2024
Category: Protocol_Calls___happenings

Author: abcoathup
Date: 2024-09-12T01:45:39.450Z

Agenda
Verkle Implementers Call #24 · Issue #1149 · ethereum/pm · GitHub; Moderated by @rudolf
Notes
https://notes.ethereum.org/@rudolf/vic-notes#Call-24-September-9-2024 by @rudolf
Recording





Additional info



Verkle Trees for Statelessness


Verkle Trees for Statelessness
Contents
Title: EOF_Implementors_Call__67__Feb_19__2025
Category: Protocol_Calls___happenings

Author: shemnon
Date: 2025-02-19T14:57:42.753Z

Agenda
EOF Implementers Call #67 · Issue #1277 · ethereum/pm · GitHub

Author: shemnon
Date: 2025-02-19T15:56:39.995Z

Agenda


Testing Update

eof-devnet-0
EEST



Client and Compiler Updates


Devnet-1
For tomorrow’s EOF call I feel we need to lock down eof-devnet-1 scope so we can start executing it.


I think we need to front load all breaking changes


Move TXCREATE into devnet-1 TXCREATE EIP-7873

This includes the Initcode transaction type
This includes the toehold creator contract
This includes removing EIP-7698 creation contract support



existing devnet-1 planned changes

Alter EOFCREATE Hashing (Just ADDRESS + salt, same as TXCREATE)
Change EOFCREATE stack order to match EXTCALL
making 0x03 container sizes 4 bytes instead of 2
Change data section to 0x04 to 0xff
Change CREATE/CREATE2 behavior when seeing EOF, back to pectra behavior
Rename RETURNCONTRACT to RETURNCODE
extra stack in types instead of total height



Arrange audit for creator contract


Post Devnet-1 changes

Metadata Section EIP-7834
TXCODEADDRESS EIP-7761  and TXCODETYPE EIP-7880



Add EIPs to backlog

EIP-5920 - PAY (needs new opcode #)

Notes


Discussed proposal for devnet 1


Nethermind is in favor, some concern with backwards incompatible changes but we are bringing them all in.


evmone/ipsilon - sounds good, want to paus pose devnet-1 changes to later


For testing, get evmone working with txcreate very fast, then EEST will be able to asses imact.


We also need creator contract support.  We can punt initially by putting it in genesis,

We need state transition support to add the contract



we need to coordinate with peerdas for transaction type number, may be a conflict (EOF gets lower number is the initail proposal)




4 byte container size

Geth: +1
evmone: has concerns about consistency with he vision for the header parsing, but it’s already been altered as you need to know the parsing of each specific section

evmone will prototype and report back in 2 weeks.





wen eof-devnet-1?

April 8th is ideal, depends on results of evmone explorations.
Title: RollCall__12_May_21
Category: Protocol_Calls___happenings

Author: system
Date: 2025-04-11T21:50:36.029Z

RollCall #12 May 21, 2025

May 21, 2025, 14:00 UTC

Agenda

Future of shared execution for L2s
Geth refactoring for L2s

Facilitator email: nicolas@ethereum.org
 🤖 config

Duration in minutes : 60
Recurring meeting : true
Call series : RollCall
Occurrence rate : monthly
Already a Zoom meeting ID : false # Set to true if this meeting is already on the auto recording Ethereum zoom (will not create a zoom ID if true)
Already on Ethereum Calendar : True #
Need YouTube stream links : true # Set to false if you don’t want YouTube stream links created
display zoom link in invite : false #


GitHub Issue
Title: FOCIL_Breakout__10
Category: Protocol_Calls___happenings

Author: system
Date: 2025-05-05T12:35:53.788Z

FOCIL Breakout #10, May 6, 2025, 14:00 UTC
Zoom Link
Agenda

Presentation by Toni Wahrstätter on FOCIL <> Delayed Execution
Presentation by Potuz on FOCIL <> ePBS
Implementation updates

 🤖 config

Duration in minutes : 60
Recurring meeting : true
Call series : (e.g Breakout room)
Occurrence rate : bi-weekly
Already a Zoom meeting ID : true
Already on Ethereum Calendar : true
Need YouTube stream links : true #
display zoom link in invite : false # Set to true to add the Zoom link to the Google Calendar invite description


GitHub Issue
YouTube Stream Links:

Stream 1 (May 06, 2025): https://youtube.com/watch?v=mSHo8gQ97v4
Title: All_Core_Devs___Execution__ACDE___191__July_4_2024
Category: Protocol_Calls___happenings

Author: abcoathup
Date: 2024-07-02T01:55:11.514Z

Agenda
Execution Layer Meeting 191 · Issue #1080 · ethereum/pm · GitHub
Moderator: @ralexstokes (filling in for @timbeiko)
Summary
Recap by @ralexstokes from Eth R&D Discord
Started with Pectra updates

Clients moving ahead with devnet-1 implementations
Waiting for a greater number of clients to be ready before we launch devnet-1, but expect to be there in the next week or two
Got an update on 7702 progress that will likely go into devnet-2; please take a look as the intention is to merge in the next week

Note: devnet-1 will reflect the current spec of EIP-7702



Then turned to discuss EIP-7212

There’s support for the feature as it brings a lot of nice UX improvements around key/wallet management with a widely supported cryptographic curve
We discussed the point around formal inclusion in Pectra, but will wait till the next ACDE to make that decision. While the EIP in isolation brings a nice set of features, it needs to be weighed against the already large scope of Pectra
There are a few minor things to address around the EIP itself, including mirroring the precompile address across L2 deployments and L1. These will be resolved over the next two weeks to tee us up for an inclusion discussion on the next call

Next, we discussed a proposal to add events to the predeploy system contracts for cross-layer communication with EIP-7002 and EIP-7251. Consensus was that this change makes sense and the corresponding contracts will be updated.
Then, we had a call to deactivate EIP-158 to simplify the effects of deploying EIP-7702 and the Verkle migration. In light of the latest updates to 7702 we no longer need this proposal and decided to ignore it.
And to wrap the call, we had a discussion around making progress on other protocol improvements like history expiry and changes to the blob mempool to streamline usage of blobs by users like rollups. We jumped across various concerns here so check the call for the details. In short, there was a call for more regular updates on EIP-4444’s progress, and a call out to various things both rollups and clients can do to more intelligently handle the pipeline from blob producer to blob inclusion on-chain.
Reminder: Goerli has been deprecated and so clients will (or have already!) dropped support for this testnet.
Recording
https://www.youtube.com/live/58_bJD_dmm0?t=35s
Title: FOCIL_Breakout_Room__February_25th__2025
Category: Protocol_Calls___happenings

Author: system
Date: 2025-02-24T17:39:48.109Z

Schedule

Tuesday February 25th, 2025 @ 2pm UTC
Duration 60 min
Recurring meeting already on Ethereum Calendar
Zoom Link

Agenda


FOCIl and scaling https://x.com/adietrichs/status/1892951240524403089


Francesco’s doc on delayed execution and FOCIL: All-in-one epbs/FOCIL/DAS fork-choice - HackMD


Discussions about IL building rules on Discord and here: EIP-7805: Committee-based, Fork-choice enforced Inclusion Lists (FOCIL) - #6 by marchhill


“Wrong fork domain used” issue


GitHub Issue
Title: Call_for_a_Regular_AllERCDevs_Virtual_Meetup
Category: Protocol_Calls___happenings

Author: xinbenlv
Date: 2023-04-27T21:35:44.071Z

Hi all, we are proposing a new virtual meetup. here is the proposal

Canonical Link: The Draft on HackMD
Fill in Interest Form: interest form to receive calendar invitation.
Discord Channel: ERC Developers | ERCRef
Ethereum Magicians Forum Tag:  allercdevs

Call for a Regular AllERCDevs
Created: 2023-04-24
Last Updated: 2023-04-24
Author: xinbenlv@, jpitts@ (please feel free to add your name if you contributed)
With input from: hudsonjameson@, kdenhartog@, anettrolikova@
Background
Hi friends,
My name is Victor (twitter.com/ZainanZhou, github.com/xinbenlv). I am an EIP Author and one of the EIP Editors. Among other areas, I contribute the most to ERC standards.
As some of our Ethereum friends know, we have been circulating an idea to hold a regular call for people involved in authoring ERCs, building dApps and smart contracts which depend on ERCs (they almost always do!), and to advocate for open standards and interoperability.
We have received quite positive responses and interests to start it, and hence the proposal.
Motivation
Provide a venue for synchronized collaboration: Today, the discussion about ERCs (the application level of Ethereum on top of EVM) is overly asynchronous. You can discuss over Github Commits, EthMagicians and OpenZeppelin forum threads, and Discord servers including Ethereum Cat Herders and Eth R&D. While the asynchronous approach has many advantages, synchronized discussion (i.e., live meetings) could provide many complements. AllCoreDevs and AllWalletDevs are great examples of how developers, when they coordinate well, can help boost a discussion, improve productivity, and accelerate social consensus forming.
Bring people together: We also hope to make it a place where great contributors can meet each other, learn from each other, and bring a touch of humanity to each other.
Specifics

Target participants: ERC authors, contributors, smart contract devs, dApp devs, researchers, security experts, economists, and generally anyone who cares for bringing more openness and interoperability to smart contract and dApp developments.
Frequency: Bi-weekly, rotating between two time zones for maximal participation (to poll the early prospective participants).
Length: 1 hour main session + 0.5 optional social/breakout room discussions.
Medium: Video Conferencing.
Persistency: Recordings, transcriptions, and summaries will be considered for public records, just like AllCoreDevs, for people who didn’t make it or who want to refer to or research them.

Sample outline of a session
As we want to create a space to bring the target participants together, here is a typical outline of a session:

20-minute show & tell sharing: finalized ERCs, reference implementations, dApps use cases, preso from AllWalletDev or AllCoreDev for cross-layer converstion.
30-minute authors of pending ERCs to share their proposal and ask for peer review comments.
10-minute other discussions.
[optional] 30-minute breakout room social chat.
Title: Beam_call_01__beam_teams____Feb_14__2025
Category: Protocol_Calls___happenings

Author: system
Date: 2025-04-04T18:07:26.252Z

Prev: Initial Call
Meeting Date/Time: Friday 2025/2/14 at 15:00 UTC
Meeting Duration: 1.5 hours

Introduction & Updates

New consensus layer teams progress overview
Funding structures and Protocol Guild updates
Legal status update (trademark issues)


Research Specialist Introductions

beam chain-specific EF Researcher Introductions
ZKVM Accelerationism Update


New Client Team Introductions & Presentations
Existing Client Team Introductions
Coordinator Introductions
Open Discussion/Closing Remarks

Future meeting schedule
Upcoming events and coordination
Next steps and action items



Youtube : https://www.youtube.com/watch?v=sSx6juIu4AI&list=PLJqWcTqh_zKEF-DMsgZZPPM4wvTw9zgd7
GitHub Issue
Title: Join_the_8th_AllERCDevs_tomorrow
Category: Protocol_Calls___happenings

Author: xinbenlv
Date: 2023-08-24T02:59:25.565Z

We will have our 8th AllERCDevs sessions tomorrow UTC1500 (8am US PT, 11am US ET, 11pm Singapore Time). Join us to learn about and give feedback to ERC-223 and others. Feel free to sign up other topics too!
https://github.com/ercref/AllERCDevs/issues/9
here are the recordings and notes


Video Recording (forgot to start zoom, so here is the access to Airgram Video): https://app.airgram.io/7065496599555735553/share/2befaf46428f11eebaf70a2cbd030b4d?from=A91fc19caf6ac11eda1a80a2cbd030b4d-7065496599555735553 Passcode: FT6H


Airgram Notes: https://app.airgram.io/7065496599555735553/share/2befaf46428f11eebaf70a2cbd030b4d?from=A91fc19caf6ac11eda1a80a2cbd030b4d-7065496599555735553 Passcode: FT6H


Fireflies Notes: https://app.fireflies.ai/view/AllERCDevs-EU-US-time-friendly-session-::RpQENYnWdTu52wC0
Title: FOCIL_Breakout__6
Category: Protocol_Calls___happenings

Author: system
Date: 2025-03-11T11:20:41.565Z

Schedule

Tuesday March 11th, 2025 @ 2pm UTC
Duration 60 min
Recurring meeting already on Ethereum Calendar
Zoom Link

Agenda


FOCIl and scaling https://x.com/adietrichs/status/1892951240524403089


Francesco’s doc on delayed execution and FOCIL: All-in-one epbs/FOCIL/DAS fork-choice - HackMD


Discussions about IL building rules on Discord and here: EIP-7805: Committee-based, Fork-choice enforced Inclusion Lists (FOCIL) - #6 by marchhill


“Wrong fork domain used” issue


GitHub Issue
Title: EVMMAX_implementers_call__1__December_5_2024
Category: Protocol_Calls___happenings

Author: abcoathup
Date: 2024-12-06T03:46:27.068Z

Agenda
EVMMAX Implementers Call 1 · Issue #1204 · ethereum/pm · GitHub
Summary
Summary by Kev (Copied from Eth R&D Discord)

Besu & EthJS: add modular arithmetic lib
Chance: Spec out poseidon and add a poseidon impl
Jared: Help chance integrate into geth codebase
Investigate whether we need to precompute poseidon constants in montgomery form
(low priority) Investigate whether opcode inversion is so costly such that it needs to be an opcode and also used in a way that makes batch inversion not viable

Notes
Notes by @pdobacz (Copied from ethereum/pm)

clients/implementations represented: Geth, EthJS, Besu, evmone, Cairo ZK-VM
progress updates:

geth (EIP-6690 prototype+bls prototype using evmmax-bls12-381 tool)
evmone (low-level lib)


Poseidon use case

no objections to select this as 1st priority use case to cover

point raised if the bottleneck for the use case isn’t calldata cost rather than mod arith cost


what constants of Poseidon are we interested in?

depends on the field one’s using.


use case of Poseidon Hash itself

merkle path verification, need 32 poseidon hashes for every update
the constants matrix is the same for all of them for a single application
constants change when you change the field




choice of assembler - Huff-based like evmmax-bls12-381 vs Yul based
how to format Montgomery constants - opaque or explicitly in Montgomery form?

needs measuring


modular inversion - should this be an opcode?

complexity of such opcode would be large relative to current spec
needs measuring



Recording
Title: RollCall_Breakout__2__Fee_Markets
Category: Protocol_Calls___happenings

Author: adietrichs
Date: 2024-01-29T18:14:28.045Z

As announced on RollCall #2, we are organizing a series of breakout calls each Wednesday. The second breakout call will be on L2 fee markets. The intention is for these breakout calls to be optional additions to the monthly RollCalls, and aimed at bringing together the subset of teams interested in each particular topic.
Meeting Info

Wed Jan 31, 2024, 14:00-15:30 UTC


Zoom link shared in the rollcall channel in the EthR&D Discord, which is bridged to the RollCall telegram channel, shortly before the call.



Agenda

Introduction (short presentation)
Rollup teams’ summary of current thinking
EVM gas cost repricing

use cases (e.g. keccak for zk)
challenges (backwards compatibility, client & language support)
removing gas observability via EOF


L1 settlement fees

fees independent of L2 prices & execution results
adapting the 4844 tx type
wallet / tooling support


Congestion pricing

differences L1 / L2
potential for unbundling EIP-1559


Open discussion

Further discussion
Feel free to add comments here with further items of discussion

Author: abcoathup
Date: 2024-02-06T07:53:24.676Z

RollCall (L2 standards) fee markets breakout call
Notes by @adietrichs
(From Eth R&D Discord)
basically, we talked about 3 main topics:

repricing EVM operations (say keccak for zk)
L1 passthrough fees, how to pay for settlement and DA cost
potential proper multidim pricing (passthrough is basically a simple 2d version of that)

takeaway was that the topic where we might be close to having something to standardize is the L1 settlement cost. we talked a bit about what to standardize there, and the main feedback was that standardizing both a 2d tx type and a fee estimation API would be the best candidates.
So we introduce the concept of “settlement gas” (name tbd), and each L2 can have their own logic for how much settlement gas a tx consumes, and how to set the price for that gas during inclusion, but there would be a standardized way for users to specify limit and max price, and for estimating cost of a tx.
So ideally we can turn this into one or two concrete RIPs and move forward with that.
Video:
Title: All_Core_Devs___Execution__ACDE___212__May_22__202
Category: Protocol_Calls___happenings

Author: system
Date: 2025-05-09T21:56:00.471Z

May 22, 2025, 14:00-15:30 UTC
Stream
Ethereum Protocol Calls Calendar subscription

Agenda

Glamsterdam planning process

Community Consensus, Fork Headliners & ACD Working Groups
For an ACD platform


TBA

 🤖 config

Duration in minutes : 90
Recurring meeting : true
Call series : ACDE
Occurrence rate : bi-weekly
Already a Zoom meeting ID : false #
Already on Ethereum Calendar : false #
Need YouTube stream links : true #
Facilitator email: tim@ethereum.org
Note: The zoom link will be sent to the facilitator via email


GitHub Issue
Title: PeerDAS_Breakout_Call__24__Apr_8__2025
Category: Protocol_Calls___happenings

Author: system
Date: 2025-04-03T13:04:42.650Z

Apr 8 (Tues), 2025, 10:00 UTC
Duration: 60 minutes
Zoom link
Ethereum Protocol Call calendar
Notes
Previous call
Homepage: DAS.wtf
Facilitator email: will@ethreum.org
Facilitator Telegram: @corcoranwill
Agenda Overview
A.  Client Updates
B.  Devnet / Testing Updates
C.  Spec / EIP Discussion
D.  Open Discussion
Agenda Details
Client Updates

PRIORITY: All teams to focus on implementing getBlobsV2 and running across clients

CL Client Teams




Team
Link
Previous Update
Timely Discussion Topics




Prysm
link
-
-


Lighthouse
link
-
-


Teku
link
-
-


Lodestar
link
-
-


Nimbus
-
-
-


Grandine
-
-
-



EL Client Teams




Team
Link
Pervious Update
Timely Discussion Topics




Geth
-
-
-


Nethermind
-
-
-


Reth
-
-
-


Besu
-
-
-


Erigon
-
-
-



Devnet / Testing Updates
peerdas-devnet-6 (specs)
Devnet-6 Open Questions
STEEL Updates
Sunnyside Updates
Spec / EIP Discussions
P0 : Open Spec PRs
P1 : Draft Spec PRs
Spec Release Updates:
Open Discussion
Discussion Item #1
Discussion Item #2
GitHub Issue
Title: EIPIP_Meeting_115___April_16__2025
Category: Protocol_Calls___happenings

Author: system
Date: 2025-04-14T11:04:17.205Z

Meeting Info

Date and Time: Apr 16, 2025, 14:00 UTC
Zoom shared on the Ethereum Protocol Calls Calendar 
EIPIP Meeting Playlist
Discussion - ECH Discord #eip-editing channel

Agenda
1. Discuss Open Issues/PRs, and other topics

 Update EIP-196: Fix coordinate description by sylvainpelissier · Pull Request #8741 · ethereum/EIPs · GitHub
 Normally, RPC is not defined in EIP but rather within a PR in execution-api repository. I like the idea, though, very useful 👌 · Issue #9539 · ethereum/EIPs · GitHub

Edit to Final Proposals

 Update EIP-3607: Fix typo by dankrad · Pull Request #9625 · ethereum/EIPs · GitHub
 Update EIP-6953: Update Historical Boundary Definitions by timbeiko · Pull Request #9550 · ethereum/EIPs · GitHub
 Update EIP-7045: fix typos by taozui472 · Pull Request #9517 · ethereum/EIPs · GitHub
 Update EIP-1679: Fixed Broken Link by donatik27 · Pull Request #9477 · ethereum/EIPs · GitHub
 Update EIP-3860: Update eip-3860.md by owenzimmew06 · Pull Request #9614 · ethereum/EIPs · GitHub
 Update EIP-1052: fix grammar and typo issues by hexcow · Pull Request #9638 · ethereum/EIPs · GitHub
 Update EIP-7251: fix typos by jasmyhigh · Pull Request #9596 · ethereum/EIPs · GitHub (should be closed?)

Edit to Stagnant Proposals

 Update EIP-7577: typo fix by mdqst · Pull Request #9639 · ethereum/EIPs · GitHub

Update to EIP-1
TBA
Other topics

 Stagnant Bot Issue:  a tag to clarify an active consideration to prevent EIPs from being pulled in Stagnant Ref: Discord.

Call for Input




Call For Input
Status
Inclination/Result
Deadline




Call for Input: Modify ERC-6492 Reference Implementation · Issue #381 · ethcatherders/EIPIP · GitHub
Open
1, Opposed
March 21, 2025


Call for Input: Allow Links to Blockchain Commons · Issue #376 · ethcatherders/EIPIP · GitHub
Open
2 Opposed and 1 Neutral
February 6, 2025



2. Other discussions and updates from past meetings

EIP Reviewers - Where to document the list?
EIP Reviewers: Survey & Contribution Report
Adding new reviewers/editors - PRs to update checklist & formalize process

3. EIPs Insight - Monthly EIPs status reporting.

 April 2025

4. EIP Editing Office Hour

Agenda 56 Video 55

5. Review action items from earlier meetings

Notes

Next Meeting date & time - May 21, 2025 (3rd Wed of the Month) at 14:00 UTC
GitHub Issue
Title: EIP_7732_Breakout_Room__17__February_28__2025
Category: Protocol_Calls___happenings

Author: system
Date: 2025-02-21T12:28:01.651Z

EIP-7732 Breakout Call

February 28th (Fri), 2025 , 14:00 UTC  
Duration: 60 minutes
Zoom link
Recordings
Previous meetings

Agenda

EIP Status
Implementation status
Interop status
Process Randao Mixes spec bug.

GitHub Issue
Title: ePBS_breakout__7__August_16_2024
Category: Protocol_Calls___happenings

Author: abcoathup
Date: 2024-08-14T03:29:44.248Z

Agenda
EIP-7732 breakout room #7 · Issue #1133 · ethereum/pm · GitHub; moderated by @potuz
Notes



HackMD



EIP-7732 Breakout room #7 Notes - HackMD
This meeting had very low attendance. Essentially all conversation was between @g11tech from Lodestar and @potuz from Prysm, therefore decisions during this meeting are temporary and require further discussion with the ePBS community involved in the...





Recording
Title: JSON_RPC_standardization_breakout__1__January_20__
Category: Protocol_Calls___happenings

Author: abcoathup
Date: 2025-01-20T21:45:08.188Z

Agenda
JSON-RPC Standardization Breakout · Issue #1252 · ethereum/pm · GitHub
Recording

Author: abcoathup
Date: 2025-01-20T21:46:51.210Z

AI summary (using )
The discussion on JSON-RPC standardization highlights the need for clarity and consistency in RPC methods used in Ethereum, addressing various challenges and proposing improvements.
Key Points
Current State of JSON-RPC
The JSON-RPC landscape for Ethereum is vast, with many methods in use that lack proper specification. This has led to inconsistencies and frustrations among developers who rely on these methods for client interactions [0:27][1:18].
Importance of RPC Compatibility Tests
Establishing a baseline for RPC compatibility is crucial. The group emphasizes the need to ensure that all clients pass the RPC compatibility tests before making further changes or additions to the specifications [3:05][3:33]. This will help identify discrepancies and improve overall functionality.
Challenges with Existing Tests
Many existing tests do not work uniformly across different clients, leading to confusion and inefficiencies. Developers express frustration over tests that fail due to client-specific issues rather than actual discrepancies in the RPC methods [1:45][2:12].
Error Handling and Specification Clarity
The conversation touches on the importance of standardizing error handling in RPC calls. Different clients return varying error codes and messages, which complicates the development process. A unified approach to error reporting is necessary to avoid confusion and ensure reliability [25:10][27:47].
Future Directions
The group discusses the potential for future meetings to include external stakeholders, such as wallet developers and dApp creators, to gather broader input on the RPC specifications. This collaborative approach aims to refine the specifications and address user needs more effectively [30:26][32:05].
Conclusion
The meeting underscores the need for a structured approach to JSON-RPC standardization in Ethereum. By focusing on compatibility tests, error handling, and collaboration with external stakeholders, the group aims to create a more reliable and user-friendly RPC environment.
Title: Thread_for_1st_Session_of_AllERCDevs_Meetup__2023_
Category: Protocol_Calls___happenings

Author: xinbenlv
Date: 2023-05-11T17:51:51.038Z

Hi all, we wanna bring to your attention for the 1st allercdevs meeting.
Sign-up for topics at the agenda issue at Agenda for 1st AllERCDevs Meetup 2023-05-16 UTC2300 · Issue #1 · ercref/AllERCDevs · GitHub
For how to participate in the regular meetup of allercdevs see Call for a Regular AllERCDevs Virtual Meetup

Author: xinbenlv
Date: 2023-05-17T14:40:16.449Z

Thank you all. The video recording is out: All ERC Dev Meeting 1 - YouTube
Title: COUNCIL_OF_PARIS__Call_For_Rings_and_Participants
Category: Protocol_Calls___happenings

Author: mariapaulafn
Date: 2019-02-04T17:17:49.467Z

Hi everyone, sorry this took a bit long, but i had a very busy January.
The call for rings with already set-up rings is here.
HOWEVER: none of these are set in stone. This Google Form is for you to propose new ones. I have already proposed one for the Cat Herders, I know I would like to be introed to this, and added @Ethernian’s Whisper one. Please feel free to add your suggestions via the form, and we will consider them for the rings. Additionally, I am planning to have a short session at the start for “spontaneous proposals”, as we will receive a lot of people and maybe some don’t check the documents beforehand. This will open the event after an intro, so we can get to know new people, hear ideas, and discuss in or after the council, formally or just sitting in a café, anything works!
The pre-set rings that don’t have participants till February 20th will be deleted to make space for new rings as well.
Preliminary Agenda with rings will be posted on March 2nd, so please mark dates so you don’t miss proposing or giving feedback.
Let me know if you have any questions.

Author: 5chdn
Date: 2019-02-15T12:17:51.338Z

There may be interest to have an Ethereum 2.0 ring.
https://github.com/ethereum/eth2.0-pm/issues/29#issuecomment-463680018

Author: mariapaulafn
Date: 2019-02-18T10:25:31.712Z

After the events this weekend, and several people interested, I added a new ring:
Protocols to preserve the people working on Ethereum’s integrity
After the events unfolded during this past weekend that resulted on a massive outburst of accusations, conspiracy theories, demands, and verbal violence triggered by mob mentality, it is time, as a community, that we take a look at other tech communities and develop our own protocols (in case of abuse of power, harassment), talk about what is tolerable and what we should condemn and in which form, and work on our own procedures to behave as a unified, however decentralized community that has mature protocols and processes to deal with event that might jeopardize people’s integrity, and therefore, Ethereum’s development (eth is developed by humans!)
This session will not be livestreamed. Participation form is here.
Topics of Discussion

Power abuse
Harassment (various forms)
prevention protocols
mobbing /cyber bullying
Doxxing
D&I

Author: boris
Date: 2019-02-22T22:37:02.013Z

We’ve moved the HackMD document here:




[Council of Paris 2019] Call for Rings Happenings


    Note: ported from HackMD. Discourse wiki mode is turned on, so regular users should be able to edit it directly. Leave a comment if you can’t edit the wiki and we’ll add your info. 
Council of Paris

When: March 4, 2019
Where: CNAM - 292 Rue Saint-Martin, 75003, Paris, same venue as ETHCC


Basic details:
Website: https://ethereumevents.global/events/2019-council-of-paris/ 28 
Agenda: https://docs.google.com/spreadsheets/d/1BYudpf2TfjO-qbAoSuzFBH0Ab_BRiQJ31VUhGoc6n_Y/htmlview 
Registration: http…
Title: Eth_simulate_Implementers__Meeting___April_14__202
Category: Protocol_Calls___happenings

Author: system
Date: 2025-04-07T13:48:51.253Z

eth_simulate Implementers’ Meeting

Date and time in UTC April 14, 2025, 12:00 UTC
Duration in minutes: 60 minutes
Recurring meeting : true
Call series : eth_simulate Implementers
Occurrence rate : weekly
Other optional Resources


Ideas for eth_simulateV2
PEEPanEIP#135: Eth Simulate with Oleg and Killarie class="onebox allowlistedgeneric" data-onebox-src="https://eips.ethereum.org/EIPS/eip-4399">
  
Ethereum Improvement Proposals


EIP-4399: Supplant DIFFICULTY opcode with PREVRANDAO
Expose beacon chain randomness in the EVM by supplanting DIFFICULTY opcode semantics







docs.login.xyz



SIWE Overview | Sign-In with Ethereum
Sign-In with Ethereum - For Web2 and Web3








Ethereum Research – 19 Jun 24




Fork-Choice enforced Inclusion Lists (FOCIL): A simple committee-based...




Proof-of-Stake





Block proposer




^focil => fossil => protocol ossification  by Thomas, Barnabé, Francesco and Julian - June 19th, 2024  This design came together during a small, week long, in-person gathering in Berlin with RIG and friends to discuss censorship resistance,...

Reading time: 13 mins 🕑
Likes: 50 ❤







Agenda

Notes from the last meeting
Client Implementation update
Test
Discuss spec for eth_simulateV2

Other comments and resources
The zoom link will be sent to the facilitator (please fill in the email and telegram)
Facilitator email: Killari@gmail.com
Facilitator telegram: @Qhuesten
GitHub Issue
Title: All_Core_Devs___Execution__ACDE___190__June_20_202
Category: Protocol_Calls___happenings

Author: abcoathup
Date: 2024-06-15T02:23:13.218Z

Agenda
Execution Layer Meeting 190 · Issue #1066 · ethereum/pm · GitHub
Moderator: @timbeiko
Summary
Recap by @timbeiko:

devnet-1: still a WIP from all teams, but we can optimstically get a version up by next ACDC with a subset of EL/CLs! note that the spec does include EL-triggered withdrawals and leaves 7702 as per the latest merged commit (https://notes.ethereum.org/@ethpandaops/pectra-devnet-1)
for 7702, @matt opened a draft PR which proposes a different delegation/revocation design: https://github.com/ethereum/EIPs/pull/8677, teams should review this, and we’ll organize another 7702 breakout before the next ACDE (poll for time in next post!)
EOF devnets will be built on top of Prague, teams should rebase. Various implementation stages being tracked here (eof/spec/implementation_matrix.md at main · ipsilon/eof · GitHub), and Erigon said it would be nice to have some EOF blocks to test with soon
PeerDAS devnets will be based on CL spec v1.5.0-alpha.3 , expected to launch in the next few weeks
I proposed a template for discussions-to threads on EthMag (Template for `discussion-to` threads), if teams have suggestions on it, please share, otherwise, we’ll get it added
@parithosh is looking for EL admins for the eth-clients repo, see the Eth R&D Discord thread for context
Next ACDE is happening as scheduled on July 4th, but @ralexstokes will be running it. Have fun !

(from Eth R&D Discord with minor edits for user names and links)
Recording
https://www.youtube.com/live/8VGf-EE6zNE?t=137s
Additional info
Notes by @timbeiko: https://paragraph.xyz/@timbeiko.eth/acde-190-recap
Notes by @Christine_dkim: Ethereum All Core Developers Execution Call #190 Writeup | Galaxy
Title: Beam_call__1
Category: Protocol_Calls___happenings

Author: system
Date: 2025-02-26T22:18:32.555Z

Prev: Initial Call
Meeting Date/Time: Friday 2025/2/14 at 15:00 UTC
Meeting Duration: 1.5 hours

Introduction & Updates

New consensus layer teams progress overview
Funding structures and Protocol Guild updates
Legal status update (trademark issues)


Research Specialist Introductions

beam chain-specific EF Researcher Introductions
ZKVM Accelerationism Update


New Client Team Introductions & Presentations
Existing Client Team Introductions
Coordinator Introductions
Open Discussion/Closing Remarks

Future meeting schedule
Upcoming events and coordination
Next steps and action items



Youtube recording
GitHub Issue
Title: Pre_Council_Call_For_Rings
Category: Protocol_Calls___happenings

Author: ChainSafe
Date: 2018-09-10T15:34:04.004Z

Hello Magicians!
@noot and I are excited to be helping out with the Council of Prague, specifically as ring wranglers. We’re trying to get an idea of what rings will be participating and who will be participating in what ring. To do this we have put together a hackmd document that we hope people will fill out accordingly.  If you have any questions please post them here.
Thanks!
Title: PeerDAS_breakout__4__July_23_2024
Category: Protocol_Calls___happenings

Author: abcoathup
Date: 2024-07-24T06:59:58.032Z

Agenda
PeerDAS Breakout Room #4 · Issue #1103 · ethereum/pm · GitHub
Key items
by Jimmy Chen (from Eth R&D Discord):

Teams are mostly focused on client stability, optimisation and refactoring
devnet-1 was shutdown last week and devnet-2 hasn’t been scheduled yet as teams are focused on improving stability and refactoring.
Teams noted the following changes for the next devnet launch

MetaDataV3 rpc query with custody subnet count
Clients to make sure initial syncing work and nodes can serve data column rpc methods reliably
Delay blob spamming to a few epochs after genesis



Notes & chat log


docs.google.com



PeerDAS Breakout Room notes
PeerDAS Breakout Room #22 Date: 2025.03.25 Agenda: https://github.com/ethereum/pm/issues/1401   CL Client updates: Prysm Database redesign to fix the inode issue on devnet-5 Francis from Base worked on EL getBlobsV2 and getPayloadV5 integration Teku...





Recording
Title: DGOV_2018___distributed_governance_conference_in_A
Category: Protocol_Calls___happenings

Author: tomislavmamic
Date: 2018-07-03T13:50:08.207Z

Hi all, we are proposing for Fellowship to support the upcoming DGOV 2018 - the first conference on distributed governance. We hope to present it to you at Berlin Council.
DGOV 2018 will provide a meeting point for the distributed consensus technologists, policy-makers, academics and practitioners to learn and share experience in self-organised organisations.
It is a forum for interdisciplinary debate on the most pressing problems the world confronts nowadays and on problem solving capacity that new digital technologies offer.
Check it out:
Intro blog post: Introducing the #dgov18 conference | by Dgov Earth Conference | DGOV Foundation Blog | Medium
Website: https://dgov.earth
Public telegram group: Telegram: Contact @dgov18
Reddit: /r/dgov
Twitter: @dgovearth
Reach out for details:
tomislav.mamic.st@gmail.com or
@Timotheus tim.bansemer@inblock.io
Title: EOF_Implementers_call__57__September_4_2024
Category: Protocol_Calls___happenings

Author: shemnon
Date: 2024-09-04T18:39:28.556Z

Agenda
EOF Implementers Call #57 · Issue #1138 · ethereum/pm · GitHub
Video




link
Call Notes



clients and compilers - no non-test updates


switch to prague


mario discussed 7702/EOF testing features in EEST https://github.com/ethereum/execution-spec-tests/blob/eip-7702-devnet-3/tests/prague/eip7702_set_code_tx/test_set_code_txs.py


Fuzzing - no new updates


Discussed converting EOF format tests into format tests.

Init containers need extra work, either double wrapping or need to declare deployed container format.  Issues include appending data
For automated testing we will move to assuming the container is deployed, and in cases where that isn’t going to work we need to notate the tests with expected outputs



New release of legacy tests - invalid tests have been removed, or fixed, or moved to EEST.  No new coverage – all new coverage comes in EEST.


ISCONTRACT

Legacy solidity will not easily be able to determine if it’s EOF or Legacy, so the code may fail compiling to EOF.  Old contracts will need new versions or alternates for EOF.
Most libraries depending on assembly would need to change for EOF anyway (any use of JUMP, CALL*, EXCODE* for example)
May be best solved in solidity?  conditional compilation or new is_contract primitive? existing solidity PR  Detect EVM version? existing solidity pr
Example: OpenZeppelin, Solady, Tycho do deep code interactions and have taken up to a year to implement.
Need to do outreach to the AA team, as they expressed concern on ACD that this may be problematic. (Piotr to reach out)



What is Erigon’s status?

Unknown status.



More on nethermind’s status

7702 is in a different branch from EOF.  7702 will land in Nethermind master first.
Will target prague in EOF branch
Running published EEST fixtures.



New fixtures will be published this week.  Need to fix an EEST bug relating to EXT*CALL opcodes.


github comment
Title: _HELP__Volunteers_needed_for_Council_of_Paris_2019
Category: Protocol_Calls___happenings

Author: markoprljic
Date: 2019-02-20T16:47:40.465Z

We’re looking for more volunteers to help with the organization of Magicians Gathering for Council of Paris 2019.
https://ethereumevents.global/events/2019-council-of-paris/
If you’re from Paris or coming to ETHCC2019 in early March join us at the Magician Council, be part of it and help us make this event better.
What you’ll be doing:

setting/unsetting the venue
provide assistance at check-in
provide any other help needed during the day

This event is scheduled for March 4th, 2019. It would be good that you can be available the day before.
We very much appreciate your help and won’t leave you empty handed. Thanks to Asseth and @jdetychey All volunteers from the Magicians Gathering will receive a Free ticket for ETHCC2019!
How to apply?
Just reach out to me via DM 
Thanks, and see you in Paris!