According to the cloud
Aleksandr Petrosyan: which
Victor Gridnevsky: thanks everyone for gathering for the bi-weekly community.
Aleksandr Petrosyan: Um, in absence of updates from you know one. I'm going to mostly focus on it out, too, just like we did last few weeks.
So let's go over a few of the
Aleksandr Petrosyan: changes that we managed to make.
Aleksandr Petrosyan: First of all, we've established a new Qing process. We are going to
Aleksandr Petrosyan: lack of a better word. Um set up a process for identifying minimal and waking examples. This should um speed up the process between submitting a bug and actually getting the bug fixed, because the person who is fixing the bug is is also the person who is trying for six hours to reproduce the bug
fruitlessly
Aleksandr Petrosyan: and wasting their time correspondingly.
Aleksandr Petrosyan: We are making steady progress in the foreign country interface for Webassembly. We kind of use setbacks related to
Aleksandr Petrosyan: the people who were
Aleksandr Petrosyan: doing this hopefully. This will be rectified in the future.
Yeah,
Aleksandr Petrosyan: almost done with it.
Aleksandr Petrosyan: The new consensus is
Aleksandr Petrosyan: tested in
Aleksandr Petrosyan: being in process of testing from that into the development. This is a little bit of the confusing. What I mean to say is, we've
Aleksandr Petrosyan: finished all the work that we have to do for the consensus remaining work is cosmetic.
We want to change the Api people
Aleksandr Petrosyan: probably impact performance, but not too much.
Aleksandr Petrosyan: We are starting a testing process for it, so eventually it will be merged upstream,
Aleksandr Petrosyan: quite possibly backported into this stable,
Aleksandr Petrosyan: so that will be um. I'll see. Eight point five. Okay, Mike.
Aleksandr Petrosyan: So we've added base sixty, four encoding.
Aleksandr Petrosyan: So that Webassembly can be in line into the Genesis block. This is useful for permission. Validators
Aleksandr Petrosyan: of interest to Greg O'shea, because um signature check conditions
Aleksandr Petrosyan: a bit more complex to operate than Webassembly.
Aleksandr Petrosyan: Of course, configuration has better default handling. We have split it into two traits, and we've removed defaults. Altogether so that placeholder values are generated and viewable.
Aleksandr Petrosyan: The default-generating program but they're not intrinsic to the values, so you can't have Silent fall back onto a default value in any case,
Aleksandr Petrosyan: whether or not this is an improvement is up for debate. But this is
Aleksandr Petrosyan: a feature that people have been asking for a long time, for
Aleksandr Petrosyan: we've hit the first major milestone in the county
Aleksandr Petrosyan: in a sense that we have access to accounts via the
Aleksandr Petrosyan: expression Api
Aleksandr Petrosyan: um. This is still alpha stage, and tests Don't pass, but i'm personally working on making them pass.
Aleksandr Petrosyan: We'll have some updates right about the time when the new consensus is managed.
Aleksandr Petrosyan: We have
Aleksandr Petrosyan: improve the user experience of using Kegami, and you know how swarm something which we have delegated to an intern is now review. It will be out of this is some module to the army. So the code that is being really isn't necessarily going to be worked into any branch,
Aleksandr Petrosyan: all but it will serve as basis for
Aleksandr Petrosyan: an extension of
it's tooling.
Aleksandr Petrosyan: So we're in progress on fixing the signature check condition. The original intention was that we would have a turing-complete language that would allow arbitrarily complex conditions to
Aleksandr Petrosyan: problem with that is, you're not guaranteed that it will even terminate.
Aleksandr Petrosyan: And since this has gone unconditionally, this can potentially clog up the entire consensus, and it could stop
Aleksandr Petrosyan: you know how um thus laying to rest any myth that we are using to get forward. So the decision was made to simplify this all by itself, and instead move the logic handling into what the standard permission dominator,
Aleksandr Petrosyan: which is the second point in this case we do need to create a N for it, so that everyone is on the same page of what is going on.
Aleksandr Petrosyan: Web Assembly is added. We
Aleksandr Petrosyan: We actually have
Aleksandr Petrosyan: base sixty, four encoding as a previous slide. But we do need to add some more handling into the genesis block, because in theory you could have it inside of a genesis block. But you don't actually have a slop for it,
so to speak.
Aleksandr Petrosyan: And of course we will need to design a common plug-in system. We've had a few discussions. Currently, we are
Aleksandr Petrosyan: debating where it is better to store the byte code and store on the source code as matter data for commission validators?
Aleksandr Petrosyan: Or is it actually better to, since permission databases are not run all that often, and you need to guarantee that they are running in a compliant environment; that they will be compiled
Aleksandr Petrosyan: on the first environment each time it's being resubmitted. This also has the benefit of having slightly better performance. Because you don't have to rely on Webassembly. You can rely on other linkage standards. And since provision nowadays that run on every transaction, this might actually matter a lot.
Aleksandr Petrosyan: But this is something that is left for the Rc.
Aleksandr Petrosyan: If we will touch upon this, but we will not conclusively solve the problem. In the
Aleksandr Petrosyan: the seminari. Optimization is like, we said, almost done. We have to conduct some tests, and it should be fine.
Aleksandr Petrosyan: The key. Some of the county structuring is something that we'll be working on
Aleksandr Petrosyan: planning to work on for a very long time, and we haven't touched upon
Aleksandr Petrosyan: because of
Aleksandr Petrosyan: certain other issues.
Aleksandr Petrosyan: Cactus interoperability is in progress. We have some promising results from the
Aleksandr Petrosyan: the typescript module of the you know highest decays.
Aleksandr Petrosyan: Webassembly. Dynamic linkage is again also something that we're working on and working on with
Aleksandr Petrosyan: impunity as
Aleksandr Petrosyan: some work left. It's not related to the Ffi, and it's related to the internal. So it won't Change the Api much,
Aleksandr Petrosyan: and we do have to dedicate a little bit more time to it. It's not going to be done by the
Aleksandr Petrosyan: but it won't affect the Api as much, so
things will be a lot easier. Then,
Aleksandr Petrosyan: of course, the unified configuration interface will allow us to specify a performance
for civilization discrimination which will
Aleksandr Petrosyan: aid in
Aleksandr Petrosyan: deployment.
Aleksandr Petrosyan: This is of particular interest for our internal projects, which I'm. Not allowed to name at this point, but eventually will be publicly available,
Aleksandr Petrosyan: and of course, but not least, we are setting up a roadmap for fixing versa.
Aleksandr Petrosyan: There's a lot of work to be done, and we have to start with something that is um
Aleksandr Petrosyan: just a good trial of the process first, and then we'll even move on to any major refract rings.
Aleksandr Petrosyan: So what is planned long-term Well, Full hypothesis? Integration is
Aleksandr Petrosyan: a long way away. Reason is, It's a work in progress, because every feature that we add also has to be integrated with cactus.
Aleksandr Petrosyan: The local reputation system. We have decided not to have a global reputation system
Aleksandr Petrosyan: offline transactions which are blocked by the accountary structuring and the power chain compatibility,
Aleksandr Petrosyan: transaction fees is something that we'll have to address eventually.
The
Aleksandr Petrosyan: and bootstrapping peers is a convenient feature that we will keep in the back of our mind, but not necessarily address instantly.
Aleksandr Petrosyan: All right.
Aleksandr Petrosyan: Thank you for your time, and if anyone has any questions, now is the time to ask them.
G.Bazior (baziorek): And I kept one question:
Aleksandr Petrosyan: um
deadline.
G.Bazior (baziorek): I'd like to think that
Aleksandr Petrosyan: we
Aleksandr Petrosyan: have a set of features. But once implemented, we can safely say it's production ready.
Aleksandr Petrosyan: Um! Since we have a time, cadence
Aleksandr Petrosyan: might give you a production ready
Aleksandr Petrosyan: for your specific use case, build that is not still considered a two release. If, say you don't require
Aleksandr Petrosyan: bootstrapping peers or a local reputation system.
Aleksandr Petrosyan: Or if you're happy to sort of like rolling release, do some maintenance and update a few things.
Aleksandr Petrosyan: Um, We are planning on testing out the versioning system with the upcoming release of the second long-term supported release cadet. And once that is done, we will
Aleksandr Petrosyan: basically be able to upgrade your home without having to wipe any information,
Aleksandr Petrosyan: and that will mean that
Aleksandr Petrosyan: you can just ask us.
Aleksandr Petrosyan: When is
Aleksandr Petrosyan: the features that you're using ready will just give you a release candidate, and you don't have to wait for the full release, so to speak.
G.Bazior (baziorek): Okay, I see. Thanks.
Aleksandr Petrosyan: Any other questions,
Aleksandr Petrosyan: All right. I guess we can Stop recording.
Aleksandr Petrosyan: Good. Thank you.