Victor Gridnevsky: Good.
Aleksandr Petrosyan: Okay, I guess we're starting with me.
Aleksandr Petrosyan: Everyone.
Aleksandr Petrosyan: i'm here to give you updates on.
Aleksandr Petrosyan: You have preview release candidate seven.
Aleksandr Petrosyan: At some point we're going to have to move the prefix to you, no one is not going to be providing any updates.
Aleksandr Petrosyan: anytime soon so let's begin.
Aleksandr Petrosyan: First of all, let's talk about the things that we have completed, we started by cleaning up all the requests we're now down to nine.
Aleksandr Petrosyan: and practically eight of them almost all of them related that you don't have to, but you know one has one more outstanding pull request.
Aleksandr Petrosyan: Which is open by Greg oh so this present.
Aleksandr Petrosyan: I think we agreed that it would be reopened in September we're not going to close it in the meantime just subic you can retain the comments.
Aleksandr Petrosyan: Now, in addition to that, we have open your QA and established a new QA process which is going to.
Aleksandr Petrosyan: Help us both track down and squash bugs in a timely manner, it will also allow us to discover bugs or quickly, and it will give more guarantees to our end users.
Aleksandr Petrosyan: Speaking of which we're working on improving the error messages and uber or ux We found that most cases well the error messages are appropriate for developers to understand what went wrong.
Aleksandr Petrosyan: They are nowhere near descriptive enough for end users, so people get confused and they don't know what to do.
Aleksandr Petrosyan: Of course, one of the headlining features of one of our.
Aleksandr Petrosyan: clients was that the request the parametric triggers which we have implemented.
Aleksandr Petrosyan: It wasn't something that we considered initially, but it is an obvious application of triggers in general.
Aleksandr Petrosyan: So, right now, any trigger can process, the events that triggered it making it a fully event driven architecture.
Aleksandr Petrosyan: Of course we're working on doctors for tutorial which is.
Aleksandr Petrosyan: victor's area of expertise and i'm getting the word to him.
Victor Gridnevsky: So the idea here would be such.
Victor Gridnevsky: Any documentation, we have currently has a code that can.
Victor Gridnevsky: stop working at some point, so instead of that will include the parts of the code from an activity code base as examples and.
Victor Gridnevsky: decay examples will always be working because they are extracted from actual code base that is tested so there's no chance, something is damaged, that would be more convenient and that would be done for stable and lps of action.
Victor Gridnevsky: So offense to live will not lose any useful information and the conversation will stay fresh.
Victor Gridnevsky: pretty much it.
Aleksandr Petrosyan: i'm not sure exactly and this extends to our other as the case.
Aleksandr Petrosyan: Meaning that.
Aleksandr Petrosyan: All current examples will eventually be synchronized and there will be no chance that acoustic a bit on the documentation site is outdated, best of all, it doesn't involve any other documentation team doing any work so.
Aleksandr Petrosyan: To be ideal.
Aleksandr Petrosyan: Now we are finished the foreign function interface for web assembly.
Aleksandr Petrosyan: almost finished, there are few kinks it needs to be ironed out of them, mostly like bugs and features which are not critical.
Aleksandr Petrosyan: But in that regard, we can already started working on wasn't dynamically.
Aleksandr Petrosyan: We also have better configurable and configuration rates, although I think that after this meeting we're going to actually.
Aleksandr Petrosyan: change those names because they're not 100% clear on what we're doing.
Aleksandr Petrosyan: This would allow us to specify configuration in a deterministic fashion, meaning that it is impossible for us to end up with a configuration unintentionally.
Aleksandr Petrosyan: also simplify adding extra configuration parameters, making them redacted or using external API and is one of the first steps towards bootstrap years, which is something that we have been working on for a very long time and wanted to implement.
Aleksandr Petrosyan: Of course we're streamlining our ci CD pipeline yet again.
Aleksandr Petrosyan: We have much smaller docker container we're planning on adding.
Aleksandr Petrosyan: Distribution specific packages because right now is completely self contained and stagnate, meaning that.
Aleksandr Petrosyan: All right.
Aleksandr Petrosyan: Any package that includes it includes one binary and nothing else, and there are no dependencies to be worried about, meaning that we can effectively use a very simple streamlined continuous delivery process for delivering packages to any distribution in the universe.
Aleksandr Petrosyan: Of course we have completed our design phase of runtime permissions.
Aleksandr Petrosyan: Our initial approach was that Iraq are compatible specific lines is going to be more suitable for private block chain use our different flags is going to be suitable for public blockchain use what we have decided was that.
Aleksandr Petrosyan: The boundary between those two is so fuzzy, it has to be non existent, in fact, we have also been requested to provide hierarchical domains, which we can talk about next time.
Aleksandr Petrosyan: Which is effectively making parts of the blockchain public and password blockchain private so a sensible solution was to make permissions and permission sets runtime dependency, rather than a compound.
Aleksandr Petrosyan: This will also automatically handle the handshake process, because then the consensus engine is going to effectively dictate what kinds of networks are compatible with times out and it will also simplify the hard fork soft fork process.
Aleksandr Petrosyan: And there was a gaping hole in our type checker, namely our expressions we're dynamically typed which was completely unintentional we have plugged it now our expression ecosystem is strongly typed and static a tight.
Aleksandr Petrosyan: and which, of course, needs a few changes from the side of permission validator signature check conditions which we are going to be addressing right now.
Aleksandr Petrosyan: One of the biggest problems, was that same as a check condition was.
Aleksandr Petrosyan: Not quite working as we have expected which led us to believe that it was also too complex system to maintain for no discernible benefit.
Aleksandr Petrosyan: So we decided to reshuffle the responsibilities and more responsibility sister the newly minted dynamic permission system.
Aleksandr Petrosyan: And instead simplify the signature checking different process of this is also going to reduce the surface area of attacks, because the vulnerability and signature check condition.
Aleksandr Petrosyan: can potentially bring down the consensus before consensus even start, which is, as you can probably guess a terrible thing.
Aleksandr Petrosyan: we're also working on Some would argue optimizations.
Aleksandr Petrosyan: There are some very promising benchmark results previously, we could handle something like 10 to 20 transactions per second This brings us closer to several thousands.
Aleksandr Petrosyan: Which.
Aleksandr Petrosyan: Which is probably the bare minimum that anyone will be comfortable with using, but there are still many areas where we can improve the performance and this is just one of the first steps low hanging fruit different like.
Aleksandr Petrosyan: Of course, there is a problem that we have encountered with updating the dependencies.
Aleksandr Petrosyan: We follow a very relaxed cadence in terms of if we don't see unnecessary feature in a rush tool chain and then even libraries, we didn't update immediately.
Aleksandr Petrosyan: But occasionally we do need to keep up with the new API is because they do change, and there are semantically incompatible versions released, so we try to do that and we came across one problem.
Aleksandr Petrosyan: hyper ledger earth that hasn't been updated in a very long time, and that holds back a few key upgrades and is responsible for all of the CDS that's can be encounters in your high view RON Carter bodies.
Aleksandr Petrosyan: We have contacted the hyper ledger versa, maintain us we're still waiting for the reply, and it is probably because they're on vacation, this is actually the usual time when people go on vacation.
Aleksandr Petrosyan: But we do need to consider.
Aleksandr Petrosyan: Also patching the versions ourselves and creating a pull request and possibly.
Aleksandr Petrosyan: Making a few adjustments.
Aleksandr Petrosyan: Of course, one of the features that we have very long tried to start and couldn't was key centric account restructuring meaning, we are moving from an email like.
Aleksandr Petrosyan: Human generated address scheme two and a half or absolute address based scheme, which will also identify different networks, allowing you know how to be interoperable with purpose or political with it future I will educators compatibility as well.
Aleksandr Petrosyan: it's going to significantly reduce the load required to maintain.
Aleksandr Petrosyan: Cross blockchain communication and consortia.
Aleksandr Petrosyan: Of course web assembly dynamic linkage is one of the things that have been working for.
Aleksandr Petrosyan: That part of the year, actually.
Aleksandr Petrosyan: The problem that is supposed to solve is the size of dynamic smart contracts now sorry just web assembly smart contracts.
Aleksandr Petrosyan: and
Aleksandr Petrosyan: Among other things, reduce the possibility of providing 40 code with undefined behavior as part of a smart contract, we are disallowing any allocations directly, without using the dynamically linked API.
Aleksandr Petrosyan: From the perspective of a smart contracts this looks like you're linking towards an operating system that has an allocated and it provides me with an allocated.
Aleksandr Petrosyan: It allows us fine grained control of allocations and the allocations, meaning that we can prevent certain kinds of memory leaks before they happen.
Aleksandr Petrosyan: And disallow them in the future if people find a way to do it in a certain way.
Aleksandr Petrosyan: And of course we're finalizing the triggers.
Aleksandr Petrosyan: i'm the scoped they are parametric what's left is the performance and some data sharing and assess that we.
Aleksandr Petrosyan: Were clean slate rerunning the entire virtual machine each time that we load a new web assembly smart contract, of course, this is a little bit wasteful and it is not entirely necessary given that we have web assembly dynamically.
Aleksandr Petrosyan: Meaning that we can track certain side effects and the smart contract itself is a purely stack based machine.
Aleksandr Petrosyan: This would allow us to reduce the number of operations that are needed to bring up web a sufi smart contract into memory executed and then have everything be committed to the block.
Aleksandr Petrosyan: So what his plan long term a pelagic practice integration again we're working on it, but this is a long process there's a lot of incompatibilities, but we need to iron out one of those incompatibilities of the key accounts restructure.
Aleksandr Petrosyan: We need a reputation system to improve internal communications.
Aleksandr Petrosyan: Again, the benchmarks, which demonstrates it's good performance will run on a single machine, it is highly likely that if we distributed the benchmarks would be.
Aleksandr Petrosyan: Much better put it is also possible that even will be much worse because of a significant time delays and packet loss and he is going to address them.
Aleksandr Petrosyan: Also, we need to worry about offline transactions, the mechanisms that are needed for them are similar to the mechanisms, I needed caste integration, but they would allow us to do, multiple interesting things involving say hardware wallet.
Aleksandr Petrosyan: keys, particularly over you become variety.
Aleksandr Petrosyan: And of course it would open more applications to using crypto as a regular currency melvin as a as a gimmick.
Aleksandr Petrosyan: Certainly we have I to release it as a public blockchain addition to a private block chain, meaning that we need transaction fees.
Aleksandr Petrosyan: And of course we need to worry about the ux, and that is done via bootstrap is, which will also involve all the handshake processes that need to go on, when we are bringing appear online from outside.
Aleksandr Petrosyan: So thank you for your time and i'll be taking questions now.
Aleksandr Petrosyan: i'm sorry I come to you.
Dmitri Venger: I believe those like no questions every single player.
Aleksandr Petrosyan: Okay excellent.
Dmitri Venger: Good coach I believe Victor has some things.
Dmitri Venger: to share with us in relations to the commendation and how we're trying to make it more transparent.
Aleksandr Petrosyan: We were there.
Dmitri Venger: Oh yeah sorry.
Aleksandr Petrosyan: So, I guess, we can stop recording.
Victor Gridnevsky: Yes, okay.