-
Notifications
You must be signed in to change notification settings - Fork 37
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
EIP Editing Office Hour Meeting 46 #363
Comments
@poojaranjan Hi Pooja, could you add ethereum/ERC#660 please? Many thanks. |
Hey @poojaranjan , could you please add ERC#674 for this meeting? 🙈😅 Sorry for the late! |
The Editor is unable to attend today's meeting. I have updated the agenda to reschedule the meeting for two weeks starting today. Feel free to add your comments for review, which will be done asynchronously this week |
While trying to "finalize" ERC-4337, we came into the conclusion that while some part of it is stable (the on-chain contract interfaces), some other parts (rpc calls and off-chain aggregation handling by bundlers) are not.
Once these PRs are added, we can extract their content from ERC-4337 itself. |
Hi @poojaranjan , could you please add ethereum/ERCs#663 for this meeting? Thank you! |
Hey @poojaranjan , please add ethereum/ERCs#680 for the next meeting. Thank you. |
Hey @poojaranjan , can you please add merging of ERC-7699 -ethereum/ERCs#399 (review) |
Hello @poojaranjan , Could the ERC-7776 please be added to the next office hours (All the reviews have been corrected +2 weeks ago), re-reviewed if necessary and merged if possible? I would highly appreciate it🙏🏼🙏🏼🙏🏼. |
Date & Time
Tuesday, Oct 29th
15th, 2024 at 14:00 UTCLocation
Zoom: TBA on EthCatHerders Discord #eip-editors
Recording: https://www.youtube.com/playlist?list=PL4cwHXAawZxqnDHxOyuwMpyt5s8F8gdmO
Agenda
To
Final
To
Last Call
TBA
To
Review
EIPs
TBA
ERCs
[From
Stagnant
]TBA
Misc.
TBA
To
Draft
EIPs
TBA
ERCs
Open Q&A
Next meeting date/time?
Other details
(Drop the Pull Request number to be added to the agenda.)
The text was updated successfully, but these errors were encountered: