Baseline Protocol v0.1 Update, 22 Jul 2020

Previous Meeting

⏯

youtube image

►

From YouTube: Baseline Protocol v0.1 Sessions 1

Description

Session with Kyle Thomas of Provide Svcs and John Wolpert of ConsenSys talking about changes to the codebase going into v0.1

A

Everybody it's uh john and kyle here from the baseline protocol and we're going to be talking now about we're going to be doing a session. We call go, don't lie and code don't lie is where we walk through the new code of the init core branch that would be pushed in the next month or so so. There's six packages.

B

That we need to look through, or do we need to talk about uh some of them are, um there's really only three that I think you really um absolutely must implement. Really, for that you absolutely must depend.

C

On so there's four packages, I think you need to absolutely depend on if you want to build something that can uh be considered a baseline compliant or in the future. uh I guess the position to absorb the rapidly involving um a base of the protocol or maybe not rapidly evolving, all those the contract.

B

C

Package and the price match, um the persistence of sex characters are um not necessarily required in order to implement uh the core minimalistic um uh baseline. uh You know implementation, um replication or just process circuit, so um we'll talk about the resistance as well. So the first package is the almost package um and what that is is a standard.

B

Unifi interface of the json.

C

B

C

Reference that was demo that kind of gave us all a lot of ideas about how to build a protocol yeah. This is the first release of what you could call this is this is this is early.000 the packaging that forms the protocol uh and patching right and then they're in, like we'll use the uh the um the architecture here to inform the standards. So if you wanna, if you wanna, dig through the level of my ide, we can also look at it on the level of maybe a little bit more content.

C

So if we look at the api, um what we see are a couple things: we have the baseline json, which um this is essentially the uh the design that um ties the basic.

B

C

To the change database and it's away to the position, contracts are easily or track existing contracts that have already been deployed, um and so we're now using this devotional contract, it's actually the same contract where it's, basically the uh the base contract. That was that was the shield that was being inherited um in the right and registered foreign field, um which is the uh the merkle tree shop contract that the watching timber project, I'll probably say a little bit.

C

We're saying, is that there's a shield contractor for people don't know is, um is the container for the mercury that stores the baseline proofs, and if you don't know what that is all about, then you know just going to go through the dots right. That'll tell you why. Why were those and what you know the fact that the baseline could be used as a state marker or a tnt lookup, and um a way of confirming that every counterparty to a particular workstep and based on workflow has verified.

C

It has generated the same results from the same code with same inputs and uh basically has the same record in their respective system. The shield contract is a part of the of the zero.

B

Knowledge process that you know.

C

The verifier circuit right go through that and you have a shield contract that the so when you try to push the the baseline proof into the mercury inside shield contract. The shield contract makes a phone call over two.

B

Very verified contracts.

C

Returned true, we can go.

B

Yeah we'll do that yeah.

C

You wind up in a shield contract being able to say to hide a lot of attributes right, so you can say somebody did something with something which allows us to not allow people just to be observing these mercury morphology changes right and say an answer, change information about who's. Doing what is that.

B

Yeah, you know that's the best.

C

Like it's really more about you know, it is not like that's like an abstracted, but unless I say the statement she has the state machine sort of what I mean is that, like you cannot move the you cannot progress the state of the process. You know if the shield contracts you know doesn't allow it.

B

Right, so that's, okay, so.

C

You're, focusing on different things.

B

This is the same thing.

C

So there's a set of functions that shield contract contains that allow you to do things like check ordering and other debt right. So you can say this. This merkle tree um item can't happen before the seven or three which one happened before the other, and so you can call those functions from uh those are all contained in the shield contract right. So yeah.

B

This is the contract that we're using. So when you call baseline, deploy, uh it says, deploy contract.

C

Given so it's actually done so, if you call baseline, deploy, deploys.

C

There's another method that we have: it's called baseline. It's actually not documented because part of this part of the standard, because it takes a little bit too it's just basically what it does is it? um Oh actually, it's basically.

B

C

It's uh what it does is it um it lets. You name a contract name the contract and that contract must be must exist on the on the rpc endpoint, but the artifacts already have to exist um like the uh that we're doing in the in the spec here in the api and in the api stack right. We have the voice shield method. If we actually want to run runs test. Would.

C

The random vm test within example,.

C

uh Registrar contract right, the registered contractor factory contractor generated a shield contract, a verifier contract and an org.

A

Oh yeah yeah yeah, so this is basically.

C

There's no registered contract.

B

Anymore, yeah there's just like the authors, there's just the erc 1820 contracts.

C

And the yeah, it's like they're.

B

Kind of important yeah.

A

Actually, what.

C

um That significantly changes something that we're doing with the gas service over here that we were interviewing the uh the register, our factory contractor, to make all the um the the free resulting smart contracts, meditating people yeah.

B

C

Some I mean this.

C

The next step in the process is well, let's define one more circuits that we're actually going to use. You know.

B

For this process.

A

Each one of those is likely going to be its own. It's it's own shield, it's under fire contract. So what you do is you you um using the privacy package.

B

You actually um you.

C

You actually can deploy those sort of all-in-one. You can do the setup, so it almost looks like this that we've broken up into more alike like as a developer.

C

Is going to have lots of processes um and so like one verify one shield player and hopefully the future of just one shield, contact in general and hold on to their fires? Really.

B

C

Know are you saying that is the cardinality here? This is really interesting. um um Now what a work group is defined by an order registry and a workflow, you can have multiple workflows defined by a shield contract and a verifier yeah.

B

So basically you have one, you have a workbench, you have assistance, you might have one more. You have one more circuit.

A

Than that and these.

C

Is the thing that actually matters when you're thinking about what does go on chain right? The current your circuit should go down the workflow and have a circuit for workflows.

B

Exactly right, right, yeah yeah, these.

C

Workflows step itself.

B

You have to do this like for everything.

C

Every second, you want to play everything.

C

And then having multiple verifiers.

C

um And people, but then people are going to learn how to manage that flexibility right.

B

C

Price tag to make it too.

B

Yeah, so look at that there that's! Why that's why they need to know if you want to come back, you really need.

C

These you know three or three three four packages that you really need to use and then the assumptions the fourth package, the contracts package- is actually also being used, but maybe it's just already been deployed for you right on the main order and your group? Okay, all right. So that's good! That's a big change right now register contract uh yeah that you're deploying at the registry in 1820. I think what you're just calling it is then yeah it's repeatable right. So now I can do is I can go to it's a people thing right right.

C

I cannot run for example. Maybe I want to create a work group. All you need to do is create a work group.

B

All you gotta do is basically like, um and what is that doing.

C

For me, the worker is it's: actually it's the it's the tv, the registry uh for all the organization is the phone book, it's the phone book, but anyways. Why would I just call people? Why can't I just know in the code. I called it like a roller decks. Yes, but beyond being a fast look up yeah, it never seemed to me that it did much well. It's.

B

C

For the public keys, it's where you can establish other uh other methods of encryption, such as uh having those problems in the same place really important um does that? Does that create an opportunity, for somebody wants to do an exploit grab a bunch of identities that might be obviously, but still right and do some analysis to figure out who they are and what.

B

C

Don't think so.

C

C

This group, this guy, is showing up this publicly shows up in these 15 different groups. I know that I'm in these twelve, I know that this one group only has two guys, and I know that guy is this. Guy.

B

In these other twice different products.

C

Parties and they're having another individual registries that are also uh they're also on chain that are, are referencing the other. You know the original keys right.

B

So I'm late for a second.