NEAR Aurora Updates, 26 Mar 2021

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: NEAR EVM Working Group Update [2021-03-26]

Description

Follow the latest from NEAR Protocol on,

Website: https://near.org/
Discord: https://near.chat
Blog: https://near.org/blog/
Twitter: https://near.ai/twitter
GitHub: https://near.ai/github

#Blockchain #FutureIsNEAR #NEAR #NEARProtocol

A

Hello, everybody today evm booking groups, weekly update. Let me share my screen.

A

A

Although this is a new computer, so I have to actually give it uh privacy permissions to share the screen there. We go.

A

And for that I have to quit and relaunch, so I shall be.

A

A

There we are give me back host. Let's.

A

Okay, can everybody see my screen right now? Oh good, good, okay! So it's coming to the end of q1 and we need to release to this net next week. I added a few discussion items regarding that here. If somebody has something more for the agenda, please pipe up.

A

Nothing so this net release by end of q1, which means next week. Let's talk about that in a sec. Let's do the updates first alex.

B

Yeah, hello, everybody, um so I was working on bridge side was helping a little bit to kirill and evgeny with their questions on uh on the earth connector, um and there were some some minor discussions with you uh bartow nothing important, no, nothing big! Some some of them are very important, but nothing won't speak.

A

Yeah yeah, so I need a bunch of discussions and things to work through on. On my end, other than all of the management stuff um implemented pre-compiles for aurora engine. We have the most important ones now the others are. These are not that used.

A

I need to get them in there, but it's not as urgent did a deployment script for the new version of the contract that elia prepared. That now has a constructor and needs to be initialized, um there's an arrow, ranging client library so that it's easy to call call the various contract methods that need bush encoded input.

A

We don't take json from most of those methods and, importantly fixed our customer customer issue reported from the community, so our pre-compiled for easy recovery has been broken in not only the original contract, but also in the near core implementation of the evmprey compiler, and that's that's now fixed.

A

So those are my updates uh you're getting.

C

We discussed with alex uh some things related to s connector and uh also I implement all uh proposals for pr. It was removed completely several dependencies.

C

Are some issues related to gas and also some other small issues, and currently it's completely implemented? All things works fine and currently I completed manual testing. So I think our next step, probably should we schedule test it and also it will be really cool if I implement some integration tests for all things,.

A

Okay, but ultimately we need this in the contract so probably time to start putting it in the contract. uh Have you looked at that yet.

C

uh What do you mean.

A

In the uh evm contract.

C

You mean sporting engine.

A

uh No, I mean the auto engine.

C

uh I I'm sorry our engine- yes, yes, I'm looking for the repository yes and uh after that, I think we can uh integrate it. No problem.

A

Okay, uh so the let's see the dependencies. How do they look now.

A

Okay, they look like they will be compatible with what we're doing. Okay, good.

D

Frank, I implemented the raw call for the bully and started replaying and sure enough. The first transaction fails due to the um wrong chain id and then I built the begin begin chain call and which is not implemented in the evm yet so I I would switch over now to the aurora engine and fix the or implement the missing parts there.

A

uh Well, the begin chain does set the chain id. So if that doesn't work, that's a regression.

A

Did you did you check that.

D

I did check it here.

A

Okay looks like that's: that's missing actually need to see what happened to that. Okay, uh so basically, you'll you'll be switching over to working on the contract and these two functions.

D

Yes, exactly yeah, okay fix fix the um basically the failures try to go as far as we can with with the replay. If you think that makes sense, I assume everybody else is busy with other stuff right now. So.

A

Yeah, I think you have now a good uh scaffold on on which to build there, so by all means take a step at those okay, okay and uh ilia. I I thought that you had a big pr too much. Let's see find it here, yes, upgradeability and corners, and I merged this the other day and I've been testing it.

A

um Did you also work on the other bits you you had to mention. You would want to work.

A

A

uh Yeah, just asking, if you, if you worked also on something else after the credibility.

E

uh No not not yet. Okay.

A

All right, so we got, uh we got the interior, we got some some upgradability for for the contracts and it's some more testing which I'm doing currently and joshua.

F

Can you see me, sir, I was having issues earlier, no.

A

No video, but we can hear you.

F

Oh weird, okay, um so yeah nothing but the math api and a few uh forward press reviews. um So the math api is now complete. It's in review right now, and I've pinged the people that I want to look at it already. uh It's tested. It should be fully documented and it brings in that every uh everyone was uh telling me about what what to do, what not to do and what to include um all that's left is the cost of the evm. I ran that twice, but it ran into two different issues.

F

uh Both of them are now now fixed. uh There was a recent uh pull request that was brought into core um which which uh which broke the which broke the uh the script. So now that's addressed, I just gotta run it one more time, and then I got the uh calculations and the cost of everything, and it's uh completely ready to go.

A

Okay, all right looks like you're getting some review comments here, bowen, sorry on the case and others too, good good good. um Yes, of course before you, you can run the runtime params estimator.

A

You can't can't really merge it, but otherwise it looks like your. Your vr reviews are coming in good. um What do you need to do to to be able to cause it.

F

I just gotta follow up on the um um what everyone is saying and also um get the cost in and then it's it's it's good. But as for like the problem, that's already solved.

A

Okay, good all right, so, let's, let's talk about um what we're going to do next week.

A

So first first we have an issue with the contact size which I'm wondering if somebody somebody has some ideas about that, I haven't done a chance to look at it yet. So this is issue 7 in the in the engine.

A

Repo and the issue is that after a particular comment, um the site's bloated by one megabyte- and it's not immediately obvious from that comment, but might have caused that. So if somebody has some.

E

So I looked into like what what's happening with the bottom file and there's like a huge data section, so there's some kind of recompiles or whatever like there's something like I've, seen similar things when I invented regex uh library into my other contract and it's like balloons like 300k, um but in this case it's yeah. It's some kind of data section from somewhere coming.

A

So some some some new dependencies pulling in some big static data.

E

Yeah exactly some pre-calculated static data yeah, so.

A

E

Like so one one important piece is actually the current: currently the computation the function. Call action doesn't actually depend on the contract side. So like optimizing, the contract size right now might not be the like.

E

I mean the most important I mean it's still important because, like it does increase performance, but actually the recent update, the neocore they place the loading and the execution, so it like kind of reduces the problem of uh loading the contract time. Okay,.

A

That's good! That's great.

E

Yeah so like, I think we should figure out what that is, but, like I don't think it's like a super important. It does not affect the.

A

Okay, great so not a blocker, and we can defer it so we'll investigate but uh doesn't have to be next week. Okay, um so let's talk about what's realistic for for this net next week, so we are certainly going to deploy to desnet next week. uh The question is what will be in in that first contract then, and what won't and, um of course, given the approach of evm as a contract, we we have the um benefit that we can. We can just deploy new versions daily if needed. So that's great. We will.

A

We will improve quickly um alex what are your thoughts on this.

B

Well, from my point of view for for the test net release, we do not need to merge f connector with uh with evm contracts. We need to have the minimum the minimum setup here.

B

um We need to have somewhere the rpc, um so so the real layer uh that is going to work with it, and so people are able to schedule transactions to our evm yeah and uh we need to have an ability for people to to get some uh base token, so yeah. So.

A

Just uh I forgot that I actually worked on the the relay right: yeah yeah, okay,.

B

And yeah we need to. We need to have uh the yeah literally the test net force, an ability for for the devs to get uh f.

E

B

Yeah I had a suggestion.

F

E

uh We can pretty much uh when, when you fly gvm contracts, there is a option to like supply initial supply and they'll be allocated to owner id. So there's a new method like in the new method, there's owner id and so that's owner id with whatever account we control. That then becomes a process that people can request.

D

A

Yeah yeah, I think that that sounds that sounds reasonable, uh so so alex. I agree with what you said: we we don't really have a chance to uh realistically pull pull through the s connector uh in for the first deployment at this stage, um yeah the relay endpoints are in the works so that that will be up this weekend. I believe and yeah ilya. Let's, um let's do. Let's do that.

A

So an initial supply for the contract when deployed and some kind of integrated, give me money function that people can call to access the integrated faucet. How does that sound.

A

No objections I take it.

B

Yeah all good for me.

A

Yeah and uh if you have time we'll make a user interface for it or something, but um ultimately it needs to be a function in the contract and and that will be a good start. Yeah.

B

We need to, and we need to also to to update the docs with the with the testnet deployment uh yeah.

A

I I have it here as an item. Yes, so.

E

Just just as uh as I mentioned, uh we need a public keys that then boeing can create uh the account for aurora on that business.

A

Okay, uh yeah right top.

E

A

A

Give the owen public keys to create um so really is. Is your contract still that we keep the evm top level account name?

A

E

Do aurora, okay,.

B

I suggested to to have aurora because, like evm is going to okay, it's not very clear for people.

E

Yeah, I think, given like there will be other.

A

A

Okay, all right so I'll get in touch with bowen about that, and let's get that done uh one day latest um okay for documentation updates um yeah, so that was the the most important thing to know for documentation updates, as in once we know the contract name, we can start to submit ps for the documentation.

A

uh Now we have, we have a very large amount of documentation actually already, thanks to to mike. um Let's see where are we? This has been reorganized. Let's see, somebody know where this is.

B

On the left, pane no.

A

Yeah yeah, but it it depends on which section you want probably develop access, yeah, yeah, yeah, okay, yeah, so we got. We got a fair bit of documentation here to to update and uh some of these instructions are for the local setup. um Most of them are bait on it.

A

So I suggest that we we will change everything to be desnet by default and probably don't really need to retain the better net concept. In most cases, it's easy enough for people to just debate on it if they are in the minority. Who is doing that?

A

um Any objections to that.

B

A

Yeah and then for this local setup. Maybe this can become uh something like an advanced section which is then for local and environment documenting some differences. Something like that.

A

Okay, so I'm going to take on the documentation, updates familiar with this documentation and let's get that ticketed.

E

A

A launch criteria.

E

For maintenance at all.

A

uh No, we we, we haven't, really spent a lot of time thinking about mainnet as yet, but next week we we're going to do the okr review and q2 okay, our planning on wednesday, I believe, and- and that means that that would be the perfect time to think about launch.

A

Criteria so we're gonna change default from bit on it to this net.

A

Okay, what other items do we have that we haven't captured so far? Let's look at our original roadmap here for.

A

A

So if we just go through this.

A

So we, let's begin from the bug bounty, so that was d scope from q1 earliest middle of next month. Q2! Any updates on that alex.

B

No updates, no updates. Okay,.

A

Gus gus asked me today about bug bounties, so we need to get back to him. Yeah.

E

So what one option we discussed with flux has been creating a pretty much uh mixture market, that you know, there's no issues with evm or with bridge and then yeah.

B

E

Like two like people to bet against that.

B

Yeah, sorry, sorry, I was not no was not uh sharing this with arta.

A

B

Do updates uh well yeah. There was an idea to so it is some something in in the in the middle, in between some kind of insurance and uh and bug bounty. Actually, so uh so we're thinking of a very simple solution, using flux uh to create a prediction market on the fact that a breach is going to be hacked and- uh and we are going to put well some some certain amount of money into into the no share so by default.

B

Buying a yes share is uh well it's something that that will potentially bring you lots of money at the moment when the the market is going to be resoluted, and this is both uh convenient for people who would like to you know, protect hedge some risks, so they they bridge some tokens and they would like to hedge it, uh hedge against the the failure of the bridge and also for hackers, uh which can buy lots of yes shares just before they are going to hack the bridge and that's why they can get, uh can get the bond.

E

Well, I think, for the bounties, the better framing will be the that there will be no like security vulnerabilities found by and reported in a proper way.

B

Sure sure yeah.

A

Yeah yeah yeah- that makes some sense okay, so we can. We can come back to that in the next weeks, um as we start thinking about those questions. um Anything else to add to that alex.

B

Yeah, I just wanted to mention that, since we have already prediction markets that are working, uh good uh people are starting slowly to use it, uh and uh so it's just like we are going to reuse uh one of the uh products that are built on top of yeah well in in our ecosystem. So it's just a cool idea to do it. um Yeah and that's. It makes.

A

Sense now I note that one one thing that we we have perhaps a little bit dropped here I mean the other other things we have under in in the works, but um have you any update on the internal partner ebm satisfaction report that we would like to send out.

B

No, I do not have anything right now and uh well. This is actually connected to with with partners being able to to work with evm yeah. So maybe maybe it's worth this coping right now. Well, not the scorpion, but literally we are not fitting in in this quarter, probably need to do it uh later.

A

Yeah, I think I think the idea here was to create the report not not yet send it around, um but it's it certainly can.

B

Yeah but we need to create a report, but but in order to create a report, we need to ask partners about their satisfaction with it.

A

Yeah yeah so far, I think not that many people have tried it on bait on it. Yes, unsurprisingly, this net is where the action is. um Okay. um I don't see anything else that surprising here.

A

Everything is in flight and uh we just need to sequence it a little differently than we had originally envisioned um yeah. So evm will be available on testnet next week and then we will figure out some kind of release cadence for getting getting ci approved changes deployed out there.

A

So we we need to discuss the upgradability, uh but that's, I think, a long conversation probably won't fit into this time frame.

A

um Anything else to add to this.

A

So we're going to yeah so we're going to to. In short, the the plan is that we we finished the the faucet functionality, give people a chance to to increase their f balances, so they can do whatever they need to do on testnet without.

A

And we will update the documentation to make this net the default.

A

We will create the top level accounts for deployment yeah, so this will be better on it than testnet. Both we actually need to to check on on beta on it. We we should probably remove the the feature flag from the near core deployed to to bit on it. That is the the evm pre-compile.

A

So we don't uh conflict with the contract approach.

A

We need to check that, with uh with this already.

A

And we have the parallel tracks going on of the s connector proceeding. I think then uh evgeny what we need to do is um you. Can you can begin integrating it into the evm contract, but it needs to be on a stay on a branch for some time, because we certainly will not be able to launch with.

A

That, okay and frank will put in place the evm, boolean functionality. So frank, you need to you need to put that behind a feature flag.

D

A

And uh that's actually the first thing to do, because you um we need to disable those methods for what is deployed to to test.

A

So it will be a bunch of tickets after after this meeting and alex, and I need to look through upgradability and key management.

A

B

Well, probably, the the real layers or the relayer itself.

A

Yeah, the relays will be will be up shortly, also hosted relays for both bit on it and disney initially uh charging nothing.

A

Which will also need to change, but not next week.

B

Do we do we actually have anything else beside this uh besides, like first four points uh to to do the deployment.

A

uh To do the deployment I I do think we need to yeah- let's listen, let's separate out, so these are parallel tracks, the s connector and the evm.

B

A

And for deployment.

A

For deployment we we need pretty much everything we have listed here. This is this is not critical.

A

Yeah for deployment we need, we need the layers, we need the faucet more tests for the contractor. I could also the balancer test still have a few issues. I'm working on those documentation needs to be updated for anybody to use it, but that can be the last thing we. This is a soft launch. Next week and yeah, we need to.

A

Put in putting process to define the process for deploying and upgrading.

A

So pretty much that that's the beauty of the evms contract approach, it's it's not very, very high of a barrier to entry to to just getting going and of course, in the same way, we'll uh will no doubt deploy to mainnet soon enough, uh just not not next week at least not on anything we advertise.

A

So that's that's! Next week now, um on a personal note, I I do have an imminent addition to the family arriving any day now, in fact overdue, and that means that I'll be needing to take a couple of days off sometime into next week, very likely, hopefully this weekend. That would work work out nicely.

A

We shall see. But as that happens, I will I will let alexan and frank and max know and then alex and frank you can. You can run the show in the meantime timing. You know these things tend to happen all at once, but let's try to get a few few babies out into the world a week from now uh anything else to discuss.

A

Anything else to discuss chance.

B

No just uh hoping for a great session next wednesday, uh and hopefully you will be able to attend it. If not, I think that we would need to to reschedule it well.

A

Most likely yes uh yeah, so um let me reiterate that the next few weeks will be also disrupted because of okr review and planning, which will take a little bit of time from everybody um and there's also a proof review undergoing which will take well not so much time from this team, but those who wish to participate.

A

It may take some time. Okay, that's everything for today, then, let's, uh let's get back to work.

D

All right bye-bye talk to you next week, bye.

F

F