NEAR EVM Working Group Update [2021-01-22]

Captions as YouTube publishes them, usually machine-generated, so product and people names can be misheard.

1. 0:06

   okay so it seems like we're live hello everybody welcome to the uh near evm war group sync weekly sync this is a weekly call that we are doing for our community and we are like discussing what is happening during the week so welcome all marta would you like to delete it sure hold on okay i assume everybody can see my screen um yeah so let's take the notes from hack md from now on i've lost too many notes to github

2. 0:47

   um okay so today we don't have a specific agenda other than the usual one last week we dealt with some some roadmap updates for the coming quarter um and that's an interesting particularly interesting recording for those who missed it um so today let's talk about the current goal the current goal is that we are we are onboarding people in the next few weeks we are actively recruiting at least one

3. 1:19

   to two devs more and we are getting getting organized for for the quarterly objectives that we outlined last time anything to add to that uh alex we actually well yeah so just just to mention to everybody that we have two people joined uh near evm and bridge teams uh so these people are eugene johanna and uh and kirilla brahmov uh they are going to mainly focus on the bridging of base

4. 1:52

   currency from ethereum to uh to to near evm which is at so guys say hello to everybody hello hello afghani and hello welcome welcome on board um so let's um let's work through our updates and then we probably have a number of things we can discuss um alex why don't you start yeah i was working uh mainly on hiring i was trying to reach so i actually reached all of all of the well the majority at least uh people in my network uh

5. 2:31

   trying to to convince some of them to join us and help us do some stuff uh some progress is is there i'm going to submit some some referrals actually and it's a bit later sorry i was working with art on uh on on on the ocrs so we were refreshing it a bit um was doing a little bit of thinking on the uh on how we can organize the the bridge into to evm so i'm not ready to present it right now but i was posting some questions uh earlier to you and uh

6. 3:09

   and uh how how we can do this so some some additional things to discuss but maybe we can move this to the discussion uh yeah and uh yeah besides that uh on the evening side probably nothing and my updates are very similar so recruiting on the one hand as in in order to make our quarterly objectives defined last week we do need one to two decks more so that's an active active topic right now and that we need people sooner

7. 3:41

   instead of later and onboarding our new recruits and internal working through um what is needed to onboard people to evm primarily but also with alex's collaboration to the bridge team and so that we can systematize this process it was rather disorganized when i joined myself as in we didn't really have any anything i could work through as a checklist and now we now we have something um and very happy to get feedback on that

8. 4:12

   if you're missing anything anything from the documentation especially as uh you can cure as we go through it uh please note either as comments or or indeed directly changing documentation anything that needs improvement in particular for um for everything to do with the near doxa repo just go ahead and submit the pull request it's no need to ask anybody um yes and and indeed a lot of hope they are

9. 4:45

   not planning uh eugene are you with us today no eugene okay um you have kenny why don't you describe a little bit uh your first week uh you're getting your honor okay thank you uh about uh my report this week uh i investigate a lot of the communication of for near and actually i try to build uh some repositories i have some problems and currently i solved all problems and actually

10. 5:27

    i continue to investigate linear documentation and yes that's sounds good and uh frank um yeah i was working through some problems with cargo uh also like reading the cargo book to understand cargo better and then uh mostly uh the crypto zombie code we have in um near core so we now also have the erc 721 functionality there and uh extended the tests visit transferring esc21 tokens

11. 6:08

    and then next up is doing a benchmark there okay so with benchmarking you're just getting going yeah i ran into some problem last week with benchmarking the um balancer tokens um so it seemed to be easier to just benchmark the erc 721 first and then move to the esc 20. okay go ahead go ahead uh yeah uh calling the balancer um contracts was more difficult uh because they need arguments and

12. 6:46

    i ran in some back there i i didn't uh figure out yet okay um would you say that um after you figure that out is crypto zombies uh is it a done deal you don't need more tests i think that's enough then yeah okay once we have the benchmarking i think that's enough okay uh so we can always do more but i i think uh it's it's makes more sense to then focus on other things okay diminishing returns okay so after that

13. 7:17

    benchmarking done yes yeah okay uh really anything you want to comment hey yeah uh i haven't done much on this side but uh i'm gonna take a look at the adding value to my transaction call and uh also uh expanding to use two bytes for the length of the method definition should have like a quick vr to near core over the weekend and then we will need to modify the uh let's see our website provider and rpc proxy to

14. 8:00

    follow um all right kirill how was your first week yeah mike yeah sorry not feeling super good um so there's a beta net chain id issue in your workflow provider where we have now a new chain id for that network in particular and just had to make a simple fix to update that in um the webview provider so that is that is fixed um how to do a quick fix to the the evm simple uh repository which is basically way

15. 8:48

    the simplest version of interacting with uh the evm and based on ilia suggestion um move the keys around a little bit so it's as simple as possible um push one of the changes yesterday for that uh oh yeah and then yesterday also um thank you evgeny for pointing out the web 3 was not available in browsers that don't have like metamask it's been a while since i have used a browser like that so thank you for finding that out some just made a super simple change explicitly importing web3 so that it all

16. 9:28

    works there that was my mistake before so that that is pushed to near pet shop so no one in any browser will see an issue now uh i did note that i haven't made an issue for this yet but near api js has changed serialization and they've done a good job of keeping notes in the change log about this but i i missed it so we're going to have to change a little bit of near web 3 provider uh as they actually change the method names and whatnot and so if we want to keep your api.js updated with that then we'll

17. 10:11

    need to make that change so i'll create a tiny issue for that it shouldn't be bad um i will note that i'm getting pulled into lots of manager tasks so i'll probably be super limited on on evm but i've got stuff going uh and the last thing is i'm uh just for fun i am making a really simple web interface for evm simple um that'll be a good place to start off and i really want to carve some time to make a video on that

18. 10:42

    so you can look forward to evm simple having a like node.js and also a super simple front end showing people how to how to use it just an html file that loads everything that's it okay sounds good uh kirill if you're back with us yeah uh hi guys sorry i had some wishes and didn't have a chance neither to turn on my video or mike so i needed to reconnect no worries how how was your first week it was very

19. 11:20

    interesting and i'm very happy to join the team uh it's a very good and inspiring projects and mostly the current week i would say that i'm at the same stage at the european so i'm setting up my development environment getting ready for future tasks and issues and at the moment uh i'm discovering the near documentation um and trying to follow the onboarding guides reading the messages what happened last two or three months or so

20. 11:56

    and at the moment mostly focused on the bridge documentation that sounds good um so did you uh did you organic did you have any any questions you wanted to raise uh everything is going okay with onboarding uh i i would say everything is going okay at the moment uh we just had uh another one-on-one talk with alex rafchenko and we have discovered together and alex told me a lot about the bridge functionalities and challenges that we will need to solve in in this our

21. 12:32

    interaction between the evm and bridge teams sounds good all right so that's the weekly updates for for this week and um let's see who we have here which are the topics that we can discuss with the current set of people um so potential topics we could discuss of course include more about the base token including now that we have as alex noted we have the plan to assign yevgeny and kirill to work on this

22. 13:01

    problem from sort of opposite sides as in evgeny from the evm team side and kirill from the bridge team side so that that would be one topic um we don't have eugene so i wouldn't tackle the question about um storage accounting that we wanted to eventually talk about anything else somebody else wants to bring up well potentially we can yeah yeah go on yeah i mean one thing i wanted to discuss is yeah just like

23. 13:34

    really clarifying when when do we have the kind of like the secure and kind of stable evm and like what and not just like kind of what we what we consider it but also like how do we make sure that uh every all the stakeholders are aligned that this is indeed true pretty much like kind of very clear launch criteria that we know everybody has agreed on right well i think that it is at least partially in in our ocrs already

24. 14:14

    and like you have agreement across validators and like everybody on a chain team and yeah in terms of the validators yeah we need we we edit we edit uh uh actually arthur would you be able to yeah since it moved um somebody has it feel free to send me yeah i'm going to do it just second consolidated all of the all cars into one place and uh yeah is it now probably i know okay yeah all right so let's go to the tv yeah

25. 15:00

    so so india you can see here that we have the evm on mainnet uh in in this objective we have a protocol upgrade uh okr and uh and there we have the metric uh if you can uh can go into the nodes then we are saying that validators agree to schedule and perform the near evm deployment as a maintenance protocol operate so so this is this is what we'd like to to to achieve obviously and we we do understand that there is an issue here that

26. 15:32

    we just cannot deploy evm to the maintenance especially uh we haven't put this thing uh for the test net uh which is our like main committed objective for this uh for this quarter uh but obviously we are going to start uh the preparation here and this is actually is going in hand in hand with the uh other topics that we would like to reach out to to the validators which is for example the upgradeability of the breach

27. 16:01

    and how it is going to be how it's going to be managed over over some period of time so so now we are going to to start with the simple versions of their upgrade ability and and can and continue there uh and and some other things too so so yeah this is something that is on the radar uh thanks for bringing this i do not think that this is something that we are going to like agree on this call because it should be like uh something like

28. 16:31

    a wide discussion for example that was done by the validators when we need to when they need to turn on the well vote what are the criteria is to transition to the phase two of the maintenance to be clear whatever's on testnet will end up in mainnet kind of within you know some period of time so i i i guess my my question are more yeah like what is the criteria for test net that you know yeah the chain like and

29. 17:03

    then and i know you have the criteria i think my question more is like how do we make sure that this criteria is aligned with everybody yeah do you want to put so we thought so our thinking was here that we need to make sure that on the trans on the test.net mainnet transition everyone is agreeing on this do we do we want to put this one one step down uh for on on the delivery to the test net

30. 17:35

    yeah yeah because whatever's running on testnet is pretty much pre-prod like yeah yes validators can like drag their feet and okay i mean ideally it should be enough time to test it but like that's not this is kind of our prod yeah okay okay okay so then let's move this protocol up right no no this is not task it doesn't make sense to move it this is the desired end result and that includes the whole roadmap to

31. 17:58

    of course beginning the conversation with the validators early yeah so we don't need to move anything here just uh yeah i mean i think it's the same questions of like security and yeah yeah but if we are saying that yeah but if you are saying that art i think it's better to move it down uh because if we are saying that uh like the desired outcome of uh of the uh of this of this quarter is that we are launching the test net uh this means that we are need we need to to agree on this

32. 18:33

    yeah which then changes it to committed yeah uh okay well there's a lot of a lot of end results on that objective but yeah we will review those with max later um right so that means that the conversation should be started presumably on the forum uh earlier as soon as the best place yeah yeah let me start this i'm go i'm going to be yes i need to need to finalize uh for example roadmaps i think that this is something that that is going to be done on the on the next week uh

33. 19:05

    and and then and then like there are lots of things uh that i need to take care of and then i'm going to do it okay maybe not just now not not tomorrow but yeah this is something that we for sure need to do right so in terms of the the launch criteria we have uh elia you are you already familiar with this software so should we perhaps review them yeah yeah i'm familiar yeah okay so i'll just quickly mention for the audience that we have we have a stress testing and then we'll

34. 19:37

    replay some f transaction logs and we've defined that as a day and active adversarial attacks for two weeks on baronets before before testnets and of course we have need to get the go-ahead from the sra team overall um we we need a little bit stricter or let's say more well-defined criteria for what are the actual um products that or projects that we would measure the success here with um i have some something in the books

35. 20:17

    with sasha hunters um and and yeah uh uh divides both a lot of alignment with other teams which is also something we are working on right now um and and of course the prerequisite of um upgrading upgrading to the berlin hard fork um right uh is this actually public this this url can we can we share this with people i'm not sure yeah well in any case we have it in the presentation from

36. 20:50

    i think that they will not be able to to access it since they're not inside of the near org yeah well in any case it's on the there is no there is a fair feature in our table so there is there is yeah we you can open the table press share button it will generate and your url that can be shared with other people so that they can view the table that's correct we are going to do this they they're going only one simple view is going to be shared with them and we

37. 21:22

    are going to do this and we are going to put it under the simple link uh that's this is something that is on on my plate i'm going to in in any case from last week's meeting notes you can you can find the same information on in the presentation all right um so let's talk about some of the some of the trickier issues um let me see if we have anybody join uh no okay so i think the the most important thing is the most important thing is the f base token

38. 21:58

    so we have to move that forward fairly fast um so the current plan is that um i'll have to start working through those changes on newport hopefully in collaboration with ilya if you have familiar um and then as we onboard uh kenny and kirill we'll start tasking out pieces of the puzzle on that side now there is a concern that i raised with max as well basically that we have we have a committed

39. 22:33

    objective here of uh being able to bridge s820 and the bridge team need to support it it's only aspirational for them so i'll address that as an issue any comments on the college uh well in general uh so so the decision for making this aspirational was that uh the bridge team need to sort out uh everything that is in the in the main objective the main committed objective which is the productizing bridge uh which is here

40. 23:12

    yeah and uh and and and we were afraid to be that we we are uh understaffed uh on this sort of yeah yeah exactly so uh so yeah but uh but uh but as you can see and and we were discussing this uh for that this is important for the evm and uh and it was a comment from max that we but we it is possible that we can we can have here misalignment in between the the teams itself it uh and uh like it potentially can be and and it just means it doesn't mean that we are not supporting you

41. 23:51

    it just means that like evm team is taking the lead here uh and then and that discussion was uh more than a week ago uh as you know so it was like almost two weeks ago and and since then uh some things are have changed so kirill and uh and evgeny are are now with us and and they are uh other people that are able and since they're like both joined different teams so and and they can go in the same direction so this is a pretty natural and we discussed that

42. 24:22

    uh that's a pretty natural thing uh for us to focus uh focus curio and evgeny on this task and that's why i think that this this base talking bridging is is something that we we well potentially can can do can do this uh this quarter and we are like resourcing this activity so so that's pretty good uh from my point of view and let's uh and let's do it let's let's keep it uh it doesn't it doesn't matter for me what is what is whether it is a red or green thing

43. 25:00

    in the type of the of the key result yes but it but it might matter a little bit if you if you say it can be potentially done this quarter you know that that would matter to the evm objectives can we do it this order or not and i suggest we figure that out as soon as um otherwise we need to re-evaluate our objectives here uh so let's talk about the base token um i think elian would you be able to provide some some guidance here um you you know the code base you wrote

44. 25:30

    most of the code you relevant code um you know it the best what do you think are the next things we need to do to move this forward so so if we just want to switch the kind of ease to be the base token uh the the to this two two things one is we need to remove use using near as a as a balance there um so that that's pretty straightforward but kind of need to go through all the

45. 26:03

    places but also we then need to figure out how to what to replace it with right so if people do want to attach near like what what to do instead uh so this is a little bit more complicated like we probably need a erc20 right wrapped near on inside avm uh and how does that connect with like the wrapped near on outside the vm uh and then the other piece is implementing a fungible token standard

46. 26:35

    as an interface on on the edm contract right and so this is actually somewhat blocked by fungible token standard not being finalized yet what was the 141 was that the case yeah 141 yeah so so it's not like i think it's in reasonably good shape i haven't like fully tracked it but uh i probably can start implementing but this is pretty much the blocking piece on that yeah the the quick comment here 141 so so the fungible token standard it was

47. 27:13

    split into multiple into into three actually parts and this one is is on only one of these parts two are necessary and one is is is optional so this is only half of a standard well the bigger half but still only half and this is about the transverse itself now and an additional uh nap should be created for the accounts itself and this is that is still what still should be done also a person from the community

48. 27:44

    said that he is he would like to uh he would like to do the reference implementation of np141 uh which is good and the overall uh uh the overall uh i don't know like uh yeah at least if guinea or eugene is uh is saying that it is in the good shape uh and maybe mike you can comment because you you were on the call the last call on the on the standard we're talking about the the new functional token standard yeah yeah yeah i would say that that's moving forward uh pretty pretty well and that's like our primary

49. 28:24

    focus on barry pickers is to get that done like soon was there a specific thing you wanted to know about this sure no maybe maybe you just wanted to add something uh in terms of how it is going but uh all good so good uh well in terms of us uh implementing that on the on the evm account uh we just need the interfaces right final interest right for that and of course you know if the interfaces still

50. 28:48

    have changes we can also adjust along the way at least up to the point when we go to distance yeah um so it's just like adjusting interface will be like will require a bump in protocol version every time absolutely but on beta net not not really hard work yeah i know and just it's way more annoying than like if if it was just a contract right that you just you're like uh but so elia did you did you indicate

51. 29:14

    that this would be what you want to start to go for and and i i can i can give a stab i think i think the piece that we really need to do is like figure out the second item here like the first and third is like they're pretty straightforward yeah it's just kind of like as soon as this the interface for for flauntable token is finalized it should be straightforward to do the yeah they're figuring out how to pipe mirror instead uh

52. 29:46

    like it's it's i don't think it's gonna be blocking right away but it's gonna be pretty hard to do stuff without that yeah um so okay and this relates to actually what what alex uh was mentioning like how do we uh in general bring tokens from outside of evm into vm yeah you need some collaboration and coordination there uh well i'll i'll take this on if we don't have any any volunteers and um this this why can one one one short

53. 30:22

    question here so i was i was like going out of the computer for for a second um so what what's the main topic here we would like to breach near inside of evm not really i mean this is about figuring out how we change to actually using fsd as the base balance yeah yeah i i understand it but this specific point well well yes how how do we do near instead so so we are inside of evm environments

54. 30:54

    yeah yeah so we're switching the the the main balance to become east but we still need near like you know like the nearest kind of the the base talking of the of the kind of outside so yeah so there's still things which are like if people attach for example if people attach balance well we can fail that's easy but like there should be a way how you bring near into you yeah so but but then like sorry but then more specific more more

55. 31:25

    abstractly right is then how do you bring any any fungible token like 141 talking into evm that's what you're asking yes so i already started to work on this um uh so i i think that's like generally uh we have discussed in the bridge team that a good good way how to do this is well first of all uh do not don't have a hard connection with the existing bridge so uh bridging the internal bridge

56. 31:57

    in between near native vm and near evm it should be like a separate contract it shouldn't be aware of of the bridge itself and this is pretty unusual because any fungible tokens that we create on the near side should be also be able to be bridged in inside of in your evm so this is one thing now uh now imagine that we have this thing now if we have breached a token from the erc20 to nep 141 um if we did that bridge now we need to

57. 32:29

    uh but but uh if we have this bridge and then nap 141 to n erc20 and then the question is that uh a user an ethereum user he needs to be able to do this breach in like in a single transaction because he he's not able to schedule near transactions so and because he he doesn't have a near account um so we cannot actually end tokens after the first bridge in in in near account the only thing that we can do is to land it into the escrow smart

58. 33:08

    contracts which can be then so we are putting this nap141 tokens after the first bridge in the smart contract and then somebody on behalf of the user uh any relayer any any type of of of service is able to call this smart contract with the near transaction and this new transaction is going to ask the the the internal bridge to move these tokens inside of the evm so i think that this is this is the way how this should be done and uh and if so then for the ethereum users the

59. 33:47

    uh the workflow will be pretty straightforward they are going to schedule a couple of transactions on the ethereum site only in the beginning of the transfer then uh some relayer is going to finalize this first transfer on your site issuing first near transaction however this transfer is going to end up in the escrow account and then the second your transaction is going to be uh calling the escrow account to transfer this into the evm and uh well this call obviously and yeah

60. 34:20

    so so like like this now in order to implement this we would need to change the proofs and this is the only thing that we need to change the proofs in the fungible token connector in the in the rainbow bridge uh and these proofs need to include one additional small field of the uh of the uh instead of having only one near account where we would like to to bring the tokens it needs to include also uh an evm account uh where we would like to

61. 34:55

    to eventually bring the tokens so it is going to be a and like the second uh the second filter it should be optional so it is going to be a simple change for the rainbow bridge uh but still we would be able to implement this now uh so this question yeah question why don't we just have a generic uh forward like the receiver is a generic forwarder which is kind of following the what fun what fungible

62. 35:25

    token standard right now became yeah because because then we need to change the the fungible token factory because then we are but we need we need to change them anyway because we need to be we need to follow this we need to follow the standard right now the new standard the new standard includes transfers with callback okay so so if you have transfers callback you pretty much we just need kind of a mint with callback which is kind of the same and and where where we will get this this callback

63. 35:59

    how do we know what what should be what what function should be so so so the way this would work uh in your transaction on the video yeah right you pretty much you format it as transfers this funds to evm yeah the s820 address yeah your account address this then like on on like the the nap 141 like connector on near side gets a mint with callback right it mints it and instead of putting it to the like instead of having receiver it it puts it into a vault

64. 36:42

    and calls a callback which calls evms yeah like you know into evm into your c20 contract which then you know says like okay yeah on this address of this user and then returns back to the walt and says yes put it in on the evm account yeah so so yeah so i i thought that this is something that is possible uh the only thing that i i what i really wanted to uh to conserve is as much of the

65. 37:14

    the the token connector the near native token connector as possible so if we potentially can can remove this and like do it with a single transaction uh and just this fungible token factory is going to call uh it's and and then the transfer is happening uh but but here we need to inject some additional logic uh in case this proof wants uh with using this proof we would like to transfer the funds in the near evm then we need to do the callback if not then just transfer it there well it's

66. 37:47

    not just for evm right this is like you can tr like you can transfer and do something with that funds directly yeah like for example it's the same way you can do a transfer and and swap it right sure sure so so it kind of just gives you more like that's why i mean this is the reason why the new standard has this like transfer and callback kind of action right so like given we're already going with this pattern it might be like reasonable to have like you know in a bridge mint

67. 38:18

    and do stuff uh what does it mean that in in the in the ethereum transaction we would need to specify uh the function and the uh well the callback function and the the uh the arguments of this function is this correct yes yes so so this what what that arguments would be is that it should call evm account method call and the arguments are the kind of the first argument would be

68. 38:54

    like whatever the contract address of the erc 20 and then the receiver address or something okay uh and what about the uh the the encoding of this so so then the event is scheduled with this information and how this event encoded are we able to get this this simple uh just like strings uh from it uh on the on the near side i mean yes the like i mean it will be like a mixed mix of things but

69. 39:34

    yeah like it's you'll need like pretty much in one place you'll need to have like rlp encoding of some things but i mean yeah yeah medium actually has has a like well first of all stadium has this but actually this is an input that the front end will be generating anyway so like it's front and that defines you know when you send funds where should i should go yeah sure sure well okay yeah in this case in this case

70. 39:58

    it is going to be just a general change for so it is not going there will be no ifs uh it's just like well if if we specify the callback then then do the callback if not then let's not do it and that's it uh okay yeah but now now the the question is how we can implement the the internal bridge and and this is what i would have posted internally so we we should literally need to be able from the

71. 40:29

    near uh uh near vm schedule for execution and ethereum transaction because uh literally this bridge what it should do it should be able to deploy an erc20 token inside of near evm it should be able to mean some tokens it should be able to transfer these tokens yeah or potentially burn if what what do you think is missing alex i think you can do all that uh i i i'm i'm just i'm just checking

72. 41:01

    so i i'm just saying that near smart contracts need to be able to schedule ethereum transactions to the evm um and at the moment yes so the thing that i'm missing in the link here is is how it is treated in terms of so it should be treated very differently from the uh from the relate ethereum native transactions because we relay ethereum encoded transactions and what we are scheduling from our smart contracts is already decoded

73. 41:34

    transactions and we need to attach to the first ones uh we need to account for the first ones with the evm gas which is obviously then recalculated in the near gas and for the second ones uh the transactions from the from the from the internal well from the near native smart contracts we need to intentionally when they are not able to attach if uh they can attach only near yeah so i'm just checking that is something that is possible right now

74. 42:05

    i believe so yeah yeah am i uh yes yeah it's just i mean so the the the kind of the mental model of edm evm is just a contract inside near and so any contract can call other methods on that contract with with the proper arguments and so so deploying a deploying a kind of evm contract inside evm okay need a little bit better better language yeah evm yeah yeah let's let's call yes let's select the contract i mean any vm byte code but let's call it solidity contract inside

75. 42:45

    evm near contract um it's just a call on a method which is called deploy okay so literally you can actually have a near contract near like webassembly contract which has inside it just uh like you know has has a solidity byte code and just you know calls evm dot deploy with the byte code and it actually creates a new contract and then you know you get a callback even and what about what about the uh the encoding and stuff like that because we have the different so yes

76. 43:22

    so encoding it coding is a pain but like you know it's just it's it's a pain that you need to deal with so it's like you pretty much need rlp to rlp and code arguments when you're calling uh contracts inside evm but like we like we have libraries in rust so any any rust contract yeah so literally we need to have like two deploy methods one is the of the encoded transaction and the other of the of not without some coding so just forget about transactions like the transactions that go

77. 43:56

    separately like there is a interface called deploy and call which is just a contract contract methods yeah there's also receive a fully encoded objection and deal with it this is a separate thing yeah it said okay not getting used in the sec yeah yeah okay okay great so yeah two two different types pretty much okay all right so let's let's table that for now we don't have a lot of time left uh one one thing i would raise is that so yes we we do need to upgrade bayonet

78. 44:25

    um preferably sooner right given that we actually are inviting people to hack on it and mike is also a question for you what happened with that blog post you plan to publish is that on the agenda still uh my read on this is it's not in the near future um honestly uh it sounds like i think marketing is working on sort of a like a broad post about like everything we're doing in ethereum including the bridge including this including um i think one other thing

79. 45:02

    so but we but we do want to invite the community and to help hack at this thing so um i i'm not exactly sure i think that maybe the best best way is to kind of like have a lot of twitter conversations about this um but i i don't really know i'm kind of giving up on the blog being published soon can i get a pushback from towards marketing and like say like can you give me estimate like one or two

80. 45:31

    weeks if not then we'll publish it without this uh strategy because we need testing like it seems like you shouldn't block content that's already there and wait for like one push i mean it can be reiterated on a future event if needed like reference i don't think you should like wait for what one i i agree with eugene yeah if if you have content and like i mean yes it's great to have like an overarching thing and we should have it

81. 46:02

    but like actually i don't think we're actually ready for overarching thing because it's not really like on main net neither bridge nor evm so like fully functioning so so i would say yeah like hey you know let's start hacking kind of blog post can go out like sooner independently of the bigger story and then bigger story can be developed as like bridge and vm getting closer to

82. 46:26

    production or in production ideally yeah i had suggested that if um if it doesn't work for the blog's timelines mike could just brought it up as a guest and he would be able to send the information to whoever needs it um mike did you already well i mean twitter twitter storm and with links to documentation always works but yeah else also also like so one one option is just yeah go go

83. 46:51

    post on the forum and just yeah get uh okay just yeah tweet about it was like and then we all retweet and also like link people who who would go up to hack on this right right that's actually uh uh we have now a dedicated evm evm sub forum here so we have under development evm and bridge bridge is pretty empty perhaps somebody can move any relevant post into there for the evm category i already moved a couple of relevant posts uh the token discussion was actually posted in economics so

84. 47:30

    i figured maybe it belongs there but the other other things i moved here just so you know i'll show you uh so mike this might actually be a pretty okay option for getting the word out um i mean uh you have you have very good markdown formatting including including you know embedding of pictures and videos and whatnot and um you can get all the feedback directly onto it it's not a bad idea perhaps that's good

85. 47:55

    okay um all right let's see we'll be on um so outcome is probably published on publish on forum soon i i think we we finished the review on that right it's it's fully everything is ready and waiting for already some time two weeks um okay but so um once once we have the blog post out hopefully we start to get people hacking on it and that does come with the caveat that we wouldn't still plan to change the world from underneath

86. 48:27

    them in terms of the base token so how do people feel about that as in the balance is someone starts hacking money compared on it balance is um right now representative so just get well until you know their balances switch from being near to east they'll just you know get their thousands yeah 100x yeah i need a i need an account right yeah this is an opportunity for lifestyle that's nice to the main at first now

87. 48:59

    right can i link it on twitter please do okay um okay but so in any case uh i think from my point of view we we have to get better net upgraded during february in order to to have time in march for all the all the things we want to do on beta in terms of stress testing and incentivized attacks and whatnot so sooner or get bait l it to be using as the as the near well as the base balance and then then people can hack on it and and we won't pull the rug under them

88. 49:40

    anymore so yeah yeah and i encourage here uh us to solve the the giant pain point that there is in the in the test nets of ethereum is that it is a really really hard thing to get uh the tokens there you're talking about the ethereum testnet cycle yes that's correct so literally in our beta net and test nets we we would probably do not want to have ethereum as is and we would not be able to have it before we have built the the bridge but we need to give people some tokens

89. 50:17

    and which is not the near tokens so it's just like let's design something that will give them will give people some tokens by default and that's it okay so actually yeah so there's like couple things here one is uh the the so the way the way so this is like the other piece is like the the ease as a token right they'll be way too minted uh so we can just on on better that leaves a thing that like some you know faucet contract can just call that and and yeah yeah and that faucet

90. 50:57

    contract has no limits but the other thing is like the all the transactions and meta transactions right they have the payment feature and so like we can just potentially disable like just charge zero for that the only the only the only problem with that is like people are not testing them the yeah it's paid on it so maybe as long as we do that don't test it you know uh yeah well well it's like we whatever we do here with faucets we should probably do and test that as well i know and we should

91. 51:33

    figure out yeah for that if we want uh bridge as well included or not but yeah yeah so those are some of the the obvious next next steps yeah and also also i just want to mention that this is i know that we run out of time but this is also connected with the initial supply of f on the main net once we are going to to deploy this so evm contract potentially this is something that we still need to discuss maybe it would be worth of uh

92. 52:04

    somebody buying beforehand before even the bridge is launched because the bridge should be launched like after the instance of the evm deployed so uh maybe we need to to put in the in the in the uh some some f already there wait why is bridge why is brush deployed after i thought well it's it's just like the next version of the bridge should be like it should be it should be anytime

93. 52:36

    yeah uh yeah for sure for sure um i'm just i'm just thinking about like the separation of concerns uh maybe yeah i would prefer us not to like yeah not to create fake youth anywhere uh yeah but this fake if might be held in the in the wallets of the of the foundation or something like that but like if if we have bridge we don't need to do this like evm should just point at that's correct that's a bridge that's contract well maybe maybe closer to this point we can we can review uh what we can do uh but yeah i'm just

94. 53:08

    just mentioning that that potentially there is something here okay well i think we are running out of time uh does anybody have some quick comments questions oh is it enough for today uh i'll write up by the way all of this on the forum so we've agreed now that um all teams are posting forum updates weekly uh this update will go not only to github discussions it will go to the

95. 53:31

    forum under the evm subcategory and we can discuss it further there all right so i take that as we are done for today yeah one one very small adjustment i i believe the the thing that would be really convenient to everybody if we are going to stop videos uh and then it will be a dedicated video for uh for the evm uh because the next next hour we are going to spend with the bridge team

96. 54:01

    and yeah yeah let's cut it because we want them as separate videos for sure yep okay well then thanks everybody and mike hope you get better soon and talk to you offline thank you bye