Baseline Protocol General Assemblies, 8 Feb 2023

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: The Baseline Protocol - February 2023 General Assembly

Description

We are excited to announce that our February 2023 General Assembly will be live-streamed on Wednesday, 2/8, at 12 PM EST, 6 PM CET and 10.30 PM IST!

This is an excellent opportunity for the larger community to stay updated on Baseline Protocol's progress across various working groups and engage with the core team. We will present the 2023 roadmap.

We invite you to tune in and participate in the Q&A session at the end of the meeting. See you there!

A

A

I welcome you all to the Baseline show today is our uh February General Assembly.

A

And this one is this: one is going to be exciting uh because we have uh pretty interesting announcements to make um and- and you know welcome to this- this beautiful February episode uh guys. Thank you for joining us uh in the live studio. We have Mark renza we have you are we have Mark cattle and sonal Ryan Jack Leary? We are all on on video, there's Jack Gilchrist, Keith, Salzman and Andreas also who are not on video right now.

A

um So thank you. Thank you all for making it today. um These General assemblies are a great opportunity for us to sync up on various initiatives which are going on with between various working groups and also give the community a collective update on what who's working on. What? Where are we going, uh especially this one where we're going to also talk about a little bit about the roadmap um and, yes, most importantly, open the floor for any questions and announcements from any community members?

A

So yeah interesting uh episode coming forward if people are watching us for the first time do visit the Baseline hyphen protocol.org and do subscribe to our YouTube channel. We keep doing the Baseline show every Wednesday at noontime, EST ite I'd like to kick off uh today's General Assembly, uh so we generally start without fridge, and we. This shows no exceptions of Mark cattle.

B

As far as Outreach, it certainly has been an interesting time. You know uh just in the entire environments around there and um uh you're starting to see a lot of you know, projects that are really starting to kind of plateau a little bit, um and a lot of that is I think you know looking at trying to tackle several different problems with different tools and different architectures. uh You know that, may not uh you know, be uh you know the best or uh you know a lot of times.

B

It's almost like the disease is as bad as the Cure or the Cure is as bad as the disease.

B

um We've been working a lot with the um you know fleshing out a lot of the real world application as far as what Baseline can be used for and really just how it's a lightweight um uh solution set. uh You know it doesn't require cloning and moving a lot of data.

B

It doesn't require that you're having to uh set up another collaboration infrastructure using your existing uh systems and just allowing them to be synchronized, and you know just that fundamental core tenac uh has so many Ripple effects, uh especially when you've got uh so many Enterprises.

B

You know the average Enterprise out there supports over 2 000 applications, but all of which is uh you know, throwing off data, and how do you, actually, uh you know, maintain control uh of all of that, especially when probably 80 of that data that you have is you're going to consider to be too sensitive uh for it to be in the hands of your counterparties. You know your your friendly competitors are still competitors, and especially when that involves uh pricing, data or customer data.

B

uh Everyone is zealously guarding that and so cloning and moving it really creates a security Challenge, and so this is getting a lot more attention right now. um You know which I'm encouraged with because people are like it's almost like the entire.

B

uh uh You know, blockchain world really got focused on cryptocurrencies and tokens, uh and all that is- uh and you know really didn't uh you know- have as much attention on the Enterprise and I'm seeing that shift quite a bit because right now, especially under constrained, uh you know, Finding I, guess economic headwinds right now, anything that is going to be. You know helping people save time and money uh is always going to have the attention. So that's what we have been showcasing a lot within the Outreach, then also our research work group.

B

uh You know Mark rimsa over. There has been doing quite a little bit about that and he can speak a lot more to that than I can.

A

Thank you. Thank you. Thanks, thanks uh and I think one of the cool uh initiatives which, uh on the LTE front, has also been the various blog post that we are publishing and there's um you know the latest post of a published by was Keith and uh I'm going to invite him later on today to talk more talk, a little more about what he published. What are his motivations and what are his findings?

A

You know, while, while writing something you have so many findings, so so yeah uh with that, let me pass on to mark rimsa for research working group.

C

um Wait can I cover some more.

A

Oh yeah, yes, short of it.

C

Okay, um yeah I think we should start using the Outreach meeting notes and just go through some of the categories. So I haven't pulled up here. um So Ethan.

A

C

Take place sure.

A

C

Have to give thank you already so if Denver will be taking place from now until the next meeting, so when we're back in March we'll be able to debrief on that event.

C

um So we started looking at our events for 2023. We do have participation, Eve Denver. The eea is sponsoring an Enterprise Hacker House, um so we hope to get some baseline Court of Outreach done. There um also we're starting to take a look at some of the events happening in Austin in April, with consensus by coindesk coming up, um and there are some others.

C

We were looking at different conferences, hosted by research institutes, um they call for papers and those types of requirements and how we can weave that into the research efforts, um but with each Denver coming up our mesh team, um some of us will be there as well as I know. Others on this call have mentioned um some. Other eea teams are starting to add to a list that they'll be joining, so we hope to do some Enterprise meetups.

C

um Our mesh team is going to be hosting an event from our r d unit, so we'll be kind of having our Enterprise Focus there.

C

um We're very soon we'll release the invite, but it'll be um an open event for coming to speak to our researchers, about the topics we focus on and our team focuses on zero knowledge and relevant technology. So we hope to use that to do Outreach for potential Baseline contributors as well.

C

We'll share more about that when that comes up and we'll go through the research work when we hand over to Mark shortly for the enablement focus, we kind of put that on the back burner for now, but we did have that Master enablement deck last year and one of the deliverables we also created in that group um I will actually find that as well, but part of the enablement work where we paused was. We created a list of persona based enablement.

C

So if anybody on the call or out there is interested in creating iterations of that Master enablement deck, we had some ideas here of different personas. We could Target the types of information they would look for. So um even though it's on hold, it can be picked up anytime and we highly encourage it. So we can create more reusable resources.

C

um We also have new Baseline stickers that we'll be bringing to Denver as our first release, um we'll try and get a little image out there. So if you know what's coming, but it's a little bit, um it's pretty much just him on the card. So it's pretty.

A

C

A

Because I can't pull it.

C

Up fast enough.

C

D

C

um So also um blogs. We have a whole section in our update today to look at some of the recent blogs um and then also with the roadmap that we'll be discussing. There are some specific Outreach items, so that is pretty much it for the Outreach team. So we're gonna be highly focused on the roadmap priorities and then yeah.

D

C

Have these other categories happening alongside as well yeah.

D

A

Think solution just to add on to the Outreach I think one key thing which I'm I'm planning to kick off after we finalize our roadmap. Is uh we also reaching out to other side bodies? I? Think that's something which we need to do more of a focused. You know um spear-shaped Outreach to these to these other standard bodies and try to collaborate with them.

A

uh The other thing you know, I must say: Keith Denver is like the most iconic uh event, which I can remember when Baseline was getting set up and all the leaders were getting together and um I was the same uh event Mark when you and John broke down together positive Denver yeah no for each Atlanta, Eat, Atlanta, okay, that was a different one.

A

Yeah, so I think I think those those have been two large events which which you know these are like milestones in my head for for Baseline, so for getting set up and getting the right, Community Support awesome, um look forward to hearing updates from you guys.

C

um Yeah I think a few other community members on call will be there like Jeff Gilchrist. um Anyone else that we're missing cool.

A

C

We can make a subgroup of who will be there, make sure to reach out and have um shared.

D

C

On Baseline yeah and have fun yeah.

A

The exciting thing for me is that Malaysia is happening this year, so if Global is organizing uh a proper Youth Event in Kuala, Lumpur and Malaysia and I recently got invite to to be on the on the organizing committee. So yeah there's there's going to be a lot of uh KL things. It's happening in May, so we have ample time to sort of design our strategy around it and how we want to take it forward.

A

But that's, but that's exciting and yeah, and there is you know, I think a good thing will be that all these guys will gather around this event. So I will also know who are the good ties. I met some guys few days back by the way, who are now interning with another one and they knew all about Wi-Fi cool, um so yeah, moving on to Mark Grim's eye he's been waiting too long.

E

Thank you um yeah. So Mark mentioned the research out group research, work group, sorry and um spent some time, though I think there's no better time than right now to share my screen and show some of the work that our team has been working on.

E

Oh that's, the wrong screen.

E

Let me go to the right one here. It is so uh if everybody remembers what the research or group was working on, we were. We were first focusing on blip one which is about um detailing. Why anchoring or zero knowledge proofs would be needed for specific steps in in a business workflow?

E

And um we we answered, we answered those questions in in the blip one working group and we started moving forward to take these International supply chain requirements that Maron and Madu at sap did a really great job of getting together and what we started doing was fleshing out these requirements into um into a series of steps into a series of steps that could be categorized into work, steps or a full entire workflow, maybe in a baseline system, and what we've been doing is we've been taking these requirements and breaking them into a series of advancement predicates a series of steps right here, which is basically a series of State transitions when someone proposes a change to State and then another person accepts a change to state and in this case, we're breaking out these requirements across the across the example of an international supply chain.

E

Though all the documents that we've that we've outlined from this diagram right here from this swim, Lane diagram there in this example at least they're all a series of verifiable credentials when state is proposed. This verifiable credential is paired with a zero knowledge proof accompanying the correctness, or rather proving the correctness of this state change proposal, which is then wrapped into a verifiable presentation which can be sent to the next actor Downstream, where they can verify the proof.

E

um They can verify the VC that they can get from the verifiable presentation, and then they can anchor that profound chain, like we've, like we've, talked about anchoring for work to basically confirm State and allow other people in this Baseline system to check that proof and verify that Theta has been updated and that it's been updated correctly.

E

So um the reason why I'm sharing this document is because we've we've finished these advancement predicates and what that means is we've been able to take this entire flow here from the swim, Lane diagram and break it in to break it out into the series of steps that I mentioned. That explains the entire flow of this entire supply chain system and all the things that you would need to do involving verifiable credentials.

E

Zero knowledge proofs proof anchoring um all the real important requirements that would allow this, allow this application to work, trustlessly or in a zero trust environment and operate under zero knowledge where no sensitive information is leaked. So now that we've been able to finish this document, the next thing that our team is working on is breaking out. All of these.

E

In all of these steps that we've outlined into a series of epics and user stories that the team that a development team would be able to um very easily digest and develop into an application that would be able to work on a simple reference. Implementation like like bri 3, for instance, that the core devs are working on right now. So the overall purpose of this work group currently is to break out all the requirements from standard into an easily digestible way.

E

That, in a sense, is almost a framework where you could really take any any sort of business workflow and break it down into a series of steps. A series of steps that you could then Baseline using the principles that are outlined in these requirements and then turn into real developer requirements that could be turned into a working demonstration or application, or um even even a even a production or it could be used to create a production implementation. Let's say so: that's the current state of the working group as is: are there?

E

Are there any questions from the group or any any other points of discussion or comments that we want to add onto this before we move on.

A

I'll just say it's a brilliant work. Thank you.

E

Thanks well yeah, there's, there's been a lot of great minds in the working group. Andreas has has helped significantly with this effort. um Maron and Madu from sap have added a significant amount of expertise from the supply chain. Side and everybody who joins us is a great contributor. So just again to remind everyone, we meet every other Thursday.

E

If anybody is interested in the content of these meetings or contributing or maybe even having a better understanding of how to Baseline an application or a business workflow, please join these calls and contribute in any way that you can and I'll I'll give it back to you. Samurai thanks.

A

Thank you Mark. That's it's pretty energizing uh update from your site, um so moving on uh now, let's hear from uh sonal on the update uh for for our actually on all articles that you're writing properties.

C

Awesome sounds good, so we've been making it a priority in the TSC Outreach team and within with other contributors, to get more content out there on our blog to make sure we're tracking all the exciting things going on so um I'll kind of start backwards. From the recent blogs um we had this blog posted by a TSC member Ogden kurtick, who um wrote about baselining fraud out of invoice factoring, um so he outlines a use case for double Finance, double financing, invoice fraud and then how to apply the Baseline protocol to this problem.

C

So I really liked this piece, because um it's conceptual it explains a very common use case, particularly to Serbia, so a smaller country and their current economic issues that they face and explains how something like the Baseline protocol would enable um bus to reduce Finance fraud. Sorry I was starting to read through it while I was explaining it, but a really great piece that I recommend to everybody. It explains major concepts of baselining very elegantly.

C

Another one is a short um well, not sure, actually it felt short but a press release. We released on the eea blog about Bri 3's third Milestone.

C

That was completed, um Mark ramsa was the main author for this one and it highlights the importance of the Bri 3 work um as one of the high priority items from last year, how it will be leveraged, going forward and explains some of the major um work that was done as part of the first two milestones and then lastly, um we just released a report um through the mesh page, so something new that we also added to the website is: if there are any pieces relevant to things that Baseline focuses on whether it's Technologies use cases, we can just kind of add a square here that link straight to other blogs.

C

So let us know anytime, you see something and we'll have it added here, um but our mesh R D team published this report on how to use the zkbm for Baseline. So Mark. Do you want to kind of give us the brief while I scroll through it.

E

Sure yeah, this is a. This- is a really really cool report. um This. This idea, right here, is from the mind of Andreas freund and the the basic the basic.

E

um The basic point that we're trying to get across with this report is that the zkevm can be used for more than just scaling ethereum the zero knowledge ethereum virtual machine is actually quite useful for proving any sort of logic, and they don't necessarily have to just be ethereum transactions.

E

The logic or transactions that can be proven through zkevm could even be Enterprise transactions and what that means is currently with Baseline on on bri 3 this. This um simple reference implementations being built out in typescript, and maybe some of the business workflows that would be running on this on this Bri 3 would be executed in typescript, and what that means is, if you're approving the validity of the execution of those transactions within within a baseline implementation.

E

There are really two approaches: one would be to go the handwritten route, where your handwriting zero knowledge circuits that prove the outputs of those transactions. The other route to go would be to take that program.

E

That's executing your logic and run it through a virtual machine or a zero knowledge, ethereum virtual machine, where the execution of that program is proven at the bytecode level and guarantees correctness of the execution of that program so, rather than just executing typescript in a baseline implementation.

E

The really exciting thing that this report details is the fact that you could actually just stick that business logic inside of solidity contracts, and you can use the DK evm as the execution engine of a BPI by executing that business logic from solidity contracts through zkevm and provably, or uh verifiably proving the proper execution of that business logic and the proofs that are the outputs of the well at least one of the outputs of the DK evm after that execution completes and then that could be used to advance those State transitions sort of, like we talked about earlier as part of that blip one working group effort.

E

So um it's a very it's a very cool report, and another thing it highlights is how Baseline can be altered in a sense to make it easier for adoption right.

E

Handwriting circuits is is great, but it is certainly easier to be able to just write normal code, run it through a virtual machine and have it automatically generate the proof for you and um our or the thesis here is that using a zkevm within a baseline protocol, implementation allows for all the benefits of ethereum without any of the drawbacks, so if you're not familiar with zkevm or how it could fit into baseline or even some of the more General understanding of what what ZK is really used for in a BPI I encourage everybody to take a look at this, this report and um reach out to the team.

E

If you have any questions on it,.

F

Yeah and and Mark great great report, and uh because I I mentioned this on Twitter, but uh this is actually a very similar type of architecture that we're going for with prvd network as a as a layer three and using a ziki zika evm, there uh I think you did a great job with this blog you're, really summarizing it as a general level in a very agnostic way of about you know.

F

What's what's the purpose and- and you know value of having ZKA evm there and uh I the the idea as well of of you, know, composability of ZK right of you know, rather than like, as you say, like doing bespoke circuits, you know being able to choose your your circuit and run it through a virtual machine to get your your output and bringing in the zkevm there as well. As you know, part of that immutable execution.

F

You know scaling wise, but you know also uh having that transaction to ethereum is you know, you know super desirable in the in the context of Baseline.

C

D

A

Yeah, it's exciting stuff, yeah, yeah, exciting stuff, I think probably the best best investment polygon has ever made yeah.

G

C

So thanks for highlighting this report, I think it's broken down really well. That explains.

D

C

Pretty deep Concepts um in relevant ways for us, baseliners um and the how it all fits together is a really good summary that I encourage people to read, um but I think it's like we've all said it's great. um It shows that Baseline keeps up with new and emerging Technologies and definitely keeps all of us in the community on our feet.

C

um So Keith you on the TS you as a TSC member, are publishing the next blog. Do you want to give us a little teaser on what it will be about.

H

Baseline keys are over no uh yeah sure, so I was looking at the kind of the previous blogs, and you know the materials that were out there and uh you know naturally I I try to put like the the development engineering kind of perspective on things, um because a lot of the pieces that are put out are are kind of do require you to be uh technically Savvy, but you know they kind of you know, do kind of hand wavy magic as we love to say that phrase when it comes to the details of them, which of course is is fine for a lot of um you know different positions and what kind of knowledge trying to gain from that article, but uh you know I want to give something a little more concrete, sometimes right and for those devs and Engineers that might be reading uh and so I started off.

H

Writing that um is like how to go about starting a baseline implementation. You know almost like the beginnings of an implementation guide right, but in a blog and then and then I was like okay well.

H

Actually, maybe I should just take the basic speech that I did in. In Amsterdam and amster base- and it like set the stage first right, we have a lot of material I feel like it starts off uh the the medium to advanced level, and we've always talked about this from the beginning that it's difficult, that on-ramp can be very you know, have a very steep learning curve right.

H

uh So instead I wrote this first part of the basics blog or at least it's just a draft right now, and uh it attempts to kind of uh shine a light on those parts of the implementation or the standard itself.

H

That I consider kind of like the uh like the sinusure of of what the implementation is and and and hopefully uh by doing that and by reading through people can build that foundational mental model and kind of bring a sense of like varissa militude in their mind to what what you know, what is a baseline protocol, implementation or standard, and what does it seek to accomplish, and how does it accomplish that and uh and yeah?

H

So that's what the draft is out there with among all the TSC members now awaiting, not everybody's critique and then hopefully that will be posted. Somebody help me with the date the third Thursday of Thanksgiving.

C

Yeah I will work with you to get.

D

C

Soon but hopefully in the next week, but yeah.

C

It was so we're a little late, we'll get it going.

D

I

For identifying.

C

A need within the Baseline Community for documentation, that's a great Focus for a Blog.

A

Thank you. Thank you so much Keith. uh This is very helpful and I think this will serve as the go-to piece for a lot of people who are just beginning uh with Baseline, so yeah, let's make it part of our on-ramp deck and use it to send to our friends when, when they ask us, uh what's this mad thing, you're doing with baselining and um okay, so that is pretty exciting stuff um and I'm glad that we continue this streak of of writing regularly.

A

We've we've actually shown more published pieces than we, then we envisaged uh for Jan and Feb. So that's that's awesome and uh yeah. Let's now move on to full times update, uh you have don't go.

G

Ahead, yes, thank you samrat, um so for core Dev updates, the kind of main um the main project at work. Right now, of course, is the uh Bri three, the simple reference implementation.

G

um The main kind of push right now for the SRI is to make sure that it can be come part of kind of a grander interoperability showcase and and demonstrate how uh you know. Different um different implementations of the Baseline protocol can work together kind of seamlessly thanks to the design of the standard itself.

G

So with that in mind, I'll just jump into kind of where things have moved since, um since the last GA kind of what's been done and what's um happening currently yeah. So we've had a couple of uh PRS that have been merged in um there's the Nats messaging service arbac, which is the role-based access control.

G

uh The work group setup as well as a couple missing. Fields issues have been pushed through and updated, so those things all kind of followed. The process that we've been using, which is to create a proposal for the individual working on the component, to create a proposal and then kind of show it to the team team, leaves comments and then discuss it in um kind of an async manner or on the weekly calls and then kind of go through implementing it.

G

um So also, there is a open PR for generation of content. Addressable hash, which is um just pending review, should be pushed in hopefully fairly soon. So, as far as like I mentioned um that with that process, you make a proposal discuss. There are a couple proposals now in the works and kind of beginning the next.

G

uh You know next pieces of this puzzle, so we've got proposals for State object, uh which is in progress now and there's a proposal for the um removing of hard-coded values from the test files, kind of moving everything out to one Central object to be called upon and then potentially utilizing mock data to kind of mock the tests up a little bit.

G

There's also discussions and a proposal to come on traditional authorization approach and kind of going about authorization in a more traditional manner. um So with all that being said, Milestone three is now wrapping up. It's pretty much on its way to being kind of polished and completed all of its requirements and, uh while it's being wrapped up still a couple components of Milestone four, which is uh focused mainly on zkp and ccsm, anchoring, have already begun development.

G

So efforts have already began alongside the wrapping up of Milestone 3, to keep pushing things along um so yeah we're. The team is very excited about kind of the progress being made and everybody's hard at work, pumping out components. So uh yeah things are moving.

A

uh Thank you so much for that. Pretty detailed, uh detailed update- and it's always good to hear that things are moving um great, um so I can probably give one quick update on the collaboration with other SEO. So what we've? What we announced the beginning of this year that this year Stacy is also going to focus on uh collaborating with other standard development organizations or bodies.

A

um So that's something which is paused at the moment because we're waiting for getting the roadmap out of the way. So once that is done, uh it's approved by the entire group, then then we're going to get we're going to Kickstart that effort of collaborating with other stos. It's going to take quite a bit of effort, but I think the kind of heavy weights we have involved in Baseline I think uh we're gonna get some traction.

A

um So that's on collaboration. I will not invite the Andreas to talk about standards and uh followed by roadmap for 2023. That's where we can all uh Andreas over to you.

J

Yes, thank you really really quickly.

J

um We are um prepping the standard uh to go from a release to full draft um by the end of q1 or Q2 um to that for that we need to add testability statements to each requirement and since we have like 600 plus requirements across these three uh three standards documents, uh that's a significant work I'm calling on everybody to help with that.

J

um The first PR is is going to go out soon. um Well, we'll we'll go uh section by section where we're adding the testability requirements. So if everybody wants to pick up a section in that and start adding testability requirements, uh testability statements- sorry um uh please uh do so um uh that's going to be very helpful.

J

um We should be able to push out the um rspr with testability statements. Soon, Keith go off timeline sometime next week.

J

For section two: yes,.

G

Oh for section two um I'm, not so sure when the entire section could be completed, but we can start pushing PR's uh in smaller chunks.

J

G

To kind of demonstrate what what it is.

D

G

D

J

I think that's that's fine. We'll show we'll do that, so that people can start picking up work and and creating their own PR. So we can, we can work in parallel, excellent um yeah, that's that's it um interrupt fast, is a must otherwise standard equals dead.

J

And with that is the um hanging chat, the the the segue over to use some right for the roadmap.

A

Yeah roadmap uh so uh and there's actually I, would rather request. If, if you could walk through the roadmap and I can yeah.

J

Can you share it or what yeah.

D

D

A

Okay, well, there we are.

J

Yeah, can you can you, can you make that like larger, so that people can actually see it.

K

J

Oh the whole thing zoom in under View yeah.

A

I have something over it: oh 100, rare, oh this one yeah yeah.

A

J

A

How about this.

J

Yes, that's that should be 150. yeah. Let's do that! That's good!

J

So, um let's, let's go through that start with a technical category, so we have three categories for the um for the roadmap: technical Outreach and standard um number one was the highest uh it's the highest priority item, which is to complete Milestone three and five for Bri three, um that is the as they would say in Latin condition, without that nothing's gonna work um that we have on our roadmap, basically for the rest of the year, um so that's a critical dependency um to get that to get Bri 3 done.

J

Hence it's the highest priority item on the roadmap. um Geographers already talked about that, so there's no need to go to go on further.

J

um Subsequently, we need an SDK for that such that um uh developers can can easily deploy and then interact with with um Bri 3 BPI.

J

So that's Q3 um and that's uh sort of like um it's actually sort of like a priority item number three um and um priority item number two, um which is the um which is the uh you'll, probably have to stretch the um stretch that further it's the interoperability.

J

You can make the B column larger, yes, so uh the BPI interoperability demonstration, which is basically taking a specific use case small but meaningful and um uh have a basically two work step. Workflow works. The one in bpia work, step two and bpib with two different work groups, work group, one we'll work step, one and work group two for work step two and all of that is a workflow, and then we will have to um create a initial State.

J

That's finalized, then um finalized uh um Resource as an input to work, step two and then um we'll be finalized there, where currently there's a um slack Channel open uh public slack Channel open. If you want to participate in the discussion. The timeline looks like this that we're going to select the use case sometime in February, um then there's an RFP, that's going to go out um to for participation in the interrupt fest with the requirements.

J

um It's already said that each BPI participant must bring at least one real world participant other than themselves, with a Target system of record to be synchronized.

J

That is um that should happen in March and April um uh yeah. Can you just like not move? Thank you um move the screen. So then, uh in the next stage is to actually do the uh sequence of meetings of um and development of, of the um uh um the implementation of the of the workflow um May through September and then test interop in September. Hopefully um this may shift depending on when Bri three is done.

J

um You know all the steps can happen until they you know. Even regular meetings can start, um so we we will see it might, it might shift by a month or or two and then um the the BPI interop should be delivered, October or November uh General Assembly or a separate event um that we're going to host.

J

So that's the sort of like that's the the the uh penultimate um uh um thing for for the Baseline Community this year. From a technical point of view, um from an Outreach point of view, this is going to be the primary event, the interrupt Fest 2023 um and again. This is where the interoperability will be demonstrated, um that's critical. Otherwise we cannot go to a full project specification.

J

um Not only do we need to demonstrate that we also need to document it. um Hopefully we can um that's going to be an interesting discussion. What documentation is is sufficient for that. um So the the um so the interrupt that needs to be organized by the Outreach working group Mark. Looking at you to head that up and um get that going, um including sponsors Etc, um can we go down somewhere one more? So that's then, then we have so that's it. Then we are also have nope. Oh Roadshow is good.

J

um The next item sort of like priority number two for the Outreach soon is the BPI Roadshow. So again there is going to be a grant that is going to be put out um by the Outreach team to um we need to raise funds for to get support outside support, to put up a sequence of um uh in person and virtual events, where um one more um BPI implementers will showcase the capabilities of the of the BPI implementations.

J

The the exact details and the law of support required needs to be determined by the Outreach working group, again Mark, looking at you to to to to spearhead this and and um I'll get going.

J

um So the idea is to have sort of like at least one event per quarter, ideally more starting in queue, Q3 sometime and then lastly, but not least, is uh says. The standard category um already touched on that. um So I don't really need to go any further step.

J

One move the center to draft status, um q1 or Q2, and then Q3 Q4, based on the interop Fest, being able to move that to a full project specification, um which is a somewhat more lengthy process, which will very likely kick us into uh 24, because there's like a 60-day waiting period for comments from Oasis and blah blah blah. So anyway, it's I I think that this is just for the Oasis standard, um so we'll for project specification. I, think it's shorter, but anyway um um we'll we'll need to make make case.

J

So it might spill over into 2024 with a full project specification. But the goal is to to to to have the full project specification approved by the pgb um by December 31st of 2023.

J

So that's! That's it! That's the road map um that the TSC set out for the Baseline Community. It is very, very, very ambitious, um but the TSC believes that it is vital um for this community to achieve those milestones um just for for its own health and continuation.

J

um It's it's important that that that this needs to be met such that we can in 24 focus on um adoption in in uh in the Enterprise space and and Focus even more on Outreach, again more cattle. Looking at you um to to to drive to drive that with the Gen, obviously generous support of both grants and uh your TSC colleagues.

J

A

Back to you, some very, very ambitious uh uh plan, indeed Andres I must say, and this is very exciting. Actually this can be the defining year for Baseline.

A

um When we, when we, you know when the Sun goes, live and next day we can actually get. You know, get real software using this in their advertising, so um so yeah with that I think we are towards the end of days uh General Assembly, but then we open up the floor for any of our other community members. I know Ryan. You wanted to make an announcement, so you're welcome to do that now.

F

Yeah, absolutely thank you Sarah. uh You know and I think I have Jack Leahy from provide here with me as well, but we're really excited to announce coming up on February 22nd at 11 Eastern, so that would be right before the Baseline show that day uh coming up on that day, we have the provide web. 3, webinar and I'll share my screen here very quickly and quick breakdown. uh What to expect at this exciting event.

F

um This is going to be a straight hour of just straight, provide news uh of. What's going on with us in 2023, uh get in depth about you know our point of view on data synchronization asset tokenization. You know how Enterprises can you know, transform uh their business processes with web3 infrastructure uh thinking about, of course, supplying the Baseline protocol to various use cases uh we'll get richly in depth with shuttle and uh showcase some up-to-date capabilities. We have around integrating sap and servicenow through shuttle.

F

um You know to prvd and again talking again about how the the role of blockchains you know, figure into there as well. uh This will be a great show. I hope you guys will make time to make it out there. uh There will be surprise guests, announcements, uh it'll overall, be a great event so mark your calendars.

F

uh I threw the link out in the chat here, but I'll put another link out into the Baseline Community slack, uh and you know once you check out this blog post uh you'll see some links here in terms of how to sign up to join the live, Zoom audience and also there'll, be a live stream on YouTube that day as well, so really exciting event.

F

I hope you guys can can be out there for our first provide web 3 webinar this year and we're hoping to extend it out uh and just have again, it's very focused on providing prvd, but we'll talk more about our whole ecosystem. You know, that's you know bringing up around that, and uh hopefully that includes more from Baseline as well.

A

Excellent running.

F

A

You the best uh Jack and Ryan, both of you for this webinar and definitely we'll try and all make it over there. So uh send me. The link I will put that in the posts that we make for uh after the show, as well awesome any.

L

F

Yeah Jack did you want to add anything.

L

uh Just very briefly, um you know from a provided perspective. We continue to focus on the adoption of the Baseline protocol. Certainly, and there are some um hopeful upcoming project sponsors, the Baseline protocol that um behind the scenes provide, has been working hand in hand with for probably over a year now, um so we're still seeking to drive the adoption of the Baseline protocol and the utilization of it um in that webinar.

L

You know we'll we'll probably hit on some areas of which perhaps Baseline protocol has been considered to be applied to, but hasn't really been, uh hasn't really been a primary focus yet today, and there will be announcement in that webinar around uh an ecosystem uh of which a product ecosystem of which that we're going to be uh rolling out and seeking to apply the Baseline protocol and the open search prbd stack 2, and we do hope that in that announcement and the applicable use case that we're focusing on there that we can continue to drive more adoption and focus on the Baseline protocol.

L

So um yeah yeah appreciate the time I'm looking forward to it. Thank you for anyone here who can come and we do intend to continue to have future future guests on it and we'd love to have some folks from the Baseline protocol join in that as well.

A

Awesome awesome wish you the best. uh Thank you Brian, okay, so we have some time at hand. Anybody else wants to make any announcements, any anything goes and I'm Jack, because what are you guys working on any exciting stuff coming up for you.

K

Yeah um real quick, uh we just uh released a bunch of things uh through battle Zips.

K

Actually, um we wrapped up battle, Zips V2, which is in uh the Halo 2 proving scheme, um and then we also uh Ian who's not currently on the call, but I think he might be listening in is uh has just wrapped up um a huge series with Aztec Noir, uh which is another proving system which can be used to write Baseline proofs, so um that'll be out very soon as well and uh we'll be moving on to next iterations on things.

K

But uh yeah look for us at uh eat Denver. If you're looking to talk Baseline.

A

Excellent excellent you and muted yourself as well.

I

Yes, I'm at um I think I'll uh keep my announcement for the next uh for.

A

The following episodes, awesome, yeah, yeah, so I know you don't drink. Something I wish you the best for that um yeah. There is a. There is a new thing which is coming up called whale pod in asean region uh recently some guys reached out and they said that it's on the lines of Shark Tank. But it's going to be very interesting. It's going to be very focused and they're calling it whale part because they're saying you know these these guys are going to team up, always in all the deals.

A

So not all deals but I mean not all the ways will team up, but most of the deals will team up Etc, so I think the important thing here is just letting you all know. If anybody wants to participate reach out to me. I know the guy is organizing it and uh it's an interesting, interesting concept. They've got some. Some initial uh backing from large groups in asean I can't reveal that uh on on this live show.

A

But if you, if you're talking, then I will let you know, there's a whole solid proposal prepared to this. So yeah hit me up for for those kind of opportunities as well. um That's it from my side I think we had a pretty solid uh general assembly for the month of February. Thank you all for uh making it to the live show as well as people who are watching us on YouTube and other platforms.

A

um See you next week with a very interesting speaker from cartesi.

A