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

Author: abcoathup
Date: 2024-09-17T10:32:18.828Z

Summary
Update by @parithosh (from Eth R&D Discord )
pectra:

pectra-devnet-3 is live! Find details here: https://pectra-devnet-3.ethpandaops.io/
Nethermind, lodestar, erigon bugs have been patched, network is at ~92% participation
EthereumJS is having issues, Are clients providing requestBytes as an array as per EIP-7685? info here: ⁠devnet-3 issues (EthereumJS)⁠
We need someone to update the builder-specs such that we can have client teams start/work on implementations: GitHub - ethereum/builder-specs: Specification for the external block builders.
Remote signer API needs updating for pectra as well, is someone working on this: GitHub - ethereum/remote-signing-api: This repository outlines standard remote signing application programming interface (APIs) for communication between remote signers and Ethereum validator clients. Remote signing service allows validator clients to offload signing of validation duties (e.g Attestations, BeaconBlocks) by managing security, slashing protection, and key management., info here: ⁠apis⁠

eof :

Testing is going well and more clients are achieving readiness for a devnet
Devnet would depend on fork split decision, likely at ACD this week
We’d do interleaved devnets, so eof-devnet-0… and a decision needs to be made if its done as prague or as osaka
We’d need to be careful not to trigger the same bugs as pectra devnets to reduce debugging overhead. One approach would be to remove the faucet (we plan this for peerDAS), but the downside is that EOF would benefit a lot from public testing

peerDAS :

Update on local devnet and its issues
Lodestar endianness bug
Public devnets once local issues are triaged
Devnet cycle would depend on fork split decision made likely during ACD this week

fuzzing :

Marius would focus on pectra fuzzing and bad block generators (also open call for other clients to implement this and take some load off of him/speed up the fork)

general :

We had a brief temp check on fork splitting and what open tasks that would make shipping quickly a blocker
Title: Join_4th_AllERCDevs_tomorrow_6_29_UTC1500
Category: Protocol_Calls___happenings

Author: xinbenlv
Date: 2023-06-29T06:16:13.744Z

See the github issue for information: [Past] 4th AllERCDevs Agenda (EU / US Friendly) Thursday, 2023-06-29 15:00 UTC · Issue #5 · ercref/AllERCDevs · GitHub
The time of event will be
2023-06-29 UTC 1500-1559 Thursday, find your timezone here
The event will be hosted on Zoom, a link will be posted on “all-erc-devs” channel on this Discord Server
Agenda will be updated and please feel free to comment to signup your agenda items.
Agenda
Main Session (1h)

 (15-20min) Featured Talk:


ERC-1363 Payable Tokens by @vittominacori


(10min) Demo Show & Tell (5-10min per slot)


https://chainrelay.com/ and ethereum-contracts/ERC-721 at main · chain-names/ethereum-contracts · GitHub by @evbots


(30min) ERC Peer Review Requests (5-10min per slot)


TCTC by @kofujimura


Special Topic


ERC to be removed from EIP, your feedback?
Any interest in signing up for peer reviewer?

Social Chat for ERCers
What do you find interesting last week? It doesn’t have to be related to ERC.
Meeting Link
Zoom Meeting Link: Launch Meeting - Zoom
Meeting ID: 886 9452 9887
Passcode: 338406
Notes
Summary
Full Transcription
Title: Pop_up_sessions_in_Berlin_today_and_Friday___stick
Category: Protocol_Calls___happenings

Author: ligi
Date: 2018-12-05T09:42:46.807Z

Will meet with @rmeissner today discussing: Add `wallet_` methods to improve dapp to wallet interaction and EIP-695: Create `eth_chainId` method for JSON-RPC - #3 by pedrouid - if someone wants to join this discussion please let us know.
Friday will be the Ethereum Meetup Berlin so we could also do some small pop up sessions in this context.
To both occasions I will bring these stickers:
ethmagicians4000×2250 3.14 MB
If you want some just ask. And if you are going to ETHDenver it would be great if you could take a batch of them to pass them on to @c-o-l-o-r

Author: ligi
Date: 2018-12-05T17:51:40.674Z

Outcomes of this session:
regardng the wallet_ rpc methods:

there needs to be a wallet_version RPC call which returns the version of the wallet_ rpc methods that it supports - should be “1.0.0” after for the first EIP
the EIP should not contain javascript code as examples but the rpc-calls/responses
wallet_sendTransactions vs wallet_signTransaction gets complicated when it comes to contract wallets - the solution that looked best to us in the end is wallet_handleTransaction(transaction,chainId,listOf(allowedMethods)) where allowedMethods in the simplest case is [“sign”] → would return the signed Transaction , also quite simple [“send”] → would send the transaction and return the transaction hash - it get’s a bit messy when it comes to contract wallets - we both did not yet have a clear vision here - input on this is very welcome!

other outcomes:
https://github.com/gnosis/svalinn-kotlin/issues/29
@rmeissner let me know if i forgot something or got anything wrong - I also forgot one thing that I had on the agenda in my mind - I think " Possible Future Methods" should be removed from the EIP - let’s discuss these outside the EIP scope and create an EIP with them when the time is ripe. With the wallet_version call we should have a clear upgrade path for this in the future.
Title: Asking_for_a_bit_of_guidance
Category: Protocol_Calls___happenings

Author: wschwab
Date: 2018-10-16T06:14:12.210Z

Hello all. I apologize if this has been covered before, but I didn’t find a relevant thread.
I’ve been following the Magicians since the creation of the group. I’m interested in governance topics, and have participated online in various conversations around it. When I saw there would be a gathering before Devcon, I jumped on the bandwagon. My main question now, is now what? I see that there are subdivisions by different interestes (the rings), but I’m sort of lost about what to expect, or what I can do/participate in. Should I necessarily be looking for a ring to join? Should I just be showing up and winging it?
Thanks!

Author: fubuloubu
Date: 2018-10-16T13:27:18.528Z

No worries, we’re all (mostly) winging it!
Coming to the event is a good starter. Participating in the forum is also great. Congratulations, you are a Magician!
We will be going over what the Rings mean at the Gathering. It’s still a very fluid process, so it will by no means be “the law”, but it will be good guidance to move forward and Do The Thing™
You can be a member of any amount of rings (including zero!) and still be a “Magician”. It’s more a signaling sub-group related to your interests. Some (like Tokens) may be more technically focused on EIPs than others (like Governance). You can get involved as little or as much as you want. We only ask that you contribute positively towards the goals the groups set.
If you are interested in volunteering at the Gathering, we have a recurring call on Wednesdays. I’m not sure where the post is, @boris can give you those details if you wish to join. We’d love to have ya!
Title: Ethereum_participation_at_FOSDEM___February_2___3_
Category: Protocol_Calls___happenings

Author: boris
Date: 2018-09-20T17:37:25.536Z

I submitted a request for a FOSDEM dev room, along with @bobsummerwill as the second contact.
Here are the details of what I submitted:



HackMD



FOSDEM Devroom Submission - HackMD





Yes, we are currently working on Council of Prague organizing and I’m already thinking about the next one, but the deadline was today so I had to submit something.
If you’re interested in being involved, leave a note here.

Author: ChainSafe
Date: 2018-09-21T15:33:16.774Z

Really cool @boris! I would love to be involved however I can.

Author: boris
Date: 2018-09-21T16:39:27.596Z

Awesome! Add yourself to the HackMD. We can talk about this in Vancouver next week and at Prague.
But first, Prague

Author: ChainSafe
Date: 2018-09-21T18:41:25.330Z

Awesome, looking forward to it!

Author: bobsummerwill
Date: 2018-09-22T07:35:23.245Z

Thanks, Boris!   Much appreciated.

Author: kirushik
Date: 2018-09-26T23:58:57.469Z

Oh, cool!
Please count me in, I’d like to help with organization (added myself into the HackMD doc).

Author: kirushik
Date: 2018-10-16T13:50:33.728Z

OK, looks like DevRooms have been selected: https://fosdem.org/2019/news/2018-10-14-accepted-developer-rooms/
There are “Decentralized Internet and Privacy” (on Saturday) and “Blockchain” (on Sunday) — do we know anyone from there? Any plans to get in touch and collaborate?

Author: mratsim
Date: 2018-11-12T09:34:54.416Z

Hey there, this is my first post here so not too sure how the fellowship is organised.
I’m part of the Status dev team and most (all?) Nimbus team will be there. At first it was for the Nim programming language but we would also be very happy to help or contribute privacy/decentralization/blockchain/eth talks at Fosdem.

Author: bobsummerwill
Date: 2018-11-13T00:25:41.489Z

Here is the Call for Proposals, open for the next few weeks.  I will be there.  I have booked my flights.
https://lists.fosdem.org/pipermail/fosdem/2018q4/002778.html

Author: ChainSafe
Date: 2018-11-13T16:51:26.537Z

I am also planning on attending, I just submitted a proposal for a lightning talk called the current and future state of Ethereum.
Title: Verkle_implementers_call__18__June_3_2024
Category: Protocol_Calls___happenings

Author: abcoathup
Date: 2024-06-06T09:44:35.622Z

Agenda
Verkle Implementers Call #18 · Issue #1027 · ethereum/pm · GitHub
Moderator: @rudolf
Notes
https://x.com/rudolf6_/status/1798557660905902393
Recording
Title: EOF_Implementers_call__58__September_18_2024
Category: Protocol_Calls___happenings

Author: abcoathup
Date: 2024-09-20T09:59:19.261Z

Agenda
EOF Implementers Call #58 · Issue #1146 · ethereum/pm · GitHub
Notes
Notes by @shemnon [Copied from ethereum/pm]

Client Discussion
Discussed Split

pt 2 should follow w/in 3-6 months
mild preference for one merge, but not enough to block
concern about scope creep and moving actual shipment to 1 year


Compiler Updates

None


Specs

Tracing

evmone will look into implementing, but may have changes to proposle


HASCODE/ISCONTRACT

Discussed AA concern in discord

AA is concerned about the pattern where non-eoa accounts are barred, HASCODE could be used to perpetuate that and slow AA adoption
Also, 721 could be solved better with ERC-165 interface
counter: AA is slowed by lack of smart contract signatures
counter: Banning EOAs possible w/o HASCODE
No conclusion yet


Could pectra split allow it to be added in V1?

Some preference to be in a follow-on fork, but preference may have been driven by time to gather data
Split is because of EIP bloat, adding a new EIP would counter the solution
At least 1 client wants to include it for V1

Absence could slow adoption of EOF (Any ERC-721/ERC-1155 or flashloan project for example)


There is concern that 721 and 1155 are badly designed, and so this pattern won’t re-occur. An update of 721 could provide the same protections and conform to modern practices.
AA accounts could implement 165, but then they would have to have the 721 callbacks active.
See note below about EXTDELEGATE and proxies


EXTCALL return codes

intent
1 - gas was not burned as part of the violation

User reverts
Some failures related to call process


2 - all gas consumed as part of the failure

Out of gas
RETURNDATA copy oob in legacy
static call violation
data stack overflow


No action today


Allow EXTDELEGATECALL to legacy

This is another use case for HASCODE, to ensure EOF proxies won’t delegate to a legacy contract

This could be solved with a “handshake” method or a trial delegate call








Testing

PRs will be reviewed
7702 testing

many clients were rejecting incorrectly
execute mode in EEST can address this problem - uses JSON-RPC only to interact with node




Bikeshedding

Can we rename types to stack-io in the spec? types was not terribly clear.

stack-io
section-info or section-spec
code-info
signature(s)




Standing agenda should move testing to the first items
Title: Future_of_EOA_AA_breakout__4__June_5_2024
Category: Protocol_Calls___happenings

Author: abcoathup
Date: 2024-05-30T02:57:19.216Z

Agenda
Future of EOA/AA Breakout Room #4 · Issue #1054 · ethereum/pm · GitHub
Moderator: @timbeiko
Recording
https://www.youtube.com/watch?v=gsc_yTdHRig&t=5s
Additional info
@rmeissner: 7702 Best Practices - HackMD
Previous breakout: Future of EOA/AA breakout #3, May 29 2024
Title: ePBS_breakout__9__September_13_2024
Category: Protocol_Calls___happenings

Author: abcoathup
Date: 2024-09-12T01:42:58.029Z

Agenda
EIP-7732 breakout room #9 · Issue #1150 · ethereum/pm · GitHub
Notes
Notes by @terence [copied from X]

Julian presented an argument that slot auction gives an out-of-protocol trusted advantage by running an MEV-Boost auction at the execution stage
Mark presented new engine API methods for retrieving payloads
We talked about whether withdrawals could be on executions and what the blocker for this is




HackMD



EIP-7732(ePBS) Breakout #9 Notes - HackMD
Julian presented a new argument against slot auctions, stating that slot auctions give off-protocol a clear advantage over on-protocol. The new argument can be summarized as follows. A proposer is better off doing the following:





Recap by @potuz [copied from Eth R&D Discord]

@JulianMa presented an analysis pretty much showing that on slot auctions there’s a “trusted advantage” that does not seem to be possible to avoid. This seems like a serious problem on slot auctions and it’d be nice to weigh against the known problems of block auctions. We decided to keep building on block auctions for the time being cause it’s an easy switch to slot auctions if they are decided later.
@ethDreamer proposed a new method in the Engine API to requests payloads by range. We agreed that it was sensible to have this method. I raised that we shouldn’t even need to have the payload to sync. Would like to talk to @m.kalinin about this, Perhaps we can schedule an informal call Misha? I think once the requests are sent outside of the payload and the block is hashed as SSZ, we should not need to get the payloads ever on the CL, and would only need to have the payload HTR.
@terence proposed that we moved the processing of withdrawals to the execution phase. Mark seemed to strongly prefer it, I don’t oppose it and even like it, but acknowledge that it’s different on the beacon chain and would want someone else besides me vouching for it. We decided to requests here for signals from teams if they rather want to move this to the EL payload processing.

Recording





Additional Info


docs.google.com



ePBS Breakout Call #9 - Trusted Advantage in Slot Auctions
Trusted Advantage in Slot Auctions Julian Ma Robust Incentives Group @ EF
Title: Notes_from_Ethereum_Magicians_session_in_Denver_20
Category: Protocol_Calls___happenings

Author: chaals
Date: 2023-03-02T18:01:24.865Z

I’m taking notes in hackmd
(They are messy, please help clean up…)

Author: abcoathup
Date: 2023-03-03T03:24:38.842Z

I get 403 forbidden when trying to access the notes.

Author: chaals
Date: 2023-03-06T15:31:00.810Z

Sorry, they should be available now.

Author: ligi
Date: 2023-03-07T07:07:28.448Z

Thanks for taking notes - much appreciated!

Author: toledoroy
Date: 2023-03-08T17:57:48.938Z

Thanks for sharing!
The entry barrier for new developers is definitely a big issue. Marketing voices are much louder than developer voices and that can steer the entire field off track. I wish I had a solution, but even if I did, I could not market it
Title: Beam_call__4__exit_queue____April_18__2025
Category: Protocol_Calls___happenings

Author: system
Date: 2025-04-10T16:00:25.502Z

beam chain call 04, April 18, 2025

April 18, 2025, 14:00-15:00 UTC
Duration in minutes : 60

Agenda




Agenda Item
Topic
Link




01
beam chain social updates by @justindrake
link


02
Minslack: Proposal to Add Flexibility to Ethereum’s Exit Queue by @michaelneuder and Mallesh Pai
link



Facilitator email: ladislaus@ethereum.org // will@ethereum.org
Facilitator telegram: @ladislaus0x // @corcoranwill
GitHub Issue
Title: RollCall__9_1_breakout___L2_execution_common_core_
Category: Protocol_Calls___happenings

Author: abcoathup
Date: 2024-12-14T01:07:48.835Z

Agenda
RollCall #9.1 Breakout - L2 Execution Common Core: V1 Scope · Issue #1215 · ethereum/pm · GitHub; moderated by @adietrichs
Title: Council_of_Paris__Education_ring_notes
Category: Protocol_Calls___happenings

Author: mariapaulafn
Date: 2019-03-04T18:26:21.348Z

HackMD



Education Ring - Council of Paris 2019 - HackMD
# Education Ring - Council of Paris 2019  ## Topics * Standards, Material Quality & Certification *

Author: mariapaulafn
Date: 2019-03-05T21:48:23.321Z

Elias’ notes (ill integrate in main doc after this week) https://hackmd.io/k166XmT8S5ysdHA_uXM02g#
Title: Future_of_EOA_AA_breakout__5__June_26_2024
Category: Protocol_Calls___happenings

Author: abcoathup
Date: 2024-06-27T03:44:15.890Z

Agenda
Future of EOA/AA Breakout Room #5 · Issue #1081 · ethereum/pm · GitHub
Notes
@poojaranjan: EOA/AA Breakout Room - HackMD
Recording
https://www.youtube.com/watch?v=_S01TtA3lao
Title: Ring_Maker_Toolkit__making_meaningful_gatherings
Category: Protocol_Calls___happenings

Author: tomislavmamic
Date: 2018-10-21T08:10:06.771Z

Dear ring leaders,
one of the things left for all of us to discuss is how to prepare and facilitate your ring gatherings for them to be as productive and impactful as possible.
The questions we ask ourselves are:

What do we want to achieve with our ring gatherins?
How do we achieve this?
What are expected outputs of our ring gathering?
How do we ensure those who are not present also get the outcomes?
How do we make our ring gatherings as efficient as possible?
…

We have started a draft document with key definitions and examples we can use: https://hackmd.io/s/SkamYQ85X
You are invited to contribute with your suggestions to the document and to discuss this on the call this week:
Tuesday 23.10.2018. 16:30 CEST (hangouts link)

Author: tomislavmamic
Date: 2018-10-24T21:01:52.109Z

As agreed on the last call, I have created draft documents of session outlines for facilitators to fill out. The reason why we do this is because these are working groups and should produce some concrete outputs and achieve some outcomes. It’s not just knowledge sharing. However you planned to achieve this, it would be appreciated if you described in this format.

Education
Wallet
Signaling
Fund Recovery
Meta Magician
Security
Token
Business Model
Subscriptions
Oracle
Data
Trust & Reputation
EIPs & Interoperability
Architects

Author: jpitts
Date: 2018-10-25T22:25:38.025Z

This is great, thanks for putting these together!

Author: tomislavmamic
Date: 2018-10-26T07:54:17.591Z

Nop probs, just let me know if you need help!
I am coming to Prague today so I can even meet anyone who wants me to help them do it right.

Author: tomislavmamic
Date: 2018-10-26T08:03:47.166Z

Hi all, @apitkevich made some great work with Architects Ring session outline, you can check it out for inspiration.
I am pasting here what I told them about Outputs:
For outputs, I would suggest you prepare the format in advance. This way it will be easier for participants to understand what they need to produce. It’s much easier filling in the existing format than coming up with the format and then filling it up, all during the workshop.
It seems HackMD or google docs are standard so you can use these, when you create the template, you can just add the link to the list of session outputs.

Author: chisel
Date: 2018-10-26T12:38:31.400Z

Thanks so much for this @tomislavmamic - I’m going to write up a general attendance feedback form in the next day or so that we can send out to all attendees afterwards. I’ll look over what you’ve crafted here as well and see if I can contribute any thoughts 
We are here at Status venue if you are around and want to have an idea jam session-- looks like we’ll be having an informal planning meeting sometime tomorrow, will post the specific time when we determine it.

Author: mariapaulafn
Date: 2018-10-27T15:10:33.794Z

Ring preparation guidelines. We will host a session to guide people through the ring making process https://hackmd.io/s/SksgelMn7
Title: History_Expiry_Breakout___April_8th_2025
Category: Protocol_Calls___happenings

Author: system
Date: 2025-04-03T17:50:29.084Z

History Expiry Breakout - April 8th 2025

April 8, 2025, 14:00 UTC
Duration in minutes : 60 minutes
Zoom link will be posted in Eth R&D#history-expiry prior to the call

Agenda

eth/69 protocol finalization
review meta-EIP
Update EIP-7801: Update 7801 to accomodate era1 file format storage and serving by smartprogrammer93 · Pull Request #9331 · ethereum/EIPs · GitHub  - Update to 7801 related to era file formats

GitHub Issue

Author: pipermerriam
Date: 2025-04-08T14:56:21.462Z

History Expiry Breakout Call Notes
eth/69 should be updated as follows:  Agreement on the call from Besu, Geth, Nethermind, and Reth.

Status message should be updated to include earliestBlock and latestBlock.  This is to allow clients to more efficiently avoid connecting to clients that do not have useful block data.
New “announcement” style message added to protocol that includes earliestBlock and latestBlock.  This message should be sent once per epoch.  It was agreed that this announcement style message was preferable to a request/response to avoid polling patterns in client implementations.

The justification for earliestBlock addition is so that clients can communicate the beginning of the history range they can serve from locally available data.
The justification for latestBlock is from multiple reasons.

To allow full sync clients to communicate the status of their sync
To provide a signaling mechanism that indicates participation in the protocol.

A modification to 7801 to change the storage ranges to align with Era file ranges was highlighted: Update EIP-7801: Update 7801 to accomodate era1 file format storage and serving by smartprogrammer93 · Pull Request #9331 · ethereum/EIPs · GitHub
Piper (me) requested feedback on the History Expiry Meta EIP: Add EIP: History Expiry Meta by pipermerriam · Pull Request #9572 · ethereum/EIPs · GitHub
Title: Eth_simulate_Implementers__Meeting___April_07__202
Category: Protocol_Calls___happenings

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

eth_simulate Implementers’ Meeting

Date and time in UTC April 07, 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: Client_testing_call__26__February_24__2025
Category: Protocol_Calls___happenings

Author: abcoathup
Date: 2025-02-24T20:27:54.538Z

Testing Call 24/Feb/2025
Notes by @marioevz (Copied from Eth R&D Discord)
MEV:

Flashbots identified an issue and are working on a fix, aiming for Holesky.
Prysm and Nimbus are progressing on SSZ & Builder API : ⁠Builder workflow with SSZ⁠
MEV Tests are using local devnets using kurtosis.

Pectra Mainnet Shadow Fork

No progress: Clients could not be synced due to infrastructure issues.
There was an issue getting mainnet data to the nodes.
Rafael started working on a fix.
Expected to be resolved today or tomorrow.

Client updates on Pectra
Erigon, Geth, Teku

No updates.

Nethermind

Marek: still everything good.

Besu

Daniel: still everything good with the release.

Reth

Roman: Local nodes updated, no major issues.

Prysm

James: Looking to merge Decompose Electra block attestations by rkapka · Pull Request #14896 · prysmaticlabs/prysm · GitHub, which is one of the attestation related items. The solution is still being reviewed.

Grandine

Saulius: A few small fixes, might wait for a few days for a release, but nothing major.

Lighthouse

Pawan: Lighthouse is still on 7.0.0-beta.0 for holesky.

Lodestar

Potential hot-fix for an issue caught during gnosis testing, which is also relevant for holesky.
Issue was not caught by local testing.
Issue related to compounding of a validator that is being loaded from DB, and only happens during proposals.
fix: ensure new withdrawalCredentials in switchToCompoundingValidator() by twoeths · Pull Request #7478 · ChainSafe/lodestar · GitHub
Nethermind team could share the details regarding the test case that triggers the issue.

PeerDAS

Rafael: Devnet-5, same spec as Devnet-4 and is basically a relaunch, which fixed the client versions issues that caused the problem in Devnet-4.
Devnet 5 Tooling: PeerDAS Dashboard

EOF

Danno: Devnet-0 is a success
3+ clients in sync in the Devnet-0.
Reth fell out for a bit but caught up afterwards.
Devnet-1 will contain all EIP changes, and will be longer lived than Devnet-0 to allow public access to deploy and test EOF contracts.
Evmone will have a proof-of-concept for TXCREATE over the next couple of weeks, which will allow EEST to fill tests and make fixes.
Rafael: Suggested having a hive dashboard for the status of the clients passing EOF tests.
Requires an EOF EEST release. Mario will work on this.
Title: Verkle_implementers_call__19__June_17_2024
Category: Protocol_Calls___happenings

Author: abcoathup
Date: 2024-06-14T22:31:02.926Z

Agenda
Verkle Implementers Call #19 · Issue #1064 · ethereum/pm · GitHub
Moderator: @rudolf
Notes
@rudolf Twitter notes
Recording





Additional info
Preimage distribution: Preimages generation & distribution strategy - HackMD
Title: Prague_Volunteers_Kick_off_call
Category: Protocol_Calls___happenings

Author: boris
Date: 2018-09-05T16:21:20.580Z

Thanks to everyone that joined us on the call today! Here are the notes EthMagicians Prague Volunteer Call Notes - HackMD
Will transcribe some of these into action items into this post after I get to the office, please use comments and PMs to self organize.
@jpitts can create a Prague Volunteers Discourse group for us and we can see if that works as a mini mailing list.
I will start a separate thread about the Status EIPs & Interoperability organizing.
Contact me directly through my profile: Profile - boris - Fellowship of Ethereum Magicians
Key Resources
Registration

Event Organizer: Become an Event Hosting Legend | Eventbrite
We’re at about ~110 right now

Agenda Wiki

Council of Prague Agenda · ethereum-magicians/scrolls Wiki · GitHub
overall skeleton, including details on sponsorship – just updated this, still need to add link to budget / sponsorship grid
if other tools (e.g. HackMD, GSheet, whatever) end up being more fluid for managing this, go for it

Event Page & Updates

https://ethereumevents.global/events/2018-council-of-prague/
Maintained by Boris, pull requests and other edits welcome via Github GitHub - spadebuilders/ethereum-events: Ethereum Community Events
Title: IETFians_to_help_guide_FEM_
Category: Protocol_Calls___happenings

Author: virgil
Date: 2018-10-29T09:44:31.607Z

At the FEM Prague meeting, @gregc mentioned how instead of the FEM joining IETF, some within the IETF wish they could be more like the FEM.
This seems an immense opportunity.  Can the FEMians ping their IETF contacts to chime in on their respective interests in the FEM—I’d like to hear from any of them what they think IETF can bring into the FEM.
On the FEM side, it would be a great win if we could get some long-term IETF handlers to assist in crafting/guiding the FEM policies and practices.
Title: EIP_Day_at_ETHDenver_2024
Category: Protocol_Calls___happenings

Author: anett
Date: 2024-02-01T07:18:15.650Z

Hello, fellow Ethereum Magicians! 
The Ops Team is back in event-hosting mode!!
Join us for EIP Day to raise awareness about EIPs, ERCs, and the improvement process and discuss how to support the development of Ethereum!
image642×646 32.8 KB
Session details!
Date: Feb 29th
Time: 10am → 2pm
Address: Denver Rino - full address available upon confirmation on Lu.ma
Tickets: Available on lu.ma. More will be released prior the event. Limited capacity - first come first serve
Coffee and refreshments will be provided courtesy of Namefi! 
POAP from this event will be claimable onsite !
Just remember, it is always better to come earlier than later as our event is oversubscribed and we are not able to expand the venue capacity 
Talks!
We will give a brief introduction to EIPs
@poojaranjan will be chatting about the EIP process and coordination from the Ethereum Cat Herders side
@ralexstokes will share his thoughts on EIPs from a core dev perspective
@bumblefudge will present the wallet working group and EIP-6963.
@yoavw will be speaking about Block level warming
EIP/ERC/RIP authors! Sign up on site
We will have sign-up for lightning talks onsite, where attendees can talk about EIPs they are working on or have contributed to and have a discussion. Prepare to present your EIP! We will provide you with a USB-C & HDMI cable to plug your laptop in if you want to show us the code!
The EIP Lightning Talks will follow a 10-minute format of:

About EIP/ERC
High-level and critical details
Discussion

Due to the overwhelming number of registrations, we will do dedicated blocks for themed EIPs/ERCs/RIPs. We will announce more details later this week!
Rough Schedule:
image900×513 59.6 KB
The schedule is subject to change
The event will be held in person only. Remote participation is not possible due to administration constraints.
Thank you to @icedcool, @uttam, @alextnetto.eth , @danimim for co-organising, help and contributions to make this event happen 
This post is subject to be updated or changed over time with more accurate information.
Relevant thread: ETH Denver 2024 Rollcall - #19 by bumblefudge

Author: danimim
Date: 2024-02-01T19:30:22.253Z

Count on me Anett, thank you!

Author: ajbealETH
Date: 2024-02-08T17:49:14.076Z

Assuming RIPs are welcome during the EIP Lightening talks, correct? We just proposed RIP-7614 and would like to briefly present.

Author: ajbealETH
Date: 2024-02-20T18:38:05.251Z

@anett any more details on the agenda/format for the “dedicated blocks for themed EIPs/ERCs/RIPs”?

Author: anett
Date: 2024-02-21T17:59:13.501Z

We are finalizing agenda today! Will update the schedule by EOD

Author: chuboyu
Date: 2024-02-21T20:44:11.258Z

Hi @anett Is the event still having capacity? I would really love to have the chance to meet everyone in person but is still in the waitlist. Thanks

Author: anett
Date: 2024-02-23T21:47:16.674Z

Hi @chuboyu we are still approving registrations! The venue has a limited capacity.
Title: Verkle_implementers_call__21__July_15_2024
Category: Protocol_Calls___happenings

Author: abcoathup
Date: 2024-07-16T13:01:34.772Z

Agenda
Verkle Implementers Call #21 · Issue #1092 · ethereum/pm · GitHub
2024-07-15T15:00:00Z
Moderator: @rudolf
Notes
Notes by @rudolf
Recording
Title: Call_for_agenda_signup_for_2nd_AllERCDevs__EU_US_F
Category: Protocol_Calls___happenings

Author: xinbenlv
Date: 2023-05-25T23:27:20.955Z

Hi all, you are invited to join the 2nd AllERCDevs on June 1st UTC1500
AllERCDevs is a regular meeting for ERC authors and contributors as well as dApp builders to come together to collaborate and advance open standardization.
Signup the agenda here: Agenda for 2nd AllERCDevs (EU/US Friendly) 2023-06-01 UTC1500 · Issue #2 · ercref/AllERCDevs · GitHub

Author: xinbenlv
Date: 2023-06-01T04:28:56.231Z

Link Tomorrow
Zoom Meeting Link: Launch Meeting - Zoom
Meeting ID: 886 9452 9887
Passcode: 338406

Author: xinbenlv
Date: 2023-06-01T04:29:12.876Z

Agenda snapshot
A placeholder for signing up the agenda for second session of AllERCDevs
The time of event will be


2023-06-01 UTC 1500-1559 Thursday*, which translates to


08:00-08:59 on 2023-06-01 Thursday in US Pacific Time.


11:00-11:59 on 2023-06-01 Thursday in US Eastern Time.


23:00-23:59 on 2023-06-01 Thursday in Singapore.


The event will be hosted on Zoom, a link will be posted on “all-erc-devs” channel on this Discord Server
Agenda will be updated and please feel free to comment to signup your agenda items.

Agenda

Main Session (1h)

[ ] (15-20min) Featured Talk:  Wallet Test Framework(WTF) by @SamWilsn

(10min) Demo Show & Tell (5-10min per slot)


[ ] (5m)HexLink by @pette1999

[ ] (5m)TurboETH by @kamescg



(30min) ERC Peer Review Requests (5-10min per slot)


TBD: (5-10min) EIP6982 Efficient Default Lockable NFTs and EIP6454 by @sullof

(5-10min) Add EIP: Social Recovery Interface by johnz1019 · Pull Request #7093 · ethereum/EIPs · GitHub by @odysseus0





Social Hour (30m)

TODO decide social hour topics

Please feel free to signup the agenda slot by commenting Below.

Author: xinbenlv
Date: 2023-06-01T16:07:53.971Z

Thanks for coming today. Recordings will be shared soon. And before that feel free to view the
AI Generated Notes by Airgram.io: Airgram | AI Assistant for Zoom, GMeet and MS Teams Meetings
AI Generated Notes by Fireflies.ai: https://app.fireflies.ai/view/AllERCDevs-EU-US-time-friendly-session-::Ep4E220xTz

Author: sullof
Date: 2023-06-01T17:37:47.028Z

Hey, I am sorry I missed it again, but the meeting was supposed to happen early this morning for me. I saw the notification only later. We need more planning. Can we use a shared Google Calendar or something similar?

Author: xinbenlv
Date: 2023-06-04T23:24:54.535Z

No worries @sullof. Feel free to signup for the 3rd one! You could also subscribe to https://calendar.google.com/calendar/u/0?cid=bW11cXExdnU0ZjF1ZHZlMDkzYXJ0Y3VpdDBAZ3JvdXAuY2FsZW5kYXIuZ29vZ2xlLmNvbQ
You could also fill in this form with your email and I can add you to the calendar invite manually too. Interest for AllERCDevs
Title: L2_Interop_Working_Group_Call__8___April_30__2025
Category: Protocol_Calls___happenings

Author: system
Date: 2025-04-29T16:32:11.362Z

Meeting Info

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

Agenda

Chain-specific addresses aka “Interoperable addresses” (ERC-7828 and ERC-7930)

Here’s a Notion page with a quick overview of the history of chain-specific address work, and where we are today. Recommend reading if you want to get up to speed in about 10 min or less 



have something for the agenda? add comment below or DM @rudolf6 on TG
GitHub Issue
Title: EIP_Editing_Office_Hour_Meeting_59__EIP_ERC____Apr
Category: Protocol_Calls___happenings

Author: system
Date: 2025-04-16T19:45:14.423Z

Date & Time
Tuesday, April 29, 2025 at 16:00 UTC
Info

Zoom: Protocol Calendar on EthCatHerders Discord eip-editors
Recording: Playlist
Editor: @samWilsn
Facilitator: @poojaranjan

Related Resources


EIP-1: EIP Purpose and Guidelines
RIP-7810: RIP Purpose and Guidelines
EIP-5069: EIP Editor Handbook
Sam’s Rules for EIPs
EIP Editors’ Onboarding
EIP editor “apprentice” handbook
EIP Reviewers: Permissions, requirements, roles & responsibilities
Workshop Presentation
EIP Reviewers: Survey & Contribution Report
EIP Editors’ Workshop video
EIP Reviewing Interest Form
Office Hour Announcement Blogpost
-
Agenda

Visit Ethereum Improvement Proposals

To Final
TBA
To Last Call
ERCs

 Update ERC-7837: Move to Last Call by jamesavechives · Pull Request #1010 · ethereum/ERCs · GitHub
 Update ERC-7631: Move to Last Call by Vectorized · Pull Request #1005 · ethereum/ERCs · GitHub

To Review

 Update ERC-4337: Move to Review by drortirosh · Pull Request #1014 · ethereum/ERCs · GitHub

Misc.
TBA
To Draft
EIPs
TBA
ERCs

 Add ERC: Margin Token Wrapper by hellohanchen · Pull Request #979 · ethereum/ERCs · GitHub
 Add ERC: Sustainable collaborative NFT collections by gfLobo · Pull Request #752 · ethereum/ERCs · GitHub
 Add ERC 7930: Interoperable Addresses by 0xteddybear · Pull Request #1002 · ethereum/ERCs · GitHub
 Add ERC: Decentralised User Profiles by anistark · Pull Request #861 · ethereum/ERCs · GitHub
 Add ERC: Instinct-Based Automatic Transactions by jamesavechives · Pull Request #596 · ethereum/ERCs · GitHub
 Add ERC: Composite EIP-712 Signatures by sola92 · Pull Request #993 · ethereum/ERCs · GitHub
 Add ERC: Ethereum Network Configuration for DApps by bogdan · Pull Request #1003 · ethereum/ERCs · GitHub
 Website: Bequeathable Tokens: A standard to allow tokens to be inherited after the owner's death by wamith · Pull Request #886 · ethereum/ERCs · GitHub
 Add ERC: DeFi Protocol Solvency Proof Mechanism by SeanLuis · Pull Request #922 · ethereum/ERCs · GitHub

Additional Reviews

PRs from Project Board?

Open Q&A
(Drop the Pull Request number to be added to the agenda.)
The EIP Editing Office Hour Meeting 59 (EIP) is scheduled for May 06, at 16:00 UTC with Editor @lightclient
GitHub Issue
Title: Beam_call__2__post_quantum_cryptography____Feb_28_
Category: Protocol_Calls___happenings

Author: system
Date: 2025-04-04T18:11:53.098Z

Prev: Call #1
Meeting Date/Time: Friday 2025/2/28 at 14:00 UTC
Meeting Duration: 1 hour

Poseidon Cryptanalysis Updates
Winternitz-XMSS Updates
Minimal zkVM Designs Update
Benchmarking zkVMs Update
FV and Conjections in Lean 4 Updates

GitHub Issue
Title: Registration_Open__Timing_Confirmation__Venue_Spon
Category: Protocol_Calls___happenings

Author: boris
Date: 2018-09-04T13:44:06.348Z

OK! So registration is now really open that we’ve confirmed a few more details. Go register then come back. I’ll wait.
The Council will convene for a full day on October 29th, with Status as our Venue Sponsor.
Status is holding their hackathon October 26th to Oct 28th, and have extended their venue booking so we can have the space for a full day of Council business. We’ll have the 28th as an overlap day of awesomeness. Plus EIPs & Interoperability sessions for the whole hackathon!
Full details in the announcement on the event page.
We’re still aiming for a max of 150 people right now. With current registration, we’ll likely hit that soon. The venue does have more room, but social scaling and food costs may be an issue.
Yes, we are still looking for sponsors, although we have the bulk of the base costs covered thanks to the ECF, Status, and ChronoLogic.
And join in the volunteer call this Wednesday (tomorrow).
All posts here: council-of-prague

Author: ligi
Date: 2018-09-04T13:53:13.960Z

Very nice! Especially like the idea of the Interoperability sessions!!

Author: boris
Date: 2018-09-04T14:36:20.383Z

Yeah, seems like a good fit! Feels like we need more time to actually sit and program together.

Author: ligi
Date: 2018-09-04T15:26:29.267Z

Yes - most definitely! Really like the idea of combining a hackathon and a magician style gathering. We should also at some point try it the other way around - first the gathering -> then the hackathon. So we can directly hack some ideas into code that came up in the sessions. But also this direction might be nice so we can have sessions about topics that came up at the hackathon. Great combination!
Title: Council_of_Prague__Trust___Reputation_Ring___Sessi
Category: Protocol_Calls___happenings

Author: Danibelle
Date: 2018-10-30T10:33:21.979Z

Here are the notes from Monday’s session in the Philosopher’s Corner…
And the names of those who offered to make sub-rings per the following breakout topics:
Dispute Resolution - Dean & Mark 
Types of Reputation - Daniel & Blake
Forgiveness - Chaals
Reputation Aggregation - Michael & Morgan
Ethereum Ecosystem / Contextual Trust -- Chelsea

Author: kronosapiens
Date: 2018-11-06T12:19:14.219Z

Here’s the thread for “Types of Reputation”:




CoP Trust & Reputation Sub-Ring: Types of Reputation Working Groups


    Hi all, 
Here is the kickoff thread for the “Types of Reputation” sub-ring of Trust & Reputation. 
To seed discussion, I want to share an essay introducing some of the uses and risks of reputation systems, and describes ways to mitigate the risk by deployed appropriate types of reputation systems to various contexts. Please read and provide feedback! 
https://hackernoon.com/reputation-systems-promise-and-peril-ae0af60595ea 
If anyone else has resources, please share and discuss!

Author: chaals
Date: 2018-11-12T13:15:19.014Z

Here’s the start of what might become a thread on forgiveness in reputation systems
Title: Protocol_Fellowship_Cohort_6_applications
Category: Protocol_Calls___happenings

Author: taxmeifyoucan
Date: 2025-04-27T20:43:48.688Z

Applications for EPF6 are open till April 30. If you are interested in core development and would like to start contributing directly to clients, testing or research, don’t hesitate to apply: Announcing Ethereum Protocol Fellowship Cohort 6 | Ethereum Foundation Blog
Title: Client_testing_call__17__December_16__2024
Category: Protocol_Calls___happenings

Author: abcoathup
Date: 2024-12-17T10:47:56.559Z

Pectra Interop Testing Call 2024-12-16 Summary
Notes by @danceratopz (Copied from Eth R&D Discord)
Pectra
No longer scheduled for inclusion in Pectra:

EIP-7742 Uncouple blobs per block between CL and EL
EIP-7762 Blob fee change (not high prio for rollups)

Progress/Open PRs for pectra-devnet-5
CL:

Add SSZ support to builder api ethereum/builder-specs#104: unclear inclusion status for devnet-5.
GOSSIP_MAX_SIZE

ethpandaops tested blocks with 40 million gas and capacity blob data: the 10MiB limit not hit.
Bump GOSSIP_MAX_SIZE from 10MiB to 15MiB consensus-specs#4041 Edit: This was decided against in the last ACDC
ethereum/consensus-specs#4045 is the PR actively being worked on. Should not be a blocker for devnet-5. Could be included or left out, depending on other devnet-5 progress.



EELS (ethereum/execution-specs) status - PRs required for test generation:

EIP-7623: Increase Calldata Cost ethereum/execution-specs#966 - will reviewed/merged soon!
Add EIP-7691, EIP-7762 to Prague ethereum/execution-specs#1054 - 7762 to be removed before merge.

EL Changes:

EIP-2537: Waiting for final BLS pricing changes:

Update EIP-2537: Gas pricing MAP, MUL and ADD operations
Update EIP-2537: MSM gas repricing
Update EIP-2537: Gas pricing pairing operations


EIP-7702: Small change, chainid type:Update EIP-7702: Update chainid to uint256
TBD in ACD this week for Pectra: Add EIP: Add blob schedule to EL config files

EEST (ethereum/execution-spec-tests) status:

ethereum/execution-spec-tests#1004 requires merge.
ethereum/execution-spec-tests#1022 needs removal of EIP-7762, then can be merged.
Release planned for later this week.

PeerDAS / EOF
No updates discussed this time; current focus is on Pectra Devnet 5.
Upcoming

Thurs 19th Dec: Last ACD of the year.

TBD in ACD Add EIP: Add blob schedule to EL config files ethereum/EIPs#9129.


EEST fixture release this week (without ethereum/EIPs#9129).
Title: Pectra_testing_call__9__14_October_2024
Category: Protocol_Calls___happenings

Author: abcoathup
Date: 2024-10-15T02:27:56.287Z

Summary
Update by @bbusa (from Eth R&D Discord)
Pectra

pectra-devnet-3

shutdown timeline by mid week. - Aim to shut it off by wednesday if there are no objections


pectra-devnet-4

alpha 8 release last week
no more blocking open issues to launch
possibly working teku image - was unable to confirm
prysm has a couple more PRs to merge in
nethermind will be ready very soon ™️
ethereumjs - bugs in engine API - working on it - ready in 1-2 days
erigon - will take a few days to get ready
besu - will take a few days - working on execution spec tests
geth passing all devnet 4 tests - engine API PR still open
lodestar - try to get it ready as soon as possible
reth - most changes in open PRs
Lightclient checking how to test 7702 transactions. Mario No support t9n in tests. Proposal for tx test - use the json instead of rlp. - Might need to impl new test format to support this new tx type. Mario gonna look into it. Blockchain test currently has support for 7702 transactions. - t9n tx type would be a nice to have but not a blocker.
launch target by end of the week



Peerdas

peerdas-devnet-3

been unfinalized for a while (7d)
lodestar issues - data doesn’t seem to be syncing
possibly do a relaunch with only validating supernodes



EOF - Fusaka

eof-devnet-0 -  fusaka-devnet-0

rebased on alpha 8 - built on top of devnet 4 spec
osakaTime as the fork activation
launch in ~ 2 weeks time



SSZ devnets

ssz-devnet-0

just launched today, no peers just bootnode
https://fusaka-light.box/
Currently only running ethjs < > nimbus pair
GitHub - ethpandaops/ssz-devnets
Want to get a dedicated discord channel for this
Title: Eth1_x_Stateless_Ethereum___Community_Discussion_a
Category: Protocol_Calls___happenings

Author: jpitts
Date: 2020-03-04T08:35:39.958Z

Please post any questions you would like asked at the Eth1.x Stateless Ethereum session.
Eth1.x Stateless Ethereum
2:50pm - 3:50pm
w/ Piper Merriam, Alexey Akhunov, James Hancock, Griffin Ichiba Hotchkiss
This session will be held today, Wed. March 4 at EthCC Paris, in “Workshop Pontoise” on Level 5.
Title: ePBS_breakout__10__September_27_2024
Category: Protocol_Calls___happenings

Author: abcoathup
Date: 2024-09-21T01:59:30.362Z

Agenda
EIP-7732 breakout room #10 · Issue #1157 · ethereum/pm · GitHub
Notes



HackMD



EIP-7732(ePBS) Breakout #10 Notes - HackMD
We thoguht it was going to be a 5 mins meeting but ended up over an hour, I didnt capture the open ended discussions rather than the actual action items. The actuon items are the following





Recording
Title: Ben___Building_on_Casper
Category: Protocol_Calls___happenings

Author: boris
Date: 2018-07-15T13:14:54.279Z

https://drive.google.com/file/d/1SIVv2Km3v6ljLecn-rpl7hhsJOwzft_C/view?usp=sharing
Title: PeerDAS_breakout__7__September_3_2024
Category: Protocol_Calls___happenings

Author: abcoathup
Date: 2024-08-25T23:08:27.905Z

Agenda
PeerDAS Breakout Room #7 · Issue #1139 · 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