eth_multicall Meeting, Aug 5, 2024
eth_multicall and eth_simulate Meetings · 5 Aug 2024 · 10:06
A meeting of the developers working on eth_multicall and its successor eth_simulate, held on 5 August 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
hello everyone I heard there's new nethermind version yep there's new nethermind version and the current version that is that you've tested before that will be testable for basically everybody as it will be a part of our release candidate for 1. 128.0 RC so yep do you know M if we can run that those release candidates in those note providers any anything that makes it to Docker Hub we can um we can use and I believe Lucas may be able to correct me
wrong here but I believe all the release candidates make it to Docker yeah of course and so basically there will be a release candidate that will be with like the verion with issues related to blob related stuff and there is an update that I created for you in the new tag e simulate so I think we would want the yeah I think we want the E simulate one this got fixes yes you do and it will have everything that is in 1.28 so it's biger do you remember how to do that clari can you create a p request and I
can review it for the operations repo yeah I can do that too okay all right we've got a new person today hello chag oh yeah I'm just I'm just uh here to see what you guys are next of the over mhm all right so basically uh we are closing closing up to the like public release at least release candidate so we'll see how it will perform on real people soon y did Cena mention he was not going to make it today or is he just running late I don't remember seeing something
from him maybe I missed it though I guess there's no info from him do we have all stuff I don't have any updates but yeah I could get the new version and then I could run the test against it yeah I had a question for you in regards with the trailer uh in one of the issues give me a second so in one of the issues uh you referenced uh how transaction behaves on sepolia can we somehow isolate Its Behavior onto like to make it work from our block overrides purely without like need for a particular particular chain or setup
because basically as you used the the latest base block the state would always like run through and update and so you would basically never get the uh the same PES that you want to expect and that this a potential issue with the test oh yeah I I think that was specifically on SE because chain ID changes the uh changes the hashes and then we cannot make a test that that has kind of different chain IDs so each chain ID is specific on what the hashes will
become I don't think it's about the latest I think otherwise the test could be probably made so that the latest doesn't matter but it's just only about the chain ID should be the SE to to get the same hases uh well basically please do add some output to that issue so that I could like at least try to maybe better understand what do you mean by that and also there was an issue called NE mind defaults 2 is z z and not null I tried to update it on my side but if you would provide an expected output pair that
would be great so basically there is hope that in current version it will be fixed but if you would try it out and like post the expected reply versus the reply that you got that would really help that's it yeah all right the cas is I'm just making a call and then getting the transaction hash and and I think in that case that it should be the same has in all the networks other than the chain ID why but there is the like State Route and it's that change the transaction has
doesn't get modified for that the transaction has only depends on the send transaction and it doesn't depend on the state at all yeah I think the only state is kind of the chain ID which is it depends on on but that's basically yeah but yeah you don't have to need to send the transaction has to already know the transaction has but the CH ID default is get get get from the multic it simulate and in that case I'm not setting the chain ID so it's setting some default chain ID value and it I feel it should default to the current chain and not to but you have to test test that you need to set your chain ID to same to seola and then try to get the
transaction H yeah all right we'll try out I'm I'm expecting that the at NM is currently saying that the chain ID is one or zero or something like that but I didn't test how I would get the matching hash like in get we had the issue that the chain ID was Zero if it's not set Shea fixed it yeah I think hashes may be something that will because all B basically most of the issues currently are like cash related uh yeah in this case about maybe about the default Val of the chain ID and the
chain ID kind of doesn't matter except only for the it only matters for the hash MH yeah I'll take a look then yeah all right so we drag time as much as possible in the waiting for CA but probably he won't come today uh has anybody anything else to add nothing for me all right all right then so we'll see you all next week thank you all for coming uh just one quick question sorry the the version that we're the E simulate version we're going to be testing um is there any chance that that
will make it into the upcoming 120 whatever release um if everything goes good or is that probably going to be delayed until then release after that at the early if you would say that everything in this version is good it will be like with these fixes in the release if you will say that not everything is good in this fixes uh the default like previous version of his simulate will be there okay so we'll try simate will definitely be there but it's like complication be it with blobs or be it without would depend on the like fixes that I've uploaded today okay okay yeah we can try any any
the release at any before it right no not a big deal you guys have your release process hasn't gone into like a hard freeze or anything yet so we have a cut off uh from the master brand but we often try to pick some further fix if if needed okay and this one is smallish in volume but as usual with this simulate it touches every every part that you could potentially touch processor faade General evm and all the stuff all the favorites okay that was it thanks all right we have a new new
comma it seems Dr would you like to tell us a little bit about you hello Hi O thanks for invite so I'm uh currently implementing on R the E simulate um implementation and um yeah I just wanted to get in touch with you after long time I just have attended a meeting after a month so I just wanted to let more details uh right now the types are been written in alloy uh which is associated library for maintaining the types of uh evm and now I have to um import them um create um let's say manage all the
header default information and then implement the simulate function so nothing new queries uh the presentation last time with um eacher channel was pretty good thanks Al and lukash I think you did the presentation I it's pretty clear so yeah that's it from my side all right perfect and with this probably will wrap up for today thank you all for coming and see you all next week bye