Avsnitt
-
EIP-7702: Set Code for EOAs
EIP-7702 adds a new transaction type that permanently sets the code for an Externally Owned Account (EOA).
Authors: Vitalik Buterin, Sam Wilson, Ansgar Dietrichs, lightclient.Resources:
-----------------
- EIP-7702 SpecificationPresentation:
-----------------
- Ethereum Pectra Mainnet Launch LivestreamPlaylists:
-----------------
- Pectra PEEPanEIP Playlist
- General PEEPanEIP PlaylistFollow on Twitter:
--------------------------
- Guest Speaker: Anders Kristiansen
- Host: Pooja Ranjan
- Coordination: Vaelyn
- Edited by: AkashTopics Covered:
-------------------------
00:00 - Quick Recap
00:25 - PEEPanEIP Intro
00:40 - Introduction
01:04 - About EIP-7702
01:57 - Anders Introduction
03:27 - Presentation on EIP-7702
03:44 - What is EIP-7702?
05:22 - Motivation and Rationale
09:28 - How it works
16:40 - Before and After EIP-7702
17:22 - Implementation Challenges
27:48 - Success Stories & Ecosystem Adoption
28:57 - Additional Links & Resources
29:01 - Presentation End
29:46 - Q&A Section
29:59 - What does EIP-7702 bring?
34:31 - Is EIP-2718 modified for EIP-7702?
35:30 - What should developers keep in mind while using this proposal?
40:11 - Rapid Fire Section
44:46 - Closing Words-------------------------
#EIP7702 #Pectra #Ethereum #PEEPanEIP -
Agenda: All Core Devs - Consensus (ACDC) #156, May 1 2025 · Issue #1490 · ethereum/pm
-
Saknas det avsnitt?
-
All Core Devs - Execution (ACDE) #210, April 24 · Issue #1462 · ethereum/pm
-
All Core Devs - Consensus (ACDC) #155, April 17 2025 · Issue #1434 · ethereum/pm
-
Deep Funding
Deep Funding is driving rewards to open source repos with a market of AIs as the engine and humans as the steering wheel.Useful Links:
----------------------
- Deep Funding Official Website
- Join the Deep Funding JuryRecent EPD Episodes:
---------------------
- Octant V2
- Open Source Observer
- Karma GAPTopics Covered:
-------------------------
00:05 - Quick Recap
00:35 - EPD Intro
00:42 - Starting words
00:59 - About Deep Funding
02:11 - Sejal Introduction
03:52 - Devansh Introduction
07:08 - Project Overview by Devansh
09:46 - What makes Deep Funding unique
16:15 - Key participants and their roles
25:49 - Collaboration with other projects
31:58 - Success matrix for first Deep Funding round
34:36 - How Deep Funding will support less visible projects
39:36 - How anyone can contribute to Deep Funding
41:23 - What’s next for Deep Funding
46:33 - Closing wordsFollow on Twitter:
--------------------------
- Deep Funding
- Devansh Mehta
- Sejal Rekhan
- Pooja RanjanOther Resources:
--------------------------
- Playlist 1
- Playlist 2
- Playlist 3
- Playlist 4
- Playlist 5
- PEEPanEIP PlaylistOfficial Websites:
--------------------------
- Ethereum Cat Herders
- Deep Funding--------------------------
#DeepFunding #funding #ethcatherders #ethereum -
All Core Devs - Execution (ACDE) #209 · Issue #1414 · ethereum/pm
-
Karma GAP
Karma GAP is an on-chain accountability protocol that enables grantees to build onchain reputation, receive more funding, and allows funders to hold them accountable and measure impact.Useful Links:
----------------------
- Karma GAP Official Website
- Karma DiscordRecent EPD Episodes:
---------------------
- Octant V2
- Open Source ObserverTopics Covered:
-------------------------
00:05 - Quick Recap
00:31 - EPD Intro
00:38 - Episode Introduction
01:40 - About Karma GAP
02:46 - About Mahesh Murthy
05:58 - Presentation
06:48 - Problems
09:07 - Solution
10:42 - Projects on Karma GAP
16:26 - Karma GAP Demo
22:53 - End of Presentation
23:13 - Mahesh on Web3 transparency
26:14 - Key matrix to initiate summary for grants
28:03 - How to add multiple repositories in GAP?
29:51 - Team feature on Karma GAP
30:27 - Preventing data manipulation
32:49 - Reputation Portability
36:14 - What is a Public Good Project?
38:04 - Key points for Public Good funding rounds
40:12 - Projects Karma GAP wants to collaborate with
41:53 - Impact measurement for grant providers and receivers
44:07 - Mahesh’s message and community call-to-action
44:48 - Closing words by PoojaFollow on Twitter:
--------------------------
- Karma
- Mahesh Murthy
- Pooja RanjanOther Resources:
--------------------------
- Playlist 1
- Playlist 2
- Playlist 3
- Playlist 4
- Playlist 5
- PEEPanEIP PlaylistOfficial Websites:
--------------------------
- Ethereum Cat Herders
- Karma GAP--------------------------
#ethereum #karma #KarmaGAP #ethcatherders -
Octant V2
Octant is built to advance the understanding and practice of decentralized governance, promote community engagement, and support public goods projects in the Ethereum and Web3 ecosystems. Octant is now evolving to scale with Octant V2.Useful Links:
----------------------
- Octant Official Website
- Octant DiscordTopics Covered:
-------------------------
00:05 - Quick Recap
00:35 - EPD Intro
00:41 - Introduction
02:44 - James Introduction
05:49 - Presentation on Octant V2
09:26 - Problems
10:03 - Octant Vision
10:11 - Value Prop
12:03 - Give your token purpose
12:38 - The Octant Model
16:10 - Basket token/Sustainability pool
17:48 - Impact Bond
21:10 - Presentation End
21:53 - Basic difference between Octant V1 and V2?
23:52 - Who are the key participants and what are their roles?
26:06 - How do we make sure Ethereum’s public good projects are getting long-term funding?
28:45 - How does Octant leverage DeFi tools to benefit individuals?
30:33 - What is needed to scale participation in Octant V2?
31:57 - Is there a way to accommodate newcomers?
32:50 - What is the next milestone after Octant V2?
34:25 - What makes Octant unique in public good funding?
35:29 - Ideal example to participate in public good funding?
37:27 - What tools will Octant use to measure impact?
38:59 - Biggest challenge in scaling Octant V2?
40:11 - Message to the community by James
40:45 - Closing wordsFollow on Twitter:
--------------------------
- Octant
- Pooja RanjanOther Resources:
--------------------------
- Playlist 1
- Playlist 2
- Playlist 3
- Playlist 4
- Playlist 5
- PEEPanEIP PlaylistOfficial Websites:
--------------------------
- Ethereum Cat Herders
- Octant--------------------------
#ethereum #Octant #OctantV2 #ethcatherders -
Open Source Observer
Open Source Observer (OSO) is a free analytics suite that helps funders measure the impact of open source software contributions to the health of their ecosystem.Useful Links:
----------------------
- Open Source Observer WebsiteTopics Covered:
-------------------------
00:05 - Quick Recap
00:26 - EPD Intro
00:33 - Starting words by Pooja
01:30 - About OSO
02:12 - Carl Introduction
03:42 - Rohit Introduction
05:10 - Presentation Start
34:23 - Presentation End
35:33 - Q&A
47:51 - Final message to open source community by Rohit
48:34 - Final message to open source community by Carl
50:42 - Closing words by PoojaFollow on Twitter:
--------------------------
- Open Source Observer
- Rohit Malekar
- Carl Cervone
- Pooja RanjanOther Resources:
--------------------------
- Playlist 1
- Playlist 2
- Playlist 3
- Playlist 4
- Playlist 5
- PEEPanEIP PlaylistOfficial Websites:
--------------------------
- Ethereum Cat Herders
- Open Source Observer--------------------------
#ethereum #OSO #opensource #ethcatherders -
All Core Devs - Consensus (ACDC) #154 · Issue #1399 · ethereum/pm
-
All Core Devs - Execution (ACDE) #208 · Issue #1374 · ethereum/pm
-
EIP-7870: Hardware and Bandwidth Recommendations
System recommendations for Validators and Full nodes.Resources:
-----------------
- EIP-7870
- DiscussionUseful Links from Meeting:
-----------------
- YouTube VideoPEEPanEIP Playlists:
-----------------
- Pectra PEEPanEIP Playlist
- PEEPanEIP PlaylistFollow on Twitter:
--------------------------
- Kev - Mason
- Parithosh Jayanthi
- Toni Wahrstätter
- Pooja Ranjan
--------------------------Edited by: Akash Kshirsagar
Topics Covered:
-------------------------
00:00 - Quick Recap
00:38 - PEEPanEIP Intro
00:51 - Introduction
01:11 - About EIP-7870
02:28 - Kev Introduction
02:51 - Parithosh Introduction
03:09 - Toni Introduction
04:30 - Presentation on EIP-7870
16:23 - End of Presentation
16:43 - Q&A Section
17:25 - Why do we need to document it as an EIP-7870? What motivated you to propose this EIP?
19:42 - What are your thoughts or response to a FEM comment - rather than publishing an EIP can be actively maintained as a list that has specs and examples of hardware that currently fit that requirement?
21:41 - How did you determine the recommended hardware and bandwidth specifications for different Ethereum nodes? Was there any benchmarking process used to validate these recommendations?
32:37 - Would providing a range as a recommendation instead of a fixed number encourage more solo stakers, considering hardware costs are a key factor?
34:47 - Would you say if any client-specific optimizations could reduce hardware requirements for certain node types?
36:03 - Are you aware of any EIP where EIP-7870 is considered under the “Required” section?
39:35 - Would you be okay moving this proposal with a normal EIP track and have it in “Final” status?
41:12 - As a new EIP Author, how was Kev's journey?
42:38 - How long will these specs remain valid?
44:54 - How soon will this proposal move to final? Are there any plans and revisions before final?
47:11 - Call to action by Toni
47:54 - Call to action by Parithosh
50:10 - Rapid Fire Round
50:19 - Rapid Fire Round with Kev
51:21 - Rapid Fire Round with Parithosh
53:32 - Rapid Fire Round with Toni
55:00 - Closing Words by Pooja-------------------------
#EIP7870 #Ethereum #PEEPanEIP #staker -
Consensus-layer Call 153 · Issue #1356 · ethereum/pm
-
ERC-7527: Token Bound Function Oracle AMM
Interfaces that wrap FT to NFT and unwrap NFT to FT based on an embedded Function Oracle AMM.Resources:
- EIP-7527
- Discussion
- Ramble On-Chain Pricing Mechanism
- PresentationOther Resources:
- Economics Paper
- On-Chain Pricing
- PremiumDAO
- PremiumDAO TwitterUse Cases:
- WrapCoin
- WrapGM
- WrapCoinLab
- AgentBallRelated EIP:
- ERC-7615PEEPanEIP Playlist:
- PEEPanEIP PlaylistFollow on Twitter:
--------------------------
- Lanyin Zhang
- Pooja Ranjan
--------------------------Edited by: Akash Kshirsagar
Topics Covered:
-------------------------
00:00 - Episode Recap
00:25 - Intro
01:14 - About ERC-7527
01:59 - Lanyin Zhang Introduction
04:29 - Presentation Starts
04:40 - What is ERC-7527?
06:06 - Motivation
07:51 - Overview of On-Chain Asset Pricing
08:47 - AMM Curves
10:58 - Bonding Curve
14:36 - Auction Mechanisms
17:49 - Introducing ERC-7527
19:59 - ERC-7527 Pricing Mechanism
22:27 - Specification
29:15 - Advantages of ERC-7527
33:42 - Application & Use Cases
36:22 - Use Case
37:40 - After Presentation
38:11 - Q&A
38:33 - How is the Use Case of This Proposal Different From Custodial Wallet Providers?
42:16 - How Can ERC-7527 Integrate With Existing DeFi Protocols Like Lending Platforms, Decentralized Exchanges, or NFT Fractionalization?
44:54 - What Security Measures Are in Place to Prevent Manipulation, Reentrancy Attacks, or Oracle Exploits?
47:32 - What Kind of Impact Will ERC-7527 Bring to NFT, DeFi, etc.?
49:27 - Rapid Fire Section
51:15 - Closing Words by Pooja-------------------------
#ERC7527 #Ethereum #PEEPanEIP #Token #NFT -
EIP-7691: Blob Throughput Increase
Increase the number of blobs to reach a new target and max of 6 and 9 blobs per block respectively.Resources:
-----------------
Presentation: Google SlidesOther Resources:
- EIP-7691
- DiscussionUseful Links from Meeting:
- Contribute to Xatu Data
- Mainnet Client Split
- Formalize Hardware RequirementsVideo Playlists:
- Pectra PEEPanEIP Playlist
- PEEPanEIP PlaylistFollow on Twitter:
--------------------------
- Sam Calder-Mason
- Parithosh Jayanthi
- Toni Wahrstätter
- Pooja Ranjan
--------------------------Edited by: Akash Kshirsagar
Topics Covered:
-------------------------
00:00 - Quick Recap
00:27 - PEEPanEIP Intro
00:41 - Introduction
01:20 - About EIP-7691
02:28 - Parithosh Introduction
02:48 - Sam Introduction
03:12 - Toni Introduction
03:43 - Presentation Start
03:43 - Presentation by Parithosh
03:58 - Why Scale Blobs?
05:28 - What Are the Blockers?
06:51 - Non-finality Events
08:31 - Devnet Setup
10:40 - Meme by Parithosh
11:06 - Learning
15:06 - Conclusions
18:27 - EIP-7742 & EIP-7840
19:31 - Presentation by Toni
21:44 - Reorg Share Over Time Chart
24:30 - Presentation by Sam
24:32 - Finalizing EIP-7691
24:44 - Deciding Parameters
25:07 - EIP-7691 Impact
25:36 - Home Stakers
26:22 - Community Contribution to Xatu
27:11 - Post: Block Arrivals
27:37 - Why 6/9?
30:17 - Presentation End
31:48 - Post Presentation Talk
33:19 - Q&A Section
33:29 - Reorg Chart Related Question - Does the Number of Participants Affect the Reorg Chart in Any Way?
35:16 - Do We Expect EPBS and ILS Proposals to Streamline Better?
35:58 - Are There Any Risks or Concerns With Increasing Blob Throughput? If So, What Are They, and How Does EIP-7691 Mitigate Them?
37:45 - What Monitoring Tools and Data Indicate the Network Can Safely Scale Up?
40:34 - Are There Any Bounties for Tool Providers?
41:11 - How Does This Proposal Fit Within Ethereum’s Long-Term Scaling Roadmap, Especially With Upcoming Improvements Like PeerDAS? Should Infrastructure Providers Start Preparing for Further Data Availability Upgrades?
44:28 - What, if Any, Changes Should L2 Teams and Infrastructure Providers Make to Take Advantage of Increased Blob Throughput?
47:39 - How Can Anyone Contribute to the Discussion?
49:43 - Rapid Fire Section
50:04 - Rapid Fire With Parithosh
52:14 - Rapid Fire With Sam
53:33 - Rapid Fire With Toni
55:07 - Pooja Closing Words-------------------------
#EIP7691 #Ethereum #PEEPanEIP #Pectra -
EIP-7706: Separate gas type for calldata. Create a separate basefee and gaslimit for calldata
Resources:
- EIP-7706
- Discussion-----------------
Other Resources:
Playlist 1
Playlist 2
Playlist 3
Playlist 4
Video 1
Video 2
Video 3
Video 4
Video 5-----------------
PEEPanEIP - YouTube PlaylistFollow at Twitter:
--------------------------
Vitalik Buterin - Twitter
Pooja Ranjan - Twitter
--------------------------Edited by Akash Kshirsagar Twitter
Topics covered:
-------------------------
00:00 - Quick Recap
00:25 - PEEPanEIP Intro
00:39 - Starting Words
01:11 - About EIP-7706
02:52 - Vitalik Introduction and current status
04:25 - Presentation Start
12:26 - Presentation End
12:32 - Q&A
12:43 - Should we push for SSZ transactions (EIP-6493) or at least SSZ payload (EIP-6404) in beacon block to keep ideas like multi-dimensional gas less convoluted to sort of bookkeep in the protocol?
14:22 - How can the framework separate the standardized fee components from the L2-specific logic (for predicting L1 data costs)?
15:42 - Can multi-dimension gas allow us to widely increase gas limit?
18:43 - Follow-up on L2 topic: How can multi-dim gas tie with the EXECUTE proposal?
19:51 - How EIP-7623 and EIP-7706 interact, and what are the combined impacts?
22:37 - What is the key milestone to determine that EIP-7706 is ready for mainnet upgrade?
27:20 - Implementing of EIP-7706 would require updates to blob base fees instruction that was outlined with 7516?
28:26 - Is EIP-7706 long-term scaling or just an efficiency solution?
30:03 - Why Vitalik believes that this benefits Ethereum?
32:38 - Is there any risk in balancing of gases?
34:05 - How EIP-7706 balances efficiency and affordability?
36:48 - How do we keep pushing limits as improvements happen on the hardware space?
38:29 - How EIP-7706 will affect transaction cost?
39:47 - Are there any security considerations while documenting EIP-7706?
41:20 - When can we expect EIP-7706 on the mainnet?
42:56 - Vitalik's suggestion on coordination part.
44:40 - Are there any areas where the client team needs additional implementation support?
48:08 - Rapid Fire Round
50:57 - Final message from Vitalik
51:43 - Pooja closing words-------------------------
#EIP7706 #Ethereum #PEEPanEIP #vitalikbuterin -
All Core Devs - Execution (ACDE) #207 · Issue #1346 · ethereum/pm
-
EIP-7805: Fork-choice enforced Inclusion Lists (FOCIL) Allow a committee of validators to force-include a set of transactions in every block.
Resources:
-----------------
Presentation: Google Slides
-----------------
Other Resources:
- EIP-7805
- Ethereum Magicians
- Eth Research-----------------
Useful links from meeting:
- HackMD by Jihoon: HackMD
- GitHub Consensus Specs
- Tweet by Arindam Singh
- Tweet by Jihoon
- Tweet by Terence Chain
- Nethermind PR: Nethermind PR
- Meet FOCIL
- YouTube Video-----------------
PEEPanEIP - YouTube PlaylistFollow at Twitter:
--------------------------
Thomas Thiery (@soispoke)
Julian Ma - Twitter
Pooja Ranjan - Twitter
--------------------------
Edited by Akash Kshirsagar TwitterTopics covered:
-------------------------
00:00 - Quick Recap
00:21 - PEEPanEIP Intro
00:34 - Starting Words
00:56 - About EIP-7623
02:13 - Julian Ma Introduction
03:05 - Thomas Thiery (@soispoke) Introduction
05:15 - Presentation Start
05:33 - Goals of FOCIL
06:08 - Why do we need FOCIL?
06:49 - FOCIL: Why now?
08:09 - Basic Inclusion List Idea
11:06 - IL-Boost/Uncrowdability
03:08 - FOCIL Summary
14:04 - Presentation End
14:11 - Q&A
14:16 - What is the basic difference of EIP-7805 & EIP-7547: Inclusion lists?
19:05 - Is block proposer gets 16 ILs each from one IL committee member and it has to include all the transaction from these lists?
19:54 - What prevents putting a transaction from a private mempool into an Inclusion List? would it just get voted down by committee?
21:40 - FOCIL for scaling?
26:45 -Currently it is whoever pays the most priority fee, right?
30:42 - What is the status of compatibility for FOCIL with respect to proposal such as 7702, epbs, PeerDAS?
33:03 - How FOCIL prevent Multi slot MEV?
36:44 - According to the authors, what is the biggest tradeoff or challenge in bringing the proposal into the next upgrade?
39:50 - What is the best way to charge fees?
44:16 - Is there any updates from IL side?
46:38 - Any matrix to keep track on this proposal?
49:11 - Where we are in the client implementation?
52:06 - FOCIL in Fusaka or in Glamsterdam?
55:13 - Rapid Fire
55:44 - Julian Ma - Rapid Fire
56:08 - Thomas Thiery (@soispoke) - Rapid Fire
58:08 - Message by Thomas Thiery (@soispoke) to the community
59:33 - Message by Julian Ma to the community
59:52 - Pooja's closing words-------------------------
#EIP7805 #Ethereum #PEEPanEIP #FOCIL -
EIP-7623 proposes adjusting the calldata cost to reduce the maximum possible block size and its variance without negatively impacting regular users. This is achieved by increasing calldata costs for transactions that predominantly post data.
Resources:
-----------------
- Presentation: Google Slides
- EIP-7623
- Analyzing EIP-7623
- EIP-7623 Post-4844 Analysis
- On Block Sizes, Gas Limits, and Scalability
- Ethereum 2077
- DappCon talk: "I like big blocks, and I cannot lie" YouTube
- Episode by @letsgetonchain:Twitter-----------------
YouTube Playlist 1
YouTube Playlist 2
YouTube Playlist 3
YouTube Playlist 4Follow at Twitter:
--------------------------
Toni Wahrstätter - @nero_eth
Pooja Ranjan - @poojaranjan19
--------------------------Edited by Akash Kshirsagar @oceansofmilk
Topics covered:
-------------------------
00:00 - Quick Recap
00:22 - PEEPanEIP Intro
00:36 - Starting Words
01:01 - About EIP-7623
02:28 - Toni Wahrstätter Introduction
04:10 - Presentation Start
04:20 - About EIP-7623 by Toni Wahrstätter
05:28 - What is the max block size?
07:44 - What is size?
11:13 - Gas Limit
13:08 - Calldata
20:07 - EIP-7623
27:04 - Specs
31:01 - Maximum block size in MiB after Pectra
33:05 - Analyses and useful links
34:08 - Authors contact details
34:50 - Presentation End
35:57 - Q&A
36:02 - Is Floorcost will apply all type of transection or for limited group?
39:21 - Is there any changes which is suggested by the community?
44:24 - Is there any challenges in adoption of this EIP?
47:23 - What will be the impact of EIP-7623 on rollups?
49:34 - Rapid Fire
51:33 - Toni Wahrstätter final message to community
52:48 - Pooja's closing words-------------------------
#EIP7623 #Ethereum #PEEPanEIP #calldata -
A Confirmation Rule, within blockchain networks, refers to an algorithm implemented by network nodes that determine (either probabilistically or deterministically) the permanence of certain blocks on the blockchain. A Fast Confirmation Rule relies on synchrony conditions but provides a best-case confirmation time of 12 seconds only, greatly improving the latency of the FFG Finalization Rule.
Resources:
-----------------
- Presentation: Google Slides
- Paper
- Consensus Specs
- Talk on A Fast Confirmation Rule from Devcon 2024: YouTube-----------------
PEEPanEIP PlaylistFollow at Twitter:
--------------------------
Roberto Saltini - @robsaltini
Pooja Ranjan - @poojaranjan19
--------------------------Edited by Akash Kshirsagar @oceansofmilk
Topics covered:
-------------------------
00:00 - Quick Recap
00:22 - PEEPanEIP Intro
00:36 - Starting Words
02:24 - Roberto Saltini Introduction
03:46 - Presentation Start
04:02 - What is Confirmation Rule?
04:06 - What is Canonical Chain?
06:50 - Why do we need the Fast Confirmation Rule?
10:05 - Quick recap of Gasper
15:25 - A Fast Confirmation Rule algorithm for LMD-GHOST
32:43 - A Fast Confirmation Rule LMD+FFG = Gasper
40:14 - There is more to Safety: Monotonicity
47:04 - Initial Experimental Results
49:00 - Last Slide - QR for Paper and useful links
49:22 - Presentation End
49:46 - Q&A Session
49:55 - Benefits and Use cases
52:49 - Does assumption act as a blocker?
54:00 - Expected timeline for deployment on mainnet
56:30 - Can this proposal be implemented on the mainnet in Fusaka?
57:57 - Rapid Fire Session
59:19 - Closing words by Pooja Ranjan-------------------------
#AFastConfirmationRule #Ethereum #PEEPanEIP - Visa fler
