RPC Standards #20

Transcript

Chase Wright: Hey, everyone. I'm gonna ping Boma, see if they're joining or not. They usually host, so…

I guess we can just get started, the harder, let me see here… Let's see… So, I guess before we get started, does anyone have anything they want to bring up in addition to the agenda that… Bomer wrote down. I'll take that as a no. The first one is about versioning information. I know that there's… some asks for us to, start doing version releases. I think we can probably start doing that relatively soon. There's a lot of… outdated and open PRs, though, that it would be really nice to get cleaned up and figure out what the

first version release should look like. Does anyone have any thoughts on that? Okay, I guess not. I went through some of these. I think most of these PRs Either… Need to get, closed? Or… The maintain… like, the person who submitted them need to come in and resolve some of their conflicts? I don't… All the stale ones from, like, 23? They seem to just… not be… no one seems to care anymore. I don't really have any insight into any of these. Like, this one is still interesting, I think.

Yeah, I don't know, this one might cause… some issues. Does anyone have any opinions at all?

Tullio Canepa: Oh, yeah. Good afternoon, I'm Tulio, and yeah, I think, It depends on what… We want to do… towards… The… the client of this… API. I mean, strictly speaking, we should still support such kind of… methods, at least for… pre-merge blocks. But then, yeah, it's… probably no one cares, really cares. So yeah, it's a bit, I have an… have an issue between being, strict in terms of At the interface level, or being… Let's see… Practical, yeah?

Chase Wright: Yeah, actually, and you know, that's a good point, because you know. the RETH team brought up this PR. And, I think the ETHREX guys have the same problem, and… Correct me if I'm wrong, I think you guys on the Erigon side, you… you… you fixed this just recently.

Tullio Canepa: Yes, yes, we did, we did recently.

Chase Wright: Yeah. So, yeah, it's kind of a double-edged sword, because, like. As you said, those methods are valid for, like, pre-merge Data, but, like… Does anyone actually care? I think that is… that is one of the main questions, because I know that… I think it's… in protocol, like, the nodes don't even need to save the uncle blocks, so, like, having the methods… That are non-deterministic. Anyway, seems counterproductive. Because, like, we can't really write tests for them. And the nodes aren't required to keep the uncles anyway. So…

Tullio Canepa: Yeah.

Chase Wright: Fair enough. I don't know, it might make sense…

Tullio Canepa: Yeah, it's probably just a technical debit, and that's it.

Chase Wright: Yeah, yeah, I agree with that. I don't really… I don't really have a strong opinion on it. This… this PR seems good. I don't know, it's just a wrapper to the main… so it's async. I don't have any problems with this particular PR. It seems fine, it doesn't really do anything. Unfortunately, I'm not… I'm not an approver, though, so I can't do anything about it. The other ones are all, like I said, these are all incredibly old. They need… fixes… I don't think we're gonna make a decision on any of these… anytime soon. Standardization of the TX pool is… is a good one. This probably needs… Need some eyes, you probably need to…

work on this at some point. I think adding tests… to this… Fo… Fixing the standard and putting tests, probably a good… next step for this PR, but it has conflicts, And I think we need to… finalize… what version 1's gonna look like, which I know Bowman was working on, but I… she's… she's not here, so… maybe we'll have to push that conversation out till the next meeting. Yeah, and that's pretty much all I got. I know that, I do have… I have this PR, which is in draft. This is an ask from the Pandas. They want a, testing Build BlockV1 RPC method. Marius did a bunch of work on Geth to support this method. The…

The standard is defined in this PR, and there's lots of conversation here. I'll post this in the, In the chat, if I can find it. Okay, here's the chat, so I'm gonna post this. So, if anyone has any input on this particular… RPC method, please… Please provide some feedback. I've started putting the spec into YAML format in this PR, which I can paste here. And… Everything is working, in the Go Ethereum fork, that this… PR is Retherencing. Unfortunately, I still need to get Marius to review the PR, and we can get this merged into Geth, and then once that's there, then, Geth will have support for this particular method. I don't know… Erigon…

can support something similar, that would be great.

Tullio Canepa: I need to take a look, but… Yeah, I think… I think so, but I will take a closer look.

Chase Wright: Yeah, apparently this is supposed to make it much easier for the Pandas to… to test, Different, like, forks and building special blocks and stuff. So, yeah, if you could take a look, that'd be great. Yeah, that's pretty much it, unless anyone has anything else they want to talk about. Oh, there's also the, What was it? The, Whenever… this… I think this is fine, but we need a maintainer to rerun it, so…

Yep. Alright, that's it. I don't have anything more, and it doesn't sound like you guys have much else either. Cool. Tulio, I know you sent me a message in Discord, so, we can chat, Thank you.

Chanderprakash Sharma: Oh, hi.

Chase Wright: Yeah, bye.

Chanderprakash Sharma: Now, historic…

Chase Wright: Sorry, you're muted again.

Chanderprakash Sharma: Hi, sorry, sorry for interrupting you.

Chase Wright: No, it's okay, what's up?

Chanderprakash Sharma: Yeah, so yeah, you guys are discussing about RPC endpoints, PRs, so I'm, like, not new to the Ethereum, I am working in Ethereum research on Layer 2 stack. But, right now, I want to participate, too, in, co-development. So, could you, please guide, like, how I can help you guys to further push the Ethereum forward? Where I can contribute meaningfully.

Chase Wright: Yeah, I mean… I think… I think… So, some of the… some of the struggle right now we're having is… is… the… Maintainers, are very, very busy. if we could get more… more eyes on some of these PRs for comments, either… Closing, or… Reviews, comments, feedbacks, anything we could get. on these, there are… Some, there are some, like, wish lists. I know one of the things that we want to do is we want to start writing tests for the debug namespace. Because there's only a handful of them for, like, debug, get, raw, whatever. We want to try to start standardizing on, like, tracing and things like that. So if you have any insight into,

like the opcode tracer, or call tracer, things like that. We really want to get some of that standardized. Another thing that was recently brought up is the, The debug set head. method. It's not currently standardized across the clients. So, like, Nethermind has a different name for it. I don't think Erigon supports it. And then, like, you know, GETH requires the block number in hex, Reth requires it in decimal, That's something that has been brought up, that we'd like to standardize the debug set head, so we can unwind the execution clients, via the API. If that's something you could look into, that would… that would be helpful. And other than that, I guess you could come into the ETH R&D Discord in the JSON RPC channel and

and help… Help organize there as well.

Chanderprakash Sharma: Yeah, sure. Thank you, thank you for this. I would like, Prioritize these things that you mentioned, and, try to contribute meaningfully.

Chase Wright: Cool, thanks. Alright guys, I guess that's it. I don't have anything else, so… Let's chat offline. Have a good day.

Tullio Canepa: Okay. Have a nice day. Bye.

Transcript adapted from ethereum/pm, CC BY-SA 3.0.