eth_multicall Meeting, Dec 9, 2024

eth_multicall and eth_simulate Meetings · 9 Dec 2024 · 7:34

A meeting of the developers working on eth_multicall and its successor eth_simulate, held on 9 December 2024. Client and tooling teams compare implementations and work on the specification for simulating transactions.

Topics

From eth_multicall and eth_simulate Meetings, hosted by Ethereum Foundation.

Transcript

hey hello how is it going for me it's going good uh for me I was able to sport the differences between uh the time stamp for get neither mind so I implemented that fixed it U but still getting differences so differen result so I am uh deing it right now yeah the deing step was pretty challenging for me setting up a rider to debug for a remote process but but I had a call with Lucas find found a work around and yeah started uh working on the differences so far so good were you

able to run the test shoot yep oh nice yeah that's why that's why uh I said that the version ofn snot net SDK it's to be updated I think I I Creed PR2 hi as well to update the do file for NE did you she not check that out MH sorry did she not check that PR out yes it is already in the merged in my hive branch and I think yours so it it works it should work now yeah it works I have checked it

loggly let me know if if it doesn't it doesn't I guess not upgrading the master Hive yes is that something that it's difficult to get to M master or Master it's Master five and not just your fork yes okay it was a it was a issue in hi actually so the docker image used for nether M was wrong so we proit fixed that yeah well I wrote that blog post

well that blog post was just update of the old blog post and then I just updated things that have changed and well there wasn't that many big changes actually mainly just the name of the method that it used to be multicol and now it's e simulate and then I'm working on one other block post that is mostly explaining what Interceptor is and then how to utilize it simulate and how you can use it it simul doing test test cases as well right um yeah as for me not so much I tried to unblock grit by um merging in the hive changes and and his PR um

yeah I'm kind of I was hoping that basan would be here uh I wanted to introduce him to you guys maybe you can try to Ping him if he's available maybe he [Music] forgot I have been also looking for public end points or Tason RPC end points and testing if they have Chas or the E simulator enabled and but there's not not that many yet and for example nosis has no is running uh NE M I think because it's producing some errors that I'm expecting

for the nether mind but yeah theosis CH work currently kind of completely but like optimis in base works very nice behind the GS H nothing from my side does Rohit have any questions or is everything clear uh for my case yeah so far everything is clear let me just find the let me uh fix the is that I getting right now yeah and if you can get that fixed then you can rerun the test and then if they match then that's that's really good but let me know once that they fix

so then I I can also run the test and then see what other the difference is there this we uh would like to get testing of the block has se and if that time stamp is fixed and I live in in the world that I'm hopefully that those block hases start matching as well I hope so m is laughing anyway yeah yeah sure sure G uh I I I'll definitely let you know my guy is laughing because he doesn't believe that those block hases will start matching after that that there will be something else underneath but I'm somewhat hopeful because the evm underneath should be the exact the same

and then there's just just default values that I think might be different so when the the user doesn't specify some uh some of the fields then net might and get might have different default values but but then we can test those as uh one thing I wanted to ask though uh I blindly changed the uh next time stamp increment to 1 second from 12 second uh is there any reason in get that why why are we doing that you mean what it should be instead you mean it should be 12 seconds uh no I'm just asking why it is

one second well the thing is that we want the time to move move forward and I think the other logical way would be 12 seconds but then that's there's all the networks that don't have 12 seconds and we thought it would be nice that it would also work work this as similar as possible in other the CH I think that was the reasoning okay okay and before we also didn't allow the time to stay still but in the novad spec we allow that that the time doesn't need to increase every time so you can keep the time step the same as well that would be also something that we could simplify if we want that instead of incrementing by one we would keep the time step as it is but I think

it's still logical innovat to always move the time forward if unless the user specify something else yeah I agree I think that's one or 12 both would be fine with me I would not be okay zero okay and we are the because there's some chains that have subse block times so then for those it would be still nice that you can just say that the time is not moving forward mhm I guess you don't have anything else yeah see said that he had to drop off okay I think nothing else for

me okay see see you next week yep see you next week by thanks bye