Baseline Protocol General Assemblies, 8 Dec 2021

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: The Baseline Protocol - 2021 Year End General Assembly

Description

A two hour session with the year in review and a look ahead at 2022 for the Baseline Protocol open source community. Learn more at baseline-protocol.org.

General Assembly Updates:

Opening Words - Samrat Kishor [02:00]

Metrics - Sonal Patel [06:00]

EY - Paul Brody & Kartheek Solipuram [08:10]

Standards - Andreas Freund [20:25]
https://github.com/eea-oasis/baseline-standard

Outreach - Marc Haddle [28:25]

Sponsorship - Carol Geyer [30:32]

Grant Walkthroughs & Demos:

Marketing Baseline Framework - Tom Lyons [34:23]

Incorporating Decentralized Identifier Methods into Baseline Protocol Implementations - Spruce & Transmute [45:15]

Test Suite for Standards-Based Baseline Implementation - Ognjen Kurtic, Dewi-Tim Davies, Ballint Sallay, & Keith Salzman [57:47]

ZK CIrcuit for Bonds - Boris Breslav [01:07:27]

Baseline 'Hello World' Battleship - Jack Proudfood, Daven Jones, Stefan Kostic, Manik Jain, & Ryan Fisch [01:14:36]

Unibright Updates (Dropping a proof on Baseledger, Baseledger Excel Demo, & Governance Guidelines) - Marten Jung & Stefan Schmidt [01:23:40]

Provide Shuttle Demo - Kyle Thomas, Biswashree Dey, Daven Jones, & Jack Leahy [01:36:52]

Closing Words - John Wolpert [02:00:44]

A

Hello, everybody welcome to our december general assembly and end of the year showcase, um as you can see, there's a big group of people here, including maybe about 15 people who don't have their cameras on. So we have a ton of members here in the community um ready to present some demos.

B

A

Walk you through some work that was done this year, all right so quickly, I'm going to breeze through the agenda. I'm sono patel, I'm an operations manager focused on baseline and we'll start off with some opening words from samurai our tsc co-chair, and then I will briefly go through some metrics from the baseline community from this year and then we have our friends paul and karthik from ey who will share some words um as baseline ogs and tell us the direction.

A

Ui is going with zkp's things like that and then we'll have a standards update from andreas foyne, an outreach update from our cattle, a sponsorship update from carol geyer, and then we have several grant recipients and core devs who will demo and walk us through some of their valuable baseline contributions from this year and then stefan and martin from unibright will give us some updates and demo how to use how to use base ledger for excel and then kyle and the team from provide will demo shuttle, which will include the excel grant work that was done by bushwashery and then.

A

Lastly, john, as our other tsc coach remember, will give us some closing words all right over to you samrat to kick us off.

C

Thanks um so welcome everybody to baseline's, ear and special and the wrap-up show uh this was truly a fantastic year uh for baseline. I would say um a truly momentous year and you know we now have two co-chairs, I being the fortunate one to join john uh in this in this mission to take baseline to the world. um With that, we also can say easily that baseline has gone global.

C

We also participated in tons of events this year, uh I'm going to take you through some of the events that that that were noticeable. That was that were uh just amazing. So so we also have uh you know participation from eaic today, um so we did, we did ea deep dives. uh You know dan and kai martin they've been they've, uh they they've also come into baseline, shows and they've spoken about.

C

What's going on uh with the ea community projects, uh we had, uh we had amazing representation at india's largest tech event, which is nasscom's annual technology conference. uh John was there kyle and andreas. They were speakers, I'm part of the core, organizing committee. For that event, we were also speakers at heath.

C

Atlanta john was representing uh us at each atlanta 2021 uh and provide, of course, being the anchors and behind it then we have a virtual london meetup nick criticos was was a speaker there and and and nick I must say that was one of the most amazing pitches for for baseline, that I've come across, so so kudos on that, and then we also had a physical event, which is all things open.

C

Then john was also a speaker there and, of course, organized.

D

C

Participation by oasis, we also were at iot world nikritikos was a speaker there uh very recently and uh mark mark haddle was a speaker at hit labs 8th annual innovation summit. Now this was also a very interesting talk mark. Thank you so much and um yeah I I totally enjoyed it there's. There are also a couple of events where I was a speaker. uh I've done a I've done a virtual session for uh students at columbia, university um there's also an upcoming eea session for uh where I'll be introducing baseline protocol.

C

So these are these. These events just just bolster our belief on the drupal, truly global magnitude of of baseline, uh we're also joined by amazing people in the core devs community um and and and the outreach team outreach team has grown manifold uh mark. How many members do we have now?

C

How are you going to figure it out.

E

Yeah about 16 and growing.

C

Yeah, absolutely, and- and I remember those days when we used to have calls where just four of us would show up so so I think I think we've grown manifold. uh This is very, very interesting and I would again like to harp on the fact that we've gone truly global. uh Some of the amazing most amazing guests have shown up on baseline shows, uh which, which john and I conduct on a weekly basis.

C

um So we are also gathering we're, also gathering interest from the other side of the world, and it's also from the asia pacific region. Very recently, we also had contact with some people in australia, so we will be presenting to them in january.

C

These are all these these. These, these all, will go a long way in in making sure that the baseline community grows uh and we get the right talent to join us and start contributing. um So that's it from my side. I I would like to kick this off and and a very amazing lineup of speakers for today. So all the best take it away.

A

Thank you and to piggyback off of what you just shared, I'm going to just quickly cover some metrics, so our community health. We have about 1, 174 members as well as 14 sponsors, which carol will walk us through the growth over this year. But what I'm most proud of currently is.

A

Our core debt group has 44 active members who have joined meetings in the last two months and that's something that we just kicked off in october, post, east atlanta and prior to that we had about six court of members who were actively attending what was called maintainer meetings at that time, which our maintainers have also grown from 6 to 11, which means the control of the repo and merging privileges and such has expanded across other contributors in the community, which is a great sign of growth.

A

During our tsc, our technical steering committee elections in september and october, we had 40 eligible voters, which means, within six months of that time period. We had 40 people different people who had pull requests merged to the repo based on signups. We have about 39 people interested in initiatives on the outreach team, as well as 25 on the standards team and then in terms of activity. So we kicked off blips this year, which are our baseline improvement proposals similar to the ethereum improvement proposals, and we have nine in progress and just a reminder to everybody.

A

Anybody can submit blips and they will be vetted by the tsc in quartus, as possibly being part of our roadmap going forward, and we are also grant gifted a hundred thousand dollars in grants this year by the ethereum foundation, which we will be um allocating 100 of it by the end of the year to completed, grant work which we'll be showing to you today, as well as just some increases in github activity, which is a great sign that we have developers and others in the community actively participating in the work being done.

A

So that's all. I will cover on that um and now I will hand it over to paul brody and karthik from ey who will share with us.

F

Hey thank you. Thank you very much uh so paul verdi, here, global blockchain leader at ey. Actually, I was really delighted to get john's invitation to today's event and the reason I I wanted to join and I don't always join in all of these.

F

I know karthik is always on board, but the reason I wanted to join in today was because uh I hope I can share a little bit about well, first of all, my thoughts about this year and then, secondly, just a couple thoughts about where I hope uh we'll see things go next year, so, first of all, in terms of this year, I I want to say you know. Thank you thank you. So now I thank you john.

F

I mean you know, I think about uh one of the very last meetings that we got to have uh before the pandemic. Like a year before that pandemic started. We got together in japan and we had this chance to kind of sketch out the ideas behind the baseline protocol and baseline and back then it was radish 34, and I I love the fact that I sent you like a christmas. I, like a stuffed radish for christmas and you're like what's this. Why did you send this to me right, uh but and I'm sorry in advance?

F

I didn't get you a christmas gift this year, so uh I'm gonna make my public apology. Now um I you know we should we really should give away some radishes. I fully agree with that comment like we it's a little piece of history um for those of you who know about rule 34, it's a it's a long running joke in the internet uh and I'm not going to explain it because I think this is being recorded, but um uh so john was like you know. We need an enterprise level, traceability system and infrastructure.

F

That will be so good that you can pick out a radish, a single radish from like a huge like shipment and know what happened to it and, of course it had to be radish number 34 because of rule 34 and again not going to explain it. It's too much of an inside joke.

F

That being said, we now have a proper name which is baseline protocol. We have proper marketing, we have proper leadership. We have. uh We have this incredible community of participants who are engaged, and this is something that that I am just kind of really delighted with right. uh What john has done in terms of engaging and driving this forward is amazing, and I could not be more grateful and really thrilled also with the work that uh provide and others have done, to kind of step in and think about base ledger so this year.

F

If I, if I think about all the things that we wanted to do with baseline protocol there's, there were two sort of major components. The first was think about the public blockchains as a mechanism for middleware, and I think we are actually really nicely on our way towards that right. um You know baselining and base ledger are big positive steps towards that.

F

The second thing is enabling secure private business logic on chain, and there are really important reasons why we need privacy and private business logic on chain and in particular, they're also really important reasons why we need to think about having business logic that can execute on chain and inputs and outputs of business processes that can be tokenized right.

F

So if I have a procurement contract or a business agreement, uh I want to be able to run that yes, yes, my regular shirts are in fact at the cleaners, it's really cold in new york today, uh so I'm wearing a super dorky, but incredibly comfortable wool shirt. um Tomorrow, I'm gonna be on this uh uh zk polygon zk summit day, I'm on a panel with vitalik, I'm busting out a shirt regardless of the temperature. For that you may see some of the side effects of cold weather. I'm not gonna, make any promises about that.

F

um But uh where was I okay? We're talking about uh kind of what the future path needs to be and the future path? I really believe one of the things I'd like to see is more work around zero knowledge, right, more work about implementing privacy, moving private logic on chain and getting inputs and outputs of the process. So a smart contract executed on chain with privacy will allow me to reliably calculate how much a company is entitled to say for a volume discount.

F

The output of that is a purchase order. I believe the output of that process, the purchase order- needs to be tokenized itself so that I can take that digital purchase order token, and I can borrow against it in a defy ecosystem and similarly, when I've shipped my product- and I have an invoice, I'm going to have a receivables token, and I want to be able to see that receivables token become transactable in a defy ecosystem as well, so privacy, more tokenization and also more stuff.

F

More efforts around building business business-to-business address books, I think, are going to be very important for fy21. We are we're doing our kind of classic agile program increment in january, we'll be sitting down and thinking about what blips we want to put forward and what sort of strategic roadmaps and we'll be soliciting advice and input on that. We also want to put uh the baseline protocol to work in polygon nightfall, which is the privacy-centric zk optimistic roll-up that we are building um that polygon is built in cooperation with uh ey.

F

So that's where we are I'll just pause there for uh comments, questions, um harsh criticism from arbitrary people in the chat that kind of thing.

G

Hey paul, it's great to see you thanks for all the kind words- um and you know there's some folks that that you haven't uh gotten know yet uh like samarat and and others who um I I think in 2022 you're going to be uh really excited to to be watching what what everybody's doing it's? It's. I think it's powerful that we're um now a co-chair environment, not a single chair. That's you know, uh that's a good, that's a good sign and I think simon's doing a bang-up job.

G

There's lots of people out here, the the uh unibri folks, but you know, one of the things I wanted to ask you about was was zero knowledge. I mean if it weren't for ey pushing. I remember resisting this a bit.

G

You pushed the zero knowledge thing hard in the very beginning when we were just cooking up some stuff and and now our statement of what baseline is, doesn't have the word blockchain in it much it. You know it obviously has blockchain in it. But it's not the first thing: you bang a ceo over the head with right. It's when you need to quit.

F

The first thing I bang for the head with.

G

Yeah, well, you can do that, uh but because you're you uh but um but you know with with a lot of folks, I'm sure you agree- I mean it's. The blockchain story is kind of on the wane in terms of uh you know, because enterprises have done six years of bad blockchain projects, so they're a little sick of it. So.

F

That that that part is true, but I don't agree with you so it that part is true. In fact, I saw a thing on twitter yesterday absolutely killed me. It was. uh It was a thing it was like this is a startup pitch deck from the future, um and it's like ours, our startup uses open source technology called sql, it's hundreds of times faster than a blockchain, and I just thought you: you can have a hundred percent of the private blockchain market.

H

I

You and please.

F

Take that forward, um but for public blockchains you know, I think, maybe in some circumstances right. I think one of the unfortunate uh lessons of the last few years as large corporations. Indeed, the last couple decades is large corporations tend to they tend to to go into early. They do a bad job, it's not successful, and then they proceed to learn all the wrong lessons. They're like wow, that failed. I guess blockchain is a terrible idea um and this is incredibly frustrating.

F

But if you go and talk to people in the finance business- and I was out by chen chenna uh chen zhur and I were out at uh uniswap the other day right I mean these people are transforming the industry, everybody in the new york area, who is focused on finance, it's spending time, thinking about blockchain and d5. So I hate to disagree with you, but uh blockchain is still top top of mind for everybody in finance and it is rapidly coming back to top of mind in supply chain. So I um that's.

G

Good but I would say you should you should not? I should I probably, I probably took you off topic, but let's talk about zero knowledge, real, quick before we lose the segment I mean, wouldn't you say that in 2022, especially zero knowledge uh techniques have become non-controversial. First of all, four companies and a real easy sell right, which is hey. um We need to coordinate, we need to prove that we have the same information and that we need to prove some attribute of that information without disclosing the actual information.

F

G

F

And the ramp on dk roll ups, zk privacy tools, the general set of kind of investment in zero knowledge, architectures and tools is going to be enormous, so 2022 is a year, it will not go mainstream and it won't go mainstream in 2022, not because it's not a good idea, but because there's still a lot of variability in the standards.

F

The proposals, the plans, there's a ton of zk roll ups that are not private uh and then with polygon, nightfall we're offering a zk optimistic rollup with actual privacy there's and by the way we still haven't dealt with properly private business logic on chain as well. So 2022 is a year in which it'll be this kind of explosion, of an innovation and investment and towards the end of 2022.

F

I think we'll start to see maturing and industrialization of these zero knowledge tools. Right always, I feel like a couple of years after I was mentally ready for us to be there, but it whatever it is. It always takes longer than you think it will.

G

You are the elijah, you are you're the prophet in the wilderness. um Yep. Thank you for that. Well,.

I

A

Thanks for joining us, paul and karthik.

J

K

L

A

Wrap us up on this segment.

K

um Yeah, absolutely, uh I think, paul and john covered quite a few importantly.

F

I will never have karthik's hair. I just I'm just gonna say that right now I will have the great t-shirts, but I would not have hair. That's sorry, karthik. I interrupted you.

K

uh Yeah, just uh let's just spend one minute on uh some of the priorities as paul discussed uh and they'll go specifically into somewhat more boring details, uh specifically around governance and how we can promote the usage of a multi-party situation in agreements that are that can be signed off by multiple parties.

K

We have come a long way in terms of standardizing the tool set, standardizing the api sets and also using standards for the baseline protocol and in collaboration with some of the ea focused groups like l2 scaling. We are also looking at some of the use cases and techniques or design approaches that can be used for scaling, l2 solutions and false points, specifically in using trolling and nightfall.

K

One of the aspects that would be great is to see how multiple parties can coordinate enterprise business to business communication and using multi-party communication and multi-party signatures and usage hypnosis type safe wallets is something that would be key as more and more organizations are joining the baseline protocol and adopting the base computer.

K

That's the last comment, I would say.

A

Awesome, thank you both so much for joining us and I look forward to your involvement um as we kick off. 2022. um karthik, it's great to have you in the tsc um and we look forward to how we can use what's going on at ey to help with our road map going forward, and next I will hand over to andreas, to cover standards.

L

Thank you. So thank you uh especially to you for your wonderful work. um uh uh This last year, it has been tr that you have been a tremendous help, a tremendous uh driver of the community. So thank you for that um so standards. um We are now paul I'll I'll, come back to what you said in a um um in a second only to say that we have now a first um draft release um of the standard.

L

We're currently I'm doing some last editorial uh um cleanup and it will be then formally published as a first release, not a draft standard yet um because the pgb has not yet defined what the requirements are for a draft standard, let alone a full project specification that is still a to-do item for the pgb um once that is settled, however, I'm sure we will quickly and smoothly move through that process to arrive at a full project specification.

L

uh Anybody who's interested um the the the current the current uh full draft, which comprises of some 300 plus requirements. um 50 plus recommendations should requirements, and I don't know how many uh conditional requirements can be found on on on github. It is a.

L

Long and boring read even though john promised he would make an uh make an audio recording of the read from that so paul. If you want to implement anything with zk, please look at those those sections that are specifically dealing with a tokenization and the requirements in order to prevent double double uh spend and look at the requirements for the for the for proof, sizes, etc. That that should be that should be should be, should be in. There should be highly enlightening, and I agree with you um we will.

L

We will need those those tokenized, um the tokenization going along with the zero-knowledge proofs, but we also not only need that, but we also need that recursively, because you need to have uh the entire audit trail um there for other purposes, as you well know, without revealing anything about the participants, so um anyone who can who can think think of an approach that does not involve uh recursive their knowledge proofs, please let me know I would be. I would be ecstatic about that um by the way.

L

If we're doing that, then we are actually one step closer to to really very compact and fast block chains, because then we can represent everything as as as zero knowledge, digests and every participant has update, keys um and, and can do that and all the validators can then simply um uh verify one proof um as a recursive um as a recursive proof.

L

Anyway. um Having said that, I would really like to to call out um a couple of uh people who have been instrumental in in in the standards work and please let me know when I'm running out of time. um You know it's like it's like kyle has been uh um tremendous um in in his con contributions, especially on the api stack, which we, which we wrangled over for for for the better part of of august and and uh september. It was a truly titanic struggle.

M

It was, it was great working with you andreas. Thank you.

L

It was it was, it was it was it was it was, um it was awesome and iso frank who's. Not here um has been a tremendous leader in in in the in the standards, work and, of course, john, has has always loved to to chime in. I will never forget our discussions about about uh work groups and workflows and work steps, and what comes first, um the chicken or the egg, and we settled on that that that they come at the same time, the chicken and and the egg they're both there at the same time.

L

So it's it's like it's like a kind of like heisenberg paradox.

L

um I going forward uh we're going to focus more on um defining uh the um apis for bpi interoperability uh that comes back to um the future of blockchains. um The the public chains will will end up being the settlement chains. Nothing else um everything will move between between l2s, so bridges are going to be really important: trustless trustless bridges um in order to move assets.

L

Across the first attempt to especially to to talk about standards around that has been done in the baseline protocol spec. Anyone wants to take a specific look at that. It is in section 5 in order to be exact, section 5.5 um and following so that that's um that is definitely significant work, because again um people don't want to be lost.

L

A

Oh, he seemed to be breaking up. Andreas.

A

Okay, we we lost him. Thank you for your update andreas.

L

Sorry that I was my my zoom zoom told me that zoom unexpectedly quit on me. So no.

A

L

Like it was, it was said, but I think I'm out of time right. So um I would I would uh um again thank you, everyone um uh uh for the work and looking forward to next year. What will drive the standards um not only to be a project specification, but we will wrangle this into the uh oasis itself as a as a a tc, and then we will make this an official oasis, oasis standard.

G

Andreas, I hate.

L

G

Interrupt but but probably important to also note right that in 2022 uh there's a real opportunity for um uh commercial opportunities in building making um in in offering uh testing services, uh certification services yeah any certification, comp organizations out there that you know trade in certifying. um uh You know standards. This is the time we'll be looking for you and um and there's some money being there. It's going to be me. Yes, thank you, john for.

L

For that, yes, we need, we need test fixtures we need test harness to to to do that. um That is, that is a that is an uh part of where also the core devs will need to come in and we're we're gingerly uh starting to walk down on that on that on that path, also, on the on the on the chord f side. So that's that's definitely going to be a multi-party uh coordinated, not under zero knowledge effort.

A

Thank you. Thanks for your update andreas and over to mark cattle for an outreach update, you're, muted.

E

Okay, uh hi everyone, I'm mark cattle, um it's always been around hanging around the baseline community for the past year and a half and uh have really started to wear a lot of hats, but uh working most heavily with the outreach team.

E

What we're doing right now within baseline protocol is, we are on the cusp of releasing a lot of capability right now and what my team is going to be tasked with doing is putting together all of the sales collateral. The outreach, the uh you know, the facing material of all interested parties- and we want to you know, come up with content that is engaging that has direct impact.

E

A lot of us are veterans of many different distributed projects that really didn't quite turn out. The way that we wanted it to, and we gained a lot of knowledge through that, and we are certainly going to be applying that um with that top of mind, as we put together all of the uh content for that uh this also includes uh getting a really. uh You know good go around of the um of the website, uh so we were gonna, be.

E

Have it be fully functional to where anybody who may be a casual uh uh interested party uh can go in and uh really you know, glean enough information out of it as far as what they can do to uh you know, move forward with it. So um all of this is happening almost uh in tandem with the product launches.

E

So many of the things that we've written in the past couple of weeks will probably need to be heavily edited based on the demos that we'll see today, but everything that you're seeing outward facing is pretty much result of an exhaustive collaborative effort from all of us and we're the ones that are really you know putting it to paper.

A

Thank you so much mark and over to carol for sponsorship updates.

B

Okay, I was, I had put together some slides. It's saying I can't show them is that I don't want to slow things down. I just never get tired of seeing my sponsor logos and I just wanted to share them with everyone.

A

um John, you may have yeah.

G

Carol carol, uh proceed and I'll see if I can get that up for you, of course,.

B

Okay, uh well, we're super excited about the year in sponsorship for baseline. um We've got three new members since the last time. Well since october, and the end of october uh arca, mover and montec, and I think they're I'm excited about them because I think they add a new diversity and dimension to the type of other sponsors, the other 10 sponsors. So now we are at 14 sponsors um and we have another real marquee international brand name company that is working feverishly on their paperwork and we're. We fingers crossed that we'll be in this month.

B

G

I hoped it was today.

B

Yeah yeah well, but but maybe before the end of the year, um and that will be something that really is going to impress a lot of people in the industry and we're just super excited about that um and then there's a potential of another large company, probably more likely in january, so we're seeing some real um momentum.

B

uh Let's see, oh my pretty slides, you don't get to see me.

G

No, you can, you can share them right now. Can.

B

I show you no okay, sorry. This will be quick, though.

B

Great all right, so those are the new logos. Those are all the logos of all 14 members we have now.

B

We started this with three baseline with consensus, the ethereum foundation and eea. We added seven. Last year, four, this year, ey came in earlier this year and the three that you saw and, like I said.

B

Hopefully that will be five by the end of this month, and I think you know I'm confident that we're going to definitely get to 20 or uh beyond, in 2022 we're really seeing that momentum start to pick up and where we talked and had long drawn out conversations before we're seeing people join much faster, and I have to do a shout out to the companies that are represented on the technical steering committee, because those tsc reps, if they weren't already sponsors, really have been doing a lot of work to try to get their companies to also put funding in this as well as their time.

B

uh The group that mark was talking about the go to market group. We have a lot of ideas for attracting more sponsors in 2022, with the new website. We're going to have a fancy, you know join button that will make it very clear, very quickly. Take you to a new join page, which will explain all the sponsorships and costs and benefits and not take you to five different places, but really consolidate that information.

B

uh The new website will actually add a page called get baselined, so prospective companies who are interested in getting more information on on their getting themselves baseline. They can be directly connected with a list of our sponsors and we'll be able to contact them and that will be driving real leads to our sponsors. So we think that is going to be a really great benefit for them um and then, as a small thing, that the baseline show we're going to um a sponsor.

B

So you know this episode of the baseline show is brought to you by splunk or by accenture, and you know just a way to not only to give a little call out to our sponsors, but also to demonstrate to the world um the pride that we have in our diverse and impressive group of sponsors.

B

So this this is by no means all the things that we're doing, but but we're excited about, but those as some major things and we're looking forward to a good 2020 2022.

A

Thank you so much carol and thank you to your team as well, and now we will shift over into some demos and walk-throughs um from grant recipients from this past year. So first tom lyons will kick us off and share his findings and experience on working on a grant called baseline marketing framework.

N

Hi everyone um hope you can hear me and uh it's great to be here. So my name is tom lyons and I was the lucky recipient of the first ever baseline grant and it was actually not for technical work. It was more for on the comms and marketing side to do some support for the uh for the go to market team, and um I wanted to share in these 10 minutes and wait.

N

So I'm going to put my little timer on, but you uh you stop me when I when, if I go too long, but um I wanted to share two things, I want to talk about the work I did, um but I also have a few thoughts on maybe perspectives on the role of grants um in in fostering the community um just based on just based on my own experience.

N

So how this all started is I come out of communications and marketing um with a um I had the emphasis on on messaging thought leadership for complex subjects. I worked in banks, I did fintech and I've been in blockchain for about getting on six years now um of two and a half of those years. I spent a consensus, so I knew john andreas and nick and after I left consensus june 2020, you know john and I kept in touch and he was talking about baseline and I was getting very interested in it.

N

It sounded um it sounded very intriguing. To me and john was saying you know it's, you know, join the community be great. If you can, you know maybe help us out, and um you know I was very interested in doing so, but in my particular case I'm a freelancer. um I have my you know I have. um I have to balance.

N

You know how much time I can put in on as a volunteer with uh you know, with um with earning a living and to what he said I could afford to volunteer and when the possibility of a grant came up, I mean this may sound obvious, but for me it was kind of like a bridge right. It was an enabler because I was able to um to justify a bit of my time. um I was also happy to indulge my enthusiast side.

N

You know by working a little bit, maybe below my rate, maybe putting a little bit of extra work into it, but it kind of got me over the hump, and I think that my point is that I believe, particularly on the content contribution side, as you guys go forward that there may be between the real enthusiasts, who are happy to just to help out and the people who may be working for sponsors who are kind of second to the project.

N

There may be a fairly large community of people of potential contributors who are kind of in my in my um in you know, kind of like me, and maybe you know grants can can be an enabler there. So in terms of the stuff I did so we're talking about last march, I think I began um february march.

N

uh I um put the proposal in the idea was, to you know, sort of help, support the go to market and outreach um outreach stuff with, by laying the front the framework or the groundwork, for um you know for some messaging and uh and content for non-technical audiences, and um what I did was I did a I proposed. I would do like kind of a needs analysis right at the beginning, so I'd come in and talk to a lot of the stakeholders.

N

You know review a lot of the documents and sort of bring a bit of an outsider's perspective um in into all of this material, and then I was going to come up with uh with a you know, with with kind of some findings and a bit of a content framework and some proposals for content- and you know I, you know there was a lot of very talented content people on the on the team already.

N

So this is really like an outsider coming in doing some of the grunt work, um you know doing the interviews and collecting the material and coming up with some uh with some proposals I proposed to do 40 hours and um the grant was was was approved and so off. I went and um in terms of the actual work over about two months I put in actually 50 hours.

N

I did a bunch of interviews the reading and I came up with this framework and again we're talking really getting on nine or six say seven months ago, where I you know um put together. You know what would look to me like some of the some of the messaging pain points and what I did was I put together a bunch of briefings for core content. So I was very cognizant during this project that we're dealing with uh in terms of contributors we're dealing with a volunteer organization generally right.

N

So I wanted to to um you know to keep that in mind. I wasn't gonna, I wasn't gonna come in with you know, with um with you know, here's what you got to do but more like here's, some proposals- and you know how are ways that we can. We can help um people contribute and make it easy for them to do, and um so I kind of approach it that way. So I put together a whole bunch of briefings. You know you know what what what can we use for a website? What can we use?

N

You know for marketing presentation. What can we use for faqs, um an onboarding package which I'll talk about a bit later and the idea was here's to have you know here's something you could pull out of the um pull out of the out of the drawer? If somebody shows up and says hey, I want to contribute content. What do I do?

N

You know you have something to do now, a lot of the stuff that I did briefings for you probably are already doing, but I think this approach of you know making it easy for contributors might be a useful way to go forward um and.

G

Can I can, I ask you a question I hate to interrupt. I didn't know.

N

No john, you don't want to go ahead. That's great yeah.

G

I mean, I think it's probably an after promote moment to ask you know it seems to me, and I'm sure you'd agree that this is the the 2022 is really the opportunity for people to do what we were doing in blockchain 2015, which is actually going into companies doing um incubators in company incubators and that sort of thing to to. But I think this is actually less troublesome right, because coordination or zero knowledge is an easy thing to sell it's an easy thing to to make sense of uh and get prioritization on.

G

What would you say? Would I would you say that there are real opportunities for um companies to um to to start making some money on that this year? This coming.

N

N

So be good because I'm not quite sure I understand the question but yeah yes, the answer is, the answer is, uh is for sure. I think you have to.

G

I did pick up covid last week, so I'm probably not speaking sensibly. At this point, I've got covert brain. I.

N

Mean I mean everything I'm doing is is to the non-technical audience and you have to just you have to explain the stuff. John right. You have to get um uh to get people on board or.

G

N

It seems like there's time did I miss your question.

G

I guess that what I'm saying is that your your work when I read it is a playbook for solutions providers like accenture and others and tcs and others to go and start making money on uh teaching the companies how to deal with this and getting their companies under you know all the transformation projects aligned with this kind of work.

N

Okay, yes, the answer is yes, I I didn't actually see it. That way to be honest with you, because I think that a lot of people are doing that well anyway, so I was thinking more in my head. You know, in terms of of of a broader community and and getting sort of visibility.

N

Okay, um yeah so anyway, so I just want to say um so. I delivered this stuff and I think maybe john you can tell me if this is true or not, but maybe um some of the most interesting stuff that I probably delivered to you might have been the interviews right. um You know to getting sort of voices from from the community of voices from the stakeholders of what people you know what what's working? What's not working that kind of thing.

N

All right and uh last but not least, I made some notes here on some of the key learnings that I um that I thought would be interesting for the community. I mean um one of the first things that that came that occurred to me, or that I saw coming into this- was that uh there's no lack of information out there.

N

You guys have a great job of you know, producing content or there's a hell of a lot of information on baseline and on on the whole on on the whole community around it and the business uh in the business case around the problem. Is it's almost too much so my message, number one was curate curate curate and um you know I think and again I'm I think you know your target audience. I remember talking to several people who came in your target.

N

Audience is going to be full of smart and talented people who, who absolutely can figure it out for themselves. That's not the problem, but they have a lot of things to do and they have other other um other opportunities. So my point was: let's make it as easy as possible for smart people to figure it out for themselves by uh providing some sort of onboarding path. um I've talked about focusing on the business conversation. A lot of people were talking about.

N

You know you have a tech driven project, but you need to step back and think about messaging from a user standpoint. um You know it doesn't mean dumbing things down, but don't be afraid to be simple. um I think you all do a very good job of that, but that's something uh to focus on benefits, business benefits, roi, etc.

N

um Making the business case for baseline. One thing that I wanted to raise was how how do you and I'm thinking into the future, getting you guys more content right? um How do you motivate content contributors, because writing is hard content? Creation is hard takes a lot of time. How do you encourage people to to contribute? Obviously, like I said, the grants can help um and again making an extremely clear and easy contribution. Pathway is probably going to be useful right.

N

That's why I did these briefings um uh and that might be a way to say look. You know hey, I show up to baseline. I want to contribute some content. I do this and that says here. What do you need? You know you have something to show them um and you um you know, sort of focus on on the benefits of being a contributor. You know you know. Working you know supporting baseline is is definitely good for your soul. There's no doubt about that, um but it might be good for your career as well.

N

I mean in in my particular case uh the project I'm on now, and I've signed a nice six-month contract with the eeas is a direct result of the work I did here. So it helped me personally and last but not least, um I think I I gave you guys some notes on on governance uh on comms governance. um I think that that's that's a very important thing. I think communications as opposed to to a lot of technical work. There's often not not one right answer, um there's different approaches, there's different angles.

N

Different people have different tastes and as much as I I love decentralization and community, I think when it comes to communications and marketing, sometimes you need a decider. So that was uh that was what I am one of the things I recommended and look. I enjoyed the work very much and I just hope it was useful.

A

Thank you thank you for your work, tom and I hope you stay in the community and help us drive some of the outreach and other work, and next we have two companies spruce and transmute, who are completing a grant. That's titled incorporating an ethereum based decentralized identifiers method into baseline reference implementations.

A

So I will hand over to the group um to present their findings to us.

D

Thanks roland and they suffer from transmute and we'll go first and then I'll hand it over to one who is going to speak about his work at it's true. So I have a couple of slides for the group to share, want to look at amazing uh for the folks who don't know transmute and transmute we are leveraging. Vc is dead, sending data to fortify global supply chain with issue trust.

D

We are deeply committed to our to building um dates as an emerging standard growth of site tree and understand the power of an element, and which was one of them, which was a big motivation for us to one be a part of the community apply for this grant. um We want that protocol to be scalable, interoperable, be high, performing and be cost efficient.

D

This is what got us to the grant in which what we want to show today is or share with the group today. What have we done? What have we achieved as part of the grant that we received I'll? Give you guys a short video that showcases the work uh showcased or share with you. Everyone on how these contributions and growth to the open source community is helping solve real problems that we are focusing on and then leave you with a couple of things for everyone to about where transmute is heading to um our work.

D

Around with this grant had two major milestones: one was about updating the site for ejs. Second, one was about updating or contributing towards a technical execution through dockerfile configurations and supporting documentation, so that was those were the two buckets of the works that we were given funding for now, with these elements for each of the milestones, through a number of pull requests that we can listen to seen on github, all of those elements have been delivered and contributed to, alongside from dashboards, to commit requests to all of those things that everyone can go.

D

Look at things play around and comment and go from there on these elements have already been delivered, they're well into it, into this community functioning and in use, and then to showcase all of it. What we have is a short video that shows how wallet create they create and resolution through these new libraries and updates code work.

D

So what you saw was through now the use of the libraries, the process of creating wallets, creating dates and resolving them feels a lot more like a lot of other things that we know, rather than the more cumbersome process that it was before that now through all of these contributions, the growth of it um transmit is not just committed to one particular open source element or community.

D

We have been contributing to a portfolio of them and we understand why the growth of these communities and these standards is exceptionally important to the broader adoption of technology and for the broader solution of the new problems that we see at the 3.0.

D

Through these contribution of maturity of technology or maturity of each of these standards, we are seeing a number of use cases unfold. The two that we are committed to as of this now is around enabling steel supply chain. So, for example, you have cross-border trade happening from mexico to u.s how the application of vcs and debts across various steps in various parties creates a sense of trust and sense of eases of friction. Points across different areas uh is a core business problem.

D

Being solved, and one of the key reasons why we are one step closer to solving these problems is through contribution to open source and constant encouragement through grants that we received, like the baseline, to contribute to open source mature that technology refine it and seek comments and contributions from all the all other developer community.

D

Similarly, within e-commerce, um working through, say a manufacturer to another country, vendor, say denmark to find the goods landing in u.s the con to use or vc's dead and the maturity. The technology is absolutely critically enabling that use space, and we see the combination of the two playing uh quite a magical way as different credentials are created, resolved and move from one party to another.

G

It's upon uh real, quick I'd, love to ask a question here, um just to sum it up and and to kind of connect the dots for for people. um This work, you know when this delivers, which is imminent.

G

um What can like our yeah we're going to show a few in a minute um some some real teams of bright people, work, building things like uh the the battleship game and the other other kinds of uh baselined experiences.

G

What what's my my experience going to be like? What's different about my experience, going forward as a developer with this as part of the stack.

D

Yeah um I have already also on the call with me he is sort of the cto leading that entire charge so orient. Do you want to comment on from a developer experience the specific elements that will change or developers will see a difference in.

I

Absolutely thank you. um So you know, historically speaking, working with decentralized identifiers and verifiable credentials has required a lot of upfront um commitment from an engineering team to onboard and understand how to use these technologies effectively together and as part of our work uh for baseline. What we've done is tried to smooth that learning curve and onboarding experience so that there's great documentation, uh simple sets of instructions for setting configuration, and that's all that you need to get up and running and have standards compliant identifiers that can be integrated into these products.

I

What creating a better experience around that developer experience does for product folks is that it shortens the time to market for product development based on these open standards. So that's what we're hoping to achieve through.

G

On a practical level, are we talking about? I mean what I remember uh one of the sessions with um the blip six team they're like what what's going on with this org registry thing. Is that gonna be easier now with uh with this, because I can construct uh standards-based uh work groups more easily? Would that be.

I

I think that that question might be better targeted towards the spruce team um for transmute, we're primarily focused on making sure that ethereum has decentralized identifiers that are as scalable and industry um sort of ready as the the bitcoin ecosystem has has been developing with ion and other div methods based on bitcoin. So it's probably a better question for the folks at spruce to answer, but.

G

Which is the other part of this uh grant? Yeah.

I

G

Yeah andreas, do you have a quick? I I don't want to hijack from sonal here, but I just want to make sure people are really getting the value and importance of this.

L

Yeah, so we're talking about um using standards, compliant identifiers, decentralized identifiers at scale. So we're not talking about 5 10 20, we're talking about tens of thousands, hundreds of thousands millions of identifiers that can now be smoothly managed um within a within a bpi right, so that that.

G

Bpi being a baseline protocol, implementation.

L

The key thing is that this will go as part of the reference implementations, so the reference implementations will come standard um with the uh did element um integrated and we'll also uh come a standard launch, a a did element node. That means we're mutually supporting.

L

um We have mutually supporting networks right so so so the the the the baseline nodes will become element nodes and therefore will enable others to to to utilize that element, even even.

H

L

Not utilizing uh um a baseline.

G

Or there's no such thing as baseline node, but like a messaging node that has baseline capabilities, for example, yeah.

L

Okay, yeah as a as a as a node that that allows you to to to create uh um create, uh um uh did element the ids right, so you can you can you can offer it as a service for um for your customers right, which is which is huge right now? You can't do that, but now you can, which means you don't have to bring anything with you now. um Implementers of the baseline protocol can offer this as a service which was not possible before until now. Now they can in a very easy way.

A

Thank you juan. If you want to hop in now and yeah.

H

Sure, uh um in the in the interest of time, uh you guys kind of just did my presentation for me. You didn't leave me much to talk about uh so yeah we're.

G

H

Actually, uh just just working on integrating uh um the transmute teams uh side tree node sort of uh as they go we're sort of playing with the the the beta, the minor releases um and what we did. um So we we um went into br1 and were um switching things around. We were, we were integrating. Our sort of general purpose did tool kit so that just sort of adds a few features to each uh baseline.

H

um Sorry, not client, not node, nut server uh instance, um and um so we we integrated, did kits so that if in uh instead of just using gnats to communicate to other elements already in the org book, if you find yourself needing to have encrypted communications with, I don't know a dead holding entity in the world.

H

uh This just sort of lets you uh passively support, sort of uh read and resolve other kinds of dids, including did element um so where uh these elements have already been uh retooled on our sort of fork of br1 and uh we're just putting the finishing touches. And you know um it's a.

M

If I may, if I may, want it's been, you know a pleasure to work with you guys on this, um and it's it's really cool to see just how you know how close it is. I think that what there's one container, perhaps that we need to add perhaps to the stack or just using, did kit through, and I did make me just it's a wrap at that point. Right.

H

Yeah yeah um it was, it was uh that that was thankfully, the the easy part.

E

H

Easy you're right so so we've already got. We've already got some some features uh bolted on or or folded in, and uh we're just waiting on. The final version of the node uh sidetree node uh to switch over the last of the things so that then each entity, instead of registering a uuid with the org book, we'll just be registering an element, did that that any entity calls the psy tree node to generate and then hands that to the org book and says: here's my here's, my calling card um yeah, so yeah.

M

Hey uh and yeah juan you know, that's that makes total sense uh yeah. I it was a huge upgrade for friday for us to be able to support dudes in that way, thanks a lot for the collaboration.

A

Yeah yeah, thank you all from spruce and transmute for joining us and for your valuable work. And now we have a group of baseline core devs who will share their work on a grant called on a grant revolved around implementing a monolith for a standard-based baseline protocol implementation. So over to you often and team.

O

Thank you sonol. Can you hear me, can you see the screen.

A

O

Cool, so I'm uh ogden, I'm a coordinator with baseline protocol since september uh when we started these core dev meetings and we soon realized that there are people who would like to get involved in the building of the protocol.

O

But at the moment the the tasks were not that well defined and it was hard to really stay, take, something which is small and atomic and to start contributing to the protocol, while learning so through some meetings, we decided that it would be good to uh to actually take the standard which is now already well-defined and to try to build a test suit around it by doing a baseline protocol implementation, which is a kind of a mocked monolith and the result is this blip blip 6..

O

So the goal was to develop a monolith which is a dependency free implementation that can be really easy to start to start to run, to run the tests and to see how it works and to use tdd. For that.

O

Through that work, we wanted to build up knowledge about the standard, so everybody who is involved while doing this also he had to go and look into the standard and try to map that to code. So it was quite a beneficial endeavor then also to have an example, implementation that can later on serve as a starting point. So if you have a a new person who wants to start contributing, you can just point them. Here is an example implementation you can play around with it.

O

You can see how the tests, which explain the behavior of some basic use cases, how they, how they are implemented in the standard and all the components below how they work together. uh We also wanted to create a basis that would then serve as a backlog to build an actual open source baseline reference implementation. So we're really mapping the standard in code and then we are identifying the components that uh that can be implemented separately.

O

I don't know, for example, a messaging component or or the virtual state machine and so on, and of course we have a test suit. That's describing the standard, so quite a big endeavor.

O

Luckily we had some motivated people to work on it, so balant davi, keith, myself uh and also with help from under restaurant. We we started working on this uh a month ago or a little bit more than a month ago. uh There are three dots here because we're open for anybody who wants to join. It's been super fun so far and quite a good learning experience.

O

We are basically starting from scratch, so you can really learn a lot about the standard and help help improve it in the process. So doors are open. uh The method that we used was we started with more programming sessions. uh For you who are programmers. You know this is a rather slow way to do things, but it's superb when it comes to building up shared knowledge, uh and we had occasional touch points with andreas to just fact check this.

O

Are we going in the right direction and he was great help in in leading us there and just a week ago, we split into into parallel streams, because we already have a feeling of how how we can split- and we already have enough of this shared knowledge. uh So we are now we want to try to speed it speed things up as much as possible.

O

What was the progress? I won't be showing you code. There is the branch which is already pushed to the repo, where you can just see all the progress for yourself, but shortly so we've implemented the initiation of a bpi, the workgroup and workstep setup through tests. Also the invitations. When you want to invite the organization to your workgroup, we have the initial workstep execution and update of the agreement state.

O

So, for example, if there is a exchange of some orders between the two organizations, you could send an order, get proof back, which is mocked at the moment and validate that proof against the bpi, and we also have uh basic messaging.

O

uh I would invite davi uh from the development team to to talk a little bit more about the progress related to the zero knowledge proofs. Now we are around.

I

Yeah, I'm here hi um cool yeah so um currently, as omni said, everything's sort of uh mocked in typestrip right now, so there's no actual zk components, there's no actual on-chain components, but we're sort of trying to emulate the behavior of them. So, rather than having actual zero-knowledge proofs, we have uh the validation of predicates with access to the actual private inputs. But I think it's worth mentioning that everything that we're doing to validate these things is still perfectly doable in, like a dural launch proof library like narc, we're just validating merkle proofs and signatures.

I

um The functional terms of a commercial agreement are going to be encoded on the bpi and in verifier contracts, which are basically like zero knowledge proofs, which can look at say.

I

The agreement in an envelope um and a proposed state object like an order and say that, okay, the I promise you that this I can prove to you that the um the item being ordered is actually an item which we agreed to be able to sell and that the signature in this order in this envelope is the signature of one of the counterparties who is in the agreement.

I

And this is the new agreement state that you get after adding the state object so- and I just want to add that this is really really been a great way to try to understand the baseline protocol. I think it's a you know. The specification is a long document and um by building this and working on this, even if it's just mocked up, I've really been able to understand a lot more.

I

What this actually means um and just think the next steps would be to finish these verifiers and start to integrate the zero knowledge aspects with the test suite and start testing these things, because that's currently not been done.

O

Cool, thank you davey, just to continue in the same direction, so last slide about the future plans. So we now have quite a good map of what are the bpi capabilities and we want to try to extract them into respective modules inside of this monolith. So, as I mentioned, you would have the messaging capability or component. You would have the transaction pool the virtual state machine and so on. This is we want to continue on based on this blip.

O

uh As david said, we want to finish the tight script, mocked of the zero knowledge proofs, so implementing the bpi transactions and the virtual state machine, as defined in the start standard. Currently, we are just on the level of exchanging messages and triggering through messages triggering the workstep execution, which is not fully compliant with the standard, but it's clear where we need to go and as a final step, we want to set up a dev meeting.

O

Once we have display blip wrapped up uh to try to translate, then the monolith into a backlog and this backlog would then be atomic independent tasks that anybody can pick up and as we go through them, we are actually together building this first open source implementation.

O

Hopefully we are not out of time. So if any questions we are open for them.

A

Now you have another minute or two any questions or comments from the group.

L

Yes, I have actually a question, um and this this is. This is uh um a question of have you found any deficiencies in the standard so far or anything that was impossibly complicated or difficult to implement, so any opportunities for improvement? Besides clarification and wording.

O

So I guess we will be able to answer that more precisely uh as we wrap up completely the work so in week or two weeks as soon as we dive into a little bit more deeper into the transactions, uh the state machine and then also the davis work, so the zero knowledge. Now we will be able to uh to give a more clear answer. Currently.

O

uh What john mentioned, for example, was what was unknown for us. Is uh this discovery of organizations when we started it was unclear? How do you do that? And but these things got got got resolved so far, so I think we are fine for now and we didn't find anything which is broken in the standard.

G

I'm still living for the day when we have a universal verified phone book.

C

Yeah, let's go type ahead.

G

A

All right, thank you so much, um and we have recorded the sessions that this working group has been um going through and we'll hopefully edit and put those together to serve as a resource for developers and others in the future. But thank you all for your work and next up. We have boris movies here who did demo um their code for their work for zero knowledge circuits for bonds. But today, boris will briefly walk us through the actual use case and value that that provides for baseline. So over two boris.

P

Thank you. Can I show my screen.

A

P

Okay: okay, let's see you can.

A

P

Yeah, you can see it's great, so just just just a bit a bit of background, um so I I kind of I and lewis we started looking for uh uh myself and luis suarez worked on this, so we started looking at blockchain a few years back, probably about three four years ago, and what, uh since most of my uh time my work time I spent in the financial industry, I said it's great technology, but uh at the same time I couldn't think of real, uh like some great value, because for specif specifically for uh public blockchains, because I said to myself- I I can't think of, like any scenarios use cases that that that a bank would put up any financial or personal information out to the public there.

P

So I said the technology is great, but I don't know I don't know really where this is going to go a little over a year ago, I came across about the same about the same time, uh baseline protocol and zkp, and uh something kind of like said to me. This is this. This looks uh like um that's that, that's something that can happen and actually it's going to benefit the the banks, the financial industry and- and I mean this whole ecosystem that that exists around us.

P

So we- and uh I do thank john and paul- and everyone actually here that uh when I started it kind of like uh when we started joining the meetings, it clarified a lot of things so what the standard is about and and how it's going to work. So we basically with lewis, we said: let's, let's try and do something real and see. Actually, if it does, let's build a circuit and take the basement protocol into the consideration and everything and let's see how this is going to work.

P

So this is like the high level, the scenario that we we we decided, we'll try out and and actually encode it. So we we looked at corporate bonds and the scenario is a company or individual works, comes to a broker and says I would like to buy a corporate bond. Typically, it's not a full bond, it's a part of a bond, but I simplified it here and the bloc.

P

Sometimes they have the bond on hand; sometimes they don't, but often they go out to counterparties and they say, let's see what we can do, can we get that bond for the client and they basically they do a request for quote um and then the the quotes come back and they select the quote. I mean we basically said here, we'll uh we'll select the lowest quote.

P

It doesn't have to be that case. There could be more rules, but we simplified it a bit here, but we said we'll pick the lowest quote and we'll and that's what the circuit is going to be about uh and and that's what basically, what the zqp comes into the picture. So so, if we we have a quote here and if you need to prove to the client, the counterparties or the regulators that we actually follow the rule and we pick the lowest quote, it's you don't have to reveal.

P

That quote, you don't have to reveal anything else, it's all in the circuit and you could prove it to accept the counterparty that you dealt with you. Could you could prove to everyone else that it was the lowest quote, because that's what the circuit is basically about and um the circle basically enforces a whole bunch of other rules that we coded in, and I mean the code obviously cannot be zero.

P

We select the smallest codes that and if they are the same quotes we pick the first one and here's a link to our zero knowledge circuit and the code, and uh I think I did it in less than 10 minutes.

P

So if there are any questions or if I missed anything, let me know I don't know louis you're welcome to add anything.

A

Thank you for sharing that with us, boris and now there is an examples folder in our main repo, where this will um where this will live, but thank you for putting that context behind, especially with your banking experience um in this real use case. um Any questions or comments from this group.

G

I'd love to see boris, you and lewis. Maybe do a video on just teaching people how to think about constructing these circuits using narc the narc team. By the way is um we just had a great meeting with them the other day, uh gn ark for folks who don't know their a zero knowledge, circuit generation tool and and creation tool. um You know it's it's it's really more about it.

G

I think it's been proven now that any statement can be proven under zero knowledge right thanks to the magic of np completeness right um and but but you have to think about it differently. So the more we can teach people how to uh approach a business problem or a bit or a piece of business logic or a use case, as it were um from a zero knowledge perspective. I think, would be great, so it might be fun for it to have a video of people.

N

G

You walk through the thinking process and constructing the actual circuit.

P

Okay and- and it wasn't uh yeah, I think we we've had a couple of twice and then, and we kind of was going back and forth with the lewis and on how uh that should be constructed and yeah. I I think a video, that's something we could definitely consider and we will have a medium document soon put out, hopefully within a couple of days, that will have a lot more details. Yeah, not just the bullet points.

P

I think I, like the logo, I don't know if anyone uh yes right, but but I I kind of like put together a logo here with zika proof and baseline next to it. So that's that's how we kind of like uh in parallel, at least to me, that's kind of I came across of this.

G

Is a zk proof, um standards, body and we've been talking to them uh yeah, so we're all kind of coming together. You can see this.

G

I think it's it's a good thing that baseline is aligning so strongly with uh with the zero knowledge community and the cyber community, but I'll talk about that at the end.

P

Okay, okay, thank you.

A

Thank you so much for watching and lastly, for our grant demos. um We have another group of baseline cordovs who took on the task of finishing up the baseline, hello, world, battleship game and they'll be walking us through it now over to you, jack.

Q

Yeah, I think uh davin's actually gonna kick us off here, but we can just do quick, intros of the team um jack, I'm a student at duke university. I did some of the like implementation of the front-end back-end for this.

R

Yeah and I'll jump in there. I think in the interest of time um we're not going to have everybody come on and do intro so I'll just run through the list. Real, quick as well. I'm damon jones, uh the head up product over here at provide. uh Additionally on the team, we had uh ryan fish, um stephan kostik and manik john, uh and it's been a real pleasure working with these guys a lot of a lot of time.

R

A lot of effort has gone into sort of putting together this this hello world, and I think it's really useful. um A lot of the processes um or the functionality that's happening behind the scenes in a baseline process is, is really complex and fitting all those pieces together. Is it's really tough to understand kind of how all these pieces fit together and uh what actions need to happen uh in these processes.

R

So it's really important that we give potential baseliners or really anybody for that matter, something something tangible and familiar and really simple that they can grab onto and apply this baseline process to. So that's where that's where this idea of battleship comes from. uh I think it fits the build pretty well. It uses uh every aspect of the the baseline process in the in the hello world we put together and I think that's a quick enough intro uh in the interest of time, jack I'll, go ahead and turn it back over to you. Man.

Q

Thank you all right, so here we have. uh Are you able to see that at home? Yes, okay, awesome! um So essentially our idea was in order to kind of demonstrate this idea of baselining between two parties. We'll use this game battleship simulated between two players to kind of represent this overall process, and so here we have two different clients pulled up each kind of connected to their own implementation and then communicating over a kafka messaging provider.

Q

And so let's say here: first alice wants to begin baselining with another player. So we're going to go over here and create this organization named alice and she's, going to create a work group in this case we're just using simple ids. So you can easily copy and paste it over here.

Q

But let's say alice shares this code with bob and bob goes over here on his other client somewhere else and signs in creates this organization and then he's going to go ahead and join that work group like so, and then that kind of kicks off the game here um and in the context of baseline, the battleship game is kind of acting as this sort of shared document and so alice and bob are both going to go ahead and place their ships on the board somewhere and it uses zero knowledge proofs.

Q

So that way, alice and bob are sharing information about hey, I'm putting my ship somewhere on the board. They're sharing a essentially a hash of where their ship was placed on the board, and so that way the other player can verify alice and bob place their ship. But they don't actually know the coordinates of the ship that was placed, and so that's kind of how zero knowledge has been integrated in here and then we can go ahead and say: okay, alice is going to start and alice is going to say.

Q

I think bob has a ship on c1, and so we can see both alice and bob receive this information again. This is all being communicated over kafka and then on bob's side. He gets this request from alice. Saying hey.

Q

I think your ship is in swear c1 and if bob goes ahead and says well, my ship is there, but I'm going to claim that that's a miss. It goes ahead and presses that and it says: okay, wait. Proof verification failed. So it generates this zero knowledge. Proof saying using the hash of his board position that we created at the start and communicated between alice and bob and alice's public input.

Q

Guess and says you know that that's not true that doesn't match up, so it gives bob another chance to be truthful, so bob can say: yep that's a hit and then on alice's side. Once again she knows the hash of bob's board and she knows her targeting square and bob communicates that proof back to her and she can go ahead and say yep verify and then once that's verified, you get this little check here and we can see down here. This is just currently running in a ganache local cli.

Q

One of the kind of last features we want to add in is a way to actually view these transactions getting added to the shield contract for right now. You can just see like something is happening here and you just kind of have to trust us that it's the shield contract.

Q

um But lastly, let's say now: it's bob's turn bob says you know, I think alice has a shift at b4.

Q

Alice, says nope, that's a miss and then once again, bob can go over here and verify that and then, once that's verified, you can see again that record of this kind of interaction is being added into the merkle tree in the shield contract.

Q

um So that's just kind of a quick demonstration of what we've come up with um just from a tech perspective. uh It's built kind of using a react. Node.Js client server, where alice in this situation is connected to her own node.js instance of the server bob is connected to another instance and they're communicating um over that kafka messaging bus.

Q

Like I mentioned earlier, we used kafka just because we were wanting to try something other than nats, just to kind of show that baseline is kind of protocol independent in a lot of cases where you can substitute in different parts of the overall protocol and use things like nets or kafka for kind of your specific use, case implementation and then, like I said, we've been using ganache just to keep it local and simple and fast, but you could easily convert this to run on something like robsten or another test net and then, lastly, all the zero knowledge proofs.

Q

uh We did using circ js, mostly just because it was very easy to run the verification of that through the client and the node service. So yeah, that's kind of it from us. If anyone has any questions happy to take some of those.

G

I must be getting weepy in my old age because I'm I'm in tears watching this. It's so freaking awesome. It just makes me so happy and I not only the work and- and this I mean this- it just opens it up. For me, I mean, and I think, a lot of people.

G

This is a this is actually an interesting use case of where you would use zero knowledge just between two counterparties- and I know you guys are already thinking about you know where you make this, uh for uh you know where you're proving the shared state to a third party where that's where baselining gets really interesting right. I've got to prove to the auditor without having them open up all my books right some some truth.

G

um You know, I think you guys were talking about um you know proving to a tournament, the game's winning state without having to show the whole game to that tournament, um which is an interesting thought. I just think it's so good. I uh sonal thanks for giving me the not not cutting me off here. I don't want to take up time, but I'm moved by this work and also by both you guys and blipsix how you worked uh live on zoom, together with the videos that we're definitely gonna publish.

G

I think those those alone are are huge, uh huge assets. I loved the way you guys pair programmed- and I don't know all together. You guys really really made an impact and should be proud of the work.

A

Thank you, john any other questions from the group um in the last minute in this demo.

P

Just a quick comment, but a lot of it can definitely translate into like real use cases that that that uh I can see in finance or fall insurance and regulatory can benefit from, because it is, it is uh yeah. It's really cool.

A

Awesome well, thank you um to the battleship team and thank you to all of the grants and cordov um presenters today. I think there's a lot of valuable work that was worked on in the last few weeks and months and super glad. We were able to show it to the community today and next up, I'm going to hand over to stefan martin from unibright who will be sharing and demoing some things for us.

S

Yes, hello, everyone thanks for having us and yeah, first of all, a very special thanks to you so now for handling the meeting so well, and also for organizing all the blips and the other meetings. It's really great and things turned to better since you are with the protocol. So thanks for that.

T

Yeah hello from my side as well, martin, here, ceo of unipride, yeah great, to see all this unique awesome, engagement and thanks to everybody, contributing and especially organizing this great event. Stefan your your stage, I guess.

S

Yes, I will share my screen quickly. Please let me know if you can see it.

A

We can see it.

S

Okay, so uh yeah. First of all, um we updated the the base ledger uh docs um on how to drop a proof on on base ledger lakewood on one of the test: net implementations, um of course, in in five to ten minutes. I cannot go into every detail, but um there are two ways on how to drop a simple proof on base ledger lakewood. It would be. uh One of them would be by installing your own node and spin up docker and run some commands and to make it easier for developers.

S

We also pre-installed two nodes under alice.lakewoodbaseledgernet and bob lakewood-based ledgernet, and I will show a short demo on how to use it. I will be using postman to do it, and basically I mean, when I'm talking about a proof this this payload, that we are sending to um drop the proof.

S

This payload here can actually be uh everything like, for example, a hash or root of a merkle tree or a partial input to a of a ck circuit or a ck proof or whatever it's not part of the implementation that we decide if that payload makes any sense in a baseline environment, that's up to the user.

S

So, for example, um I could create some some merkle tree and calculate some hashes up to the root hash, and I can just take that one and I can go to a postman environment where I actually dropped that proof on trace, ledger lakewood. It's just a simple api call on this case bob at lakewood and yeah. It's described all in the docs, and we would like to invite everybody, of course, to to use it.

S

For example, if you do not only want to go on a local ganache for dropping grooves, you can use the base ledger testnet as well, and to show a small example on how this could be used.

S

We worked on an excel demo, where we synchronized two parties again alice and bob, so it's comparable to to what we just saw with a um with a battleship demo, um but we show something where the two parties actually do not have to hide anything from each other, because they're, for example, sharing a business document where it's uh totally okay for the other party to to see it, because it's somehow sent off chain and the only thing that is um anchored on base ledger is the agreement that both agree, that they have the same version of the document so, for example, being alice here.

S

S

Suggest a synchronization on a let's say, a name or a name list where I can put last name and first name in the in the first step and then in the next work step. I could also provide a nickname for myself. So alice did that and bob um can check for new states here. Perhaps we have to wait a little bit.

S

So here I see that alice did a proposal with last name and first name and if somebody should know the problem of germans that are called stefan is that there are always two ways of writing: stefan one time with f and one time with ph.

S

So as I am written with f, I of course reject this one and then it would go back to alice, who should provide a better uh version of that until bob finally agrees to that. So we see rejected here and I can make a new proposal uh yeah and- and all of this lead to um sorry just a second.

S

All this leads to something that uh we made a small demo implementation, for. We already showed that at eth atlanta, with two subsystems- sap systems synchronizing each other. So if you uh think of all this version, history that I just showed for just one case like a wrong name and an initial suggestion, then a rejection by the other party, then perhaps we have new versions. We have again a rejection, another new version and then finally an approval of that one. So we can go into the next work step.

S

All this is bundled in something that we propose to call a trust mesh in this implementation, and this way you can easily use base ledger and many baseline patterns to just sync objects between two parties.

S

So I also want to thank stefan kostic, especially for the work on the trust mesh visualization here and also on the excel great work and yeah. We are very excited about future development and hope you can.

S

You can join us and uh also use the base, ledger, testnets and now we're hanging over to martin.

T

Yeah thanks jeff and for the the demos and of course you can see all the transactions that we just created on on our explorer on lakewood.baseless.net as well. I followed them yeah there they are so yeah to save the precious time. I would like to use a few minutes to talk about the upcoming mainnet and the the proper placement of tools and libraries and sdks like we used in the demos, is a good example for one of the many decisions that have to be made on our road to the to the base. Latching mainnet.

T

We pointed them out on this slide. Yeah, you can see it. I hope um it's about finding the the right acceptance criteria for our mainnet candidate, so the software running on the blockchain nodes.

T

As we have multiple implementations, um we will have to select the minute implementation out of the candidates, obviously um be sure on the node operator, prerequisites from a technical side of things and from a staking side of things, make sure that the ubg token model is included for staking transaction cost, handling, revenue, shares and rewards being paid out and grants given in ubt and, of course, think about integration of all.

T

The solutions like like payment solutions, staking portals connectors to sap and other systems, and so on, and the important point you want to make here is that these decisions are vital decisions and for an enterprise, great solution.

T

This decision making and the documentation and later evaluation of all these decisions and the reporting on them should be professional and very much decentralized, so decentralized, for example, as the as unibright token already is, and that's why we founded the base ledger governance council um to make sure that uh base ledger is not a one man or two men or two-end enterprise show, but a very decentralized enterprise, blockchain ecosystem, uh decentralized, meaning independent from from single parties, which is vital from an enterprise application. Point of view.

T

For customers, but also from a legal and regulatory side of things, um just a side note, we've been talking to to exchanges to centralize exchanges, for example, and decentralized or being decentralized, is a super important metric for evaluating tokens.

T

So um let's have a yeah: let's have a glimpse at the governance council, because we're very excited to have great founding members under the council, with the consensus mesh um iconic from from frankfurt's financial district conserker finsport from serbia, spo and unibright, and obviously the purpose of the governance council is to have a decentralized and ever-growing body.

T

So it's an inclusive thing, an ever-growing body that advises and decides on strategical things like requirements to become a member of the council or running a validator node, making sure that the talking model is applied correctly and uvt is used correctly.

T

um Of course, there are all these technical decisions like how many nodes you want to to have in the network, whereas the sweet spot we we want to see um how can we include open source frameworks best and and um open source based, ledger best um strategies and timelines on updates for the platform. Of course, how do we handle those and, last but not least, everything around customer onboarding? How do we go to market best?

T

How can we give brands in ubt best to parties and people contributing to the ecosystem and, of course, think about further decentralization, because this will only be the beginning and we want to ever be more inclusive and decentralized.

T

Yeah, so everybody feel will encourage to to engage in the governance structure itself or on the developing side of things or on running a node or or staking helping us make this solution.

T

One of these solutions for for baselining as a as a layer, 2 or layer 1.5, as we see it, anchoring to ethereum whenever needed, as outlined in our white paper and showcased on various events in the last month and as just seen in the demos, and we will make sure that the ubt token will be the one and only token needed inside and outside of base ledger for everything due to regulatory demands.

T

um Yeah and the lounge is set for q1 next year. um We will make sure that all decisions and announcements are from now on made official via base, ledger dot foundation and base lateral.net, and we're very excited about everything. That's going on in this great community. um I mean what we see with all these blips is outstanding and we are very motivated to move forward here and contribute as much as we can so by the way.

T

Thanks to this um two dev teams, I know that have been putting in extra hours the last weeks, thanks yeah to close, perhaps uh some very small remarks on on nfts, not the unibride nft watches this time, which just raised an outstanding six figure figure number for for charity. Thanks to jack of the unified team, um I mean there's additionally a lot of potential around nfgs in the baseline enterprise space as well.

T

So we are very happy to announce that unibright is collaborating with tree trunk on the technical side of the things so have a look at treetrunk.io and from the use case side of things. um Yeah things are exciting. Given the personal history of stefan, the unibright co-founder with his great history in the music and media space, I guess we will see some great things around nft coming up from from us together as well. So please engage everyone and great to be part of this whole outstanding journey.

A

Thank you. Thank you both so much for the demos and updates, and next up, I'm going to have to hand over to the provide team um to hopefully show us an exciting demo of shuttle um kyle over to you. First.

M

Yeah, thanks upon martin, uh just wanted to follow that up by saying uh you know, uh working with unibride has been a really awesome experience and I think that we've we've done a lot together to further this initiative. um So you couldn't be more proud to. uh You know, avoid being able to pull off there um yeah and thanks all for for um for that, I'm a little bit sick. I've been I've, been having some cold for the last couple days, um so bear with me, um but you know.

M

Let me let me uh share my screen here.

M

All right: can you guys see it.

A

M

Okay, so shuttle um you know, has sort of been much anticipated. I think, um in terms of you know, we had the 0.9 release earlier this year uh that showed sort of the the makings of a no code, workflow designer um that really looks to entangle work step. You know: entangle, zero knowledge, uh proofs across multiple work, steps in a multi-party workflow and so um just to show you know sort of a couple of a couple of examples.

M

um So I've got I'm essentially showing uh here um an organization that I've selected, uh it's called, provide uh and a work group that I have called baseline j 2021, and you see that this is a targeting development environment. um If you look at the workflow here, um essentially, let's actually look at this battleship one.

M

So if we, if we look at that, um what you see is that you can design um you know, essentially the steps in a workflow right. You know what I mean and uh this this is. This is nice, because uh there's a lot of considerations that sort of go into um uh designing. You know designing these things when it comes to circuits and if we can make it easier and easier for citizen developers to get involved and say I want to use.

M

I want to do these five steps and they can click a button to deploy it, that that gets us a lot closer to adoption, and so, if you think about you know, you have a purchase order. We've seen this before uh in terms of just like what this flow looks like, but um we're really excited about is being able to enable um a whole lot, a whole lot of different circuit types. Like um the bond circuit.

M

uh You know really any any circuit that you want to build uh just through the ui, and so then your development team can uh can essentially wire together the circuits and um and networks and uh and really build build out. Something um you know build something out that that that's meaningful so I'll show you this this here. Real quick, just go quickly through this.

M

So this last work step. You know we're going to require finality.

E

You actually need to.

K

E

So let's try that again.

E

I'm off camera.

M

E

M

Alpha version we're actually releasing a beta version in this here in a few weeks, so so.

E

There's a few issues here and there, but it's pretty solid: let's do sorter.

M

T

You're going to see.

B

M

After we get through this.

M

You're going to see that the uh all of the artifacts get deployed, all the provers from the from the you know. So in the standard there's, this concept of provers uh a circuit is one uh is one example of a career, uh one implementation of a zero knowledge circuit. That is.

M

M

And then, finally, and so on, the last work step we're going to require finality um and see. As you say, it says when selected this work step must be settled on the consensus, control, consensus, controlled state machine and then, of course, you, you know you can select a domain model uh and that will um be shared with your your counterparties. So you see now that that's you know we can see here um the trigger.

M

Like sort of the trigger point I know earlier, some folks were saying you know you could use kafka uh instead of gnats. um You know I wouldn't recommend it, but you certainly could, and if that trigger becomes supported in our in our marketplace, um then you could certainly select after here as a trigger um we've been working.

M

You know this has been a great year for real uh we've been working with all sorts of incredible organizations, and it's just such a humbling experience to have integrations with the likes of sap, with microsoft, with the splunks of the world, um and so many others. You know with the salesforce integration we're working on and excel. You know you'll see how how this washers work has uh has really converged on ours. um So so it's really exciting to see to see this, and then you see some other icons here, um so these works done.

M

So this is a draft right. So this is. We have the concept of workflow workflows like prototypes, which is what you're seeing here in the designer, and we have the concept of instances after you get through designing your your workflow. You can deploy it and that becomes an instance and I'll show you what that means.

M

Essentially, all of these draft work steps are going and the underlying approvers in this case circuits, will be deployed uh and the artifacts generated and deployed to the to the network entangled across um multiple, so you'll see there like there's a tenancy there's, also select, you can select a layer, one network right that you want to that. You want to work against and then provide privacy gives you the ability to work on a layer, two network.

M

um You see, we have the base, ledger peach treatment test, that's supported, um and I think that what you'll see soon from provide is. Is this new concept um around something much more permissionless, much more decentralized around the the um uh the the interoperability or sort of the architecture of architectures between layer, one and the layer? Two and and really the governance structure around that. um So we're interested in that so and then there's also some additional uh stuff about the vault and payments here.

M

But um you see like this sort of these icons represent the different components that are uh that are used in the work in the work steps uh it's a little redundant because payments- and you know, base ledger- are always used, but we just wanted to leave those there in privacy as well. um The way that the way it works is the artifacts are deployed. The proving artifacts for each circuit are deployed uh those go through privacy they're distributed across every every. You know, uh participant in the network and then um as work steps are executed.

M

uh Those the proofs that are generated are propagated through the network written to base ledger and then eventually, um this part of other workflows rolled up. um And you know you sort of see how it goes from provide privacy to base ledger to the layer one.

M

And what we're really looking at when I say architecture of architectures is allowing for the network to um be completely decentralized and govern itself towards um the parameters that need to uh be in place to ensure that the interests of the organizations using the network- and in this case, like the proof, the base ledger number, are- um are aligned with the validators in the crypto community as well.

M

um Because if you have um too much, you know, let's be honest when, when baseline, as paul said earlier, we're not going to hit mass critical mass just yet next year. um And so you know before we get there. We're going to have this lopsided number of crypto uh and and the crypt of interest represented by the crypt or crypto community interest represented in the validators and on the network. And it's gonna initially outweigh the interest of the customers.

M

Unless something that some sort of um fair and balanced governance structure emerges to to sort of handle that okay, so what I'll do is deploy this and you'll see it's sort of pending deployment. So essentially all these all these um all these circuits just got deployed and you'll, see that this this workflow, so we.

G

Just generated a bunch of circuits.

M

Like all these zk circuits just got deployed um and what you'll see is? Oh, what's that's.

E

A little bit that's a little interesting, but uh let's see what we can do here, just a layer and just to layer on in here very quickly. This certainly being deployed here is in context of the procure to pay workflow, which we are implementing for uh coke one north america, in the upcoming very soon here.

R

Implementing by way of exactly what you're seeing shuttle.

M

Yeah, so um all right, so, let's see if we can grab one of the work steps out of here to look at what what that looks like and then we'll also hand it over. So you see like this is a hybrid stack right. So, like I'm running a a small number of like I'm running, my local baseline stack and I'm running it, but I'm also using um I'm pointed at an operator which is currently like our cloud model like the provide cloud, but the the.

M

uh Although, for example, all the bottlers in kona are running the provide stack uh and pointing at um you know the kona instance uh that's running on kona's coda's operating environment. um I think that's sort of to jack's point as well, uh and so what we're really seeing is is this um this uptick in uh a number of large organizations that are running the provide stack um that need. You know that are going to need um these proofs distributed and uh these uh the zk roll up process uh marshalled for them.

M

From from the inception of each like uncompressed, I say: uncompressed really meaning like just the raw initial uh zk proofs um start cruise and then the I, the first tier of compression being the zk roll up uh containing those of those uncompressed proofs and then um the third layer being the zkzk roll up, where you can do real interesting enterprise, d5 things on on a layer, one um so really really marshalling from that. The inception of those proofs all the way through uh to the zkzk roll up on the public.

M

Blockchain um you know is, is a huge, huge opportunity and, and it's a big problem to solve, and so that's what we're we've bitten off and I think we're we're well on our way here to uh to making that a reality um and been very much. uh You know very humbling, and uh very much of you know uh as a result of this community, so very very uh pleased to be here.

E

um Let's see if we can grab a a workflow, uh a work stuff brother.

E

I'm gonna grab your work stuff id, so there we go.

M

Oh there's the approver, let's see if I get the work stuff details, if it gives me more, I think well. Excuse me.

M

First steps: ah yes, uh let's, let's make that a little prettier! Oh, let's.

E

Let's make it a little bit.

M

A little bit prettier than that.

G

You missed a comment there. Oh no, are you using spaces and not tabs man.

M

This is curl john, but yeah. I use spaces bruh just kidding. I guess.

E

I am oh, you know what I do.

M

um It's new, this new m1 max is really nice. um John. Do you like yours.

G

Yeah, it's so nice, it's like butter, oh my god, psych.

M

Yeah, okay, I'm done don't! Let me down now come on.

E

M

E

Now we're good.

M

So there's definitely uh oh you said I missed. I missed something hold on.

M

E

Hold on bad illegal url, I didn't copyright, something.

E

Did I not copy.

R

The url right, I could have sworn that I did no.

M

G

Somebody's going to put this segment of the video on open c just get it.

E

M

We go, that was that's much prettier! Okay! I don't know it's a lot of work for that.

E

So what you see here is that not only so like.

M

This this individual purchase order where, when it was deployed, it actually went and used to provide privacy service underneath to to compile and deploy the artifacts and then so. We have basically five five new circuits that are deployed and uh what that means is now when the workflow instances uh that are that will be created by way of sap interaction. uh Thanks to our great forensic circle um and again, you know, you know hacked up to unibright there for for putting us in the same room there.

M

um You know, I think uh yeah, it's really exciting, because all you've got to do is use your sap system now and then this this. um You know these artifacts, like you, know the the the proverb the zk circuit, the one that's going to generate the uncompressed proofs is ready to go and then provide that we have a couple of other workflows that were that we're actually looking at now designing ourselves using using shuttle uh on our for our for our own purposes to design a workflow that, for example, um like provide.

M

It's gonna provide payments l2, you know ck roll-up, workflow and then it'll be like you know. um The first step will be like aggregate, you know or like ingest proofs, you know, but you get the idea. This workflow will like this workflow will take all the proofs that are uncompressed and compress the net that level uh and that cert this circuit will make sure that they are validated along the way and exit to the properly configured and govern l2.

M

um So, uh with this said, I'd like to thanks for letting us show this off and it's still a little bit. You know night's not quite released yet, but we're definitely gonna be shipping it uh this year uh in december, and uh we're really excited to make it super easy for kona and its network, and uh and and all these.

D

M

Organizations in the community to wrap their head around and fingers around something that uh that will scale um you know get to enterprise scale, which is I'm really. I guess the word would be bullish on uh this whole. This whole, you know model um because paul I mean paul brody.

M

You think he heard the man he said that we're not gonna be there yet we're not gonna get get to mass adoption, which means we're so far ahead of the game like let's make like this is going to be the most exciting year of my life coming up.

G

Much more massive adoption in 2022, it means.

M

There's going to be huge adoptions yeah, there will be huge adoption.

G

I don't think we're going to be on like tick tock with zk proof, yeah.

M

No, no it's going to be huge next year. I don't know not.

R

A bad attitude: that's.

L

M

I'm saying that yeah.

L

John, it's like it's like if you, if you make it, um um if you make a twerk video video to that, it's like it will go massive.

G

Twerk, that's a real thing.

M

If I get a cameo from you in it.

L

I will, I will totally.

M

L

We do it, we do a trio trio, it's like it's like.

H

L

Ever and it's like the the we, we start, a the tick tock challenge the most most.

M

L

H

M

Yeah every five seconds just cranks it out.

L

Exactly the most embarrassing twerk video to to to to to to zk proves, I guarantee.

M

Yeah, that's a great idea. We should ask metallica, we should ask the talent if he would participate.

L

Oh yeah, totally one one, one last thing: uh kyle on the on the um you know: you're you're, when you know for the for the for the entire workflow right, you need to like schlep all the proofs, along with it yeah right um that that's the that's the problem right. So it's like it's like, because, if you're not allowed to you to to schlep the proofs along, you have a problem yeah right, so the invoice can't prove anything and that's where again, zk zk zk.

M

L

To have it, you have to have it, there is no way there is there is. There is no way in hell that you can not have it yeah.

M

If you, if you.

L

M

It you can't do anything on layer, one in d5 and what's the point.

L

That that is, that is exactly right, because you, because you don't have have have uh you, don't have the the proof of of of all the work steps. So it's like exactly exactly so.

M

So uh this so I know we're getting we're running short on time, but this washer yeah, please please do um uh show the other show the excel side of this uh working.

G

B

E

M

Just loads of fun.

E

Miss washrooms.

M

We have two minutes left, but I think that's probably enough to get the gist of where we're at.

F

And, and just very and just very quickly, on behalf of the provide team.

N

We just want to say thanks to those involved in the baseline protocol,.

E

Community sonal john samurai mark. Thank you so much well,.

N

The always folks, as well as the oasis.

E

Folks and the eea folks, we greatly appreciate this part this year.

M

Yeah and we we have- we have a really interesting paper that we're going to share with the community in the coming few days and uh we're really looking forward to hearing feedback uh on how we can really take this thing to the next level. So thank you.

A

Thank you dishwasher. If you want to quickly walk us through.

J

Yeah so uh like the flow of uh how the work steps and the workflow uh everything uh kyle showed some like uh the excel add-in is also following the same uh pattern. So here I am part of the work group uh that uh kyle had shown you guys the baseline, ga 2021. So if you click.

L

J

So this is a workflow that he had created so here you can create workflows. Also, uh you click on that. The same work steps that you saw on the shuttle you can see it here.

M

There's a few issues in the on the front end anyway. The point is this is so close to being like fully integrated with shuttle, so it's so exciting.

J

uh And yeah just.

J

And here uh this table that you can see here, it has already been mapped so, and you can see it's been baselined.

J

So, although I have all the columns here and my counterparty will also have all the columns that they want to be uh baseline and the primary key is given and with that uh we'll be able to sync up so yeah.

M

And what the mappings do on the on the the stack instant side so like you'll, have you have the sap uh sap.

H

M

You know the model uh like for the different you know in the in the ecosystem, and so one thing that's been overlooked a little bit um and we talked a little bit about it about this in the standards, uh discourse was was how we do mapping um and I think we've got a pretty straightforward solution where the excel user can um can map to whatever the uh so two degrees of separation and essentially from the ecosystem operator map the fields to um to whatever that you know, whatever that you know, sap data model is um and dynamically uh dynamically be able to verify, uh improve, prove uh in the domain.

R

And to sort of add on to that, um we focus on enterprise a lot, but I think real adoption and acceptance of the baseline protocol is going to involve a lot more than just enterprise and there's not a supply chain in the world that doesn't have somebody along that along that supply chain using excel. So we thought.

G

R

G

M

Finance exactly banks.

G

Use excel. This is hugely important, and our friends at microsoft should be pretty happy because we just saw two excel demos, so you're welcome microsoft and.

M

Thank you for watching. I mean I wish we could show everything we have like.

P

We have this, we have.

M

A listing for azure, that's got the d365 connectivity and um you know really working with the ecosystem. There too, and I just want to say one more thing: um the provide team has like tons of heart and uh and like just they're they're, just it's an incredible team, uh and so I'm really grateful for for everyone on our team as well. So thank thanks. Everyone appreciate it.

G

And thanks thanks provide team for uh hosting the east atlanta as well bushwashery before we move on um you're one of my my heroes. I love you so much.

E

G

The company could you I didn't. I couldn't find your. How do people find you're doing some pretty cool stuff there and yeah? What what's the company? So we give you a good plug for that.

J

So it's currently called d phi d, phi b e, f uh double. I that's.

M

About to make this.

G

M

Like an offer, she can't refuse.

G

All right, let's just let's let it go, what does it say again? Sorry.

J

J

Yeah everyone can find me on linkedin with my name and the my company is called the defy so d e f double I and anyone can like ping me there and I'd be happy to have a chat with uh and.

G

Very quickly, what do you probably outside of provide.

J

So currently uh like services on aml and verified credentials, I'm working on that like on my site. uh So if anyone is interested and would like to uh implement something for their company, like I'd, be happy to help out.

G

Thank you for watching.

A

Thank you and we're two minutes past time, but john. If you want to give your closing words and then we'll wrap up.

G

Well, gosh, I think um it's, it's all been said. uh We can probably take the screen share off now, yeah. I think uh this is two hours of really great stuff. What I saw was uh harmony right. uh It's not in a standard body. You don't often get harmony and there's certainly been. uh You know many. You know with many humans. You have lots of different uh points of view. Lots of things sloshing around, but this last year, we've matured to the point where we have multiple coho uh co-chairs.

G

We have we're trans national in in a in a much more uh real way than we ever have been before. We have huge corporations that- and this is not unusual- you have to live for two years before they they before they feel you're safe enough to invest some time in now they are at the top level of the company. um I'd like to by the way, um uh give credit to mehran shakri over its sap, among others, who has been doing great leadership.

G

Blip one is is mehran's, um and it really has to do with showing where zero knowledge is useful and where you don't use it in an enterprise workflow like supply chain and that's really important, because it paints the negative space. As you know, you want to say what do we do? What do we not do? What is it not useful for um so uh credit to mehran and on all that?

G

What I liked on this, uh the show that that sonal, um really almost single-handedly pulled together with the team um I've been running around trying to build this tree trunk business is, is, is a flow from here's developer tools. You know simple, clear practitioners can get their hands on it. It's at the code level to a ccsm like base ledger to hey, I'm an enterprise, and I don't want every and I want some.

G

I want more help than or I want you know, maybe uh non-practitioners- to be able to build these workflows in a visual way right. Those are that's the progression I saw and it all kind of works together. um So I'd like to see, I'm sure we're going to see more of that. The best thing this year to me was watching real developers pair programming on in real time, through the november october november december time frame, love to see a lot more of that we'll be raising more money for grants.

G

So we can see more of that, because that helps everybody lifts all boats and it shows new developers where they're not alone right that they can see. What's what was going through the minds of the other developers that came before them this coming year, 2022 is going to be uh the year, I think not only of dids and vcs, but also of of practical zero knowledge uh applied in the baseline way um we're seeing uh zero knowledge standards. Bodies coming are in our direction.

G

um I'd love to see some of them be on on oasis as well, so that we can all be sisters and brothers, and- uh and this is not a story- that's controversial to companies.

G

The blockchain story for the last six years has been controversial. It's like wait a minute. I want to put data on what that's a big giant threat surface, that's kind of scary to me, honestly. If we can sell that, we can sell anything um working together and coordinating is being forced upon everybody. Today, everybody has to work together and coordinate across company lines, and that is terrifying to a company who has a duty of responsibility to protecting their information and the information of their clients.

G

How do you do that and coordinate at the same time? It's a it's a conundrum and that's where baseline, the baselining approach, as has been shown through some wonderful demos. This time I mean you know, people can now you can get your hands on that code and start playing, especially that you know the uh what two different excel demos and uh my favorite thing, uh the the uh battleship demo.

G

um You can get your hands on that code and um and and and start working. So that's this coming year is all is going to be all about. That is just building more examples, and I think that we don't have a lot of barriers left between uh us and um excited new people coming in from companies and on their own all over the world. Building chapters just like semrat and dishwasher and others have done.

G

um Also, I would maybe, in closing I'll say that that uh what semrat and bishwashri and others in in india and asia pac are doing. That's when you know this kind of stuff, that's the place you want to be so uh building a great community. There is hugely important. It's important all over the world, but um I think, as somebody said, you know where, where where semrat- and you guys are- is uh sort of the back office of the world and uh if you don't have adoption there we're not going to go anywhere.

G

So it's a very important place to be, um and I think that's all I've got to say. Thank you very much.

A

All right, thank you to all of.

G

A

Speakers and um all the listeners.

I

In the audience.

A

Excellent have a great day everybody.

C

Big thanks to everybody, cheers.

T