eth_multicall Meeting, Feb 3, 2025
eth_multicall and eth_simulate Meetings · 3 Feb 2025 · 5:43
A meeting of the developers working on eth_multicall and its successor eth_simulate, held on 3 February 2025. Client and tooling teams compare implementations and work on the specification for simulating transactions. This meeting covers a client implementation update and the spec for eth_simulateV2.
Topics
From eth_multicall and eth_simulate Meetings, hosted by Ethereum Foundation.
Transcript
do we have any updates uh so we are working on prototyping this tracing part uh Rockit is a bit uh loaded so I recruited one of the interns and we are like uh partly there but still not fully there I expect we will be fully there in in this week I can give you a PR but it's like I said partly there I got interns working on it uh yeah we have a intern working on it currently but it's a really good internship task because it's pretty well
defined and uh mostly can be it's mostly about refactoring and making this more um uh reusable with different kind of tracing methods uh so it's yeah it should be fine it's it's looking good at the moment uh the progress he started uh me last week and I expect him to finish like this week sounds good that is for both of the tracers or just are you focusing on one of the uh both because it will be more or less the same it will be just passing a different different Tracer into it so it should be very reusable pattern I guess hasn't look in the tracing yet
no I I don't have an update I've been meaning to look at the estimate gas but um been quite busy with uh ptra updates so not busy with the gets vulnerability no uh not so much the others were busy with that one yeah it's working on that it simate now Gabriel if you're talking you're on mute I'm sorry uh for pzo we are aiming to have the initial implementation passing the hi
test we have uh the majority of Test passing to I think around 15 or 16 tests failing so I have to look into to see uh what's the issue with the ini implementation but yeah progressing that that sounds really good if you have only 16 failing that's almost most of them passing and are you getting the same hash as G is getting or is the hash different BL hash yeah the hash is different um I did change something in g i I need maybe to discuss with someone uh and then the hatches match it um but yeah
uh the hatches don't match exactly with uh my implementation but yeah if if we pass the parent to the next block in G then it matches so uh I need to to investigate that as well but like doing that change like uh I got like 16 16 17 errors failing yet so yeah the parent hash um yep the hash and the parent hash um is the head yeah I I think gap's implementation doesn't pass like the hash the next block or something I'm I'm not I'm not quite sure
interesting so it's not counted into the hashing of the next block yeah okay I can uh look into that but if I if I pass the the return of the the block simulated to the next block then the hashes match in gaav okay can you uh send over your patch uh yeah yeah yeah definitely great I wonder if that would fix the issues with nether mind not matching the hashes as well oh might be but might be something else too yeah it's probably needed but not sure if enough
but that would be really nice if you can get those two clients match already maybe we can compare uh my hashes as well with the mine um to see they matching yeah you should be able to run nethermind test as well with with Hive MH yeah can do that tomorrow and I think that's the there's also the block size which differ in the ne mind B is getting the same block size or is that also different okay I don't know what what there's a specific definition what what's the block size supposed to me that might be
that the net minder get disagree on what's the definition of it in the first place RIT do you have any updates I uh no no updates from my side been busy with the other commitments okay do else no thank you guess we could wrap it up then talk to you next week everyone thank you guys bye bye bye