RollCall #2

Transcript

okay let's do this thing so hello everyone welcome to roll call number two hope everyone had a good New Year and uh everyone is ready to get back into things I will post the agenda in the chat quickly um is in the chat and uh as usual this will be available on YouTube after the fact a recording of This call okay um so first topic for the day uh is uh EIP 7587 um that is an EIP for reserving a pre-compile address space for uh rips so

basically we can have our own uh addresses to play with as we discussed on the last roll call uh We've brought this up now twice on the um uh all core devs call uh the the the L1 coordination call and basically it seems to be General consensus that this is a good idea um the plan is to have it uh finalized and merged by the next um the next uh all core devs which is uh the uh Thursday not this week but next week at which point uh we can start issuing uh pre- compile addresses as as as we need for the roll call

Process uh which is pretty cool uh and then we'll guaranteed to have no conflicts uh with the the the L one what the the one exception here or not exception the one thing that Still Remains to be seen is whether the L1 process if they start adopting the um rips we have whether they will reuse our address range addresses or not um this remains this is just an open topic and I think we'll probably be evalua on a Case by case basis in the beginning uh as they look at things like whether they would like to include R1 or not but uh at the very least we have the guarantee that there won't be any conflicts and uh I don't

think it's I would be surprised if we didn't see some kind of merging of using the same the same addresses for um the the things that are redeployed on L1 so that's the major the main topic there and then uh the next that I mean does anyone have anything I'd like to add to to that that's awesome great to hear yeah no pretty excited to have our I sposed to play with um yeah that is fun Basics but uh yeah it's important uh great yeah so moving on um the what one

of the main impetus is to get this done so quickly is the R1 pre-compile that I know everyone is uh very excited about um and I believe so that is Rip 7212 I believe that has been finalized on scar yes today oh go ahead okay today was the first the last day of the last call deadline and a few minutes ago terized it and it's now the final rip and ready to be implemented by an Rob yeah this is really cool go ahead

ask yes and and just to mention basically we um already in in um coordination with uh allod we already assigned the very first address in this in this I pre-compile range to to the R1 pre-compile that should be um what's that ZX 100 or ZX 200 I always forget ZX 100 I think right yes um 100 yes okay um and so while while we we're going to wait until next alod defs on like a week from now to finalize the EIP that officially blocks the entire pre- compare range we already brought up the one um case in particular also on Alf so so Bally this

this one address is is already kind of finally reserved for for our one from the AL side as well so so this is really fully no no caveat final so any any layer to I mean I I assume no one no one is going to ship that one want pre compile literally in within the next week but but the the um the precompile is is really ready to go so any any team that is interested of course again the the the IP process is is supposed suppos to be opt in um but but for anyone who is interested um the B comparison are ready basically yeah thanks thanks for upd

there guys so yeah just just to reiterate what that means that like when rip is final that means that the only changes that we can see uh moving forward are changes sort of around the like just the the wording and explanation but the actual standard itself is not going to change uh if we need to change the standard itself uh we will need a new um a new rip and a new address for for using that um that so we can ensure that they're no conflicts so everyone is free to implement this should they choose to do so or not should they choose to do so as well so yeah um

any any other comments on uh on this rip nope okay great uh it looks like we're really shredding through the agenda today which is pretty awesome um and then the last topic I have on the agenda before we get to some more General discussion is the idea of rip working groups which ansar's been thinking about a bit so I'll hand over to you sorry I had to finish my congrats message in the chat um great yeah so so basically uh I already kind of mentioned this on the on

the last call um of course we were all a little set that we we didn't end up having our inperson event in Istanbul where we already had kind of worked out um an agenda that I I think we all were pretty excited about so there's a bunch of topics that just you you know we would be really happy to to dive in but the main roll call doesn't seem like the right place so the idea is just as an experiment um for the next between this roll call and the next roll call the next roll call will be in in five weeks so that gives us four Wednesdays in between um the plan is to have four breakout sessions same same time same length um but of course with a big difference um and otherwise weekly would also just be way too too too too much of

course while the main rollal call we would really really like if if if every team has representative here of course for the breakout sessions it's much more it's going to be specific uh topics and then this attendance only only makes sense for people who actually are specifically maybe have already worked on this topic or interested in this topic so so it's it's it's fine to skip uh the calls that that you're not interested in um so then then on on next roll call we can we can have like a little retrospective see whether this one makes sense at all whether we want to keep it up maybe keep it up on a slower cadence once we basically work through the initial um um topics we wanted to to to go to in at the inperson event um or or just leave it as this oneof um for January

basically um so we have four calls which means four topics to choose and the idea is uh to choose the topic for the first week now um I have a candidate I I'll go into that in a second and then I I'm I'm going to publish an each medition thread hopefully today or tomorrow um where we where we can basically see prioritized other other topics people people want to talk to I'll have some proposals kind of coming out of this event but but I think since then there's also been a few new topics and the roll call chat and everything so so we can select the other threes and three and then the idea is that we'll announce the the breakout calls at least a week in advance for each of these calls um and they'll be on the on the calendar as well and we'll

also announce them in the in the telegram chat so so you should hopefully be aware but again attendance very much optional for those so specifically for um um I mean just briefly of course in case anyone thinks this is a terrible idea wants to propose any adjustments before I go into the topics specifically but I assume okay yeah I wasn't thinking just just wanting to give some room um so then for next week in particular we were we had a question here basically for teams and and in particular a topic that came up very recently was uh Erp 4844 and the dun hard work obviously that's now fin um actually scheduled for for this for the

test Nets um for ethereum and then we basically already are now on a pretty tight that timeline pre prei timeline for mainnet as well so the question is of course at some point that also means that layer 2 should start kind of testing testing uh their for Integrations um we we are not aware specifically like how far along the individual teams are on this yet so we we we were basically the idea would be to have one of these St be be a 4 for four testing call where we will have some of the layer one testing people and then the kind of the the layer two teams that that that are interested in in kind of talking about this come on and and talk about testing but we were not

certain whether next week might be a bit too short notice or whether teams would already be ready so the question basically that I would have for this group is whether you all think this makes sense at all and then whether you think you'd be ready for this by next Wednesday there ready and then I have fallback proposals for topics if if that's too short notice uh yeah Harry um yeah I was just going to say on the uh on the arbitrum side that sounds good to me we're uh kind of currently

targeting having uh having something kind of viable for uh having a a man having a Mand a main net release candidate is by the end of this month uh so certainly in a good place to talk about and uh obviously very top of mind yeah hey I'm working on the um 444 limitation for op stack um I just post in the comments um we have finalized our spec uh and are well along the way of implementing it um hope to have a devet running on one of the uh Denon hard Forks uh shortly I'm aiming for end of week but that may slip till next week um

so we'll definitely have a release candidate by the end of the month I'm happy to talk about any of sounds good um of course the IDE is to have this be as useful as possible any team specifically that would think they would get more value out of this if it was say one or two weeks uh later more close to say the sepolia um hard fork or is next week fine for everyone of course again only those teams that are actively working on this anyway should show up to the breakout

call or who are interested I mean I guess it depends on what are the goals are the goals to just to kind of explain where we're at or to discuss options of implementation I suppose yeah what what would the topics be at this um breakout session I guess maybe a little more specifically right so um I I think basically depends a little bit on um when we we'll have the call if we have it next week it would be more about preparing so talking about the different kind of aspects for for the individual teams like how ready they are and then what what what specific kind of aspects they they would want to test and maybe some

insights from the testing team on how to best support this um if it's a little later say more towards the the sepolia um uh hard Fork assuming that um zolia is where most teams would then end up testing it um in in in in real life beyond the dev Nets then we could kind of talk more more concretely about um yeah seoa specific issues got it um yeah I mean next week's gonna be really busy for me so so selfishly nextra week could be good but I could do either way I'm flexible wait were saying selfishly next

week would be good or would not be good because you're busy no no selfishly I'm really busy next week so it would be better to have an extra week but I can be okay right yeah Vlad dropped Vlad dropped a comment already for zync but essentially we should be ready by next week as well um obviously anytime after that is also adequate for us yeah I think good with either next week or the week after um definitely like the of having a having a call for sure since I think there a lot of interesting Dynamics to uh to talk about sounds good um yeah well then I

I'll just say that um yeah given that no one seemed to have a strong preference to have it as early as possible maybe we can we can then just pick the the Wednesday two weeks from now that is the um 24th which would also make it six days before the seoa hard Fork which seems like a good time it's not hopefully not too busy because it's not right after like the week after might might might might just every might be busy busy so could be could be the The Sweet Spot so so then we'll have the the breakout call two weeks from now and I'll I'll set that up and I um announce it more more officially next few days um then that does leave next week um I had

the the the the the two um the two fullback proposals that I had for next week um would be and like I guess it depends a little on how how in- depth people would want to go or whoever would want to show up then um that could be either the the smaller topic which which just be pre-compiled again so basically having another look at at the the the standardization the the the range how to for example um keep track of the the status of which rollups are um plan intending to to um to ship which which pre- compiles and and how to keep track of these things um then there's also the idea of progressive um pre-compiled so basically how to how to have a standard of where where the individual

application doesn't have to specifically be be recompiled for every different chain but could have some sort of fallback there could be some standard for a just evm implementation um and some automatic routing um so that that you just call one address but under the hood it just always works no matter whether there is native pre-compile or not deployed um so basically this this all all all the topics related to pre- compiles um all the alternative a bit more on the theory side a topic that I've been looking into last year as well would be fee markets so how can we get from the count situation of everyone just having some sort of somewhat pecky way of charging users fees because you always have to account for both the

layer one settlement cost right but then also the layer two intrinsic gestion pricing so how can we kind of turn this into a more uh principled uh possibly say two-dimensional but that's just one option um fee market so so those were the kind of the the two ideas I had for for alternatives to talk about is there anything is there one of these two topics that people would be more excited about for next week I I'd love a call about Fe markets I feel like there's a lot of great stuff we could do there yeah I agree at the same time I think

that pre compiles are probably just uh easier to do and also it's something that we can Implement right away uh and having fee Market it's more like long-term Vision so I don't know what is appropriate to for first next week right yeah that's that's roughly what I expected okay let's let's do this way then um I don't want to take this out too long uh let's have next week just talk about pre-compiled because that also means that we have then and then we

have fee markets as the topic after um for per so basically the next three breakout sessions then would be um pre compar for for four testing and then P markets that gives also a little bit more time to actually prepare maybe for for for for people who are interested in in the Fe Market side um and then we'll pick one more topic to round it out um and then we have the next roll call I think that makes sense if anyone disagrees Last Chance otherwise I'll just um post the announcements shortly after this um and then we can just see where this goes okay sounds good sorry um BR this out um

but thanks I think I think those are good topics hopefully productive so yeah looking forward to talking talking with you all or again whoever wants to show up for those um over the next few weeks back to car awesome yeah thanks osar um yeah I think it was a great great topic choices uh I think specifically uh one other thing is worth pointing out here is that we'd like to bring on like other relevant parties that have been doing a bunch of research or um have thought about this on the L1 side so the testing call we'd like to get some of the testing people from the one side there uh so we can just have sort of meaningful cross layer

discussions to at these uh uh these working group calls and with that it brings us us to the end of our agenda um is there anything else people would like to discuss on this call uh there was uh the EIP rip 7212 uh about the SEC p256 A1 so p256 curve uh standardization uh I think it was ulas who pushed it to the agenda yes let's see yeah so I think uh I think you joined

about five minutes late M um we that's okay I'll read the uh summary uh it's all all good all good uh TDR is um we finalized the uh that RP as it stand because there were no no comments uh in this this uh um the final period so it's finalized at a address 100 Z 100 okay thank you mhm anything else uh people would like to discuss good

on going twice okay well uh everyone maybe just just briefly mention um because uh we no right like in the in the protocol call calendar in case anyone has seen that the next roll call is on at the wrong date we we're going to fix that shortly it should be February 14th not February 7th so the next roll call will be February 14th yep thanks everyone for attending um hope to see lots of you in these working group calls especially the testing one and uh otherwise we'll be chatting async and definitely see all of you next on February 14 thank you thanks everyone bye

bye