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

Author: pet3rpan
Date: 2018-11-12T11:15:08.571Z

In Sydney we are having a blockchain hackathon fairly soon ~ in three weeks and would love to potentially introduce an Magicians Satellite…
As I began to actually think about it: it made no sense since most of my city actually has never heard of the Ethereum Magicians or even participate within the core Ethereum community - most are tech enthusiasts who have attended weekly meetups, workshops and crypto-hackathons that occur two to three times a year. There also aren’t too many individuals who actually work full time in crypto, unlike cities like Berlin or Toronto.
Going back to the main purpose of Magician Gatherings: Events where the Ethereum community can self-organize to maximize technical opportunities, share ideas and work together effectively, online and in person, across national, organizational and other boundaries.
It doesn’t look like that you can hold a typical Magicians gathering with too much meaningful conversation when not too many people are the same page. But I don’t think Sydney is the only city like this…
What are some any other events (doesn’t need to be an magicians event) that could be held that could generate thoughtful conversation around themes and issues - despite being an event geared for introductory ethereum community members?
I guess, my purpose here is to inspire greater awareness and involvement from my local community to participate in the greater open source ethereum ecosystem.
Would love any thoughts~ cheers

Author: boris
Date: 2018-11-12T18:48:19.947Z

I think starting small and connecting it to a shoulder event is great.
Can you explain what Magicians are? Can you review the EIPs process (jpitts How To EIP presentation is here)? Can you explain that anyone can get involved, help out, ask for feedback, and teach collaboration?
Is it a recruitment drive? Are you trying to onboard new Magicians? Are you shilling our principles and processes?

Author: pet3rpan
Date: 2018-11-16T11:31:28.003Z

I think the goal is introduce the local ecosystem to the online governance of Ethereum and in doing so shilling the principals and processes of the magicians. I might just re-present Jamie’s slides of the EIP process that you linked there.
Title: About_the_Protocol_Calls___happenings_category
Category: Protocol_Calls___happenings

Author: nicocsgy
Date: 2024-08-02T11:56:16.312Z

This category is exclusively for Protocol Calls & happenings.
Title: Client_testing_call__16__December_9_2024
Category: Protocol_Calls___happenings

Author: parithosh
Date: 2024-12-09T15:51:19.890Z

Testing call summary
Pectra
pectra-devnet-4/Mekong
Grandine is now fixed and network is at >98% participation
Missing rate is from ethereumJS perf issues
pectra-devnet-5
We discussed existing open PRs:

Pass max_blobs_per_block into Engine API methods: Decided to include it in a future devnet to give us more time for consensus, so it would not be included in the latest release
Rename PartialPendingWithdrawal field index to validator_index: Included in devnet-5 since its a minor renaming
eip7251: Limit consolidating balance by validator.effective_balance: Included in devnet-5 since its a minor renaming
changes required for EIP-7742: Waiting to be merged in

EIP-7762: Increase MIN_BASE_FEE_PER_BLOB_GAS was brought up in the context of finding out the increased testing load. The testing team had an initial look and the tests that need updating indeed overlap with EIP-7691, So the topic of inclusion of this EIP would be brought up on ACD with this new information.
Update EIP-7762: Move to Draft was brought up for discussion as well, the decision was to close the EIP as it introduces a decent amount of testing delays.
Update BLS precompile costs was also discussed. EL devs please have a look before ACD this week, Marek might reach out for an update.
An up to date spec-sheet can be found here
Gas limit change

The community has recently been pushing for a gas limit increase, some issues were found with the increase and have been outlined here.
3/5 CL clients on the call agreed that they were going to increase the GOSSIP_MAX_SIZE value in a future release (before pectra). The other 2 CLs were not present to state their viewpoint, but potentially one client is against and one client is for the change.
The worst case of a staggered rollout were then discussed. There should be no issues as long as the block size is not bigger than the lowest GOSSIP_MAX_SIZE set on any client on the network. Beyond that size, we might see the client with smallest GOSSIP_MAX_SIZE missing slots.
Such a change would introduce a non-equal p2p network and we usually strive to avoid that as well as strike to batch such changes at hard forks.
Since we lacked all parties to make a decision, we would do so on the PR here or in existing async channels.
In the meantime, the testing team will carry out experiments with a staggered rollout and other attempts at breaking the chain

TLDR: Please read the ethresearch post here. As long as the recommendations are followed we should continue to see a safe network.
peerdas & eof
No change, waiting on pectra unblocking
Title: Beam_call__1__beam_teams____Feb_14__2025
Category: Protocol_Calls___happenings

Author: system
Date: 2025-04-04T18:12:14.580Z

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

Introduction & Updates

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


Research Specialist Introductions

beam chain-specific EF Researcher Introductions
ZKVM Accelerationism Update


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

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



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

Author: abcoathup
Date: 2024-10-24T05:35:10.821Z

Agenda
EIP-7732 breakout room #12 · Issue #1188 · ethereum/pm · GitHub
Summary
(Copied from Twitter)

We reviewed the new & better all-in-one fork choice design by @fradamt. There’s a lot more nuance than what’s covered in the meeting notes, so please watch the recording if you’re interested
Next steps: focus on devnet, then update consensus specs to the new design

Notes



HackMD



EIP-7732(ePBS) Breakout #12 Notes - HackMD
Today we had the honor of Francesco on to explain latest thinking on All-in-one forkchoice design





Recording
Title: Protocol_Research_Call__2__May_14_2025
Category: Protocol_Calls___happenings

Author: system
Date: 2025-05-08T23:37:32.533Z

Protocol Research Call 2

May 14, 2025, 14:00 UTC
Zoom link will follow
Youtube and X stream links will follow

Agenda
Topic: Near-term EL scaling features. Agenda will follow.
 🤖 config

Duration in minutes : 90
Recurring meeting : true
Call series : research call
Occurrence rate : monthly
Already a Zoom meeting ID : true
Already on Ethereum Calendar : true
Need YouTube stream links : false
display zoom link in invite : false


GitHub Issue
Title: ePBS_breakout__4__July_5_2024
Category: Protocol_Calls___happenings

Author: abcoathup
Date: 2024-07-02T02:21:38.352Z

Agenda
ePBS Breakout room #4 · Issue #1083 · ethereum/pm · GitHub
2024-07-05T14:00:00Z
Moderator: @potuz
Notes
ePBS breakout #4 notes - HackMD
Recording
https://www.youtube.com/watch?v=WC9XsungamU
Additional info


Ethereum Improvement Proposals


EIP-7732: Enshrined Proposer-Builder Separation
Separates the ethereum block in consensus and execution parts, adds a mechanism for the consensus proposer to choose the execution proposer.
Title: FOCIL_breakout__1__December_13__2024
Category: Protocol_Calls___happenings

Author: abcoathup
Date: 2024-12-11T02:59:12.880Z

Agenda
FOCIL Break-Out Room · Issue #1210 · ethereum/pm · GitHub
Summary
TLDR by @soispoke (Copied from Twitter)
We discussed some of FOCIL’s features but mostly focused on coordinating efforts on the implementation side.
Core devs are obviously quite busy shipping Pectra and peerDAS, but we settled on the end of January as a realistic timeline to get to a working devnet
Notes
Notes by @matthewkeil (Copied from ethereum/pm)
Spec Stability

CL spec is relatively stable
EL spec will be formalized with a PR to EELS

Spec Questions

Fork-Choice slot/block enforcement via proposer-boost reorging. This might/should need to be a separate EIP

Inclusions/Exclusions for First Round

Blobs will not be included
Maybe not verify IL’s for first round of integration testing

Rough Timeline

Shoot for first week of January for next meeting
Hope that by that meeting we can have at least 1 CL and 1 EL ready to test with
Shoot for attempting to set up a basic Kurtosis/Hive network between the first clients on the next call

Spec Test Goals

Engage with Testing group to figure out timeline for work on spec tests

Active Branches

Geth: GitHub - jihoonsong/go-ethereum at focil
Lodestar: GitHub - ChainSafe/lodestar at focil

References Posted During Call

https://meetfocil.eth.limo/
https://notes.ethereum.org/@jacobkaufmann/Sy7sNHKVye
FOCIL with geth - HackMD

Implementation Notes
Goal should be to keep discussion strictly in Discord and on the website https://meetfocil.eth.limo. Telegram and Twitter should be avoided to help corral the discussion to a single (or two) places.
There are two cases in the execution case. When sync’d and before sync. Should the CL be notifying the EL to check the IL’s? This will be different cases for when syncing and after sync is complete. A PR will be opened to the spec to dial this in.
EL will look at specifying that if an IL is passed in then the IL should be checked, if not then the IL’s will not need to be verified to check the block. Terrence requested for @Jihoon to open a pr here? Pull requests · ethereum/execution-apis · GitHub
Recording
Title: Creating_a_new_category_for__Regional_Sessions_
Category: Protocol_Calls___happenings

Author: jpitts
Date: 2018-11-21T05:14:29.709Z

Are there upcoming events which might make good occasions to organize work?




Will there be EthMagicians gathering at EthSingapore? Regional Sessions


    Not sure if we had one yet in Asia, but I will be there and happy to get that going if necessary @boris are you going by any chance?
  

Also, please do provide some feedback about the term “Coven”. There are probably better words. I thought a play on “Conclave” might be funny as an alternative: “Convlex”.

Author: Annavladi
Date: 2018-11-29T02:58:40.751Z

lol  good thing its not convent

Author: jpitts
Date: 2018-11-29T03:15:24.491Z

Probably we need a simpler name than any of these that gets to the bottom of it

Author: jpitts
Date: 2018-11-29T19:57:49.518Z

Ok setting it to Regional Sessions for now, sometimes I get carried away.

Author: jpitts
Date: 2018-11-29T20:12:41.458Z

Proposed “About Regional Sessions”:

All it takes is for someone to take responsibility and start organizing it!
The Ethereum Magicians name can be used w/o permission
Please introduce the Magicians to the group and let them know they are Magicians too. This presentation can help, it is HTML hosted on GitHub.
Please announce it to the Forum.
Sponsors can be lined up and the event can be supported in any way. It is up to the organizer.
Some things which may happen:
– Education sessions
– Lightning talks
– EIPs moved forward
– Work to help Rings operate

Anything else we might add?
Title: PeerDAS_breakout__15__January_21__2025
Category: Protocol_Calls___happenings

Author: abcoathup
Date: 2025-01-09T09:34:30.245Z

Agenda
PeerDAS Breakout Room #15 · Issue #1240 · ethereum/pm · GitHub
Notes & Chat log


docs.google.com



PeerDAS Breakout Room notes
PeerDAS Breakout Room #15 Date: 2025.01.21 Agenda: https://github.com/ethereum/pm/issues/1240  YouTube video: https://youtu.be/wwqqmvQJx2E  Client updates: Lighthouse Implemented PeerDAS activation at Fulu and peerdas-devnet-4 spec Fixed a few peer...





Recording

Author: abcoathup
Date: 2025-01-28T23:46:55.076Z

AI summary (using )
The PeerDAS Breakout Room #15 covers updates from various teams working on Ethereum’s development, focusing on progress, challenges, and future testing strategies.
Client Updates
Lighthouse has made significant progress, including full readiness for interrupt testing and running the latest Electro code. However, a state route mismatch issue arose during transitions to full [4:01]. Manu reported implementing a custody group count and working on the C library, which still requires optimization [5:01]. The Prism team is also addressing a state truth mismatch and is in the early stages of implementing validator custody [5:50].
Decoupling and Testing
The teams are focused on decoupling custody groups and preparing for integration testing. The Grandin team is moving the P code activation into full and stress testing their reconstruction flow [7:35]. The discussion highlighted the need for thorough integration testing before moving to the next development phase [12:27].
Development Specifications
The current DEET spec is under review, with teams encouraged to track progress on custody-related pull requests. The consensus spec version has been updated to ensure compatibility with the latest changes [10:15].
Future Steps
The next steps involve all teams working on local testing and interrupt testing with other clients. The goal is to ensure all scenarios are covered and to prepare for a definitive test in the coming weeks [29:15].
In conclusion, the breakout room emphasized collaboration among teams to address challenges, optimize processes, and ensure a smooth transition to the next development phase.
Title: Ethereum_Magicians_Summer_Sessions___Get_there_ear
Category: Protocol_Calls___happenings

Author: anett
Date: 2020-07-15T10:20:33.365Z

We are going to host Ethereum Magicians Virtual Summer Sessions - an amazing virtual event scheduled for July 29, 2020. 
The gathering will feature moderated Zoom calls for discussing EIPs and coordinating, and a game-like social experience for the “entrance hall”… where you can voice-chat with others based on proximity. A key feature of the conference software that we’re using will enable us to place “posters” describing a paper or EIP around the entrance hall. We will be able to gather around the entrance hall. We will be able to gather around a topic and discuss it in small groups, similar to what we might do in hallways outside of talks.
Join this event to get to know about latest updates that following groups have, get answers to questions about how those groups started, their progress and ask questions.
MagiciansSSbanner1920×1080 527 KB
Details
Date: 29/July 2020
Time: 3pm CET → 6pm CET
Check the Timezone of the event
RSVP: Eventbrite
Article: Medium
Join
Zoom talks
Meeting ID: 857 8436 4467
Passcode: Magic
Schedule:

Welcome
3pm → 3:55pm Social Governance
4pm → 4:55pm EIP Improvement Proposals group
5pm → 5:55pm EIP-1559: Fee market change
Goodbye

Claim your POAP
Post screenshot from the event to this thread & you will receive link where you will put your ETH address and claim your POAP token 
This event will be front running of the Ethereum in Enterprise 2020 Conference
Stay Magical

Author: Amxx
Date: 2020-07-29T20:22:17.593Z

Thanks @anett for organising this, it was nice seeing you all despite these difficult times.
Here is the screenshot for my POAP 
Capture d’écran de 2020-07-29 15-57-081920×1080 308 KB

Author: nathPay
Date: 2020-07-30T07:58:33.908Z

Hi  ! Thanks a lot for the meeting, I understand how magicians works now  !

(My screenshot for the POAP  )
Screenshot_20200729_1509331616×977 364 KB

Author: anett
Date: 2020-08-06T10:25:39.367Z

Hi @Amxx it was nice to e-meet you 
Claim your POAP in your DMs

Author: anett
Date: 2020-08-06T10:28:39.229Z

You’re welcome Nathan 
Thank you so much for kind words, open your DMs to claim you POAP
Title: EIP2537_BLS_breakout__October_14_2024
Category: Protocol_Calls___happenings

Author: abcoathup
Date: 2024-10-12T00:14:12.293Z

Agenda
EIP-2537 Breakout Call · Issue #1176 · ethereum/pm · GitHub
Summary
TLDR from Kev (Copied from Eth R&D Discord)

@ralexstokes will try to reach out to users to see what they think about not having subgroup checks
One possibility was to add a flag, but it was noted by @mratsim that this becomes a pain for zkEVMs to implement this branching logic
Removing G1MUL and placing it inside of MSM did not seem to have a lot of backing, though there were folks advocating for it as an equalizer, if we decide to add more opcodes like the subgroupCheck
There seems to have been consensus that the precompiles were underpriced

I think most decisions will be downstream from figuring out whether users want to have subgroup checks
Recording
Title: Eth_simulate_Implementers____Meeting___48___May_05
Category: Protocol_Calls___happenings

Author: system
Date: 2025-05-02T11:10:19.012Z

eth_simulate Implementers’ Meeting # 48,  May 05, 2025

Date and time in UTC in format May 05, 2025, 12:00 UTC

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 via email
Facilitator emails: Killari@gmail.com, pooja@ethcatherders.com
 🤖 config

Duration in minutes : 60 mins
Recurring meeting : true
Call series : eth simulate
Occurrence rate : weekly
Already a Zoom meeting ID : false
Already on Ethereum Calendar : false
Need YouTube stream links : false
display zoom link in invite : true


GitHub Issue

Author: system
Date: 2025-05-05T12:26:12.845Z

YouTube recording available: https://youtu.be/dotZwMwz_8Q

Author: system
Date: 2025-05-05T12:32:00.637Z

Meeting Summary:
No summary overview available

Click to expand detailed summary
In the meeting, Sina and Killari discussed the status of their project, including a bug fix and the need for further testing. They also considered merging their meeting with another one, but were unsure about the time. Sina expressed the importance of getting all tests passing before merging the spec and test. They also discussed the need for more updates from Netamount and Beijel. The conversation ended with Sina planning to contact Beijel after a release.

Next Steps:

Sina to ping Be suit to review the tests after the release of the bug fix in cath.
Killari to explore the possibility of merging this meeting with the RPC Standards meeting.
Sina to continue work on estimate gas and tracing after Petra (in 2 days).
Killari to check the status of Besu’s implementation and its closeness to Geth.
Sina to follow up on getting two clients (possibly Geth and Besu) to fully agree on the spec and tests for merging.

Recording Access:

Join Recording Session
Download Transcript
Title: Qualitative_interpretation_of_the_EIP_0_Values_Sur
Category: Protocol_Calls___happenings

Author: jpitts
Date: 2018-06-07T06:57:04.803Z

Are there any thoughts about methodologies / processes / approaches for interpreting the EIP-0 Shared Values survey?
Can anyone here connect Jarrad to resources or individuals who are involved in social psychology and related fields, specifically qualitative interpretation of survey results?
Context:
@jarradhope posted this to the ethereum/governance channel:

@lrettig @jpitts and everyone else here. I would love to start herding the cats to do the interpretation phase of survey results, how we can can distill it down into a document, quantitative analysis is pretty straight forward, our ipynb can be found here datasets/201805_EIP0_shared_values at master · status-im/datasets · GitHub, but how to best go about qualitative interpretation and the process around it alludes me
Some ideas are that participants can write separate Google docs as an intermediary layer, we comment on those then try distill those docs into a ‘master’ doc until it’s revised
We could introduce some structure, but we’d have same coordination problems coming up with document structure itself
In short, what do we think is the best way to create this shared values document?

Author: jpitts
Date: 2018-06-08T04:01:14.851Z

Related tweet by Virgil Griffith:
https://twitter.com/virgilgr/status/1004921779251445763

Author: pet3rpan
Date: 2018-06-09T10:54:27.727Z

Currently working away at it, let me know what anyone else is up to

Author: tay
Date: 2018-06-21T04:56:39.718Z

For history’s sake:
The Survey Itself

https://docs.google.com/forms/d/e/1FAIpQLSfjRL9cdeueC322RDK86soBv79VsgLQeGlibUL5PuWrte_-og/viewform

Raw Data


https://github.com/status-im/datasets/tree/master/201805_EIP0_shared_values


https://docs.google.com/spreadsheets/u/3/d/1nmWZKJq-ndF0uZGnHgQZq7Lm2_0xJbYWxmQTOrgIFfg/edit#gid=840981558


Some Light Analysis


https://twitter.com/avsa/status/1003655572590342145


https://www.figma.com/file/I0r0qsykpH459ti94LrVql3q/EIP0-Responses


https://medium.com/@seven7hwave/scaling-the-community-five-takeaways-from-the-ether-f327fb00adb1
Title: Meeting_at_EthCC_
Category: Protocol_Calls___happenings

Author: chaals
Date: 2023-06-29T00:15:18.208Z

Who is going to be in Paris?
It would be good for the Magicians to meet in person, and talk about where we are going, where the Magicians fit into the space and how to be useful and productive.
I hesitate to say “governance” because that sounds like it could get us into discussions that try to be more formal than is warranted, but I do think it’s valuable to have a community that talks to each other, and to the other parts of the space that are relevant to what the Magicians try to do.
We have a potential venue in Paris La Defense (basically at the RER train station, so not that hard to get there). The question is whether there is a day that is good enough for a critical mass of people to actually turn up - suggestions/requests welcome.
Note that I’m brand new to trying to organise Magicians things, although I’ve spent a long time running Working Groups for e.g. W3C and the Enterprise Ethereum Alliance as well as more informal groupings. So I am afraid that with such short notice this is going to be a little scrappy, but I believe we can pull something reasonable together.

Author: morganjweaver
Date: 2023-07-04T00:20:58.765Z

Hey Chaals! Will totally attend if it’s within my schedule to do so. Before the 21st seems pretty viable to me as the Hackathon won’t be in full swing yet.

Author: chaals
Date: 2023-07-11T00:37:44.845Z

This much response seems to justify nothing more than a possible informal get-together at some point, so I will aim to plan something of that nature.

Author: julesl23
Date: 2023-07-11T18:02:21.083Z

I’ll be there, mainly sightseeing initially as I was too late to know I was available to go to Paris
so missed out on tickets for EthCC  
Keep me in the loop if there is a get-together. Thanks.
Title: AllWalletDevs___call__33___May_21__2025
Category: Protocol_Calls___happenings

Author: system
Date: 2025-04-16T17:32:11.125Z

AllWalletDevs, call #33, May 21st, 2025

May 21, 2025, 17:00 UTC
Duration in minutes : 60
Recurring meeting : true
Occurrence rate : monthly
https://allwallet.dev

Agenda

TBD

Other comments and resources
The zoom link will be sent to the facilitator (please fill in the email and telegram)
Facilitator email: sam.wilson@ethereum.org
Facilitator telegram: @SamWilsn
GitHub Issue
Title: Pectra_testing_call__10__October_21_2024
Category: Protocol_Calls___happenings

Author: abcoathup
Date: 2024-10-22T23:25:25.401Z

Summary
Update by @bbusa (from Eth R&D Discord )
Pectra
pectra-devnet-3

Has been shut down friday.

pectra-devnet-4

Started last week Friday currently at ~75% finalization
Erigon/reth/grandine issues mainly
Erigon - working on final spec changes - not yet merged, some design changes - hopefully ready in a few days
Grandine - Fixing attestation verifications
Reth - 7702 transaction was submitted v set to 15 in the auth items - issue has been clarified by lightclient.

pectra-devnet-5

Nethermind - 7742 implementation is in progress
G11: short modification for EIP7742 - Update EIP-7742: update the required EL headers and the gas fee mecha… by g11tech · Pull Request #8979 · ethereum/EIPs · GitHub
Open issue regarding the naming convention for max blob and target block activation.
Discussing whether we want to have the public devnet on top of devnet 4 or devnet 5 spec - depends on client implementation progress
BLS precompile pricing discussion - no decision made yet - possibly have an update by thursday

Peerdas
peerdas-devnet-3

been unfinalized for a while (14d)
metrics update: teku implementation is in progress

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 ~ 1 week time
Besu is ready go
Reth has osaka - haven’t been tested yet
Nethermind - work in progress

SSZ devnets
ssz-devnet-0

no updates
Title: PeerDAS_breakout__13__December_10__2024
Category: Protocol_Calls___happenings

Author: abcoathup
Date: 2024-12-11T02:45:52.683Z

Agenda
PeerDAS Breakout Room #13 · Issue #1202 · ethereum/pm · GitHub
Notes & chat log


docs.google.com



PeerDAS Breakout Room notes
PeerDAS Breakout Room #14 Date: 2025.01.07 Agenda: https://github.com/ethereum/pm/issues/1236  YouTube video: https://youtu.be/0QfCxSbhRk8 Client updates: Prysm Able to start at Deneb and transition to Electra &amp; Fulu Able to start a node at Fulu...
Title: WalletUncon___DEVConnect_Istanbul
Category: Protocol_Calls___happenings

Author: ligi
Date: 2023-08-09T16:05:16.630Z

The first ever WalletUncon will happen at EFDevconnect in Istanbul on Friday 17. November 2023
Let’s have conversations on how to improve wallets together in a collaborative way! Submit your proposals here: https://cfp.walletuncon.org
More information/RSVP here: https://walletuncon.org
Title: Stateless_implementers_call__27__November_4_2024
Category: Protocol_Calls___happenings

Author: abcoathup
Date: 2024-11-06T00:05:32.676Z

Agenda
Stateless Implementers Call #27 · Issue #1196 · ethereum/pm · GitHub moderated by @rudolf
Notes
Recording
Title: PeerDAS_breakout__9__October_1_2024
Category: Protocol_Calls___happenings

Author: abcoathup
Date: 2024-09-19T02:27:26.501Z

Agenda
PeerDAS Breakout Room #9 · Issue #1155 · ethereum/pm · GitHub
Notes & chat log
PeerDAS Breakout Room notes - Google Documenten
Recording
Title: PeerDAS_breakout__3__July_9_2024
Category: Protocol_Calls___happenings

Author: abcoathup
Date: 2024-07-06T01:35:39.176Z

Agenda
PeerDAS Breakout Room #3 · Issue #1093 · ethereum/pm · GitHub
Moderator: @hwwang
Key items
by @hwwang (from Eth R&D Discord):

devnet-1 has many forks that would be hard to recover. See the meeting notes for the issues)
ACTION: relaunch devnet-2 by the end of the week with all the client fixes.
Please review “Decouple network subnets from das-core” PR (a potential devnet-3 update): EIP-7594: Decouple network subnets from das-core by ppopth · Pull Request #3832 · ethereum/consensus-specs · GitHub
Teams want to include https://github.com/ethereum/consensus-specs/pull/3800 into Pectra so that PeerDAS can be a pure network update (not hard fork).

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: PeerDAS_breakout__11__October_29_2024
Category: Protocol_Calls___happenings

Author: abcoathup
Date: 2024-10-16T04:04:08.254Z

Agenda
PeerDAS Breakout Room #11 · Issue #1183 · ethereum/pm · GitHub
Summary
[Copied from Eth R&D Discord]

Client teams have been working on sync refactoring, pectra rebase, various optimization and devnet issues.
peerdas-devnet-3 is in a pretty bad state and will be shut down today. peerdas-devnet-4 has been scheduled for end of November.
Client teams discussed whether to activate PeerDAS at the Fulu fork, and agreed to discuss with the wider group in the next ACD.
Discussions on various spec changes: consensus-spec#3832, consensus-spec#3993, and activation of EIP-7742. Client teams to review the PRs and provide feedback.
Discussed PeerDAS metric PRs, client teams to review and provide feedback.
The next breakout call will be cancelled due to devcon, next call will be on the 26th Nov.

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: _Things_we_agreed_on_____Things_that_excited_us__a
Category: Protocol_Calls___happenings

Author: ligi
Date: 2018-10-31T03:43:51.732Z

The notes coming in from the working groups are great - but might sometimes be a bit raw and hard to digest with the little time we have in life.
So my suggestion is to boil it down to e.g. “Things we agreed on”, “Things that excited us” and “Problems we have”. I will start for the Wallet-Ring:
Things we agreed on:

Our mission shall be from now on “Make wallets more useful, interoperable, user friendly, private, decentralized, safe and accessible.”
For scaling reasons we will form sub rings (Mobile, Desktop, Hardware)

Outer rings still exists - just augmented by inner rings for specific discussions around one of this sub-topics



Things that excited us

Storage of private keys
WalletConnect
Wallet reputation
mETHadata

Problems we have

We are infested with some centralisation and need to cure that better sooner than later

Note: we only voted on “Things we agreed on” - for “Things that exited us” and “Problems we had” I basically just took from our notes 
Also what I think would be a nice touch: let’s make ceremony that enables each participant of a session to sign the “Things we agreed on” and perhaps even the full protocol of the session.

Author: boris
Date: 2018-10-31T04:59:54.444Z

Yes.
I’d like to go one step further and move some items to Scrolls repo issues where people can signal consensus and sign up to move work forward.
There are several items from Meta Magicians and EIPs that fit this.
Changing / agreeing / renewing the Charter of the Wallet ring is what I see you doing here. And if a Charter is not regularly agreed & renewed. A Ring dissolves. I know we’re barely forming them — but it should be clear that  energy is required to keep going.
Love it. Thank you @ligi
Title: Education_Ring_Session
Category: Protocol_Calls___happenings

Author: jpitts
Date: 2019-03-04T11:30:49.981Z

Education Ring session notes:
https://hackmd.io/k166XmT8S5ysdHA_uXM02g
“Who are the ones being educated?” sub-ring discussion notes:
https://hackmd.io/Md4OxlWPTaC4HyTYRKWUyw
Title: EVMMAX_Implementers_Call_4__March_20__2025
Category: Protocol_Calls___happenings

Author: system
Date: 2025-03-05T18:41:08.241Z

EVMMAX Implementers Call 4, March 20, 2025

Date and time in UTC in format March 20, 2025, 12:00 UTC
Duration in minutes : 90 mins
Occurrence rate : monthly
Other optional resources

EVMMAX Implementers Call Playlist
EVMMAX Breakout - Devcon SEA L1 R&D Workshop
Poqeth: Efficient, post-quantum signature verification on Ethereum



Agenda

Client Updates
Open Questions

Other comments and resources
Next call on April 17, 2025
GitHub Issue
Title: Installed__Discourse_Math_Plugin__for_using_LaTeX_
Category: Protocol_Calls___happenings

Author: jpitts
Date: 2021-06-22T06:59:29.952Z

This is to announce that with the latest upgrade we have installed the Discourse Math Plugin. Thanks @hwwang for the suggestion!



Discourse Meta – 3 Jun 24




Discourse Math




Plugin






official
math





:discourse2: Summary Discourse Math uses MathJax (default) or KaTeX to render maths in your Discourse forum.   🛠 Repository Link https://github.com/discourse/discourse-math   📖 Install Guide How to install plugins in Discourse     Enabling Math...

Reading time: 4 mins 🕑
Likes: 88 ❤

Author: xinbenlv
Date: 2022-11-28T16:46:17.374Z

Thank you for doing this. But it seems not working right now
I missing be something here, could you help me out or check if this Math plugin is working?




EIP-5982 Role-based Access Control EIPs


    We are definitely happy to add these events into IERC_ACL_CORE if getting your support, but if I may take sometime to clarify and make sure we are on the same page about the implications. 
We want this new EIP to be compatible to OpenZeppelin, more specifically we are looking at IAccessControl.sol between OZ v4.4.1 - v.4.8.0 
Therefore the methods and events of IERC_ACL_CORE needs to be a subset of AccessControl.sol 
$$ 
S_{IERC_ACL_CORE} \subset S_{OZAcessControl.sol} 
$$ 
The events of questio…
  

$$
S_{IERC_ACL_CORE} \subset S_{OZAcessControl.sol}
$$

Yields unrendered as shown
2022-11-28_08-46-30772×138 6.38 KB

Author: Pandapip1
Date: 2022-11-28T23:42:24.879Z

Test:
$hello_{world}$
EDIT: Can confirm that the tex doesn’t work.

Author: anett
Date: 2022-12-06T22:56:37.675Z

@jpitts can we update the plugin ?
Title: My_computer_has_died
Category: Protocol_Calls___happenings

Author: Pandapip1
Date: 2023-01-03T01:46:48.417Z

CC @SamWilsn @axic @gcolvin @lightclient
My computer (unexpectedly) broke on the 26th or 27th (I forget), without any other suitable device, and with my passwords/2fa codes not backed up. This (Ethereum Magicians) is the only means I have to contact you right now, since on this computer, GitHub and Discord are blocked. I’m just letting you know that I am not, in fact, dead.

Author: xinbenlv
Date: 2023-01-03T02:30:30.625Z

That’s too bad. Definitely backup your 2FA rescue codes next time. Hope you recover to normal digital life soon

Author: Pandapip1
Date: 2023-01-03T12:25:55.895Z

I’ve got the backup codes still (of those, I always keep a physical copy). I just happened to be on vacation and it would have been a 9hr+ car ride to get home and another 9hr+ car ride to get back, through the polar vortex.

Author: SamWilsn
Date: 2023-01-03T14:12:05.258Z

Glad you’re okay! Thanks for letting us know. Hopefully your holidays aren’t entirely ruined.

Author: Pandapip1
Date: 2023-01-04T21:15:58.100Z

Update - I now have access to my GitHub account on one of my older desktops.

Author: Pandapip1
Date: 2023-01-04T22:43:47.432Z

Another update: just got into my Discord. Man, that’s a lot of “happy new year” pings!

Author: xinbenlv
Date: 2023-01-04T22:55:52.454Z

Great to hear. Thank goodness. It seems the only place you didn’t turn on 2FA is ethereum-magician, @Pandapip1 ?

Author: Pandapip1
Date: 2023-01-04T23:03:41.223Z

That is correct, but I actually use GitHub sign-in (and I do use 2fa for GitHub)! Thankfully, I happened to already be signed in to my Gmail on one of my old computers, where I was able to set a password for Ethereum Magicians. I was also, from my google account, able to access the backups of my 2fa application secrets, although it took some wrangling.
Title: RollCall__6__July_10_2024
Category: Protocol_Calls___happenings

Author: abcoathup
Date: 2024-07-02T01:50:29.834Z

Agenda
RollCall #6 · Issue #1071 · ethereum/pm · GitHub; moderated by @CarlBeek
Summary:
https://notes.ethereum.org/@CarlBeek/RollCall-6-Summary by @CarlBeek
Recording
Title: EOF_Implementers_call__59__October_2_2024
Category: Protocol_Calls___happenings

Author: abcoathup
Date: 2024-10-04T11:39:24.111Z

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

Current release tests (EOF on top of prague) are broken

Besu had a 7702 bug, all non-7702 tests are fine.
Next release will be released after devnet 4 is released
PR reviews are mostly caught up
Testing focus is on devnet 4 for the next week


Compiler

Vyper create from blueprint needs a re-work for EOF.

Create form EXT Contract would have helped.
Cannot blueprint off of any contract in EOF like you could in legacy
A factory deployer would be good, delegate call into a contract that EOF creates. As opposed to an initcode only contract




Osaka Migration

Clients need to target Osaka for EOF activation
Tests need to target Osaka, including moving tests in source tree
We have 6 more months to reifine the spec

We can look into HASCODE
We can reconsider EXT*CALL return code numbers
cleanup: EOFCREATE stack order
cleanup: Remove hashing of container in EOFCREATE
cleanup: Rename RETURNCONTRACT to RETURNCODE




Open questions

Implications of gas introspection: regarding a gas to eth EIP.



Next Meeting:

Rename RETURNCONTRACT → RETURNCODE
HASCODE / ERC-721 solution
EXT*CALL return code, keep or revise?
EOFCRAE stack order
remove container hashing in EOFCREATE

Recording
Title: Verkle_implementers_call__23__August_26_2024
Category: Protocol_Calls___happenings

Author: abcoathup
Date: 2024-08-03T02:01:11.690Z

Agenda
Verkle Implementers Call #23 · Issue #1121 · ethereum/pm · GitHub; Moderated by @rudolf
Notes
https://notes.ethereum.org/@rudolf/vic-notes#Call-23-August-26-2024 by @rudolf
Recording





Additional info

Verkle - Spec tests summary - HackMD
Binary Tries vs Verkle by @gballet
Title: L2_Future_Session_3____users____Expanding_on_what_
Category: Protocol_Calls___happenings

Author: jpitts
Date: 2020-11-27T09:19:41.926Z

As part of our “Ethereum L2 Future” virtual conference series, Magicians Ops is organizing a session today Friday 27th Nov. 4pm CET to introduce the community to the L2 roadmap proposal and start mapping out stakeholder needs and concerns.
 Session 3 agenda and related links
Session 1: Starting with L2s  on 13th November 4pm CET - Notes
Session 2:  dApp development on L2 on 20th Novemberr 4pm CET - Notes
Session 3:  Ethereum L2 users   on 27th Novemberr 4pm CET - Notes
Recordings:
Starting with L2s  - YouTube
dApp Development on L2  - YouTube
Ethereum L2 users - YouTube
Announcement - Medium article
Please join us and share this event with folks who are interested in this topic.
If you can’t make it – or even if you can – please help out by replying here w/ resources, ideas, needs you can think of relating to dapp developer experience, user experience, tooling, etc. as they relate to L2s, rollups, ZK rollups.
Some starting points:




A rollup-centric ethereum roadmap


    What would a rollup-centric ethereum roadmap look like?
Last week the Optimism team announced the launch of the first stage of their testnet, and the roadmap to mainnet. They are not the only ones; Fuel is moving toward a testnet and Arbitrum has one. In the land of ZK rollups, Loopring, Zksync and the Starkware-tech-based Deversifi are already live and have users on mainnet. With OMG network’s mainnet beta, plasma is moving forward too. Meanwhile, gas prices on eth1 are climbing to new highs, t…
  

https://medium.com/matter-labs/evaluating-ethereum-l2-scaling-solutions-a-comparison-framework-b6b2f410f955
Feel free to add comments / links / ideas regarding L2s and usability.
We are looking forward to see you joining the sessions
Title: Client_testing_call__15__December_2_2024
Category: Protocol_Calls___happenings

Author: parithosh
Date: 2024-12-02T14:49:58.470Z

Summary 
Pectra


pectra-devnet-4

Has been shutdown.



Mekong

Update on the public testnet non-finality incident from last week as well as the associated spec tests Update
All the client teams have updated their CLs to fix the issue.
We’re currently at ~86% participation and the clients will be notified on their issues



devnet-5

EIP-7742 related PRs will get a last look before merging
EIP-7691 PR will be merged soon after
EIP-7251 PR will also get a last look and be merged in
The aim is to have the consensus-spec PRs merged by mid-week and a release ideally before ACD
Engine exclude empty requests PR was merged on the call
EIP-7742 PR needs a rebase after the latest EIP changes and should be merged after
Once the EL changes are merged in, the execution-spec-tests release will follow. The tracker is live here
We will gate the entry to devnet-5 based on the execution-spec-tests passing.
The hive instance using the spec release will be available ASAP for clients to use.



Peerdas and EOF

Once devnet-5 spec is out, we will pin these releases for EOF/PeerDAS codebases to rebase on top of
A new EIP to update the max code size might be added to EIP, more on that at ACD
Title: ePBS_breakout__8__August_30_2024
Category: Protocol_Calls___happenings

Author: abcoathup
Date: 2024-08-20T01:52:37.382Z

Agenda
EIP-7732 breakout room #8 · Issue #1135 · ethereum/pm · GitHub
Notes
Highlight by @terence:
Moving to slot auctions seems imminent at this point, the question is when. If we want to have slot auctions for the very first client devnet, then the sooner the better


HackMD



ePBS Breakout #8 Notes - HackMD
ePBS Breakout #5 Notes





Recording
Title: Magicians_in_Berlin_2019__Rings_organizing_around_
Category: Protocol_Calls___happenings

Author: jpitts
Date: 2019-06-13T23:29:34.987Z

I’d like to start helping organize ways for Rings to gather during this week of many events in Berlin. Perhaps we could create a general program and take advantage of any time and space available throughout the week.
I believe that MetaCartel Demo Day in particular would like to have some UX-related sessions.

Aug 19
MetaCartel Demo Day
https://www.metacartel.org/demoday-2019


Aug 19-21
Web3 Summit
https://twitter.com/web3summit
Note: the Web3 Summit is 40 min away from the Demo Day venue by shuttle, which means that on Aug 19 Magicians should take care to plan sessions accordingly.


Aug 21-23
DappCon
https://twitter.com/dappcon_berlin


Aug 23-25
ETHBerlin
https://twitter.com/ETHBerlin

If you know the situation on the ground at any of these events, and if it will conducive to having some space for work sessions, please list them below!

Update: Please fill out this Call for Rings form to let the organizers know what topics / EIPs you’d like to discuss, and if you’d like to organize a Ring. We will work on an agenda so people can know where Rings and Councils are gathering throughout the week.

Author: markoprljic
Date: 2019-06-18T20:57:16.682Z

I’ll be there for the week, not sure about timing for the council or any rings to organise during the listed events. It will be pretty busy overall but if we can lock some time and space and commit to it that might work.
I know that dgov is running a node on Web3Summit (that’s where I’ll be mostly), maybe another node for magicians?
Dappcon might be more appropriate for the gathering IMO and @mariapaulafn might have more info regarding the space.
Looking at the dates we won’t have a free day in the week so the rings will need to fit somewhere “in between”.
If I can help anyway with organisation please let me know.

Author: anett
Date: 2019-06-26T07:05:34.982Z

Hi everyone👋 We have finally put up The Call for rings form.
Operations of Magicians are collecting the topics and would love to put up a list of proposed Topics / EIPs soon.
We will be more than happy if you would add the one that you would love to discuss about. But on a plan is to have a short session for “spontaneous proposals” too. 
We also want to be able to help any Ring meet on the sidelines of any event in Berlin during the “conference week” ie Aug 19 - Aug 25. 
In the meantime we are working on getting a space for this year’s Council of Berlin. Possible dates for a Berlin Council 2019 are Aug 20 and Aug 21.
I will announce Topics of discussion/ EIPs and exact date and venue soon

Author: dominic
Date: 2019-07-09T12:41:16.231Z

I’m going to be in Berlin the 24th and 25th, would love to meet anyone else from the https://ethereum-magicians.org/c/working-groups/constrained-resource-client-ring if present.

Author: anett
Date: 2019-07-09T18:59:05.278Z

cool  can you please fill out this form and join our Telegram channel
Thank you
Title: Lightning_Talks__Web3_Stack_by_Jack_Platt
Category: Protocol_Calls___happenings

Author: boris
Date: 2018-07-15T11:09:52.314Z

https://docs.google.com/presentation/d/1nSgcBH6F23iHYhnv4d5ovZKe9mtZh8ptSLPCf6Uf-Iw

Author: brunobar79
Date: 2018-07-15T23:03:16.422Z

Can you update the permissions to “anyone with the link can view”?
Thanks!

Author: boris
Date: 2018-07-16T09:36:48.327Z

Done. Sorry about this, permissions on mobile seem to be difficult, just getting back to a laptop now.
I don’t have permission to do this, but making this “owned” by @jplatts12 likely useful as well.

Author: boris
Date: 2018-07-16T10:45:00.137Z

@jplatts12 own thread should be canonical Lightning Talks: Web3 Tech Stack
Should delete this topic.

Author: brunobar79
Date: 2018-07-16T16:23:37.886Z

No worries @boris and thank you!
Title: Lightning_Talk__Ethereum_Status_Codes_ERC_1066
Category: Protocol_Calls___happenings

Author: boris
Date: 2018-07-17T20:26:38.926Z

Brooke’s (@expede) presentation on Ethereum Status Codes:


drive.google.com



ETH Berlin Council&nbsp;—&nbsp;ESC.pdf
Google Drive file.





See the discussion thread ERC-1066: Ethereum Status Codes (ESC)
Video of the presentation:



view.ly



Lightning Talk: Ethereum Status Codes ERC-1066, Brooke Zelenka - FEM Council...
Brooke Zelenka presents her code for implementing status codes as returns & messaging for smart contracts. Discussion thread and PDF link: https://ethereum-magicians.org/t/lightning-talk-ethereum-status-codes-erc-1066/770 Thanks to Santiment...

Author: fubuloubu
Date: 2018-07-17T22:38:34.924Z

Wooooo! This is an awesome idea!

Author: ligi
Date: 2018-07-18T07:49:05.010Z

1066 is great! Especially like the fact it makes things translatable - this will be big improvement for UX in the future. We will have the same problem with signed data standards. Will add 1066 to the EIPs in the wallet ring. Thanks for the lighting talk and putting effort into making an EIP!
Title: PeerDAS_breakout__1__June_11_2024
Category: Protocol_Calls___happenings

Author: abcoathup
Date: 2024-06-12T02:10:01.563Z

Agenda
PeerDAS Breakout Room #1 · Issue #1059 · ethereum/pm · GitHub
Moderator: @hwwang
Notes & chat log
PeerDAS Breakout Room notes - Google Documenten
Recording
Title: AllWalletDevs___call__32___April_16__2025
Category: Protocol_Calls___happenings

Author: system
Date: 2025-03-19T15:54:07.162Z

AllWalletDevs, call #31, April 16th, 2025

Apr 16, 2025, 17:00 UTC
Duration in minutes : 60
Recurring meeting : true
Occurrence rate : monthly
https://allwallet.dev

Agenda

TBD

Other comments and resources
The zoom link will be sent to the facilitator (please fill in the email and telegram)
Facilitator email: sam.wilson@ethereum.org
Facilitator telegram: @SamWilsn
EDIT to trigger the bot
GitHub Issue