Filecoin Plus Notary Governance, 15 Nov 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Fil+ November 15, 2022 Notary Governance Call

Description

The November 15th community governance calls to discuss the Filecoin Plus program.

Slides and (with all links): https://docs.google.com/presentation/d/19_O6ZEs_AWae8ASlbVUnMhbZjSuhhyIM8f9YyaObiRA/edit?usp=share_link

Agenda
4th Notary Election
- Election Timelines
- Open time for community questions

How to join a Working group

Proposals Discussions
Proposal 702
Discussion 666
Proposal 625
Proposal 631

LDN +Application Discussions

If you would like to attend these meetings LIVE, the Fil+ Notary Governance calendar is available at: https://calendar.google.com/calendar/u/0/embed?src=c_k1gkfoom17g0j8c6bam6uf43j0@group.calendar.google.com&ctz=America/Los_Angeles

Follow Filecoin!
Website: https://bit.ly/3ndAg44
Twitter: https://bit.ly/3ObND0x
Slack: https://bit.ly/3HKfFy7
Blog: https://bit.ly/3HFZFNv
Reddit: https://bit.ly/39N4Jmv
Telegram: https://bit.ly/3bkP8Ly
Subscribe to our newsletter! https://bit.ly/3Oy8J9j

#filecoin #ipfs #libp2p #web3 #nft

A

All right well welcome to the first uh notary governance call of November 15th. My name is Kevin. Let's take a look at what we have high level for you planned for today. We kind of keep the same format as we go through these We'll add proposals, We'll, add topics, but at a high level, if you're joining or watching for the first time. This is kind of the flow that we approach. We start out with uh hello. Some housekeeping attendance make sure that everybody who's joining knows how to get the information for this deck.

A

Then we'll move into the notary elections we'll talk about what applications we've received any questions you have and go over the timeline then we'll get into proposals and discussions. These are pulled directly from the notary governance, GitHub repo, we'll flag, anything that's currently underway and make sure that it's on your awareness give you a chance to weigh in view the comment, add your ideas and feedback and then we'll leave some time at the end.

A

If there was anything that you might have that you wanted to add for this call on discussions and then we also open it up for any LDN or applications that want to flash tag or discuss their issues. This is obviously time dependent. So we ask anybody who's interested in this to record a brief four to five minute video. That way in case we don't have time for them to give a full presentation. They can answer any questions and then I'll share that with the notice.

A

So with that, let's take a quick look at the team, so the governance team is made up of a combination of the notary groups, the working groups, the trust and transparency, so you'll see deep myself, Galen Simon, Phil, Casey RG on this call many times Casey's, not here today kind of Pops in, but if you need anything we're available on slack and we kind of have a focus area for those of you that have been with the bill Plus for a while, you might have tagged deep myself RG for any issue that you might have had going.

A

What we're trying to do is specialize a little bit more as the community grows. It gets more and more difficult to triage and get you the help you need so make sure like. If you are looking for like an LDN application, if you tag Galen and RG, it will go a lot faster than tagging.

A

Deep in myself feel free if you are blocked or you can't find anything to always use us as appropriate, but again we're just the friendly team to back you up as you go through if you're on the call for the first time or you're joining after a while you'll notice that a lot of our names might not be filled out and it makes it really difficult to come back and look at this for SLA participation.

A

So if you do click on the top three dots, you can edit your name and hit rename and if you just change it to something where it makes it easy to identify like where you're from or what your organization is so I. Just changed mine from Kevin to Kevin at filecoin Foundation goes a long way to like making it more easy to answer your questions.

A

So if you wouldn't do that, we'd be very grateful if you're joining this call, whether you're a new applicant to the notary program, a storage provider or you've been coming here for a while, we use airtable, so markdown who's been on the call and then make sure we Mark you down for an SLA participation so to grab that link the deck is online. I'll also grab it right here for you by clicking this link here and I'll. Put this here in chat. You go ahead and fill out this air table.

A

We'll then use this for the SOA credit for you coming and spending your time on. This call with us now so you'll find that link inside of the chat right now all right. We now have multiple sessions that are ticking off. We talked a lot about this at Phil Lisbon. If you haven't had a chance to watch those videos or check out the slide decks. A few. uh A few slides later in this I'll make sure that you have the links available, but there's two working groups, the trust and transparency and the e-fill plus.

A

So if you were looking to get started with this, if you haven't done it before on the screen, right now is the basic information uh when they meet what their core missions are, as well as what their slack information is. So again, these slides are in the chat of this Zoom call and then all the information to join these. This will be important for those of you that have signed up for your notary application and want L4 or higher scoring I think it's even L3 you're committing to join one of the working groups.

A

So this is the information to kind of kick you off on the right path before we really get started on that. So before I go on I'll pause for any questions. I know we have some new folks on the line, but before we get into the agenda on the notary elections, is there any questions about the format we're going to talk about or anything on, the call.

A

All right some changes just posted in chat, Steve, Simon, myself, we'll get back to you and get through it all right, notary elections. Let's talk about what's going on with this right now, 91 applications received so far so I pulled this. As of maybe 30 minutes ago we had maybe 30 applications come through just last night alone. This isn't unusual. We usually have an open period for around two and a half weeks and we get the majority of the applications the last two days.

A

So if you are a notary on the call, you would have got a DM from me last night, just saying: hey, friendly check-in I saw a few of you get it in, but if you were expecting to become, if you expected your application to be there- and you didn't see it- please flag me with the DM, but as of right now, 91 applications to date, you'll see me, go through and assign it to myself, add a tag, and it just makes it a lot easier to make sure that we're giving you what you need if you have not applied yet if you were Keen to apply if you're coming for the first time, you'll go to this GitHub file repository.

A

If you have any questions, it's posted in the fill plus slack, and that has all the information on the slides where to go with the links but to fill out an application, just click that link new application and then update the fields as best applied. If you were a third round notary and applying for the fourth, you could just essentially take your third round application copy. It paste it in this. Fourth, there's only a couple new fields: we just modified the SLA.

A

We asked for some more information on where you geographically operate, so that's just as simple as going through there as you go through next step for us is sweet, Phil and I will be spending our Thanksgiving collecting all of these applications and then essentially putting them into a rubric those thumbs up and essentially what you say is like: if you have a stake, that's applicable to an L1 score. We give you that score. When your SLA is an L4, we give you that score.

A

We make it as extremely transparent as possible, there's no privacy that goes through with this. Everyone can see everyone else's scores and we'll be posting that back. So, in order for us to do this, we may need additional information from your applications. So that means, as far as like next steps, here's what to expect right now. Applications are open, so folks are submitting still we're not doing any scoring we're just waiting for them all to come in once this application period closes. I will add a comment. Excuse me to each individual application, like hey.

A

We've received it. Thank you so much next steps are standby and I'll be sending you a link to a essentially additional information. We collect some information on the back side that we don't put in the issues just to give you a little bit more privacy. Things like email like best way to contact you. What time zones do you operate in?

A

If we need more information on your application, this will go out to a hundred percent of all the applications, so look for it in the application itself and we'll have all the contact information we'll also be using this time to ask any clarifying questions. So, if you say you're associated with, like a certain organization, we might say, like hey great I, see that you're affiliated with you know: JPMorgan Chase.

A

Can you please verify your email with this organization or something basic as we kind of Link these back, and this will be the first step before we start the due diligence on the kyc KYB after the notaries are selected. So my feedback here is that, if you've turned in an application, you will will be getting information from Phil and myself, probably early next week, for you to fill out so be mindful to check back in your application.

A

I'll tag it, but next week you'll be asked for any additional information that comes through once we do that. This is what the timeline looks like. Currently, applications are open, we're in the highlighted period. As you see on the screen right now and on the 16th, we will cut off new applications coming in so be very mindful to get those in and then from the 16th through December 9th. That's when we'll be scoring. So that's that time to please check your application.

A

Please check your email or slack that you gave us to list for that questions, because if we reach out to you and we need information to make your score more more transparent or to unblock something- and we don't hear from you- we'll just go with what's in the form so that might cost you points so be very mindful to check your comms during that period, Then on December, 9th we'll send a mass post out to the fill plus slack Channel share all this information with you, as well as update the GitHub repositories and contact all the newly selected notaries, for congratulations, so at a very high level.

A

That's what we're currently doing with the applications. That's where we currently stand and with uh the timelines, and this is what we're working on right now we answered these two FAQs I'll leave them up on the screen and then I'm also going to like unmute and open the lineup for any questions. Comments concerns for anybody on the call who wants to discuss the notary election. So this is your time. Does anybody have any comments or questions for the application process? Right now,.

B

um Is uh what's the deadline for getting in applications uh tomorrow.

A

Yeah, that's a good question. Thanks for that Alex last time we had a tied to Pacific time, I. Think it's just going to be your time zone. So I'm not going to be like a stickler like a college. Professor, like you know midnight just tomorrow, is the deadline where we stop saying like Hey, we're actively soliciting these so just get it in by Wednesday your time zone it'll be okay,.

C

Do you mean, like Wednesday, end of day or end of life? Okay, thank.

A

D

Hello, Hey Kevin, uh so you messaged me.

E

D

On the slack I I just message back: did you see just want to check out.

A

D

A

Appreciate you doing that and then I'll just leave that application into our our slack channel. That way, we have that comes.

D

But yeah thank.

A

You for writing that.

D

Okay, thank you so much.

A

Eric floor is yours, bud.

F

Oh hi, sorry, uh so uh could you please pardon the the part which you say how to do kyc with fail for the notary application.

A

Yeah so after the notary is selected, what we'll do is we'll send a very small amount of fill to the wallet address that was provided to us in the application and what that does. Is it one verifies that The Ledger is all properly set up and the wallet is good to go, and then we also collect information on country of origin. There are some countries that we're not allowed to work with and store that information. So that's that last step in the process.

A

So as far as like, once, the notary has been selected, we'll be reaching out and we'll be sending you a small amount of fill to that ledger address as part of the verification line with.

G

A

Your base of operations and that kind of information.

F

Understand, thank you.

H

Is Alex Alex? Are you uh raising your hand again for another question or are you I.

C

I just forgot to lower it all right.

A

Sounds great again any questions just ask it in the thrill plus Channel. Send me a DM if you're a little bit shy, whatever it works, but I think the big thing is thank you for all of you that have put in your applications and you'll be hearing from us next week. As far as like a ping in the actual application to start that dialogue to get your score all set up, any questions feel free to keep them coming and we'll get back to you.

A

So with that, we have four proposals to kind of chat through today. So I'm going to turn the floor over to deep. If you want to take over for 702, but.

I

Sorry, yeah um I think seven or two we've talked about um a couple of times. Now we it came up in um Lisbon and Phil, actually I think might be better. If you, you chat.

H

uh Yeah yeah, so uh 702 came up because, uh as you guys have known recently like uh the LDN multisig um has been depleted of datacap recently, uh that's because uh Phil has been has been happening and um root. Key holders have not responded in time uh to refill this uh LDN multisig. As a result, people uh complained- and there were a lot of um uh that- that was a big bottleneck uh and so uh to to fix this. We decided to uh increase the refill amount.

H

So uh basically it used to be the case that root keep holders would refill the LDN multisig with a two-week expected uh usage volume. So we expect this amount of data cap to be finished within two weeks, but then now we're going to do it um with a four week expected value volume, um making it a larger amount that gives a gives us a bigger buffer uh for um for until the the data cap in the multistick finishes.

H

So basically, every time we we refill the LDN multisig, we just keep filling it up with double the amount this time. um So that's the first thing. The second thing is: uh rookie holders have also had trouble, um even if they wanted to sign. um There was a big bug. uh Last week that prevented them from signing, uh and that is really difficult. So uh we uh we need to train them to kind of like just in case the front end fails to sign through the Lotus node.

H

So those are the two things to kind of like remedy the situation of data cap depletion um and yeah. So I think those two will basically fix the data cap problem for uh this LDN multi-sig. uh If you have any thoughts or comments, uh you can like feel free to comment on this issue or like DM me.

J

I

Thanks Phil and see, if there's any questions, sorry, this is a net new one. I had this slept with a different one in my head, but I think this will help a lot in terms of just reducing the friction, at least from from our side like it's often Gill and I, that are pinging and trying to get rkh up and if there's any bugs, then that slows things down and so reducing the cycles that we have to take with people that are less in the loop I. Think is a good thing.

I

The second thing is we initially set up the two-week thing as a security uh recommendation where I was like. Oh don't pre-assign like that quote, unquote that much in a gap like up front to the ldm multi-second case like V3, doesn't work or it doesn't feel like a good move. uh But at this point I think we've. You know it's been several months that we've been operating it and that we have a decent amount of confidence in the system and so feels like a good change to me, but I'd love to hear if anybody disagrees.

H

um Also uh shout out to Faith for bringing this up. uh This proposal wouldn't exist without her like bringing it up as an issue uh in the discussions.

A

K

H

Well, uh with that, we can hand it back to okay ray for the next issue,.

I

Okay, um I'll do a quick intro on this and hand it over to hang Hao actually, uh who I think will be here to present the slides, um hey folks. So this one is on index, saying um I.

I

Think hangout will give you a little introduction to the network indexer, but the idea here is effectively ensuring that some Phil plus deals or some subset of verified deals being made on the network that are expected to be like opening deals and have fast retrieval enabled should automatically be called out uh to the network indexer as well, so they could be better tracked and and tested against in the long term uh hung out. We have your slides integrated, so we're gonna pull you up if you're there.

I

If not I, know that torfin is also around for the Bedrock team.

B

Cool thanks: um this is Brenda and Lauren we're in the cup we're from the uh that route side of things and sorry for the styling misalignment here didn't know, there's a template for this call, uh but yeah, but today we just want to discuss more on the.

B

uh What would be the ideal scoping for the typical indexing uh if you mind going to the next slide uh so for contact uh Network industry, you can view them as PC notes that runs that we run to store the index so that we can enable the company Discovery efficiently at scale uh more efficient than DHT, and uh today the the setup is we basically default or announce the index, and if you want to not announce, you can turn it off.

B

This is designed based on the Assumption back then, that we have is most of the data in the network are public, so uh we just added to default announcing of the index and the goal right now we're thinking that we want to embrace more and more Enterprise use case, especially with private data. So how do we involve this infra to better serve these needs, among which one of the decision we want to make is uh what kind of difficult indexing mechanism we should do that will better serve these non-public data.

B

Specifically, one thing that we plan to add is to have a is public flag in the deal structure, to set the deal as public and which implies that this data, since it's public, can be indexed and can be retrievable for the deals that are not public. They are set as not public.

B

uh There is longer term plan to introduce excess control, with the help of like Partners, let's say, gravity and Lighthouse storage, which are working on these solutions that we could include integrate with, and this is kind of similar to the common Cloud practice like AWS, where uh you know by default, they assume your data is private and then, if you want, you can make it public and with public there's no control over the uh there's, no gating over the data.

B

So there's more there's more comments on this, uh which I I actually need some inputs from this call. At the last slide, which we will come back on to this is public plug, and the main question that we want to discuss is what data should be before published to the investor. uh This meant to be more like a discussion.

B

I hope in this call, instead of us uh deciding uh to uh what direction that we want to go, for, we do have a preference, but uh we just we just want to present some options here for now. I'll go to the next slide. Please.

B

Yeah, so there's I think mainly these three options that come to our mind and if you have other suggestions, feel free to all suggest as well. The first one that we're talking about, which is what deep is providing the contest on, is the only default Investing For, a Few plus deals, and basically we check if it's fast retrievable enabled and if it's a verified boost and because we assume that these are the deals that need to be reliable for retrieval and as a result, it might make sense for them to be default.

B

Index this is configurable, so you can turn it off. Basically, by setting that is public flag to be false, and if either of these criterias are false, like the associate will be verified, then we default not in that, unless you configure it otherwise, which is setting this public to uh to chew, there's a link of to the more detailed proposal. Let me just paste it quickly in the chat.

B

Thanks um yeah, so you can feel free to comment more over there as well, which uh shows more details in terms of how uh this could be implemented and uh what, if we go with this, what kind of detail planned over there and the second option is basically to not invest for all by default. So all of the deals will not be indexed by default, uh assuming privacy of the data and you can configure on each individual deals to turn on the investing basically by setting the is public to true.

B

This is there's some nuances in how this could be done. uh Our inclination is that if we goes this past, we don't want to touch the Legacy index because it gets complicated of how do you update those?

B

Oh in that, so we'll keep the old one impact, and uh one selective only applies to the Future deals going forward and the last option is sort of in line with what we're doing today is people indexing for all of the deals, and we can configure to turn off the investing for individual deals by setting that is public to false.

B

So this gives more capability of to configure individual deals and it's more in line uh kind of in line with what we're doing today, but it has a stronger Assumption of the on the on the publicity of the data.

B

um There are obviously pros and cons for each of these um I kind of want to open up. If folks uh won't have your inputs on what what? What do you think? Is there any uh the outstanding issues, especially on the first option, and uh that you have in mind and we can kind of discuss from there.

I

Oh thanks for sharing hangout um I had a I just had the question around like uh the like, in which layer this change actually happens, like my understanding is that this is just like a you know like an update that we can make at the markets code.

I

um What I'm curious about is what would happen if this were to like change again in the future or if, in this future, world of fvm, like New Deal making markets introduced? uh How does like Network indexer get updated, or how do we continue to do that call out? um This is just like I guess, my.

B

I

Of knowledge and where, in the stack this this would come in yeah.

B

I

Think right in this case, yeah yeah.

B

uh It didn't quickly go to the next slide. It might be a good segue to discuss the the other open question that we only uh get input on. uh So the second Point here is uh so this is part of the new proposal which uh align with the Boost. Oh, it's, the Boost latest schema and uh right now we're thinking this is not Unchained. We we want to know if this is something that uh should be should be on chain for the oh. Actually, the slide hasn't been updated.

B

It looks like uh let me just quickly about this link, so uh the question that we have is: do we need on-chained visibility on whether the client has requested fuel plus deal to be public or private or not, because we think that notary probably will only get accountability if the data is on chain. uh So this is still an open question that we also want to get inputs on.

H

L

H

Ahead, sorry go ahead from my perspective. I think that that information should be public because it will like hold um people like it'll, hold them more accountable right uh for their actions, yeah, but I I, don't know. I would like to hear everyone else's thoughts.

L

Yeah, so one of my my questions would be like: what's the impact on the network industry infrastructure for for having like everything, public I, think that's that's probably the best default. uh Just because everything is is a very public. You can encrypt it and and why not? But um at the end it's uh it's public. So you can. You can find every student and the content so, whether it's public or not, it's probably more on the encryption and not on the like uh findability of it and and so I guess.

L

The question is more on the network indexer decision for for, like your own infrastructure and impact, so I, don't know that that's uh those are my thoughts. uh Probably keeping everything public is is the best default. So.

I

I think the the challenge you're going to run into hangout at like the keeping it public and like on chain and stuff. It will be around like using terminology that is subjectively interpretable right like saying something is public like it's actually a combination of other parameters, um so I think when you do take this to being like public data like on chain data, then I think it's actually those parameters that have to be lit up as well-known Fields.

I

So it's like was The Proposal made with Foster people like maybe that just needs to end up somewhere on chain um was like is, is uh I, don't know like we, because retrievals aren't on chain it's kind of hard to track like even historically like who's who's retrieving.

I

What and how much, but maybe we start just there and then, like your storage Market, in which case happens, to be the storage, Market actor with Boost and all the other stuff that we've built so far happens to interpret the combination of verified, deal and faster table, and maybe scrape data from fill Plus or whatever is open as like something um that's one way to do it.

I

The other way to do it is like making that notion of whether or not something was meant as open data or public data to be Unchained itself, as part of like, for example, today, like the way we know that is, we scrape an application right like when somebody applies for data cap. They write like oh, this is open data or I, expect this data to be available to anybody, and that is not represented anywhere on chain, and maybe that something like that needs to become part of like on-chain.

I

As part of like the deal proposal from the client address,.

M

I

Ends up as part of an artifact of the deal and I could see many additional use cases for that. uh So I am personally pretty supportive of that. um We'll just have to figure out exactly how you'd expect that to be defined and do it in a way where it's like very, very objective um and cannot be interpreted in different ways. If that makes sense, I.

B

Think it makes sense we're definitely not against doing this on chain, probably uh we probably need to if we want to actually enforce or meditate validate these things. I guess like in line to your point. Oh if you can go back to the to the last like uh maybe to to kind of discussion, pointers uh for for number one option.

B

I think the inherent uh here underlying thing here is that we're kind of making assumption on what are the data that should be uh public, uh because we are basically picking a subset of the data that we want people index on. I wonder: is there? Is this the correct assumption? Is there any concerns for kind of scoping the default index into this way um and then the second to to Alexander's uh comments, I think uh if we do default index for all?

B

Basically, what we're doing today, uh one potential risk is then basically for the clients that actually want to store the uh say, Enterprise private data are they? Are they like against this kind of people, Copic mechanism, so that that specifically I am curious? If there's any uh folks on the call that handle these kind of Enterprise use case can chime in and comment on what you think about uh option number three as well.

I

Yeah I'd love to hear from some of the notaries and storage providers in the room.

I

Eric Faye Neo Patrick thoughts on this.

F

uh Yeah, for me, I think I agree with Hong Kong I think this is a really important step for the development of the retrieval. Market actually is I think that this is uh open. The fast retrieval well improve also will improve the retrieval experience from the clients and also enhance the delivery of the Saturn network, am I right.

B

Yeah yeah I mean yeah, so we mean investor, allows the content, uh discovery, which is a part of the crucial pass to the ritual as well uh right now, I think the state is basically we already have. This enabled uh it's default on uh and yeah, and the question is whether we should scope it down uh for the private for the to respect more of the private use cases. The Enterprise data storage side of things.

C

Yeah I I think we we uh we needed to uh demo uh demo and uh maybe we will uh show us right.

M

B

Oh sorry, I didn't understand the question.

C

uh I mean: is that and uh I'm not sure in this future in proposal is uh to uh uh what what what's the status for these Futures and do you have a sample date, example or or another? Thank you.

B

You mean, uh what's the date, propose date for the change.

C

Demo, simple demo yeah, maybe maybe oh.

B

I see you mean like demo for scoping the index itself, yeah yeah, I, I. Think right. Now we want to kind of figure out. How do you want to scope it uh so yeah? So we want we have. We won't have a demo on how do we sculpt it? But if you were thinking about from The Experience wise, uh regardless of what option that we go for, uh it will be an option. It would be basically have it's public included in the deal structure and uh you can set it uh with different configurations with Boost.

B

More that we want to figure out more is on. uh How do we give the option for SP to scope this uh uh investing side of things.

C

D

C

D

Guess, for the I mean for the file plus program like if it's like file Enterprise, uh it should be like defaultful.

D

You know to be off in some ways, but they can like turn it on because, like for the like most recent, like application, I saw their data is like they can be public, but for most of the file plus Enterprise project, especially for the one like you know, the steel storage, one which you know, and it requires some of their data to be private, so that that's the reason like that, like what we want to have like a file plus Enterprise right.

B

Yeah uh secondary Point uh I'm curious, though in this case, because because on the flip side, there's also benefits of uh publishing the the data that is okay to be published to the network, so that, like, for example, we have a discovery of where the content is, and also ritual uh program depends on relies on the index as well, so I'm thinking for the number one option uh for the first retrieval and verified deals. Those are basically considered as not not the private ones right, so is it okay to before.

D

Yeah yeah I mean the normal five plus one is good, but for the foil plus Enterprise, it should.

B

Be understood, yeah yeah, understood, yeah, I.

I

Think I think that's tricky right, because that means I guess like that means because you can't you don't know Phil Plus on chain or not on chain. So then that means three is problematic for Enterprise.

I

I

What are you hearing.

B

Oh I didn't quite understand dude. Can you repeat that so.

I

It I guess going back to the point if, if there's an issue with e-filled Plus versus like regular film, Plus or whatever, then the implications that the class of client influences, what option is feasible, which then means um Enterprise would not want this to be the case.

B

I

That means, because you don't know when something is Enterprise or not Enterprise, you can't go for three.

B

You for I'm not quite familiar with EQ Plus, or do they how? How do you distinguish EQ plus deals versus it's.

I

All off chain, distinguishing all it all the results in, is basically you're going through a slightly different notary due diligence pipeline, um and the expectation is that the data is private and encrypted and likely not to be retrievable by like anybody on the internet, but from an on-chain standpoint. I think it's very very hard to distinguish. Even if you went with option number one, it could be that those deals are made with fast retrieval and all of them will be verified.

I

Okay, I, don't functionally see how we can actually serve that as a need other than like I guess to put this differently I think distinguishing between classes of customers like going back to your original question, distinguishing between classes of clients that are coming to the plus pipeline is basically impossible, because there's no Unchained representation of what type of client they are, and so, if you go for number one, let's say like functionally the difference between one and three is probably not that different I would imagine.

I

Most verified deals are going with last retrieval and uh we'd probably end up more in a game of having to educate, Church providers anyway and so I think, like you could go with one and say that, like that's, that's because you're expecting Foster People to be better correlated with open data, and so that's why you're picking one or I think you could position this to go for three and say Here's.

I

How you're gonna like have a robust like notification and education plan for storage providers, and then your actual stakeholder in this decision will probably become storage providers, and so I would like to understand the implications on like SPS from my.

B

I

Actually, uh to pick between two and three.

M

I

Think does that make sense yeah.

B

Yeah I think that's a really really good call here, um yeah. If, if you pass here's Assumption of the data shouldn't be public and they could be fuzzy enabled well faster, should be enabled and verified deals. Then yeah. The number one might might be the wrong Assumption of uh what this should be public. Then, in this case, sounds like so I'm hearing sounds like the default off, but while giving the option to set set, the two is public. It goes true to pop to index.

B

It sounds to be the seems to be the case that uh will work for yes, the least assumptions on these things. It.

I

Does have the least assumptions, but it will also be the less likely to drive the most default adoption of the indexer and so I.

B

I

Turns into it turns into a trade-off thing on like. Are there actually any downsides of announcing for a search Provider from like a resourcing standpoint and a risk standpoint right um makes.

B

I

I think that if you can present that, then I think we you can either rally the community around option two or option three, depending on what like SPS, are SPS that are actively doing business development, basically, that that's your stakeholder they're, the ones that will likely bring the the heaviest weight vote.

B

Yeah definitely um is there any other uh SP that I want to chime in I. Don't want to hold uh this call for too long here. So uh what I'm thinking is I could post an update to uh to discussion 66 here uh regarding the option to an option, Street and then uh I would love to hear more from your use case or your use case or any uh any concerns or or bias that you have on this, and we can follow up from there.

B

If there's no more comments here.

B

Cool, if you can go quickly, go to the last slide. I'll just quickly call a node, which I think is important. uh So when we say it's public I just want to clarify that, even if it's public- it's not false, uh it is public, is false. It doesn't really imply for privacy uh just want to clarify here, because to achieve this, there need to be additional layer of access control and all these to be built on top which the team uh para team is looking into in the near future.

B

But without that happening uh setting the is public. It goes false, doesn't guarantee for piracy just want to uh make it clear over there cool.

B

All right, thanks, dude.

L

What what would be the difference between is public and is indexed or or something more.

L

B

That um I think it's public. Basically, it reflects the status of the deal like what you think the state uh the deal should be public or private and uh indexable or retrievable, or more, like the implication of that state.

L

But it isn't, isn't it that what's the this option is is about like if, if that's uh that's to be indexed and for for the network, indexer I, don't know I, guess yeah, just commenting.

B

Right right, if you say it's public, false uh I'm, sorry, if you say it's about it's true yeah, the implication is uh we do want to uh index the data, but we're using the is public because it's more reflective of the the state of the deal itself. Let's tie to the implementation details here, I.

M

I

Just as a note, we actually have two governance calls every day that we have them so there's a second one, I think uh 6 PM Pacific time.

I

um This is of course recorded, but that will be a different audience. So, if you're available or if girlfriend wants to come, it might be cool to have you guys there too, we'll be a slightly different audience. uh If not, we have this recording it's going to be available publicly, and one of us can update the community to check that out.

B

Okay sounds good. We are far with you on the link for that.

I

Sounds good thanks for coming! uh Carry it back to you, sir.

A

Wonderful thanks guys this one is just a real, quick check-in, so we talked about this at Phil, Lisbon and I. Think we talked about this on the October 18th call. This is just one of those going going gones that Blue Light Special that we like to highlight- and this is the LDN application we've asked for the addition of country of origin. So if you had any strong conviction, this is your last chance to kind of log into this issue.

A

625 is linked in the PowerPoint that I put in slack as well as in the GitHub, but just a final input for you before we close this out. This was that last community and 631 is the exact same boat. This is in the final days before we close out this proposal. So if you'd like to review this issue, it's essentially adding the email address to the LDN template makes it a lot easier for the kyc kyd. We had no real, strong pushback on the 18th or during kz's talk at Phil Lisbon.

A

So just consider this one friendly reminder if you'd like to log in give a thumbs up. If, if you like, it give a comment, if you'd like to see anything changed, but this is one of the last calls for 631 all right. We posted the links for Phil Lisbon inside of the slack Channel and on the notary governance. This is just a friendly linking it for anybody who may have missed these or want to tune in the point of Phil.

A

Lisbon was a recording session for people that might not be as familiar with the program and wanted to learn more about it. We translated all of the talks into Mandarin, so if you wanted to see the subtitles that should be available for all the talks we have listed so Simon and Phil led the introduction to the program. The intent of this one is, if someone had not heard of Phil plus, and he wanted to give them just a quick 10 minutes on what the program is, how does it work and how do they get involved?

A

That's where you would tune in to sign into Phil's talk, Galen and deep, led a state of the program, much more deep dive on one of the metrics. What are the kyc excuse me, the kpis that we're looking at and what's going to be happening coming forward in the next round of quarters, so we have 2023., Casey and RG, both LED specific sessions to their working groups. You could check those out the runtime, for their talk is around 15-20 minutes and in the run time of questions is another 15 or 20..

A

So if you're looking for just a real quick Deep dive into like what is this group, how would I get involved? Those are great places to start if you're really time is of the essence, just watch their talks and skip over the chats and you'll get a quick sense of how to get involved with it, and then the last is the notary election. We had shared some of like the common questions, some of the questions that would be applicable to the applications and going over that.

A

So if you want to watch that video, it's all there for you as we go through it. So with that we are looking at maybe about 10 minutes left on the call. We have four ldns that have prepared videos. We won't have time to show all four, but we will let them introduce themselves and I'll make sure the links are shared before we do that. I wanted to turn the floor over if anybody had any Flags any questions or any items for discussions for the community. Now the floor is yours.

A

All right that works as well, okay, one last uh plug here- is the link to the air table. If you joined after the call, you might not see it in the chat that came through a little bit earlier, so I'm just going to repost that airtable link here. This is how we use it for the SLA. This is how we use it for the participation we'll be updating this as we go forward, but one more shot on that. So we had four ldns that prepared videos.

A

What I'm going to do is I'm going to post these videos in the LDN application review, slack Channel as well as in the notary channel. So you can take a look. All four of these applications are around two weeks. Old. Few of them are like really brand new, so these are highly motivated organizations that are really Keen to move forward. So they wanted to get this on your radar rather than playing the video here. That might not be the best use of time.

A

Maybe what we'll do is we'll just give them a minute or two just to kind of, say, hello, introduce their program without screen sharing and then all of the video will be available for you, notaries to watch later. So I might mispronounce this, but the roching info Network were you on the line? Did you want to say just a quick hello and uh make sure there was any questions that might come for you.

A

All right no worries. What about you, our dobo might be this pronouncing that are you on the line right now.

A

G

Maybe just going off.

A

Is anybody who made one of these videos or an LDN applications on the line? The floor is yours, so if you're here unmute it's all you.

A

Eric I see that hand call you bud. Okay,.

F

Sorry I I I was asking the Deep for, for the uh project beacons. The Martian dressed was empty, so kind of Highway help you to refuel it. We're waiting for that. Thank.

I

You good call thank you, I realized now that uh Galen had made the request, the rkh, based on an older line of logic, which send a limited amount to that notary right, so I think we just need to get one more uh proposal. Moving on that that that is um something we can do on our end.

C

I

If you want to play any of these or drop links to them, I think we can call it here. Yeah.

A

Yeah I agree, rather than playing the videos I'll just make sure that those links are in the calls in the channels, and that way everyone back all right. Last call before I give you all a couple minutes back on your lives. If anybody has any last thoughts inputs, this is the chance.

D

So a quick question for the Notre application. So do we have to use the like new address this one, this one like the last side.

A

When you say new address like a new Ledger address separate from your third round, yes,.

D

Like the last time like you asked us to to give you the new one right.

A

That's a great question: maybe I'll go and then deep I might click it back to you, I think. During the third round we were also simultaneously rolling out the multi-sig for the LDN V3, which required us to have that new address deep. Is there any reason why we can't just use the same address from last on this? Fourth.

D

I

Sorry when you say that you mean like notary, you cannot reuse, their notary address, correct.

A

Correct can they use the same address from their last? Yes,.

I

So in the past, the reason we had we requested notaries to roll addresses for each election uh was primarily for two reasons. The first was that it made it significantly easier to track performance of a notary over a period of time, and the second was because it forced Norris to reevaluate, especially those that were applying as organizations just healthy practices on who actually owns the address.

I

Who has the Ledger, uh or this is security access correctly set up for it, I think, given the improvements in chain scraping, as well as the fact that, like the application process itself, has become significantly more robust, I think it's reasonably safe for you to keep the same notary address for now. If that changes, for whatever reason, we will be sure to tell you in the next three weeks, but I think you should continue with your same address for now and that's okay.

D

I

Good question: thank you.

J

A

Already filled out with a new address should I turn. It.

J

I

Up to UV no pressure at all, if you prefer just keeping the same one I think you should go for it. Okay,.

M

A

We have three open issues on the community side, so we'll talk about those give you a chance to weigh in before we close them out we'll have plenty of time at the end of this call, we have extra time in the morning for anything you guys might want to raise it's not on the agenda and we had four LDN applications submit videos, so I'll be linking the video content and if you have any questions, if they're on online we'll give them a chance.

A

So with that we'll kick right into it: friendly hello from the governance, Team Deep, Galen, myself, RG, Simon and Phil. We all take a specific aspect of the roles within the philplus community to back you up. So if you have an issue and you need help feel free to tag us, one thing that we are asking is that please don't just tag all of us for any issue that you have. It creates spam and then usually what happens?

A

Is we just tune out because there's so much so if you need something with trust and transparency or ldns, RG and Galen perfectly aligned anything with like elections or notaries, or the on-chain address tag me and I'll back you up and of course, if you're ever stuck, you can always tag me to kind of route that as we go through it, obviously Simon and Phil onboarding, with notary incentives and looking at these programs as we go forward if you're on the call right now, if you change your Zoom handle, it makes it much more effective for communicating with you.

A

So right now my name says Kevin, but if I click on my picture, I can rename and put something like filecoin foundation and then that way, if anybody has a question or wants to ask anything rather than just being a random name, just makes it a lot easier. As we go forward I'm going to post the link here in chat to the air table, you see some vets that have been on this call for a while you're very familiar with this.

A

If you've been doing this right off the bat, this is how we track the SLA for the participation points just being part of the community showing up giving your feedback or just tracking. It goes a long way. So this is the link to the air table. It's in chat, go ahead and fill that out when you have a free moment.

A

Okay, the two links for the true working groups that we have are right there on the screen. Right now, you might have noticed in the notary application that when we asked for SLA participation, one of the fields listed hey if you'd like to get more points and get really active in Phil plus we'd like to see you join the working group. Here's the information for these two working groups. If you were Keen to have this slide deck. This is also in the Phil plus slack Channel, and the thread comments too.

A

If you want to follow along, but in the trust and transparency working group, they meet the opposite times. As this governance call takes place at 30 and 1730. All the links are right there and their whole perspective is.

A

How are we looking at this this model to bring out more more trust, I, guess, that's why that's in their name and the second program there with the Enterprise fill plus pilot, you might have heard Kevin Z talk about this at length, but they also have an application form for you to join and what they're looking at is. How do we scale this program and make this more applicable for a wider audience? So two really good missions. If you want to get involved, that's all the information to dial in with them as we go forward.

A

So with that notary elections. Here's where we stand as of this morning, we had 91 applications, that's come through this just blows it out of the waters, probably like 40 percent more than we had at the third round of Elections earlier this spring. Probably it's well over a hundred as of today, if you've turned in your application, you'll see it right there in the GitHub repository and what I've been doing is anytime.

A

These applications come through, I've, been going through and assigning it to myself changing the label, and this is just a really quick way that lets. You know that I've actually seen it received it and gone through. So as long as you've seen your application come through and seen it changed, it's in you're good to go. What happens next is. If you haven't already applied, we really recommend that you do so just come into the note. Hub excuse me, GitHub, come to the notary governance, you'll, see the link there and just create an issue.

A

You fill out some information about yourself, your organization, how long you've been participating and that'll be the basis that we use to start scoring your application.

A

The way that scoring process works is essentially, we read through each category, it's all public, it's all transparent and we assign a numerical system to whatever the question is and why you put it in that process is going to take us about two weeks and we'll start on that on Thursdays.

A

So what we'll do is we'll read through each and every application, we'll assign a numerical number to each question that you filled out and then we'll reply back in your GitHub with the score: hey, here's four out of five three out of five and we'll essentially give you the opportunity to provide additional information to raise your score or provide any kind of questions that might be outstanding. So with that the next steps are this currently right now, you'll see all the GitHub applications, labeled and updated.

A

Next myself and Phil will be going through each one of those applications and then sending you out information like hey. We didn't see anything about a bookkeeping plan or hey. You forgot to write a number on your away or hey your website didn't work. Can we get some more information, we'll be doing a lot more of that we will link inside of the application that you submitted. So the request that we have is that you please check your application because you'll see some threads come through.

A

If you wait until like December 8th to write back we're, probably not going to have time to incorporate it so the faster that you could write back to the questions that gives them more time for us to really incorporate it back onto it. So this is definitely one of those. Please don't wait to the last minute to provide any information because it might not get incorporated as we go through once we get all that information, we'll give you a score, we'll give you a chance to kind of look at it.

A

We'll combine all those scores in the last couple of days and we'll announce the people selected for the fourth round of notary elections on December 9th. So with that, we have two questions that seem to be coming up quite a bit, so you just want to give them an air time and then I'll open this channel up for any questions that anyone else might have so skipping ahead.

A

Here's the two main questions that I'm getting number one if I'm already a notary, whether it's the second or third election, do I have to reapply so short answer. No long answer is this highly recommended and here's the reason why we had notaries that were in the second round of election that did not apply in the third, which means they didn't complete a lot of the additional, updated diligence and kyc and kyd.

A

So when it came time to add them to the multi-sig for LDN V3, we didn't have any information and they we had a proposal and it didn't pass to add them. So essentially what you're doing by reapplying in this fourth round, aside from re-upping your data you're, essentially future proofing, anything that might change to stay current with the program you don't have to. If you have your data and you're all set you're good to go, but we strongly recommend it's the same application just with a few more Fields just copy.

A

All the information from your third provide a few more additional information. But again it's not mandatory. Just strongly recommended to Future proof anything that might come down the pipe. The second question is: if I've already turned in my application, what happens next or if I turned it in too early? Those of you that turned in an application before the proposals I've already tagged your issues in GitHub. If you have any questions the best way to flag those is in your applications, but essentially you're good to go.

A

We'll just ask for a little bit more information as we go through. So what happens next is we'll be just collecting these right now the window closes tomorrow. So, if you haven't turned in your application, tomorrow is your last date: we're not going to be sticklers with time zones. Just close a business Wednesday I'll make an issue in GitHub and say: hey we're going to cap. We've already done it. So, whatever your time zone is Wednesday. Is the deadline to kind of submit that we'll score everything and announce it on December 9th.

A

So with that I'm going to mute and see if anybody has any questions anything about the process with the elections.

A

All right, I'll consider that time we hit a lot of these. If anything comes up plenty of time, Diana will get through it all right. Here's the open issues that we have on Deck Phil would you feel comfortable speaking to 702 and 666 or Simon. Otherwise, I'll try to take a swing at him and probably.

H

I got it, I can uh speak for seven or two I appreciate that floor is yours, but hey cool, um so uh proposal 702 came about because um there was a previous proposal um shout out to uh Faye uh fayan of carnologic for um creating a proposal. 662, uh 662 um and 662 is basically asking hey uh recently. uh The LDN multisig has been running out of data cap a lot um and because of that depletion it's become a bottleneck for our notaries to get their data.

H

Cap I mean um notaries to issue their data cap to the clients.

H

um That is a big issue, so um so our current proposal uh to solve this is to increase the amount of uh refill uh from uh every week. um So, instead of refilling the data cap, um the LDN multi-sig to a two-week expected amount. We're gonna refill it to a four week expected, uh meaning that, um like, instead of refilling it up to a point where we expect this amount is going to be used up in two weeks.

H

We're going to refill it up to a point where we think that this amount is going to be used up to four weeks.

H

um This would give uh the LDN multisig a greater buffer, so there will be less instances where you won't get your data cap, because um the LDN multisig is empty, um that's one uh and then two. We also realized that, um because of uh Lisbon uh and because of all the travel, all the crypto events happening this week.

H

A lot of the root key folders have not been able to respond uh very early uh to refilling the LDN multisig so um and on top of that, sometimes even when they do so, there's a bug with the front end and they cannot side actually side to refill the multisig, which is really difficult. uh So we are gonna, also train them to make sure that they know how to use the Lotus node.

H

So then they can sign it from there instead of flying in front of from a front end, uh just in case at every empty zone. So uh with these two in place, uh there should be way less instances when the multi LDN multi-sig uh is um out of data cap and therefore that would be less of a bottle. uh If you have any thoughts or comments, feel free to reach out to me or write it. An issue or if you have any comments now, you can also uh speak up here.

H

um Ciao uh I think this is a question about uh the notary election. uh Yes, you do need a ledger for the round four notary uh election. um We do need an address. You can use the same address as you did for uh the round three.

H

Any questions about notary elections or this issue.

H

All right, cool, I think with that I'll give it back to K rate to talk about the other issues. My.

A

Man, thanks Phil. We also have a guest speaker. How are you on the line? I see your uh Avatar. There are you, okay to uh speak to 666 in the next 702 yeah.

B

A

B

Am I going to the next slide cool server formatting was in aligned with the field Plus card. There was no, where um hi everyone Hong Hao here, uh I'm with torfin we're both from the barrel team, specifically on the investing side of things, uh and today we wanted this commercial. You want to discuss the scoping for uh default, investing it's less of an announcement more of hoping to get feedbacks from folks in this call on some of the options that we're considering for investing okay and go to next slide.

B

Yeah so contacts today, Network industry, basically for post now, where these are kind of beefy machines that we run to uh store the index and uh enable the content routing for falcoin and ipf best network um to help scale the PHD, and today the investor is set to default, announce index plus the configuration do not index it, and this was designed based on the assumption that most of the data in the network are public data. So that's called that's why we designed to be default index and unless to specify otherwise the goal here.

B

Is we notice there are more and more demand for Enterprise use case, more private data and we're thinking about evolving the platform infrastructure to better serve these business needs, among which one of the things that we're thinking is?

B

uh Should we change the default indexing mechanism to better serve these non-public data's need specifically, one thing we plan to do is want to add its public flag to the Dual schema and basically, if you set it as true, it means means that the data is supposed to be public, which implies it could be indexed or cheap and for deals that are set as not public.

B

We plan the later introduce Access Control to help guard the content, and this is essentially working with C gravity and uh Lighthouse storage sort of solutions to integrate with the access control mechanism. This is pretty much in line I think with the common car practices anywhere like AWS or Azure. It's basically have no assumption on the data that the data is public unless this is set as public and we only index those ones. So we have more comments on this.

B

More notes on is public flag that we can discuss more in the last slide, but the question we want to get to is what data should be default public published to the investor, and we have a couple of options that we'd like to discuss here. If we go to the next slide, thank you um there's three options. In short, the first option is we scope down the in that, before investing to only index for the Falcon plus deals that are have fast receiver enabled and verified those?

B

This is configurable, so you can also turn it off. By setting that is public equals post and if either fast, retrieval or verified is false. Then we default not to invest it unless it's configured. Otherwise there is a proposal that has more details in this I would place it in the chat. So this link includes more detail on how this could be implemented.

B

The second one is a more conservative option, which is we default not to index for all of the deals and unless you configure uh to turn it on for specific deals by setting the is public flat equals true, and this is a more conservative option and it obviously it has some potential impact for the historical data as well. The thinking over here is, we don't want to change the historical data because there's a lot of complexity over there.

B

So if we go with this option, we'll leave the Legacy index intact for the older deals, but going forward once effective. It applies to the Future deals going forward and the number three is in basically in line with what we're doing today default index for all of the deals, but uh adding capability to configure turn off indexing for specific ones by setting is public, those plus yeah. So that's pretty much it for the different options.

B

I would love to pause here and and just open the floor, and here, if it packs from from folks on the call, especially uh folks that has experience doing private data storage or Enterprise use cases. uh What do you think about these options?

B

Yeah, strong reference.

K

Here, hi hi: this is Charles, hey, Josh, yeah yeah. It's a great idea uh during speaking I like his idea to have the access control. We do connect it to lots of universities.

K

They really care about. uh Example, emphasize that those data, we don't want the people outside the lab to be accessed. Some of them is okay, some of it's not so they really. They were asking us about how to process that we don't have answers for them and since this one will be a good approach.

K

um Right, however, like on a notary side, uh I'm not sure like um this is already something like what happens with the Enterprise, not only applications like only Okay. So it's become us. Something like it's harder to Define is the the data is accessible, so maybe how to manage the um I say. Oh it's a little bit more flexible right. So I think this is more flexible than the um the one. Only it's not really encrypted data. So basically it's just the access control right.

B

uh I think there's two things here: one is uh whether we're in this basically announced it for Content Discovery, and then there will later be additional SS control on top of that, I think for Access Control, referring to things like Wireless Blacklist, these kind of yeah, and that's that would be additional. That will be introduced.

K

Yeah, okay: this is yeah, it's IP based or something like a traditional like uh wallet based or um or email based like a web 2A so which will it will be like you mean for the.

B

Access control yeah, where it's IP based.

K

Or what is the based or email based.

B

Yeah I, don't think that has been fully thought so uh Lauren, basically on the both side, they're working with the gravity right now, the current slot is to be in line with what C gravity is doing, which I believe is IP based, but uh don't call me for that yeah, but but the goal is to integrate with different Access Control Solutions into the market market, to help guard the content, and over here this is kind of like the first step, which is uh on whether we default publish the index or not.

B

Okay, cool thanks, uh someone I'll raise hands uh Danny. You want to jump on jumping this yeah.

N

So I just wanted to clarify a couple of things. So um uh just so I understand- and you may have explained this- so I got distracted so fast, retrieval first, the first retrieval flag is just basically signaling that there's a heart copy, an unsealed copy right of.

M

N

Of the deal and uh a verified deal, what does what does that signify?.

B

Spokes here can explain more my understanding this, whatever ideas are the ones that are passed by the notary uh and um yeah I think Paul. We joined this morning's call, uh so there is a feedback from this morning, which is which personally made me feel like number one. It's not really feasible is uh e field class program, the Enterprise field plus program. uh They would have data that are also fastest human about and verified deals, but they are Enterprise data and they want privacy, so uh so yeah.

B

So we hear pushback this morning regarding the first option and and more specifically, uh what I'm wondering right now is like. If, uh for the use cases, uh do you see the do you see like if we default index for all the views and have it and allow it to be turned off for individual deals that you see reflect over there? Basically, the mechanism that we do today for the private data storage or there's a strong reference that these should be all default in. That's all.

N

So um I guess one of the things I wanted to to check is that, um even though this is in the index uh uh right now, um there is no actual access control on any of these things. So when you yeah so this is, this is purely about indexing.

B

um I think I think we can view if it helps uh we at the mental model that I took right now is that uh there is there's indexing layer which is more like uh whether we make it content with this content discoverable. But this doesn't imply much on the actual retrievability side of things and on the achievability side, uh there need to be Access, Control layer, so also by setting the it's public flat equals. True, like saying this, data is public, it's very similar to kind of what AWS you say. This data is this public.

B

Then, basically, you know there's no getting to this content at all, but when you, when you buy to say like on AWS side, when you add it as by default, equals false, which means that it is not public, then there's all these additional layers of sh control, authentication that comes into place, which I think we will also need to introduce for Enterprise in Brooklyn.

N

So this is a bit more this. This is public bin is more like kind of a robots.txt kind of um uh uh thing where it's basically flagging. Please don't Index this right, um because you could have a third-party indexer that that actually, let me break that into a separate question which is so these flags, and this information is not stored on chain right.

B

That's a great question: uh if we can go to the next slide, I think there's a discussion Point actually on this, uh which is the so I'll talk about number one later, but for number two right now. We're thinking uh this is we'll include, is public in the deal proposal which is not on chain. We in this call we actually want to understand if there is demand, if there's any need that actually justify this information to be stored on chain, because I'm not quite sure whether we actually need it on chain.

N

um So I guess my question is about the indexer, which is, if this stuff isn't stored on chain. How are you, how are you seeing it? Are you watching the traffic on the network for these? um These deal, proposals.

B

Oh you mean so basically today, how it works is that uh there is this uh deck store that uh boost boosts. Basically, the market basically generates these data in the direct store in necessary. You leverage that store as the source of shoes and uh and there's advertisement generated, uh and basically industrial sync, these that Source data into the industry um so yeah. So once it's public it's introduced, then basically there will be additional data in the desktop store that we can chat from and then for those one. We just don't generate the advertisement. Okay,.

N

So one of the reasons, the reason I'm asking all of this is really for how this affects the notary um due diligence. um One of the things that we've sort of been thinking about is tooling to make it easier for us to retrospectively take a look at um what data has been stored, and so uh you know one of our conditions might be for non-enterprise Phil, um uh that that is public should be set true right. So this is more like okay.

N

If we set up these rules and that, for instance, Phil uh Phil plus Enterprise can choose to make is public uh false, we might want to require other um other verified deals to to allow indexing.

N

um So I think that might be one thing we do sort of reciprocally. On our end,.

B

Yeah yeah I think that's something that we need to align, uh which, with whatever approach that we decided to go with or we need to align with field plus, if like say, if they want to do reputation, system, retrievable checking this sort of thing, then uh yeah then hope there should be alignments of like these. Data should be indexed and retrievable so that uh they can be held account.

N

This is this is not so much like you making the roll around number one, but as stipulating that, if you want a verified deal that isn't an Enterprise deal, it needs to be faster, achievable and it needs to be public. I think we require it to be faster achieved. Okay,.

B

N

B

Think that's the case.

B

um James I saw your hand up.

C

Yeah um uh a note on that last comment: uh Phil plus, does not require fast retrieval. uh That's just a slingshot requirement for that I know of.

B

um Oh sorry, I'm curious uh for people outside of things. Beyond slingshot is there any field, Plus data that are required or expected to be retrievable.

C

That just depends on the client. um You know working with the SPs, if they'd stay, that they want the SPs to have fast retrieval for it. uh Otherwise, there's no other guideline.

B

H

There's um I think the film the data program team is trying to develop something, maybe in the future, to like um kind of like create incentives for people to make it retrievable. uh It's still in the works, though so um it will come out in the future. There will be something called like uh validation, but like checks that can ping you to check. If you have like something retrievable um well,.

J

C

Retrievable and fast retrievable are different right. um Yeah.

H

B

Training differences over here.

H

What do you mean like Saturn,.

C

uh No fast retrieval is a config on the minor side that you store a unsealed copy of the data, so you don't have to unseal uh before Retreat uh before people can retrieve the data.

H

Yes, and by so by retrievable, did you mean, like you, just keep a sealed copy? Yes, okay, yeah I meant fashion. Few, oh.

C

H

It um so we want to figure out how we can check whether people have a non-sealed copy um and that's still in the works, but in the future there will be something there.

H

um I think that's the direction, we're heading.

B

Okay, yeah I, think in that case, I would imagine happening as um so for slingshot program we're already working with uh xinjia Team for uh enforcing indexing. So I think there's probably no question about that.

B

But beyond slingshot for any purpose deals that has requirements to uh be checked on faster sure, like say by dubot, then uh yeah, then I I think there will be some sort of I guess there will be some source of shoes from the data programs about these are the data that need to be checked on that need to be fast retrievable, and then uh we can basically make sure that these data are indexed through. That is public black.

B

Or is there any strong opinions on uh on whether this is public flag should be on chain or not?.

J

J

Is speaking um in my own opinion, I, don't think uh this public should be Unchained. It should be only a local configuration with um yeah. That's what we laugh at that um yeah. Any special reason we need to to have this Unchained it's because the index is actually uh index itself.

J

um Yeah. If you don't have the index um yeah in indexer, you you, your data, you still could be. It could be a favorable right. um So we only ask the um your service provider, um who has the yeah Falcon plus deals, uh must have their data, be the retrievable, so they could Define yeah if they want to be uh indexed or that yeah it will be. No no configuration would be very it's not helping.

B

Okay sounds good, I. Think that's what I'm inclined to right now too, is I'm, not sure if I see the clear reason why this should be on chain, because you can check the indexer for this data or Deck Store. So, like mostly investor, you should be able to check it over there. So I'm not quite sure if it is something that's required to be launching uh but yeah, but if I don't hear any rejection uh that I think we'll keep it off chain for now uh and revisit later. If we hear strong requirements on this.

L

What's the timeline for the decision, the final decision.

B

I mean we want to make decision ASAP.

B

So uh if we go back to the last slide for those three options, um yeah so the next step, what we're thinking is we'll update the discussion post that we posted earlier the link here with the kind of outcomes that we gathered from this community, and then our team has some opinion on which direction to go for and then we'll basically uh have internal alignment based on these feedbacks and then we'll post a follow-up on the working group channel for what we decided to go, uh what we propose to go with and then we can go from there if we get majority SPS approval, but this should happen pretty soon.

B

If we want to make the changes here.

L

And and how long is this song, like the couple of weeks or next week or to have to have that yeah.

B

It's yeah you, you call it as an interesting time, because I normally I will come into your timeline, but I, wouldn't because I'm actually uh moving over to the fbm team and everything's gonna, be the new piano over here. So I don't want to overspeak, but for him, uh but he's still ramping up. So we need to. We will figure out I'll get back uh soon. Once once we have an alignment internally like we start playing on the team.

L

All right thanks.

B

B

Dr Kevin uh back to you, I think we're not here.

A

Outstanding appreciate you joining the line, appreciate you giving the rundown I'll make sure that this is in the video we'll have the subtitles ready for anybody that might have any more follow-up questions.

A

Here's the last two, these are hardly is deep dive. These are two open proposals, we're going to close them out this week. So just consider this like one last chance for feedback 625, it's asking in the LDN application for your country and Industry questions. This wasn't too controversial. There wasn't a lot of feedback in the issue, but this is just one last call I'm going to pause. If anybody has any strong conviction on why this should not go through this. Is that last moment, at the wedding before the vows are approved,.

A

See no frantic waving of hands we'll move on, feel free to post in that GitHub KZ we'll be closing that out. The other one is 631 very, very similar. It's an email question to the LDN template. This just really helps with the trust and transparency if we're going to be candid with it.

A

So, if someone's asking for this large amount of data, we just like to have some way to verify that they're with the organization that they are claiming to be so, including the email in that template just adds to that level of kyc that we're doing again. This wasn't a very controversial issue. I'll put 631 in the chat. If you want to take a look at this one, but just consider this one friendly flag. These proposals have been open for about three weeks, we're going to close them out. So just one last chance.

A

If you, you had strong conviction to come through all right with that Phil Lisbon. That was a great event. It was nice to see some of you guys there in person.

A

We had all the recordings from the Phil plus day that happened out there, transcribed and posted to YouTube they're in the notary governance Channel on YouTube I'll link that here shortly we also have the subtitles translated to Mandarin I hope that was helpful for those of you that aren't English speaking by native the five main talks that are, there is Phil and Simon walk through a program overview, the intent of that 10 minute.

A

Video was, if someone had not heard of filecoin plus, and he wanted to just link them to somebody talking about it at a very high surface level view. That's what that 10 minute clip is Galen and deep spent about 30 minutes, giving a state of the union on the field plus program. What are the goals right now? What are we trying to move to in 2023? It's about a 20 30 minute video with some questions booked into it.

A

Then we had RG and KZ both give a retrospective on what their working groups are trying to accomplish, how to get involved, their individual talks for only 15 minutes. So it's a really quick digest. If you were curious about it, then there's another 20 minutes of questions, comments and discussions, and the last video is with the notary election. It's going to be outdated here in about three days, but it was just pretty much an FAQ how to get involved. What's the goal of the notary program and how are the elections going to work?

A

So all of those are on the notary governance YouTube channel. If you have any questions comments, please let me know and we'll get that updated for you.

A

So with that we have about 20 minutes left, which is rare with a group of 45 of us on the call. Normally we solicit topics for the agenda inside of the GitHub, we'll save time for the LDN applications, I like to turn the floor over to anybody on the call. Is there anything you wanted to flag discuss or raise as a question just feel free to raise a hand and we'll call on you to call.

A

You know when to call a good thing when we see it all right, if anyone changes your mind, just feel free to stick that hand up. Oh.

C

I think there is a question in chat.

A

E

Hi there I just wondered: how is the file plus e program tracking.

H

I think I can speak to that. uh So we just uh did the pilot for ethyl plus um KZ is the person on this, but he's uh he's out today.

H

um He like so the pilot is running, we're going through our first few applications and seeing how that goes depending on how the first one goes, we'll decide how to develop the tooling afterwards. So currently, what you can do is like uh you apply uh e-fill plus you go through kyd with KZ, and there are um different steps to it.

H

um You can just slack Casey on um uh through DMs to like ask them how that works, and then afterwards, there's a notary process where you are assigned to random notarities and those two random notaries have to prove you. uh This is for he filmed us yeah.

G

Also, if anyone just wants to just stay up to date, um we do have a field plus Enterprise working group uh just to get the latest updates or just to learn more about it. So I can also copy the working group slog channel into the chat.

H

Yeah, uh we have calls once a week, I believe uh and that's where uh they give updates of how, if ifo plus, is working.

E

Okay, great and just quick question about those two notaries: do both two notaries sign it up have to sign it off and are they from two continents? How does that work.

H

uh So, currently it's completely random and it's since it's a pilot program, uh those notaries. It comes from a unique set of 20 notaries that like and these notaries volunteer to be part of the evil uh experiment, and um so like these people, it's just like this 20 notaries and it's just randomly from those 20s, um and we know that these 20 notaries participate a lot and they're good and they do due diligence properly. So um that's why um yeah they volunteer in the future.

H

We have plans to make it by region and by industry and more on that end, but we don't have enough um Range to do that. Yeah. We don't have enough notice to do that. Yet.

E

um Perfect and one last question: what do you foresee uh the uh once you submit an application? How long do you think that uh diligence process will take? Are we saying seven days uh from apply to sign off to data cap awarded.

H

Is this for the fill Plus or Phil plus engine uh file e?

H

um Yes, uh so for e-fill, plus file e plus, um so this would take depends on the KYB process and depends on how fast um that can be done, because how it works is we're Outsourcing to a third party um for the kyd process, before it's adding an extra step? Basically, and that's like the the Outsourcing, the due diligence to like a KYB.

H

um We we want to do this because it's for private data right. um So that's why the extra step, so what I can tell you is that it would probably um realistically like as this scales it would probably be longer um depending it really depends on on like how fast you like. Do the kyp I, guess that if that makes sense, yeah.

G

Just also jump in real quickly um Jonathan. These are all really good questions again. As Phil said, um this is a pilot, so hence entailing that we are still Gathering data. This is for us to actually see and kind of experiment. What we can see from this um I think these are all good questions that you can ask towards the um the field plus Enterprise working group chat, uh which Casey is involved as well and I, believe these are just again good questions and feedback that we can get to hopefully improve the overall experience.

E

All right thanks very much.

H

I I think the short answer um right now. It should be faster if you keep in touch with Casey a lot, uh but in the future it might be slower, as default plus gets bigger.

H

um That's the short answer.

M

N

H

M

Think someone has.

H

Their uh Darlene.

O

Hello, everyone and I have a question that what if my note is two days away, it will be two years old um it. It can be used to provide that I have two years in the notary rubric.

O

In the time, commitment.

H

L

I guess that's related to the not not re-elections um yeah.

H

Sorry, could you repeat your question? Okay,.

O

um My question is: if my notice two days away, it will be two years old. uh Can it be used to provide that I have two years in the time commitment in the notary aerobic of the notary aerobic.

H

uh uh ah Yes, so I think for the time commitment, um I believe this is: are you talking about like engagement to the program or or time commitment at the top of the um give me a second one? Second, one yeah.

H

Yes, I believe it should be two years yeah.

H

H

J

O

Okay, thank you.

A

Sweet thanks for raising that Phil feel free to Circle back the the two last things I want to flag and then we'll we'll give each other some time back in chat. It looks like we have issue 301 I can't tell as I'm multitask. It looks like this is just waiting for a second notary signature, there's any notaries on the line right now that want to be the second signatory on this one it looks like fenbuchi came through, asked some diligent questions.

A

This is kind of stalled for the past few weeks, I'll flag, this for review in one of our channels, but you might see this come through in the chat if any notaries on the line want to sign this, it looks like that's still waiting, so I'll just put that out there for the radar. On that note too, we had four ldns submit videos for their applications as well. What's nice about applications and notaries? Excuse me ldns that take the time to do. This is just trying to make that diligence process a little bit faster.

A

So, with these four videos, they're, obviously Linked In This slide deck I'll, also post them in the notary Channel, as well as the fill application review, but just any notaries on the line. If you're looking for like a really quick application, that might already have done a lot of the diligence for you without having to follow up and really dig deep. Ideally, the goal of individuals taking this step is to put that on your radar.

A

I know that we had Flags specifically from dubu today, so I'll be posting that in a notary channel, it's a TV online sharing platform, they're looking to Fast Track that ones that come through so again, I'll post the videos for these in our notary Channel, as well as the regions that they're specific to. But if any notaries are on the line and want to take a look.

A

I'll also pause to see if any of these LDN applicants are on the line- and they just want to take just a quick moment and answer questions not give a presentation, but just any kind of updates that they want to share right. We'll make this last call any Alibis saved rounds or any last thoughts before we call it.

A

Wonderful well, thank you, everybody for coming to the second notary governance, call of November 15th, we'll post this on YouTube in the next couple of days. If you have any questions, please post it in slack and again, the election deadline closes November 16th, which is tomorrow. Thank you very much have a great night. Everyone cheers.

H

Thank you, everybody, so yeah.