Baseline Protocol The Baseline Show - Office Hours, 26 Aug 2020

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Video 6 of 6: Baseline Protocol v0.1 Reference Implementation Part 2

Description

The Baseline Protocol team takes you through the code of the v0.1 update.
Previous video: https://youtu.be/2WXvTHR4_7Q
Go to https://baseline-protocol.org for more information.

A

So what I've done? I ran this mdm test command and we see the the stack come alive, so we've got it. Ident alice, ident, not streaming the service called in chain um a couple of consumers which are mapped streaming: consumers, the nethermine client for alice postgres provide nats, which is a fork of the nat server that provides decentralized, bearer token authorization.

A

This is an enterprise grade authentication service that then these tokens, um rather a an enterprise grade authentication or an authorization service, called ident bins. These tokens, which then provide explicit access to specific subjects, for example, bob authorizes a specific uh set of subjects from alice uh and signs the token and then delivers it to alice uh when he invites her to uh this baseline worker um alice gets a stats demon, uh which is basically a a a service event chain that um does analog. It basically subscribes to um various various blockchains.

A

The various networks that um that uh that that alice in this case is interested in the stack requires provides back requires redis for caching uh key value pairs that are accessed frequently the vault instance, um and then you see bob's stack start to spin up as well, and then we see like a bunch of logging happening and then we're starting over here is uh the creation of bob's creation of the work group, uh essentially in his local ident service.

A

uh Ident is the uh the local service that uh that implements the I registry interface, the baseline uh api, the baseline spec. uh You see some assertions about how bob has um you know the work group bob's work group that he just created has a bearer took and it's authorized for it. That's a similar.

A

Similarly to what I was mentioning uh regarding that and how that works, um and then a few assertions about how the erc 1820 registry contract in erc or registry contract uh I've been deployed for the work group, um and you see like um the initiator, which is bob in this case. uh You see the the you know. His configuration is saying so that, for uh you know the instance of his initial, you know for his uh participants back.

A

um It basically asserts that he is the initiator, which means that he is uh when that's true um or just like his instance, will be responsible for deploying automatically deploying the work group contracts, for example. The reason this happened is because bob was the initiator um bob is also as the or the initiator is also um it's not required, but likely responsible for setting up the first uh workflow, uh meaning uh the first zero knowledge circuits that are required for uh the work group to be productive in the baseline context.

A

So we do make some assertions around housing. There's some output from socrates, there uh we're using a very basic, no op circuit. um Basically, some assertions are made about the uh how a unique identifier it was generated by um our privacy cert, but by the baseline privacy package, uh every every new uh setup. That's it's! uh Every trusted setup that's run in its service. uh It gets a unique duid assigned to it.

A

The printing and verification keys for the zero knowledge for the zk smart circuit. Basically, the doctor t rocker 2's uh is outputting these keys, and you know in memory nothing's being written to disk. uh In this case um it starts with the verify the raw verifier contract solidity source code was generated properly.

A

It also asserts that the the workflow circuit identifier stored on bob's participants back.

A

It also asserts that the workgroup shield contract was deployed and that the network shield contract was.

A

A

The verifier contract that was generated um during the trusted setup step was also deployed to the blockchain. In this case. We're talking about robson, take a look at roxanne.

A

So if you take a look at roster, you see a couple of minutes ago. We had this transaction pop up over here.

A

There we go so in roster, you see, we have this transaction, we subsidize the transaction uh for the for the deployment deployed to contract, uh which deployed some contracts. Essentially, the work report registered contract was deployed, um and then we made some research that you know we made some assertions around um the bobs or like workers, the bonds participants back had a local reference to um the.

A

On the you know, the erc 1820 registry contract, the org registered contract, um the shield contract um that the shield contract had been tracked in the off chain mercury database. This is actually um a very awesome feature, um a huge shout out to uh tomas, and that is another mind for um just going above and beyond, for this release to um to deliver that. You know this functionality.

A

I think we'll be doing a um sort of a focus segment with with uh very soon to to dig into the into that um very good stuff, um we're asserting that the um um the workflow circuit. uh You know that bob's organization has a reference to the workflow verifier and that the identifier is also cached.

A

We are asserting that that a nas connection has been established, we're asserting that that bob's stack participants back successfully connected to nats and established a listener or a message handler for asynchronous handling of the baseline.inbound uh map, subject, which essentially allows for any uh authorized uh they're like any anyone.

A

Who's been authorized against using using a bearer token find by bob can connect to bob uh and as long as bob is granted permission on the baseline for that for those um those connecting uh entities to publish messages on baseline.nbc messages, they are protocol messages uh based on vertical messages that are handled by bob um bob is a server that bob's organization is inserted in the local registry. It's asserted that um the on-chain registry uh bob that bob's um got received a k1 key pair.

A

um Basically false uh um is used the vault service that is part of the provide, stack and part of the the ivault interface with the baseline protocol.

A

That eyeballs interface is used to generate a k1 key pairs of ethereum public. You know, ethereum address um the address representation. The ethereum public address representation that k1 key pair um is used uh sort of as a sort of like a primary key.

A

If you think of a traditional relational database- and that's used to look up the organization uh on the blockchain, interestingly, that that um that k1 address that public ethereum address is never used to find any transactions and that's another interesting um functionality or feature that um our vault, the provide vault service uh supports, is the ability to restrict uh signing so like you can use use. uh You can be certain that um you're not leaking sensitive information to the blockchain, because the way the vault service uh protects you from yourself essentially um like.

A

Essentially that address is never used to sign a transaction that key rather uh and then the hd wallet is subsequently generated for each organization. You know that uses the vault and those hd wallets, uh never allow a single. You know one account within within the uh with them.

A

No no hierarchical deterministic, like key derivation path, is ever used to sign two transactions. It can only be used to sign one transaction uh and that again uh creates uh more guaranteed anonymity, uh and you know it's harder to you know it's no transit. There's no address ever assigns more than you know more than one transaction, it's much uh much safer in the context of a work group, much safer in the context of the public blockchain.

A

um You know, there's yeah, that's a good feature, um the organization's associated with the local work group uh and then here's some here's the assertions around the vault. uh He created a default vault for bob. It created a default set of key pairs for bob. It created a you know: an elliptic curve, a baby ginger elliptic curve key pair for bob.

A

It's used for the the um it's just it's a special curve, that's used for for the privacy protocols, um the k1 key pair was generated, uh and then- and basically you can use that key pair then to resolve the organization on chain and identity. So that's where that 50 milliseconds comes in this actually hit the public blockchains to verify hey. That organization is in the is in their word registry contract and that and the key that we expected to be keyed against, like that primary key that I mentioned using the primary key loosely there.

A

It is. It is keyed against that primary key and then um sort of the big, the big one, the most important one, the one that's gonna do all the heavy lifting here uh is is the the dip hd uh wallet that, like I mentioned just just moments ago, uh will only let you sign a transaction uh with with a derivation path once or one transaction for derivation path. Sign um awesome.

A

So then we start to talk about alice, and we uh we assert that hey um alice was invited to the work group. um Alice then accepts the invite and a bunch of uh of similar.

A

uh You know um well, this is the invited context, so we started uh that alice's, you know, has the same config like this, how we did bob except we assert that alice is not the initiator of the work group, um not just for some sanity around um around the chesapeake. um We verify the um we.

A

Basically, we make sure that the work group that alice got a copy from bob when she pulled down um the data about the work group uh from bob and bob bob invited her alice was like yeah uh I'll, took the invite she's. The decoded bear jwt bob citra as part of the invite process, to look up bob to look up the work group and to pull down data from bob directly, because bob also included that assigned jwt in the invite for alice.

A

So alice could directly look bob's, messaging and point out on the public blockchain and connect directly using um assigned bearer authorization. Token uh then, did by the item service.

A

Yeah so uh similarly uh we're going to make some assertions that alice when she pulled the data down, she got. You know uh a same copy of all the costume contracts that bob got. You know the rc1820 registry contract, the on-chain organization registry contract, um the work group shield contract the off chain, merkle tree database got tracked that shield got tracked um and then um there's a local reference to the the verifier, uh the workflow verifier um and the workflow circuit identifier was also cached.

A

Similarly, to again we're going to establish analysis was alice able to subscribe to baseline.inbound protocol messages, um see what she was was alice registered in the look into her local work registry.

A

Was she registered in the on chain which she was? She was with alice added to the org registry contract on chain um and.

A

Where she associated with the local, uh the local work group, um alice's vault, got all the same uh treatment that bob's did and then here we we uh we make some additional assertions about counterparties here, which is really a nice addition um where we're talking about uh how um each like bob has a local reference to alice and and alice, has a local reference to bob, and they can both talk over the baseline protocol, and you see this initial proof generation work step um that actually- uh and you say we see this log message and we see some um like the the tx rx counts are being started here.

A

um You know they're, uh we might, we might put in a couple of more uh test tests into this suite, but um you know all in all this is this is about. As far as we were able to get uh for the v 0.1 release, um I'm not disappointed. I'm not disappointed in the result.