EIPIP Meeting 117

Transcript

[Music] Hey, heat. Hey.

Heat. Heat. N. [Music] [Music] Hold [Music] on.

[Music] Hold on. [Music] Heat. Heat. [Music] Heat. Heat. N.

[Music] Heat. Heat. [Music] Oh, [Music]

hey. [Music] [Music] Hello.

[Music] Hey. Hey. Heat. Heat. [Music] Heat. Heat. N.

[Music] Heat. Heat. [Music] Oh yeah.

[Music] Okay, perfect. Well, uh, welcome everyone to meeting 117. Um, today we have what? One, two, three, four, five, six, seven things to talk about. Um, so this should be a pretty quick call. Um, we'll start with the um add Shanghai fork check for code access

list and EVM. So, what's going on with this one? Um, EIP 5027 is superseded is not supported. Um, so it looks like we can just close this. Um, the author will not be updating the CIP. Sound good? Yep. All right. Easy enough. Uh, got some typos to fix here. Um, can you paste this link? I can go. Oh, yeah.

Yeah. Nice. Okay. Yeah. So, what's going on with this one? 5081 typo. The choice. Yeah, seems a reasonable should be presumed. Sanction type. They're all finalized. Oh, I was the author. But that's not uh that's stagnant, right? Um it doesn't take a uh ERC it doesn't take an EIP IP uh IP meeting to review these things. No, I just think

they haven't been reviewed in a while. So PER puts them on the agenda. Oh, sure. Yeah. Yeah, I can author approved it. Uh I think I I'm okay with 50 A1. But uh do you usually prefer two different two EIPs in separate pull request or uh usually but for small things it really doesn't matter. Like the the only downside is that it'll ping all the authors at once. Yeah. Um uh yeah, I can approve for Yeah. Are you okay with both of these? Ignore. Yeah.

Yeah, I'm I'm okay. Yeah, I think they they would just uh need to like Yeah, every once in a while our editorial llinter changes and then it's bad old things break. Uh yeah. Yeah. But I'm okay with this. Cool. Yep. EIP1 spelling issues. Uhhuh. All right. Let's see what's going on here. Yeah. Okay. A good reason to transfer ownership is because the original author

no longer has time and then they have a good reason to transfer ownership is that the original author has time. Um, uh, the third one, the third one. So, sorry. Um, so 101. Let's change here. Yeah, we're on Sorry, we're on um fix spelling issue in heaps 9261. Yeah. Yeah. I have no uh preference.

You're free to merge them or reject them. Oh, that's EIP1. Okay. Um, yeah, that doesn't this one is like EIP1 definitely should be its own pull request, I think. And even so the Yeah, the it's not like that's not a a proper request. I think we can reject like changing the call to that. Yeah, these are all really really minor. Um yeah I mean and then I don't see that adding value either like it's grammatically correct for both and then changing one to another is like I don't know this is

clearly no value add yeah giving them feedback yeah a little Yeah. All right. So on to 9629 fix typos and complexity analysis section.

And these are probably actually typos. uh data complexity of the network aggregate. Yep, that's that's should belong to the the author, right? Uh it's probably got a final um or maybe not. Oh, it's because it's in in an assets file without actually modifying the um the proposal. So, the the bot can't figure it out. So it just throws it at at us.

Your bot is great. It's okay. Yeah. Like as as a fallback uh throw back to the to the to to to the editor group. That's great. Yeah. Yeah. Okay. In that case that will prove and then maybe maybe we should also add this to this bot scope like to let bot know uh asset EIP number should belongs to the same author.

Yeah exactly. Um fix duplicate and author but this VR is good. Should we repres? Yeah, I'm okay. Yep. Yeah, I think that's a good uh fix. Yeah, this is an and and that's certainly something that can be merged. Um and then dead links. I hate these. Oh, BIP 44 had a typo.

Interesting. This is in an older EIP. Yeah, totally makes sense. Yep. But that link should correctable. Yeah, but we should use the long form link instead if we're already editing it. And we should also add a link to BIP 32 and BIPS [Music]

Hm. Sure. Yeah. Comparing. There you are. How's that? Okay, cool. Oh, no worries. Okay.

Wait, did this get merched? Oh, you approved it after I was Okay, that's funny. Um, let's go back to this. Where are you being pulled? No, you're pulling into that one. That's not what I want.

Um, yeah. You know what? This really isn't that important. I'm not going to spend time on it. All right. So, then we have a call for input, which is uh allow links to the execution APIs. Um okay. So, we have a pull request here. Uh, 9809. Um, oh, that's you your call for input. Yeah. Yeah. Somebody opened this um p request allowing links.

Um, we want to restrict what kind of link? Uh, we just want to make sure that it has the um the commit hash in there. Oh, I think I'm in favor of links that EIP ERC allows. Yeah, I'm I'm also in favor of this one, too. I think it's important to be able to link to uh the definitions for API endpoints. So, yeah. So, this closes on July 6th. So if any other editors are are watching this after the fact comment on this please yeah I was just in favor. Okay perfect

yeah adding condition just make that in favor difficult so I just didn't favor now. Awesome. Uh yeah then we have um moving on to other discussions and updates. Uh so I've been working on for a while now the new version of the EIP website. Um all that's left to do before we switch over is clearing up the uh backlog of pull requests. So uh to that end uh Pua and I have been organizing these review blitzes. So they're longer form meetings where I try to get editors on and um just go through as many poll requests as possible. Um we haven't scheduled the

next one yet, but hopefully it'll be soon. Uh and then uh once we get the poll request numbers down to something reasonable, we can make the switch over to um the new version of the website. Yeah. Can you can I contribute? Oh, absolutely. Yeah. Yeah. Yeah. Yeah. Because I've been doing some SEO stuff and then I realized that uh some of the uh metadata tags could be improved so that they show up in different search engines and social media when they share additional information. I can do that. Yeah. Here I have um um what's that under? I am super happy.

This is completely server side rendered. So yeah, that was my problem with the other um I like that. Yeah, I like that. This is probably where you'll be contributing. If you're going to be working on SEO, um, sounds great. Yeah. And if you need help actually running the rendering and everything, just let me know and I can give you a hand with that. It's a little hairy. Um, but it's not it's not the end of the world.

Sounds great. Let me Yeah, let me book some time for myself to do this. I think this is going to be important. and thank you for uh for for keep being Sam. I was like, "Yeah, that's all like that what you always do. Uh thank you for the great work." And then um but yeah, that's just another day of Samuel Rosen. Oh, thank you. Um all right. Uh yeah, so we have a recording of the last year review blitz.

Uh there'll be another one coming up, so keep an eye out for that. Um that we have the status reporting. Oh wow. Good gender getting there. 24. It's awesome. Look, we're making a we're making an impact. That's that's good. Um, how many new drafts? Guess. Yeah, improving.

Yeah. So, we got five new core, five new ERC's. Yeah. Nice. Oh, yeah. I guess there's no new living. That makes sense. We finalized one of each for June, 10 in May. Wow. Nice. Making progress. Mhm. Cool. Um, is there anything else we needed here?

Um, inclusion stages. Wow, I love this visualization. This is great. Yeah. How do you how do you read this? That's my thing. So, blue is schedule for inclusion. Red is declined. Deferred. That's awesome. Yeah. Oh, deferred. Yeah. And then it's pulled out of the EIP itself. That's awesome. Yeah. Great job setting this up. This is this is great.

Um. Oh, so it shows the evolution of the fork over time as well. That's that's super cool. Yeah. No, that's that's awesome. Um, and then we have the relationship. Yeah, it would be even nice if uh if it will show the the relationship between these like if there is the same EIP moving from one stage to another stage it will visualize like there is a line from here to to the other one.

Oh, graph graph. That's nice. Are these are these dependencies? Nice. 7702 depends on Yeah. Yeah, that looks right. Yeah, that's neat. Yeah. Oh, this this deserves to be on the um uh athereum.org website. This is really really nice.

Oh, yeah. Yeah. Cool. Yeah, this is great. have a Can we have a like some kind of owner system or wondering like we can we as an editor group come up with the like things we really like in the features we really want to encourage in a EIP insights and then just like send them this is a the certificate of of of of reward or honor or prize that we as an order editor groups uh issued or grant for them to kind of uh uh just as a way to thank them, but also I think it would be an honor for for the volunteers who put their heart and soul

into building these. I'm not sure if there's anything set up, but uh I'm sure they'd appreciate it. Yeah, at least we can send an email and then put a little note. Yeah. Yeah, absolutely. Yeah, this is great. Is this page helpful? Oh, I can't I can't get to the There we go. Yeah. Yeah, I am going to do that right now.

Ah, or just share to the ad group uh Discord. Exactly. My uh Sam's favorite and I would say Victor's favorite. I like the graph. Insights inside.

This is nice upgrades. Cool. And then the authors. Yeah. So I think that's the end of the upgrading. Um we have the EIP editing office hour which I think is next week. Um and that's it. Um uh can I bring something up and show it to you? Yeah, of course. Um let me stop streaming.

Yeah. Uh so this is a um oh what what happens to my screen sharing? Okay let me try this. Um so this is the uh and weekend eithe news um but with AI support basically uh um I missed the time when we have weekly news and then so um a intern applied and then uh she uh was good so um we invite her to kind of create this experimental project to generate uh newsletters uh that's uh pulling it source from

different places just like it was hand curated in the past. Uh and this is a early version episode sample episode. Uh and of course we need to improve the quality down the road and then we need to add human to the loop. Uh but I I just want to show you the progress and uh also invite feedback. I mean that's awesome. I I I feel like writing summaries is one of the like huge strengths of AI right now. So yeah, I love this.

Great. Yeah. And then of course uh Sam, love your feedback. I'll share a private uh episode with you. Uh and then feel free to uh send your your feedback and then we'll keep improving it. Uh and also if you are watching a recorded version, uh feel free to ask me for uh for the private review and then soon we'll launch it to the public. you should be able to see it in GitHub or anything like we we think this is a valuable uh um infrastructure and then we are I I'm personally very sad to see it uh go uh but I think with AI we can make this happen and just imagine this could also happen to other than the mainet it could happen to other

significant projects and then they can use this to generate their own uh uh updates and then help people coordinate and collaborate. That's it. Awesome. Yeah, thanks for showing that. That that's really cool. Cool. Yeah, thank you. Thank you for uh hearing this is helpful. Shout out to the uh main contributor, Angela Lee. Great. I think that's it for today then. Um thanks for coming and uh to everybody watching the recording, thanks for watching the recording. We'll um see you next month. Take care.

Thanks. [Music] [Music] Hey.

Hey. Hey. Heat. Heat. N. [Music] Heat. [Music] Heat. [Music] Heat. Heat. N.

[Music] Hey.

Hey. Hey. [Music] down. [Music] Oh, hold on.

[Music] Oh yeah. Heat. Heat. N. [Music]