Repository navigation
EIPIP Meeting #132, Nov 18, 2026 #2288
Description
UTC Date & Time
Nov 18, 2026, 16:00 UTC
Agenda
Meeting Room: Zoom
| Issue | Deadline | Pending on |
|---|---|---|
| ethcatherders/EIPIP#414 | November, 04 2026 | Decision (Rough Consensus) |
Editors’ Discussion
- Website: Fix the Auto Stagnant Bot, which has never run in this repository ERCs#1952
- Status Update checklist for Authors & Editors: Editor's agreement
- to add this list to CONTRIBUTING.md
- to add 2-3 main points to bot's comment along with a ping to editors for review
- Keeper of Consensus: Nomination & vote
- AI in the EIP ecosystem ref: Comment
Updates on topics from earlier meetings
- Notes & action Items from EIPIP 131
- EIP Editing Office Hours
- Editors' availability -> add to the schedule
EIP Insight
Community feedback/update
- Project Showcase or feedback: if interested, please leave a comment.
- Devcon 8 India Community Hub: Luma
Call Series
EIPIP Meeting
Autopilot Mode
- Use autopilot (recommended defaults for this call series)
Duration
60 minutes
Occurrence Rate
monthly
Use Custom Meeting Link (Optional)
- I will provide my own meeting link
Display Zoom Link in Calendar Invite (Optional)
- Display Zoom link in invite
YouTube Livestream Link (Optional)
- Create YouTube livestream link
Activity
github-actions commentedon Oct 26, 2026
⚡ Protocol Call Resources:
🔗 Zoom: Custom meeting link (see issue description)
✅ Calendar: View | Add to Calendar
✅ Discourse: Discussion Topic
Cybercentry commentedon Nov 2, 2026
Hi @poojaranjan, could I please add: ethereum/ERCs#2117? Thank you, Leigh C.
garyyang-finchip commentedon Nov 3, 2026
Requesting a slot for three ERC PRs, if time allows:
ERC-8338: Token-Bound Executable Skills
ethereum/ERCs#1879
Status: new ERC (Draft), open since July 14, CI green, no merge conflicts. It has been in the review queue since Meeting #108.
@jochem-brouwer's review (Changes Requested) has been addressed in full: the unrelated erc-8419.md was removed, RFC 2119/8174 are linked, the external repository link and deployment pointer were removed from the assets, and normative keywords in Security Considerations were lowercased. Re-review has been requested.
Question for editors: is anything else blocking the merge as Draft?
ERC-8414: Token-Bound Task Tenders
ethereum/ERCs#2005
Status: new ERC (Draft), open since September 9, number assigned, CI green, waiting on a first editor review.
ERC-8419: Know-Your-Agent (KYA) Framework
ethereum/ERCs#2012
Status: new ERC (Draft), open since September 19, number assigned, CI green, waiting on a first editor review.
I can’t join live this time; happy to follow up on any feedback in the PRs. Thanks!
jochem-brouwer commentedon Nov 13, 2026
I want to agenda the topic of AI in the EIP ecosystem. I think we do not have to discuss adding
AGENTS.mdto the ecosystem ethereum/EIPs#12661 but I am not yet convinced if we should auto-merge documents which pass CI and pass the checks AI could do.My general fear is that if we write EIP documents by AI and also review them by AI, then these root documents are all written by AI. We should move carefully here. From my perspective these documents are used to communicate ideas (specifications) with the community and also serving as an archive/memory to document why we did specific things. Documents written by AI are clean and convincing, but could not be what the author originally wanted. It is thus important that we as ecosystem as whole figure out what we as community want and collaborate with the authors to reach that point. If this is all done by AI, then the future concepts are not written by us, but only by AI, and this might not converge to the similar specification if we would only do this by humans. The world is moving fast and it is evident we should accelerate our process, but this should still lead to equal results (yet faster).