Print Endorser Initial with airSlate SignNow

Print endorser initial

hello welcome to another sprint demo from the ever name team that contributes to hyper ledger and sovereign projects this week we're you we so I'm just not off by apologizing especially to the team we recorded a demo two weeks ago and it's sitting on my laptop I'm gonna get it to youtube today along with this demo so people will be able to enjoy that so if you haven't seen the last demo there should be two new demos for you to look at if you're watching this one um so I do appreciate all the efforts the team puts together to do these demos I think it's it's good guidance on uh it helps me a lot to understand what happened and and I think it helps a lot with external cloud late collaboration with with other contributors in these projects so today we're gonna talk about the work we did in this print our main focus on the node side we're continuing our efforts on pbft view change we are gonna talk a lot more about those in a couple of weeks because they're they're getting close to being where where we can share more public you can obviously look at master and see what happened but but they're they're almost to the point where there's completed work to show I besides that it was a lot of polish there was some improvements we made the transaction off the way the transaction author agreement works to the some bug fixes to the way that public ride access works to the way that endorsers and authors interacts so we improved a lot of those kind of things not necessarily bugs in the product but requirements bugs or improvements to polish on the way that the the features work in practice so that's been really useful I appreciate the work the team did on that the we're gonna and we didn't release the release is coming really soon here now we're in the final stages of testing there on the Indy SDK side we're also getting a new release of the SDK out and we demoed two weeks ago tab-completion in the CLI I we discussed some improvements based on that demo you'll see those improvements in the in the way that history works or the time kaboosh works and the his reworks the Michelle history we also did some some bug fixes and and we've been working on a support for the leisa boon - so we'll give an update on that that's coming soon I know people have been excited for us to support this year's a boon to LTS so that's the main items there and on the sovereign token side of developments we we talked previously about our support for for being able to manage the the UT EXO the active UT EXO transactions we we talked about that in the last sprint we sprint demo we finished us some of that we finished up the way give fees work and got a release out we've also been working on some helper scripts to help people that are managing large wallets or or large amounts of tokens and the distribution process so if that ever gets approved we'll have a clear process for doing that in a secure way and that's the that's the summary of what we've been working on so with that I'll let all I'll stop sharing my screen all that artem take over and share the the improvements he made in the SDK for the way transaction endorsers work then we'll have Alex share with us the the fix to high poorly communicated requirements and public right access wasn't working the way we expected so Lin benediction of the foundation realized that and we were able to get it corrected and then vladimer will talk about the new releases so that's the plan for today see sure your screen Artem's yeah hello everyone so Maya dam is about transaction endorsed and let's consider situation when I'm a in out or transaction I would like to post for example schema the letter but I don't want to accept some limitation or regardless of leisure like transaction agreements of payments or something else' but I have some relationships with someone who is who can endorse my transaction submit to the ledger so we as you can you that functionality from the windy point of view being edited just one you function this function calls in the appendix endorses doors it's very simple function that just append the indoors afield to request but are these function append some limitation for workflow how we should with request will be used and now I would like to show a simple demo demo simple demo screen I had written this sample on pythons houses sample use our last living this table the ocean and in this demo I have three are three authors I and some one person is the outer who would like to publish the transaction to the latest kima at skin transaction to the ledger VISTA serving is over him as the author of this schema the second author is endorser who will publish it and then also a trustee just for getting the IDS for outer and indoors from the ledger so here has fabricated collaboration steps like all connecting to the pool open involves engaging gauges and next as a more important steps here has preparation ascending transaction to the ledger let's start my program program and this program will pass on building scam request this is if your step with a major difference kima transaction yeah here here it move to next step I need to look at the auto transaction and here we can find schema transaction yes it is here's our original schema request next I have to come you the windy function to appending doors to this transaction here was an original request and endorser the ID we append it Alex Lutz request again and here we can found a real endorsed Newt it also filled the few clearance was to another actor uh next here in portal moment both original transaction author and in dorsal root sign transactions so here I have to space according multi-sided wavefunction I it's a for the cost of we can call like multi site functions like a typical sign function buzz opinions the second signature it's a bit early to call multi site to get buff signatures of altar and endorser and so let's move to the next step let's look now we have one signature from original ops of autumn and go next so I cannot single is it now let's look it should honor quest we have signatures that are now I would like to submit this request to ledger schema rebound apparition oh yes ah just send it so here we can see the trans our request has been successfully sent to the letter here our response we can see here that I just like me to separate green letter thing so if you look response we can find indoors endorser field and also we can find this different field is transaction altar I like find it odd data here and from so that fields are different it means as original author will be our first person without any role on ledger but and also for this transactions will be different let's go first I check that this game actually has been written yes we get I get schema dispose it contains data so let's eat I believe I would like to note that endorsing keeps in request a later network this network administrator can find who actually send this transaction and should be recharged in case of his a certain ledger and also the fit thank you that looks this is a very highly requested feature the sovereign governance framework version 2 allows the con introduces the concept of endorsers being separate from authors but the ledger didn't support that until now so thank you for that the so to be clear an author says the endorser has the relationship with the foundation to be able to pay for rights there's no other payment system on the network now and we need to ensure that it's that people can't found the ledger things like that and so the endorser has a billing relationship with the network governance with the foundation and then who's who's executing that governance and then the author doesn't need that relationship but the author needs to identify who the endorser is in advance so that they can include that the ID of the endorser before they sign the transaction if they decide to change the endorsed so they have to regenerate the transaction which i think works really well uh now Arden there's an endorser field in an author field is I was going through this yesterday with Linda the foundation uh he asked is it can you have the endorser field optional because you might have an author without an endorser can you have an endorser without an author can you leave the author field blank or do you know should sign and endorse a filling dish you know like a whole transaction it's obligatory to have both fields in this case excellent that's what we accessible we expected but want to confirm very good thank you for that right any other questions anybody house ok we'll move on to the very brief pause we'll move on to the next next item so Alex let me share my screen ok so I'm going to tell about one of our recent improvements can be considered as a new feature or fix about being able to create new jgies without endorsers so let's start with a use case there's a use case so this is more less or in specific use case and this is about the user who doesn't have an endorser role if you would like to create a new party on the letter pain and tokens so just remind of course how the offensive authentication defining or what users can create new JG it's described in terms of our rules and of course I default our rule in Internet is that only endorsers only endorsers can create new d edges so user must have an endorser role to be able to create this is a left arrow sorry network since it's for some payments it's going to extend this rule to allow non endorser users to create new jetties and pay in tokens and this particular use case is it's the user for example aries who would like to create a new GID it may even not have any D ad on the ledger because endorser of course it has a role on the letter and also it has the edge on the letter but it is she doesn't have any edge on the letter she would like just to paint tokens and create a new D ID for herself example and this data can be further used for creation or for credential definitions schema and so on okay so how it's related to signature the current assumption in engine load and solving that every transaction must be signed and of course the ledger must be able to verify the signature so the question for the ledger is how it can do this what public keys the letter should be used for this purification and for this new use case in the case where Alice doesn't have the edge on the letter we ask for this question that Ennis must sign that transaction by the public key associated with the newly created D a G so alias creates a new da d she creates a new public key where key associated with this GID and she signs that transaction by this newly created the ID this is how it should look from this use case point of view the current behavior bars endorse area that it signs the transaction by the existing the ID on the letter that the endorser has so why it didn't work before the fix as I said every transaction that my letter must be signed and the only way how the ledger was able to verify the transactions as signatures to find the public key is to pleasure - this is a di D and the corresponding public key must be present on the ledger and this case it is doesn't have any items or jobs that's why Steven certification failed before the fix but my important thing that the exception for the described situation is a extra transaction in solving plugins because it's not signed by a DI jion's alleged it's signed by a payment address which is a Krypton image so it's his in this case address is equal to the public key so the ledger can get the public key just from their transaction since this is a payment address okay so how it's all related to the earth rules although it's possible to set an hour's constraint to require zero signatures to require zero signatures and bezzerides down for transfer payment transaction the general assumption as we have seen on the previous slide that all the main transactions must be signed by at least one where it's signature and all the signatures must be created against the D ID present on the letter so even if you have specified this rule that we support any role with one signature yeah so the signatures required even if it were zero we still get an error from the ledger because at least one signature must be there so what has been changed but has been fixed there are two things the first thing that has been changed is a signature signature if occation it didn't remove the assumption that every that my in transaction must be signed so this is still true but what has been changed is how the signature verification is and now we allow signing by a newly created edgy as well as described here I'm sorry as was described here so we can sign the transaction by the newly created the idea so now this era fication of signature has been changed so known in transaction or must be still must be signed by the ID present on the ledger but for a unique transaction we allow signing against against a newly created Eid and the very key of course there are checks that the newly created Eid really associated with the working the second thing the second thing that has been changed is a related to the hours constraint although now they accept of legend signatures in case of media creation network administrators might want to configure whether it's allowed to use such signatures for the action of creation of new GID and other potential actions or not that's why it was decided that these checks are done explicitly so a new flag called off ledger signature was added to ours constraint to specify if valid signatures created against the keys which are not present on the ledger are accepted your notification of required number of signatures the flag is optional and it falls by default examples when we when network administrator may want to set this flag to true is the use case that we just considered creation of new DNA permissionless mode another possible example is signing by crypto names we don't support it for now but if there are some requirements for these it can be easily done what do you mean by a crypt in him this is where the the d8 is equal to public key so we have just an identifier and this identifier is actually public it's like in payment address thanks because for the letter of the main I think in order to verify the signature it needs to find the public key so the main way how the letter does these it it finds a very key associated with the GED or not of another word suggest gets a TIG dog the second possible option in case of new GID creation it can get the new the newly created key and the third option is to use a Krypton name that is a user explicitly says I send these by this public key okay so this is an example of the new house constraint to add a new GED in permissionless way so you can see this is our constraint or so we would like to allow creation of new GID either by one endorser one user who has ad ID on the legend has an endorser role or we would like to allow anyone with annual to create a new JG if a huge base in tokens and we still require one signature and we do support all Fletcher's signature this is this is a new flag of larger signature equal to true so in case of sovereign default rules so I would expect that this how it will look like if for some reasons the network administrator doesn't want to be able to create new J IDs by the IDS not present on the letter this flag can be set to false okay so this was implemented in both India node and in these decays it's a number of tests showing this behavior you can see that all the tests pass I'll just quickly go through these the first test is about well as I said before the default rule for creation of new GID on Indian note not on solid but on internode is that only endorsers only users with endorser a role can create them and if you try without any changes to create a new JG by a user who doesn't have any JG on the letter it will be rejected in the next test we change the aus constraint for the action of creation of new ji ji saying that any or with off ledger signature can do this and in this case with the new fixes that we did the creation succeeded so of course so now I also check a couple of edge cases in order to make it happen the very key must be present must be specified because the larger needs needs aware key to verify the signature against because we still require one signature also we require that the destinations and UDID should be properly created and performed and so on so pretty that's it thank you it's excellent to see step by step is getting closer to the vision of the sovereign network which is fully is fully decentralized public utility for identity with with strong governance democratic governance and with the allowing transaction authors to have endorsers if they handle payment for them and be able to have public right access through permissionless right access if you have attached some kind of payment token those are key steps in that direction so that's really valuable it's exciting times now Vladimir's can give us an update on the the release process hello can you hear me yep I just want to say about my changes and additions that were made in external partners are going to share screen yes so we we have on the India note and sovereign site major changes as a new the IDS can be created without endorses that was described previously transaction otters don't need to be endorsers now to just deal transaction and and submitting to ledger can be performed with endorser also we now our tea acceptance mechanism should used should use date and not exact time not exact timestamp and also some bug fixes were performed it that were connected with incorrect request validation and some zmq issues that were found during previous testing also some work were performed on the CD pipeline site and in system tests and also there are many SDK changes on the decay side in the windy and weeks of token so we have a hotfix of forget you teak so request and now it has a limit limit for each sources that returned from the request and also it this request now use puja nation so we are able to return all unspent uijik sauce from some with some shift it is implemented as from parameter for this request and also or we have an addition that we can make state proof for verification for this type of request so most of the changes on the lips of tracking site were connected to our get ETA request and also there are the windy changes so now we have new a couple of new transactions in Indi CLI that is that that sign and the fi address and also there are some v6 changes and also all changes that were performed on say in the node side that connected with off ledger signatures are also supported on the windy side so i believe thats all from you excellent thank you for that the the work to you bill sign with payment address was a partnership it was initially submitted by Mike at the Somme foundation and we will desist on that so that that's gonna be nice simplify the process of exchange of payment addresses between between users of the network and the the the other useful addition is with VC X has some changes that remove the dependency on the Evernham agency that was submitted by a Doug on the Evernham team and was nice about that is that the sovereign connector app in the sovereign foundation github that was released about in December of last year hasn't received much attention because it was too tightly tied to the Evernham agency and with a little bit of work that could be removed now and it could probably be made to work with the the aries cloudy agent python the occupy that was contributed by the governor of british columbia so if somebody wants to look at that this is a good time to look at that looking at what's coming up really briefly on the we're going to largely take a break from working on the sovereign token side of things that's looking pretty good now and and we're gonna take a break on their on the ending node side we want to be very focused on pbft view change so we can get it done in September we're gonna make a lot of progress there we might be able to otherwise but our main focus is pbft view change on the sdk side we're gonna start looking at we want to get some new documentation out as we look at the splits the the evolution to air Ares a lot of the SDK is gonna move to Ares and what's left is going to be the the indy resolver it's gonna be very specific to the Indian legend but the wallet and pack unpack and some of these helper items are gonna move into areas so we want to get the documentation for the current as to keep published we want to improve it so it can feed into that conversation about architecture and we're gonna start working on fully qualified the ID support we need to figure out the architecture there and we have some clean up some some polish work to do so that's the main goal there with that we're out of time is any Brent thanks for joining do you have any questions O'Brien Rd dropped so we're out of time thank you for everybody who did a demo and all the work that went on this these last two weeks if anybody who watches this video has questions you can find us at pound Indy on chat hyper ledger org that's a rocket chat instance and of course you can also interact with us by raising to your issue and and commenting on the issues we've art we're working on so thank you everybody also in wiki hyper legend org there's a list of meetings that are useful there's an indie maintainer is meeting every other Monday and there's a we participate on the Ares working group calls that happened on Wednesdays as well as the identity working group calls that happen on Wednesdays and Thursdays so those are good ways to to collaborate with us so thank you very much