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

Author: system
Date: 2025-03-05T18:43:59.281Z

eth_simulate Implementers’ Meeting

Date and time in UTC March 10, 2025, 12:00 UTC
Duration in minutes: 60 minutes
Join Zoom Meeting
Recording: eth_multicall Playlist

Resources

Ideas for eth_simulateV2
PEEPanEIP#135: Eth Simulate with Oleg and Killari

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

Add more discussion items or async updates.
The next meeting is scheduled for March 17, 2025 at 12:00 UTC
GitHub Issue
Title: EVMMAX_implementers_call__2__January_30__2025
Category: Protocol_Calls___happenings

Author: abcoathup
Date: 2024-12-11T02:56:05.912Z

Agenda
EVMMAX Implementers Call 2 · Issue #1208 · ethereum/pm · GitHub
Title: Thank_you___you_are_a_really_great_community_
Category: Protocol_Calls___happenings

Author: chrisek
Date: 2021-03-15T04:56:13.734Z

Hi, I signed up recently, but I watched you a lot earlier, I think you are the best communuty around: D
A lot of substantive speech, helpful people and kindness!
thank you!
Title: CoreDev_July_Online_Meeting
Category: Protocol_Calls___happenings

Author: boris
Date: 2019-05-30T23:45:58.421Z

From CoreDev call there didn’t seem to be a lot of appetite to meet in person, and we are now only about 7 weeks away from the earlier dates proposed:




CoreDevs ETH1x / Istanbul Meeting July Poll & Feedback Ethereum 1.x Ring


    We’re in the midst of sending out wrap up emails and links from last weeks CoreDevs Berlin meetings. 
Here is the email that went out: https://md.spade.builders/lXX8_RxoRGyr6zunhmTuqQ 
Please also use this thread for feedback for those that attended, those that viewed the livestream, or those with other comments 
Potential Next Meeting
Here are two polls to gather feedback on timing and location of a next meeting. 
We have one volunteer @meknab who has said she can help out on the ground…
  

Talking to @shemnon, let’s schedule an online conference.
Danno would present an Asiago April 2020 hardfork plan, and by then we’ve likely got a ton of Istanbul topics that would benefit from live discussion.
I’ll suggest Tuesday July 23rd, 7am to 11am PST.

Author: boris
Date: 2019-06-02T00:11:38.510Z

Should ETH1-ETH2 Bridge be a topic of discussion? If anything can make this easier, getting it into Istanbul would be good, or at least planning for the April hardfork.
See @cdetrio’s thread:


twitter.com



Casey Detrio (@cdetrio) on X
@cdetrio

I'm guessing other devs and researchers are starting to have similar thoughts, iterating on the idea of an eth1-eth2 bridge. And I'm excited to see what they'll propose.

Author: fubuloubu
Date: 2019-06-02T02:15:51.660Z

Yes, it should be. @ralexstokes and the rest of the working group (myself included) should be able to figure out what phases there might be, what forks they might be ready by, and give a good estimate of the schedule for integration of this key component of the ETH 2.0 Phase 0 release. We can at least get started.
Title: Lightning_Talks__Web3_Tech_Stack
Category: Protocol_Calls___happenings

Author: jplatts12
Date: 2018-07-15T11:08:45.336Z

View presentation

Author: boris
Date: 2018-07-19T08:53:17.144Z

Video:



view.ly



Lightning Talk: Web3 Tech Stack, Jack Platt & Community Signalling, Griff...
First half, Jack Platt from the Presentation and discussion thread: https://ethereum-magicians.org/t/lightning-talks-web3-tech-stack/726 Second half, Griff & Phil covered Signalling. Presentation and discussion thread:...
Title: RollCall_Breakout__1__EIP_4844_Readiness_Check
Category: Protocol_Calls___happenings

Author: adietrichs
Date: 2024-01-19T16:48:57.486Z

As announced on RollCall #2, we are organizing a series of breakout calls each Wednesday. The first breakout call will be on EIP-4844 testing. 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 24, 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

Goerli post-fork status update
Summary of testing plans by L2 teams
Discussion

Upcoming Sepolia fork
Mainnet rollout timeline
Open section



Further discussion
Feel free to add comments here with further items of discussion
Title: Osaka_devcon___Japan_Blockchainweek
Category: Protocol_Calls___happenings

Author: Ethernian
Date: 2019-05-24T10:43:28.134Z

Would we like to have a new FEM gathering in Osaka?
Maybe as a part of Japan Blockchainweek (just an idea)?
cc: @boris

Author: manhuichi
Date: 2019-05-24T10:59:49.912Z

Yes please! Japan Blockchain Week will consist of a list of events hosted around DevCon5. It would be a great way to get the local community involved. This will bring not only Ethereum enthusiasts and followers but the whole crypto community together and to learn about Ethereum ^^

Author: Ethernian
Date: 2019-05-24T11:01:57.960Z

@manhuichi,
Are you one of BlockchainWeek Team? Can we contact you for more details?

Author: manhuichi
Date: 2019-05-24T11:04:15.542Z

Yes  feel free to DM me email huichi@provenance.events

Author: timbeiko
Date: 2019-05-24T14:51:45.411Z

FWIW, it would be very accommodating schedule-wise if this was the day right before Devcon (Monday Oct. 7th), as people could fly in over the weekend and just stay for the entire week.
Title: Notes_from_Data_Session_in_Berlin
Category: Protocol_Calls___happenings

Author: tjayrush
Date: 2018-07-25T14:43:47.406Z

These are my notes from the session I and Ben Bollen held on the second day of the council.  I’d be very happy to get any corrections/additions/clarifications, etc.


docs.google.com



Magicians Discussion - Blockchain/Account Scrapers and Data Accessibility
Nominal Topic: Improving the node to promote running more nodes / Preparing for Sharding  Actual Discussion Topic: Is there a “data problem”? Is there a danger of Ethereum data access becoming centralized?  ---- The following notes follow Chatham...
Title: Stateless_Implementers_Call__30__February_10__2025
Category: Protocol_Calls___happenings

Author: abcoathup
Date: 2025-01-29T00:00:17.583Z

Agenda
Stateless Implementers Call #30 · Issue #1263 · ethereum/pm · GitHub moderated by @rudolf

Author: ihagopian
Date: 2025-02-15T16:40:31.207Z

Call summary & recording
Title: Council_of_Berlin___Closing_Circle__Video_
Category: Protocol_Calls___happenings

Author: boris
Date: 2018-07-17T18:44:40.829Z

view.ly



Final Closing Circle - FEM Council of Berlin - Day Two
The final closing circle of the event. Feedback from the group, feelings about the event, intentions for the future. Comments and other discussion in the forum: https://ethereum-magicians.org/t/council-of-berlin-closing-circle-video/767 Thank you...
Title: Interop_Working_Group_Call__4___Feb_24__2025
Category: Protocol_Calls___happenings

Author: system
Date: 2025-02-21T07:24:12.664Z

Meeting Info

Time/Date: Feb 24th @ 4pm UTC
sign up for calendar invite here
Zoom: shared in the “L2 interop working group” telegram prior to the call
Recording: tbd

Agenda

review of the Open Intents Framework
l2-interop GH repo

[want to present? add comment below or DM @rudolf6 on TG]
GitHub Issue
Title: OpenZeppelin_Adopts_Diamond_Storage_for_Upgradeabl
Category: Protocol_Calls___happenings

Author: mudgen
Date: 2023-09-15T13:23:35.328Z

Recently OpenZeppelin changed the variable storage for all of its upgradeable smart contracts to use Diamond Storage. This is a major change.
Here is the merged pull request: Use namespaced storage for upgradeable contracts by frangio · Pull Request #4534 · OpenZeppelin/openzeppelin-contracts · GitHub
Here is the issue about it on Github: https://github.com/OpenZeppelin/openzeppelin-contracts/issues/2964
Here is an article that describes how Diamond Storage works: How Diamond Storage Works - DEV Community
Title: All_Core_Devs___Consensus__ACDC___148__January_9__
Category: Protocol_Calls___happenings

Author: abcoathup
Date: 2024-12-14T01:17:09.756Z

Agenda
Consensus-layer Call 148 · Issue #1218 · ethereum/pm · GitHub moderated by @ralexstokes


Agenda summary
by @Nixo (Copied from Twitter)
Pectra testing
 Builder specs v0.5.0 for Pectra released 
 devnet-5 (live soon™) may be the last devnet. A devnet-6 is possible, but if 5 is smooth, could see testnets (Sepolia & Holešky) by… Feb?
relevant: testing, consensus & execution teams
Post-Pectra
PeerDAS & EOF are scheduled for inclusion in Fusaka (the next fork) - they’ll go over any updates
The name for the fork post Fusaka is being chosen (vote here: G-star name for Consensus Layer upgrade after Fusaka) - prolly’ll be chosen this week

Summary




All Core Devs - Consensus (ACDC) #148, January 9, 2025 Protocol Calls & happenings


    ACDC #148 summary 
Action Items 

Continue implementation/polish for pectra-devnet-5. Be on the lookout for devnet launch in the next week or two!

Summary 
Shorter call today that mainly focused on pectra-devnet-5 logistics. 

Touched on a few open questions/PRs for devnet-5 specs. Open items have been addressed.
Touched on client implementation progress. Various stages of readiness, but all CL clients are very close to being ready for devnet-5 launch.
Going to check-in with EL clients on next …
  

Recording



youtube.com


- YouTube
Enjoy the videos and music you love, upload original content, and share it all with friends, family, and the world on YouTube.






Additional Info

Gloas chosen as G-star name for Consensus Layer upgrade after Fusaka
Reminder: standardized validator hardware requirements: 
Ethereum All Core Developers Consensus Call #148 Writeup | Galaxy by @Christine_dkim
Highlights of Ethereum's All Core Devs Meeting #148 by @yashkamalchaturvedi

Author: yashkamalchaturvedi
Date: 2025-01-09T16:30:12.694Z

Call Notes:  Highlights of Ethereum's All Core Devs Meeting #148

Author: ralexstokes
Date: 2025-01-10T19:06:53.385Z

ACDC #148 summary
Action Items

Continue implementation/polish for pectra-devnet-5. Be on the lookout for devnet launch in the next week or two!

Summary
Shorter call today that mainly focused on pectra-devnet-5 logistics.

Touched on a few open questions/PRs for devnet-5 specs. Open items have been addressed.
Touched on client implementation progress. Various stages of readiness, but all CL clients are very close to being ready for devnet-5 launch.
Going to check-in with EL clients on next ACDE, but expect to launch devnet-5 in the next week or two.
Assuming devnet-5 has no issues, we should be on track to start discussing dates for forking testnets Sepolia and Holesky to Pectra in the next few weeks.
Had a request for last call on a networking PR to add IPv6 support to ENR records. PR here has been merged.
Had another request to provide feedback on a minimal set of node requirements to facilitate community coordination and help with protocol R&D. Document here: Hardware Requirements - HackMD
Closed out the call with a discussion of a poll to help find a star for the “G-fork” after Fusaka. Community favorite is Gloas.
Title: PeerDAS_breakout__12__November_26_2024
Category: Protocol_Calls___happenings

Author: abcoathup
Date: 2024-11-02T01:09:41.875Z

Agenda
PeerDAS Breakout Room #12 · Issue #1193 · ethereum/pm · GitHub
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: Council_of_Paris_2019__Shared_Accommodation
Category: Protocol_Calls___happenings

Author: markoprljic
Date: 2019-02-07T09:13:04.454Z

Hi everyone!
A crypto week in Paris is upon us and we’re probably all looking for accommodation and want to stay on budget. That’s why I wanted to reach out to all of you and see who’d be interested to book an Airbnb, share the house and split the bill?
Just give me a ping here to be considered during the shared house initiative 
cc/ @tomislavmamic

Author: Alchemist33
Date: 2019-02-25T13:13:15.448Z

Hi! Are you going from Zagreb? Did you already book accommodation?

Author: markoprljic
Date: 2019-02-25T13:27:35.210Z

Yes, I’m flying in from Zagreb. Why do you ask? Are you also coming from Zagreb?
Some of us here already booked a Hostel St Christopher's Inn Canal, Paris - 2021 Prices & Reviews - Hostelworld
Check the 12 Bed Mixed Dorm and see if there are any spots left, we’ll be in the same room

Author: Alchemist33
Date: 2019-02-25T13:47:23.780Z

I am flying from ZG on March 4th. Whats up with this shared accommodation proposal? I’ve talked to Tomislav (sa imenjakom mojim:)) on Telegram. Maybe we’ll have few more people flying from Zagreb.

Author: markoprljic
Date: 2019-02-25T13:52:58.824Z

No one replied back then so we booked this stay.
I’m flying in on March 2nd.

Author: Alchemist33
Date: 2019-02-25T13:56:25.130Z

OK. I’ll check AirBnB first, usually I stay next to Pompidou, but this hostel also looks nice.

Author: Alchemist33
Date: 2019-03-02T11:22:27.929Z

Cao Marko. Bukirao sam st christopher - vidimo se tamo. Pozdrav.

Author: markoprljic
Date: 2019-03-02T13:59:52.113Z

Great! I’m already there, see you soon

Author: Alchemist33
Date: 2019-03-04T21:43:31.025Z

Ej, jeste u hostelu? Koji ti je telegram nick?
Title: Call_for_EIPs_in_next_AllCoreDevs_call
Category: Protocol_Calls___happenings

Author: timbeiko
Date: 2019-03-23T13:15:54.044Z

The agenda for the next AllCoreDevs call (#58) has a call to discuss EIPs for Istanbul.
So far, no one has submitted any to be discussed, but have been several being discussed on this forum.
I just wanted to highlight that it may be worth it for the proposers/champions of these EIPs to attend the next call to discuss them. I’ll link a few here that have been discussed recently:

https://eips.ethereum.org/EIPS/eip-1829
https://eips.ethereum.org/EIPS/eip-615
https://github.com/ethereum/EIPs/issues/1559
https://eips.ethereum.org/EIPS/eip-665

Author: boris
Date: 2019-03-23T14:32:51.314Z

We’re probably going to need to reach out to folks and explain how to participate.
Eg Leave comment on GitHub issue, then hang out in AllCoreDevs Gitter to get the Zoom link before scheduled call.
@Recmo should get on the call for one.

Author: timbeiko
Date: 2019-03-25T18:35:54.318Z

Good point. I didn’t want to tag everyone who was involved in the discussion of an EIP on this post though

Author: lrettig
Date: 2019-03-27T00:51:51.323Z

EIP-1789. We’ll submit a properly formatted EIP very soon.
https://github.com/ethereum/EIPs/issues/1789
Title: EOF_implementers_call__62__November_27_2024
Category: Protocol_Calls___happenings

Author: abcoathup
Date: 2024-11-02T01:11:38.638Z

Agenda
EOF Implementers Call #62 · Issue #1192 · ethereum/pm · GitHub
Notes
Notes by @shemnon (Copied from ethereum/pm)
Testing Update

How to handle State tests with invalid EOF?

state tests - reject test if any EOF is invalid
Block tests - only an issue in genesis? Abort if EOF in genesis is invalid.
Imported blocks - presume valid as create TXes are how they are added, so invalid EOF should result in an failed transactions.
Extends to 7702 - 0xEF01 validation?


EOFWrap Tests

ports over legacy tests into EOF if it ports, stopgap for full testing
feat(tests): port ethereum/tests test cases (tracking issue) execution-spec-tests#972 will ultimately port all old tests



Client and Compiler Updates

No client updates, mostly focused on pectra
Solidity working on EOF as an experimental feature

eof: Support functions (CALLF, RETF, JUMPF) solidity#15550
eof: Implement stack height calculation solidity#15555
EOF: Implement ext*calls solidity#15559



Spec Updates

Compiler Metadata Section

Kaan from Sourcify Team
Current practice is to just append
would want a separate metadata section in EOF.

Unreachable by code (a good thing)
contains the CBOR data solidity produces


Current status of appended to data and behind constructor fields makes it hard to find
Experimental Solidity EOF handling is to put CBOR metadata at the beginning of the data section.
Would insulate code/data indexes from variable CBOR sizes, such as if experimental flags are logged.
Next step is an EIP



Brief discussion on header section numbers
EOFCREATE hash - ipsilon/eof#162 (comment)

danno wants a “0xef01” hash added
Solidity has concerns about the genericness, would prefer container index
Bad salt management could prohibit multiple deployments
Should hash include auxdata, not just code data?
possible issues with cross-chain deployment. The more mandatory data makes same address contracts difficult.
note: some people don’t like metadata has in CREATE2, would compiler metadata be excluded from address derivation?
Are there security implications? Would the “code hash” guarantees be forgotten about? Could compilers compensate?
Please add comments to the thread.

Recording
Title: Ethproofs_Community_Call__1__team_intros__new_feat
Category: Protocol_Calls___happenings

Author: system
Date: 2025-04-10T16:27:37.298Z

Ethproofs Community Call 01, April 25, 2025

April 25, 2025, 14:00-15:00 UTC
Duration in minutes : 120

Agenda




Agenda Section
Agenda Item
Details
Presentation




Intro
00
Ethproofs Introduction
link


zkVM Team Intros
-
-
-


-
01
Ix with John from Argument
link


-
02
StarkV with Maya from StarkWare
link


-
03
ZCray with Jim from Irreducible
link


-
04
Boojum 2.0 with Michael from MatterLabs
link


-
05
Ceno with Ming from Scroll
link


-
06
Scroll zkEVM with Rohit from Scroll
link


-
07
Jolt with Justin from a16z
link


-
08
Keth with Elias from Kakarot
-


-
09
Linea zkVM with Olivier from Linea
link


-
10
Nexus zkVM 3.0 with Michel from Nexus
link


-
11
o1VM with Danny from O(1) Labs
-


-
12
OpenVM with Yi from Axiom
link


-
13
Pico with Mo from Brevis
link


-
14
powdrVM with Leo from powdr
-


-
15
R0 with Jeremy from RISC Zero
link


-
16
SP1 with Uma from Succinct
-


-
17
Valida with Mamy from Lita
link


-
18
zkEngine with Wyatt from NovaNet
link


-
19
ZisK with Jordi from Hermez
-


-
20
zkMIPS with Stephen from ZKM
link


-
21
zkWASM with Sinka from Delphinus
-



Facilitator email: will@ethereum.org
Facilitator telegram: @corcoranwill
GitHub Issue
Title: Future_of_EOA_AA_breakout__3__May_29_2024
Category: Protocol_Calls___happenings

Author: abcoathup
Date: 2024-05-30T02:35:04.398Z

Agenda
Future of EOA/AA Breakout Room #3 · Issue #1053 · ethereum/pm · GitHub
Moderator: @timbeiko
Summary
Call recap by @timbeiko

We’ll be merging the PR here pretty much as-is as a v1 for 7702 which L1 teams can consider for Pectra/devnet-1: Update EIP-7702: refine based on discussions by lightclient · Pull Request #8561 · ethereum/EIPs · GitHub
In next week, same time, we’ll have another breakout call to follow up on (1) potential spec changes, (2) an ERC-standardized version of the proxy contract and (3) best practices for wallets to adopt 7702

From Eth R&D Discord
Recording
https://www.youtube.com/watch?v=0vHHhZgrJ58
Additional info
Notes by @poojaranjan: EOA/AA Breakout Room - HackMD
Berlin workshop notes by @adietrichs: Summary AA Event May 24 Berlin - HackMD
Proxy pattern idea by @matt: 7702proxy.md · GitHub
Title: PeerDAS_breakout__5__August_5_2024
Category: Protocol_Calls___happenings

Author: abcoathup
Date: 2024-08-03T02:08:54.074Z

Agenda
PeerDAS Breakout Room #5 · Issue #1114 · ethereum/pm · GitHub
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: Verkle_implementers_call__22__July_29_2024
Category: Protocol_Calls___happenings

Author: abcoathup
Date: 2024-07-30T08:30:02.752Z

Agenda
Verkle Implementers Call #22 · Issue #1119 · ethereum/pm · GitHub
Moderator: @rudolf
Notes
Notes by @rudolf
Recording
Title: ePBS_breakout__2__June_7_2024
Category: Protocol_Calls___happenings

Author: abcoathup
Date: 2024-06-07T08:06:15.969Z

Agenda
ePBS breakout room #2 · Issue #1060 · ethereum/pm · GitHub
Recording
https://youtu.be/w7Wa6oprEhQ
Notes



HackMD



ePBS breakout #2 notes - HackMD
Auction items:

Author: potuz
Date: 2024-06-07T21:26:07.079Z

Thanks a lot for posting this. Here are the notes



HackMD



ePBS breakout #2 notes - HackMD
Auction items:
Title: FOCIL_Breakout__8
Category: Protocol_Calls___happenings

Author: system
Date: 2025-04-07T13:23:48.886Z

Schedule

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

Agenda

Quick updates on FOCIL and statelessness
Presentation by Julian Ma on IncluderSelect
Presentation by Benedikt Wagner on zkFOCIL
Prysm <> Lodestart interop
“Activation Epoch” vs “Real fork” discussions

GitHub Issue
Title: RollCall__8_1_Breakout___EVM_Equivalence_on_L2__Oc
Category: Protocol_Calls___happenings

Author: abcoathup
Date: 2024-10-09T01:50:09.784Z

Agenda
RollCall #8.1 Breakout - EVM Equivalence on L2: Past, Present, Future · Issue #1171 · ethereum/pm · GitHub; moderated by @CarlBeek
Notes



HackMD



RollCall 8.1 Summary - HackMD
Recording:





Slides


docs.google.com



RollCall Breakout: EVM Equivalence on L2
EVM Equivalence on L2: Past, Present, Future RollCall Breakout #8.1 1





Recording





Rollup-geth




Introducing rollup-geth RIPs


    Hello everyone  
During RollCall #8.1, we introduced rollup-geth, a collaborative effort between the Ethereum Foundation (EF) and Nethermind to create a fork of Geth that serves as a common core for Rollups. 
Long-Term Goals

The ecosystem has expressed interest in having a common-core repository for Rollups to base their work on, which would reduce fragmentation across different EVM Rollups in terms of functionality and implementation.
Our goal is to create a Geth fork that fulfills this …

Author: Chloe
Date: 2024-10-27T17:14:55.386Z

Written summary of the call: RollCall 8.1 Summary - HackMD
Title: COUNCIL_OF_PARIS__Cat_Herders_Ring
Category: Protocol_Calls___happenings

Author: mariapaulafn
Date: 2019-03-04T18:34:55.845Z

https://hackmd.io/qNPJtohEQRWf1CeTbgLKOQ
Title: Client_testing_call__13__November_21_2024
Category: Protocol_Calls___happenings

Author: abcoathup
Date: 2024-11-22T00:53:27.216Z

Summary
Update by @parithosh (copied from Eth R&D Discord )
Pectra
pectra-devnet-4

PK is performing deposit tests on the devnet, more information here: #allcoredevs
Plan to shut down Monday unless there are objections
Mekong public testnet is live. If there are new client images to be used, please let us know. Mekong will not be updated to devnet-5 specs.
devnet-5 spec discussion as well as open PRs, we discussed adding a new field for MAX and TARGET blob counts with the _ELECTRA suffix into the spec config.yaml, to indicate the new values to be used at the fork. This would be consumed by the CL along with other EIPs to communicate the blob change to the EL.

Peerdas and EOF

Once devnet-5 spec is out, we will pin these releases for EOF/PeerDAS codebases to rebase on top of

Additional info

Summary by @Christine_dkim
https://pectra-devnet-4.ethpandaops.io/
https://mekong.ethpandaops.io/
Title: Client_testing_call__22__January_27__2025
Category: Protocol_Calls___happenings

Author: danceratopz
Date: 2025-01-27T15:45:43.986Z

Interop Testing Call (Jan 27, 2025)
Meeting Summary: Devnet 5, Devnet 6, and Related Updates
Pectra Devnet 5

Devnet-5 is finalizing successfully again after addressing key issues.

Dashboard link


Client Updates:

Erigon: Fix implemented, resolving key issues and enabling finalization.
Lodestar: Syncing is functional but block import issues persist (only 6 blobs present in blocks with more than 6).
Prysm: Issue under investigation, early stages of debugging.
Lighthouse: Debugging ongoing; no update yet.
Geth: Issue appears resolved, pending verification.
Grandine: Node resynced, debugging continues, and it is now proposing blocks.
Besu: Block processing issue identified, tracing and debugging underway.


Hive issues remain a blocker for Devnet-5 and need resolution before progressing to Devnet-6.
Decision: Continue with Devnet-5 until fixes are in place, then transition to Devnet-6.

Pectra Devnet 6

Spec: @ethpandaops/pectra-devnet-6
Timeline: Tentative release this week, dependent on client readiness and passing Hive tests.
Consensus specifications are finalized.
Execution spec test release this week, all PRs in place.
Plan:

Add Devnet-6 to Hive for clients already passing Devnet-5.
Clients that pass devnet-6 hive can then join devnet-6.
Enable MEV from the start of Devnet-6 (Bloxroute ready for testing).


Next steps: Ensure all clients address outstanding issues to meet the timeline.

PeerDAS

Updates to configuration values shared in the PeerDAS channel.
Interop testing underway, progressing well.
Lighthouse team close to PeerDAS devnet readiness, working on improvements and testing stability using Kurtosis on Kubernetes.

EOF

Preliminary testnet spec shared: EOF Testnet Plan.
Initial fuzzing with Geth, Besu, and REVM shows no errors in overnight run—indicating readiness for Osaka Devnet.
Decision: Launch EOF devnet next week following Pectra spec finalization.

Hive Updates

ethpandaops have added a github action for hive, which executes all clients in parallel, resulting in a 6x speedup and at lower cost.
Hive integration for testing Devnet-6 is a priority, as it remains a critical tool for identifying client issues.

Key Links Shared in the Call

Fork Monitor
Node Monitor GitHub Repo
Hive Testing Workflow

Next Steps

Continue debugging and fixing outstanding issues in Devnet-5.
Transition to Devnet-6 as soon as Hive tests are passed.
Plan EOF devnet launch for next week.
Ongoing PeerDAS and Kurtosis testing to ensure stability over time.

Thanks for the notes @poojaranjan!
Title: RollCall__7__September_11_2024
Category: Protocol_Calls___happenings

Author: abcoathup
Date: 2024-08-03T02:13:06.015Z

Agenda
RollCall #7 · Issue #1134 · ethereum/pm · GitHub; moderated by @adietrichs
Recording
Title: Chainlink_Hackathon
Category: Protocol_Calls___happenings

Author: hawksz
Date: 2020-08-26T00:16:57.893Z

The Chainlink project is proud to announce the Chainlink hackathon! Let’s build the next generation of universally connected smart contracts.
Totaling $40k+ in prizes, this is Chainlink’s biggest hackathon of the year. Get the opportunity to learn and work with some of the best in the business and build something stellar.
This is the window of opportunity to be apart of something great! Truffle, Loopring, DappU, Aave, Tezos, ENS, Gelato, and more are joining as some of the esteemed sponsors.
Register here
Title: Holesky_Incident_Debrief__February_26__2025
Category: Protocol_Calls___happenings

Author: timbeiko
Date: 2025-02-26T15:58:49.322Z

Holesky Incident Debrief Notes
State of Holesky

The chain is operating with limited block production on the “canonical” minority chain

Currently seeing 4-8 blocks per epoch (12-25% of expected blocks)
Goal is to reach 75% block production before coordinating mass slashings
More peers on the correct chain improves synchronization capabilities
Stable block production is critical for maintaining chain liveness



Immediate Action Items (Before ACD Meeting)


Priority: Restore Validator Operations

Focus on getting Holesky validators and full nodes back online on the correct chain
Client teams to share their latest valid versions on the ACD agenda
Instructions for validators:

Enable validators with slashing protection enabled
Use this verification method to confirm correct chain: https://gist.github.com/samcm/e2da294dab77e93ad0ee0e815580294f





Sepolia Fork Planning

So far, consensus is to proceed with Sepolia fork as scheduled, to confirm on ACDE tomorrow
Client teams to confirm their releases for the fork
Any concerns about proceeding should be raised immediately



Testing Infrastructure

EthPandaOps to begin preparations for pectra-devnet-7, which will:

Support approximately 1 million validators (comparable to mainnet)
Allow validator handoffs to staking pools, infrastructure providers, and DVT clusters
Include a faucet for manual validator deposits
Provide a platform for testing consolidations that can’t be tested on Sepolia





ACD Follow Ups


Holesky Recovery Assessment

If missed slot rate is <25%, begin coordinating controlled slashings of client team validators
If above 25%, determine steps to improve block production



Sepolia Fork Confirmation

Final decision on fork timing
Client teams to confirm release readiness



Mainnet Preparation Requirements

Discuss criteria and testing needed before mainnet fork



Slashing Strategy

Once more validators are back online, estimate how many are slasheable
Coordinate slashings in controlled batches to avoid overwhelming the network
Begin with core developer validators and Genesis validators
Process will take several weeks to reach finalization (limited by exit rate of 8 per epoch)
Validators reaching 0 balance through slashing penalties will eventually exit

Node Operator Guidance

For synced nodes: Enable validators with slashing protection ON
For unsynced nodes: Update to latest client release and resync
Important note: If validators can attest without disabling slashing protection, they likely didn’t attest to the invalid chain

Next Steps for ACDC (Following Week)

Teams to share retrospectives on the incident
Discuss long-term mitigations for similar issues
Evaluate the effectiveness of the recovery process
Plan for comprehensive testing of consolidations on devnet-7
Title: Looking_to_Hire_someone_to_help_me_write_a_technic
Category: Protocol_Calls___happenings

Author: androlo
Date: 2020-03-04T09:19:48.119Z

This is not really an Ethereum issue, but I’m looking for someone with experience in writing technical documents to help me finalize a paper. This is an opportunity for someone who is used to writing papers to earn some money on the side. I ask here because I am a big Ethereum fan, and I can’t really stand being around people who aren’t, so I want to check here before going to some agency.
The job would include a number of voice sessions taking place over a month or so, and some work in a github repo helping me to structure some text. The money will probably amount to a few thousand Euros or so. The exact details would be discussed, but it will be some kind of contractor solution with invoices and proper paperwork etc. (no payment in crypto currencies).
The paper is on mathematics, specifically on a fractal curve that is very similar to Minkowski’s ? (question mark function) and the likes. Generally it includes subjects like continuous fractions, farey sequences, stern-brocot numbers, modular groups, etc. There is no need to be an expert on any of those things though as I am mainly looking for someone to help with the writing and structuring of the document, but You should at least have taken basic college/university algebra and number theory otherwise it’s just plain weird. You also need to be able to write good english.
The scope is not entirely clear because I have been working with this on-and-off for over a year, and I have tons and tons of stuff, but since I do it mostly for fun and haven’t really had any plans on publishing it I just keep adding and removing stuff. Right now I’m reducing it significantly, and I think it would probably be best as a 20-30 page article-style doc, but this would have to be discussed as well.
If You are interested, please answer here in this thread or by sending me a message.
Thanks // Andreas
Lambda_1to200_harm954×590 52.1 KB

Author: androlo
Date: 2020-03-07T05:10:31.337Z

Forgot to mention: This request will be up for a couple of weeks and is active until I put a note here saying that someone has been hired. The work itself will take place during april-may, and it can be spaced out so that it doesn’t interfere too much with other commitments.
Title: _Ethereum_In_The_Enterprise__AMA
Category: Protocol_Calls___happenings

Author: jpitts
Date: 2020-07-28T18:01:42.576Z

Hello! Attendees of the “Ethereum In The Enterprise” virtual conference can ask questions about the community here.
Also, for the regulars here, check out the upcoming conference: https://www.conference.entethalliance.org

Author: jpitts
Date: 2020-07-30T18:08:00.226Z

Here’s a slide I realize was missing from the talk! It describes the general release process.
image1430×794 91.6 KB
Title: All_Core_Devs___Consensus__ACDC___134__May_30_2024
Category: Protocol_Calls___happenings

Author: abcoathup
Date: 2024-05-31T00:17:01.723Z

Agenda
Consensus-layer Call 134 · Issue #1050 · ethereum/pm · GitHub
Moderator: @ralexstokes
Summary
Recap by @ralexstokes:
This call was packed with various discussions around scoping the upcoming Pectra hard fork.

Began with a recap of devnet-0, which generally went really well!
Next, covered a variety of updates, extensions or modifications to the existing EIP set
Then turned to a new EIP (number 7688) to consider inclusion reflecting learnings from devnet-0
Touched on early PeerDAS devnet alongside devnet-0, which also went very well given how early the implementations are
Spent the rest of the call discussing fork scoping for Pectra

Check out the call for the full color
Many teams/contributors expressed a variety of options
Rough consensus formed around the importance of PeerDAS
To reflect an intent to include PeerDAS in Pectra, while derisking feature sets and timelines, client teams agreed to build PeerDAS as part of the Electra fork with a separate activation epoch

If PeerDAS R&D goes well, this activation epoch can simply be the Pectra fork epoch
If client teams discover difficulties with PeerDAS after implementation over the coming months, we have the option to set the PeerDAS activation epoch after the Pectra epoch (including possibly setting it so far in the future we would be able to schedule for a future hard fork)


Otherwise, we agreed to keep the existing Pectra scope as is


We didn’t quite have time to finish the discussion around EIP-7688 (stable container SSZ upgrade), which we will cover on the next call!

From Eth R&D Discord
Recording
https://www.youtube.com/live/Lrk99mKiWaU?t=286s
Transcript
pm/AllCoreDevs-CL-Meetings/Call_134.md at master · ethereum/pm · GitHub
Additional info
Notes by @Christine_dkim: Ethereum All Core Developers Consensus Call #134 Writeup | Galaxy
Title: Listing_great_initiatives_and_projects_initiated_b
Category: Protocol_Calls___happenings

Author: tomislavmamic
Date: 2019-01-31T20:05:07.611Z

Discussions happening in the forum and at gatherings have produced many great ideas and proposals since the start of Ethereum Magicians.
It would be great if we could have one list of all the projects and initiatives which had their beginning within Ethereum Magicians.
The most interesting would be active projects and initiatives, whereas activity means one or more people working on it regularly and/or substantial budget dedicated to it.
Let’s create this list for our inspiration ahead of Council of Paris.
Please, mention the project name, people running it and where/when it started with relevant links/info.

Author: tomislavmamic
Date: 2019-02-01T13:50:22.389Z

TennaGraph is the first one:
https://twitter.com/thegrifft/status/1091085680401358849
Team: @GriffGreen and @MaxSemenchuk
Funded by Aragon Nest
Presentation from AraCon 2019: https://youtu.be/DhMvMTwArXA?t=3960

Author: lrettig
Date: 2019-02-02T16:46:13.971Z

The Ethereum Cat Herders were born out of FEM: I made an announcement onstage at the Council of Prague for help with PM work and it grew organically from there.
Title: EOF_implementers_call__64__January_8__2025
Category: Protocol_Calls___happenings

Author: abcoathup
Date: 2024-12-14T01:14:12.027Z

Agenda
EOF Implementers Call #64 · Issue #1217 · ethereum/pm · GitHub
Notes




EOF implementers call #64, January 8, 2025 Protocol Calls & happenings


    Call Notes 
Testing 

Need to merge 1 PR
Fuzzing updates - execution-spec-tests/src/ethereum_fuzzer_differential/__init__.py at shemnon/eof-fuzz · shemnon/execution-spec-tests · GitHub

Client Update 

No Client Updates
Rebase off of Perctra-5

Need at least 3 for the devnet


Compiler support

Reviewed the PR list
How will small proposed changes impact?

Not too bad.
Hashing is more impactful
Need to totally nail down all changes before the experimental flag gets removed.  Flag may remain until…
  

Recording

Author: shemnon
Date: 2025-01-08T16:58:07.629Z

Call Notes
Testing

Need to merge 1 PR
Fuzzing updates - execution-spec-tests/src/ethereum_fuzzer_differential/__init__.py at shemnon/eof-fuzz · shemnon/execution-spec-tests · GitHub

Client Update

No Client Updates
Rebase off of Perctra-5

Need at least 3 for the devnet


Compiler support

Reviewed the PR list
How will small proposed changes impact?

Not too bad.
Hashing is more impactful
Need to totally nail down all changes before the experimental flag gets removed.  Flag may remain until mainnet is live (not even testnet, mainnet)


Assembly syntax for EXCHANGE opcode is still undetermined (absolute byte encoding, vs nybbles, vs stack index, all off by 1 issues)

Off by one also leaks into possible SWAP/SWAPN numbering as well (DUP/SWAP are already inconsistent)
Frangio’s summary - Assembly Syntax for EOF Stack Instructions - HackMD

Exact is Frangio’s recommendation







Spec

Metadata - EIP-7834: Separate Metadata Section for EOF

EVMONE will look into a spike


EOFCREATE/TXCREATE Hashing

Summary doc - Potential scenarios of updating the new contract address schemes for EOF - HackMD
Also pre-ERC for standard contracts Comparing ethereum:master...shemnon:eof/txcreate-factories · ethereum/ERCs · GitHub
Shipping temp check

When there are no deal-breakers
2025 seems tight
Best to tie with PeerDAS, unless there is a large differential

So the EL and CL fork major features at the same time
But PeerDAS/EOF not as tied as, say, withdrawals




Devnet-1 punch list - EOFv1 final tuning · Issue #165 · ipsilon/eof · GitHub
We need to disuss the ACCOUNTTYPE opcode - EIP-7761 - MUST/SHOULD - dealbreaker for app dev until it’s in.

is ERC-165 a viable alternative?
What would app devs accept?
Title: Stateless_Ethereum_Session___EthCC_2020___Links_to
Category: Protocol_Calls___happenings

Author: jpitts
Date: 2020-04-22T05:47:31.068Z

Stateless Ethereum - Summary
EthMagicians, EthCC 2020
Full Notes by @timbeiko / Tim Beiko

Stateless Ethereum Project Overview by Piper

Questions (with links to Answers given by those in the circle)
What are the downsides of too many stateless clients?
We say we’re not interested in stateless miners, but if there are no full nodes, how can we mine?
Do we foresee the possibility of stateless clients on their own mining blocks? 
How do we change the roadmap? What is the process to change/add to it?
It seems like there is a low hanging fruit to develop stateless contracts vs. a full stateless ethereum network. Is there an interest in doing that? 
How many full nodes do we need to keep having to have a healthy stateless client network?
How do you see the initial sync being faster?
Can we add a new JSON RPC API that requests the witness for a given block?
Could you do a full sync with witnesses faster than you can do it today? 
What do you mean about bad witnesses?
Could we enable predictable state access / access control lists on Eth1?
When do you expect the current effort to go in production? Would that be pre-”Eth1 coupled to Eth2”
Based on the current roadmap, how are contract developers affected?
How does the change from a hexary to binary trie affect witness generation?
What research needs to be done to motivate increasing gas costs ASAP? 
If stateless clients come out, does that mean the overheads for syncing the current 9-10M blocks would still apply? 
If you split the gas costs for witnesses and opcodes, could we see lower gas costs for state reads and writes?
What are the top 3 questions to answer to solve stateless clients?
Our average block is ~24kb and if we want to have 1MB blocks, how do we get there? Should we double every month until we get there? 
When talking about the size of witnesses, would it be good to be more granular about what the various parts of it, to handle the various parts differently.?
Comment: Not sure it’s wise to add a new experimental crypto to L1. Need an extra amount of effort and evidence for the proposer of this system.
How do we know this is effective? What if there are things we didn’t foresee and this lowers the TPS?
Are you soliciting reviews from the community? 
Where can people go to participate?
If there are developers that want to tackle converting the binary tree to a hexary one, what should they do?
Title: Eth_simulate_Implementers__Meeting___March_03__202
Category: Protocol_Calls___happenings

Author: system
Date: 2025-02-26T21:45:11.872Z

eth_simulate Implementers’ Meeting

Date and time in UTC March 03, 2025, 12:00 UTC
Duration in minutes: 60 minutes
Join Zoom Meeting
Recording: eth_multicall Playlist

Resources

Ideas for eth_simulateV2
PEEPanEIP#135: Eth Simulate with Oleg and Killari

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

Add more discussion items or async updates.
The next meeting is scheduled for March 10, 2025 at 12:00 UTC
GitHub Issue
Title: RollCall__8_2_Breakout___L2_EVM_Common_Core_Kickof
Category: Protocol_Calls___happenings

Author: abcoathup
Date: 2024-12-05T02:32:23.659Z

Agenda
RollCall #8.2 Breakout - L2 EVM Common Core: Kickoff · Issue #1201 · ethereum/pm · GitHub; moderated by @adietrichs
Recording
Title: Client_testing_call__24__February_10__2025
Category: Protocol_Calls___happenings

Author: parithosh
Date: 2025-02-10T17:27:56.625Z

Key Decisions & Next Steps

Going ahead with testnet Pectra forks:
Announcement in ACD channel; client teams should prepare for releases. Dates can be found here.
Tx Pool Tests:
Testing team is currently working on them.
PeerDAS:
PeerDAS-devnet-4 is now live, planning for future devnets has started.
EOF Testing:
Kurtosis-based testing now works, EEST is going to be used to trigger bugs at the start.
ePBS & IL Testing:
Proceed with standalone domain testing before considering mainnet inclusion. Kurtosis integration is complete.

Devnet 6 Updates
Devnet 6

~95% participation rate, stable devnet with no large unknown issues
MEV relay of flashbots still has a validation issue, that’s being fixed soon.
Lighthouse noticed a kzg verification edge case that they are trying to triage.
Prysm fixed a cache issue last week.
Kurtosis is updated; most clients are passing all the Hive tests.

Testnet Pectra fork

All clients present confirmed going ahead with the testnet release. The other clients will chime in on discord.

PeerDAS

PeerDAS Devnet 4 is live and stable so far.
Out-of-memory bug in Prysm; PeerDAS test scheduled for tomorrow.
Full focus after Pectra completion. Hence the planning of devnet-5 has already stared.
Peerdas devnet 5 spec 
Note: The breakout room has been moved to be weekly instead of once every two weeks.

EOF Testing

Kurtosis integration is complete, 3 client devnets can now be locally spun up
EEST is being used to trigger bugs in the local devnet, some changes are required and will be discussed with the testing team.

ePBS & Inclusion List (IL) Testing

Standalone domain testing for IL & ePBS is ongoing.
Title: ERC_1155___Soon_to_be_finalized__but_one_remaining
Category: Protocol_Calls___happenings

Author: jpitts
Date: 2019-04-12T18:36:41.058Z

This was Tweeted today by @PhABC:

ERC-1155 is soon to be finalized, but one remaining contentious point concerns existing smart contract wallet and the general problem of smart wallets supporting future standards.

https://github.com/ethereum/EIPs/issues/1155

Author: jpitts
Date: 2019-06-18T07:20:48.555Z

I assume that they worked out this one remaining point.
So, ERC-1155 is final, yay! 
https://blog.enjincoin.io/erc-1155-the-final-token-standard-on-ethereum-a83fce9f5714

Author: Amxx
Date: 2019-06-18T09:13:24.831Z

jpitts:

the general problem of smart wallets supporting future standards


This is not a problem with tokens standards, it’s a problem with smart wallets not being upgradeable. Once you provide a smart wallet with upgradeability mechanisms, this is no longer an issue.
Title: The_Fellowship_of_Ethereum_Magicians_1st_Workshop_
Category: Protocol_Calls___happenings

Author: jdetychey
Date: 2018-04-13T11:00:25.545Z

The recording was a not as smooth as the rest of the conference sorry for that

Author: jpitts
Date: 2018-04-13T23:18:05.798Z

Thanks for posting. It is great to have this online now!

Author: gregc
Date: 2018-04-22T16:44:49.266Z

Thanks, Jerome…!