Introduction

The speaker welcomes everyone to the Notary Governance Call and outlines the agenda for the call.

Agenda Overview

• The speaker introduces the agenda for the call, which includes government updates on the roadmap, FAQs, proposals, and working group updates.

• The speaker highlights a new training video created by Phil and walks through some FAQs that have been received in Slack.

• The speaker discusses five proposals that will be discussed during the call and provides an update from KZ and Enterprise Phil on private data.

• RG will discuss two proposals (8-9 and 8-33), as well as provide an update on the accelerator program for Greater Heat.

• There will be time at the end of the call for any discussions or open issues.

Participation

The speaker discusses how to participate in future governance calls.

Joining Future Calls

• To join future notary calls, individuals can join a public field channel where all upcoming times are posted.

• If there is an item someone wants to see on a future agenda, they can leave a comment in Slack or GitHub issue 24 to 48 hours in advance.

Participation Tracking

• Participants must fill out an airtable form with their meeting time, date, organization type (notary, storage provider, applicant or community member). This information is used for leaderboard tracking purposes.

• Starting in two weeks' time, participants will use a leaderboard to track participation. A token code will be sent during each meeting which attendees can use to mark their attendance.

Governance Update

The speaker provides an update on governance.

Slack Channels

• There are a series of Slack channels for discussing issues that impact the social channels within Phil Plus.

Governance Team

• The governance team is available to support individuals with onboarding, unblocking notaries, and answering questions. Contact information for each member is provided in the deck.

Roadmap

• The governance team has been working on a mission statement and roadmap for projects in flight. Galen will provide more detail on this during the next call.

FIP 56 Last Call

This section discusses FIP 56, which aims to change the consensus and model in crypto. The last call is currently open for two weeks, and there is a discussion thread available for more information or questions.

FIP 56 Last Call

• FIP 56 aims to change the consensus and model in crypto.

• The last call is currently open for two weeks.

• There is a discussion thread available for more information or questions.

Dashboard, Glyph Verifier, and Community Standards Board Issues

This section covers three issues that were flagged on Slack: dashboard not displaying full data cap allocations, glyph verifier not operating as intended, and community standards board usage reminder.

Dashboard Issue

• Winan flagged that the dashboard was not displaying full data cap allocations.

• Phil and Simon fixed this issue. As of last testing over the last two days, it has been resolved.

Glyph Verifier Issue

• The glyph verifier system was not operating as intended when someone requested less than 32 gigs of data.

• Phil and Simon fixed this issue as well. It should be back up now; if anyone sees any issues, let them know.

Community Standards Board Reminder

• Slack discussions should be conducted professionally without derogatory language or slang terms/names. Discussions that may take longer should go into GitHub instead of Slack.

Additional Issue with SSA Bot Not Refilling Wallets

This section covers an additional issue with the SSA bot not refilling wallets due to an API issue.

SSA Bot Issue

• The SSA bot was not refilling wallets due to an API issue.

• This issue is likely due to glyph making an update for the FVM. It should be transitory and not come up again, but if it does, logs will be in place to investigate further.

How to Use the Registry

This section covers the basic steps of how to use the registry, including logging in, connecting your Ledger and GitHub, finding applications, and signing up.

Using the Registry and GitHub

• To use the tooling, you need to sign in to the registry to view applications and select them.

• You can also open up a GitHub account from within the registry. In GitHub, you can see all of the details on an application such as who's the organization, how long have they been around, where are they using data, and how are they storing it.

• If you have any questions about this process or need help with anything related to notary work, you can ask in the Fill Private Notaries channel.

Frequently Asked Questions

This section answers some frequently asked questions about notary work.

Can I Sign an Application if Another Notary Has Declined?

• Yes. Just because another notary has declined an application doesn't mean that you can't sign it. If you uncover additional information during your diligence or know more about a provider or application than another notary did, then feel free to sign it. However, be transparent in your diligence by providing additional information on why you're making this decision.

Can I Use a Form for Diligence?

• Yes. Some successful notaries use forms like Google Forms or Airtable to collect diligence on an application. As long as it correlates with your data diligence plan and is transparent so that other notaries can see what questions you're asking.

How Can I Ensure Transparency in My Diligence Plan?

• Make sure to come back into GitHub and leave a comment on the application after any communications, whether it's in Slack or email. This will increase transparency and help other notaries see what questions you've asked. It also helps if there is ever an audit on what this form data was.

Where Do I Find Applications to Sign?

• There are three different places where you can find applications to sign: the registry, GitHub, and the Fill Private Notaries channel.

Notary Communication and Registry

This section covers how to communicate with applicants and find LDN applications awaiting signature.

How to Communicate with Applicants

• Use GitHub and Slack to contact applicants.

• Check the registry for LDNs awaiting signature. It's around 300, but there is no way to sort them.

• View GitHub applications to scan through if something is in your country of origin or workflow.

Can Notaries Sign for Applicants Who DM Them?

• Yes, notaries can sign for applicants who DM them because their notary information is public in the repository.

• Be sure that you're doing the diligence in the application means that if Lucky was to message you and say hey can you please look at my application and you look at it any kind of communication on the application isn't taking place in that slack but it's taking place so that's that's a great way I'm happy to hear that

• If an applicant DMS you and says hey can you please review my application, go ahead.

Multi-Sig Launch Update

This section covers updates on multi-sig launch.

Multi-Sig Launch Update

• The multi-sig launched two weeks ago (835).

• All notaries who completed their disclosure form, set up their Ledger, and verified it in the registry are cleared to start signing.

• A manual process will add notaries who missed the initial Ledger change date.

Open Proposals

This section covers open proposals on GitHub.

Open Proposals

• Four issues are in the last stage and open for one final round of input: staking proposal, auto close after two weeks proposal, KYC on data cap removal, and trust and transparency.

• Leave comments on these proposals even if it's just love it or hate it. This helps the team provide the right tooling and documentation as well as keep notaries active.

Introduction

The speaker introduces the topics that will be discussed in the call and mentions that they had an issue flagged by the community regarding multiple datasets.

Multiple Datasets

• The community flagged an issue regarding multiple datasets.

• Discussion on whether multiple datasets should be in one single application or spread across.

• Proposal to convert files to a Json file for increased trust, transparency, standardization, and reliability.

Json File Conversion Proposal

The speaker discusses the proposal to convert files to a Json file and the ongoing discussion about whether there should be one big Json file or many small ones.

One Big Json File vs Many Small Ones

• Engineers Fabri and Hussein, as well as Catelyn from the dmup team, have thoughts on this proposal.

• Pros of having one big Json file: easier to scrape since it's just one file; minimizes number of files in GitHub repo.

• Cons of having one big Json file: merge conflicts if editing two applications at same time could lead to inconvenience for notaries.

• Leaning towards many small Json application files but open to thoughts from others.

E4 Plus Graphic Data Pilot Update

Kevin gives an update on e4 Plus graphic data pilot including statistics, ongoing tests, and next steps.

Statistics

• 11 new applications came in Q1; 25 applications over five-month period (end of October).

• Averaging around five to six applications per month.

• Nine applicants have received data cap and are onboarding data making deals.

Testing

• Ongoing testing for KYC and KYB (know your customer, know your business).

• Third-party products being used to get approved and build initial trust.

E-Fill Plus Program Update

Casey provides an update on the E-Fill Plus program, including allocation assignments and plans for automation.

Allocation Assignments

• Two notaries are assigned randomly to each allocation.

• The number of allocations is growing, with multiple applications being assigned per day.

• Notifications are sent via GitHub, so make sure emails are not going to junk.

• Allocation request amounts will be increased to accommodate larger data sets from Enterprise customers.

Plans for Automation

• Processes such as assigning notaries and following up on comments will be automated in the future.

Client Experience Survey

• A client experience survey will be sent out in the next two weeks to gather feedback on working with SPS through the process.

CERN POC

• CERN via COSP will onboard a small POC of three and a half Pips, with allocation request amounts increasing to over six and a half Pips times five copies (20+ Pips).

Q&A Session

Participants ask questions about the E-Fill Plus program.

Next Call Schedule

• Bi-weekly calls are held every other Tuesday following the same timing as the notary call. Participation has been low, so updates are also provided asynchronously in the EFO working group Slack channel.

Data Cap Turnaround Time

• The usual average turnaround time for data cap is less than a week or 95th percentile. Statistics can be found on the Interplanetary Statistics page.

Other Questions

• Other questions are asked and answered, including the typical data cap size and waiting time.

Code of Conduct

The TNT working group has decided to create a standalone code of conduct, parts of which will be derived from the contributor covenant. The detailed post describing the code of conduct will be published tomorrow in the TNT working group Channel and pinned for everyone's convenience. Until the details are finalized, they will proceed with the current consensus model where they open a GitHub issue, have a timeline for discussion and consensus, and then ratify it that way.

• There were questions about who will enforce the code of conduct until the details are finalized.

• In the medium term, there will be a TNT board that will ratify decisions through consensus.

• Consequences include giving a public warning that might impact a stakeholder's reputation, blacklisting addresses using tooling being built, flagging this to stakeholders who take care of Falco and slack, and permanently blacklisting an account or address from Auckland slack.

Upfront KYC

The proposal for upfront KYC is considered passed. Community members are recommended to do some checks on behalf of the community. They want other community members from other regions to take charge of scoping out a third-party KYC vendor so that they can conduct checks on behalf of the community.

• Main concerns were regarding KYC solutions for Asia region and Philippos governance team becoming data owners.

• Community members in Europe have taken initiative to create a form and do these checks.

• They want other community members from other regions to take charge of scoping out a third-party KYC vendor so that they can conduct checks on behalf of the community.

• They will post a form in the TNT working group channel for community members who might be interested in doing specs on behalf of the community.

Trust and Transparency Working Group Call

In this section, the speaker discusses three main updates related to trust and transparency. The first update is about enabling third-party KYC and address upfront to prevent abuse. The second update is about a pilot program initiated by a successful SP in the ecosystem to onboard other recipes. The third update is about the launch of Fem onto mainnet.

Updates on Trust and Transparency

• Enabling third-party KYC and address upfront to prevent abuse.

• Data cap is a novel resource in the network, so there needs to be a cost associated with applying for it.

• A pilot program will be designed, and results will be posted for community review.

• Pilot program initiated by a successful SP in the ecosystem to onboard other recipes.

• 30 existing non-public miners will become Falcon SPS, bringing close to 200 Pips of Rob by power data (roughly translating to 1000 Pips of data cap).

• They are willing to do KYC, but they will not use UFO Plus for this.

• A public issue will be created on GitHub for full transparency on what they're trying to do.

• Launch of Fem onto mainnet

• Opportunities for building stuff on FVM for Fill Plus

• Data cap can now be obtained as smart contracts written on FVM.

Q&A Session

• Participants are encouraged to participate in comments on GitHub regarding these updates.

• Participants are invited to ask questions or raise any issues from Slack or the community.

Introduction to Moon Landing Program

In this section, the speaker introduces the Moon Landing program and explains its purpose.

Purpose of Moon Landing Program

• The Moon Landing program facilitates newer recipes to onboard their ecosystem by storing large open datasets.

• Participants in the program act as data preparers asking for LDN and data cap so that they can work with storage providers also participating in the moon landing program to store these data sets.

• The program encourages 10x replication of each dataset for disaster resilience purposes.

Governance Call for Filecoin Community Members

In this section, Lucky introduces a governance call for Filecoin community members.

Details about Governance Call

• Lucky is the governance project manager at Filecoin Foundation overseeing bio quality improvement proposals.

• The first Community Governance Town Hall will be held on March 27th.

• The call will cover topics such as FIP governance 101, network upgrades, and hearing back from the community regarding perceived governance.

• Lucky drops a registration link in the chat for those interested in attending.

Conclusion

In conclusion, this meeting covered two main topics: an introduction to the Moon Landing program and a governance call for Filecoin community members.

Introduction and Agenda Overview

This section provides an overview of the agenda for the notary governance call.

Introduction and Agenda Overview

• The call is introduced as the second notary governance call of March 14th.

• The agenda for the call is outlined, including updates around notaries, proposals, working groups, and discussions.

• The time frame for the call is discussed, with a reminder to check the Google Calendar for accurate information.

• Slack channels are highlighted as a key communication tool for participants.

Conclusion of Call

This section covers the conclusion of the notary governance call.

Conclusion of Call

• The end of the call is announced.

• Participants are thanked for attending.

• Information about where to find a recording of the call is provided.

• A reminder about upcoming calls is given.

Final Goodbyes

This section covers final goodbyes at the end of the notary governance call.

Final Goodbyes

• Participants say goodbye and thank each other before ending the call.

Updates Around Notaries

This section covers updates around notaries that were discussed during the governance call.

Updates Around Notaries

• An update on an onboarding guide video is given, along with information on how to access it and FAQs related to it.

• Slack discussions that may have been missed by some participants are reviewed.

Proposals Discussion

This section covers proposals that were discussed during the governance call.

Proposals Discussion

• Two proposals from Phil and one from community members are reviewed before moving forward.

• Participants have a chance to discuss these proposals before moving forward.

Working Group Updates

This section covers updates from the Enterprise Field Plus and Trust and Transparency working groups.

Working Group Updates

• Updates from the Enterprise Field Plus and Trust and Transparency working groups are given.

• Participants who were not present for the morning call receive an update on what was discussed.

Governance Call Timeframe

This section covers the timeframe for future governance calls.

Governance Call Timeframe

• The UTC 1500 and 0-1 time frame is discussed, with a reminder to check the Google Calendar for accurate information.

• Potential scheduling conflicts are mentioned, with a plan to reach out to notaries in the Slack channel to ensure that this time frame still works for everyone.

GitHub Issues

This section covers how to use GitHub issues related to notary governance.

GitHub Issues

• The importance of using GitHub issues is emphasized.

• Participants are encouraged to drop comments in relevant issues if they have topics they want discussed or reviewed.

Communication Channels

This section covers communication channels used by notary governance participants.

Communication Channels

• Slack channels used by participants are highlighted as key communication tools outside of GitHub.

• Participants who may be lost on where to go can reach out for help.

Notary Governance Roadmap

The government's team is working on a notary governance roadmap that outlines projects to improve the project and make it more stable. The roadmap will cover documentation, tooling, and strategic exchange proposals.

Projects in the Notary Governance Roadmap

• The notary governance roadmap outlines projects to improve the project and make it more stable.

• Projects are categorized into documentation, tooling, and strategic exchange proposals.

• The roadmap will be rolled out in detail during a call in two weeks.

• A public roadmap will be available for viewing.

FIP Discussion

Lucky from the Filecoin Foundation joined the call to discuss FIP (Filecoin Improvement Proposal). The FIP is in its final call for input, and there is still time to provide feedback.

Details on FIP

• Lucky from the Filecoin Foundation joined the call to discuss FIP.

• The FIP is in its final call for input.

• There is still time to provide feedback on the FIP.

Bug Fixes

Four bugs were identified with Glyph updates. SSA bot was unable to detect whether an LDN application was out of data cap. Glyph verifier could not issue 32 gigabytes for auto verification of client applications. Interplanetary dashboard had issues populating data points.

Bugs Identified with Glyph Updates

• Four bugs were identified with Glyph updates.

• SSA bot was unable to detect whether an LDN application was out of data cap.

• Glyph verifier could not issue 32 gigabytes for auto verification of client applications.

• Interplanetary dashboard had issues populating data points.

Bug Fixes and Community Communication

This section covers the gratitude expressed towards Catalin for fixing bugs last minute, as well as the importance of clear communication within the community.

Bug Fixes

• Catalin from the dmup team fixed a bug that required creating another service to download and decompress data before putting it on the dashboard. This was done within a few hours.

• Without this fix, the bug would not have been resolved.

Community Communication

• The community has improved its communication standards, which has been helpful in keeping everything above board.

• GitHub and Slack have seen marked improvements in communication.

• Standards have been linked to ensure everyone is adhering to them.

Video Tutorial on Registry Applications

This section discusses a video tutorial created by Phil on how to use the registry to view applications and sign an approved data cap.

Video Tutorial

• Phil created a short, succinct video tutorial on how to use the registry.

• The video walks through step-by-step instructions on signing into the registry, connecting your Ledger, searching for applications, and more.

• The tutorial is posted on YouTube in the Phil plus section of Filecoin's channel.

Fill Plus Registry Optimization

This section covers Ezra's optimization of Fill Plus Registry for faster loading times.

Optimization

• Ezra from Keiko team optimized Fill Plus Registry so that it loads much faster than before.

• Instead of waiting several minutes for all applications to load, it now only takes a few seconds due to rendering differences.

• Bugs may still be present with this new launch.

Notary Questions and Answers

In this section, the speaker answers some common questions that notaries have about their role in the diligence process.

Can I sign an application if another notary has passed on it?

• Another notary passing on an application does not prevent you from signing it.

• Diligence plan would fall on you.

Is using a form to do diligence allowed?

• Using a form to do diligence is allowed and can be successful.

• Bias towards transparency is important when using forms.

How can I ensure my diligence is transparent?

• Communicating in GitHub is one of the easiest ways to ensure transparency.

• Leave comments in GitHub about offline communication with data applicants.

How do I know which applications to sign and how to communicate with applicants?

• The registry is a great tool for finding applications to sign.

• Check out the slack Channel fill Plus application review for more opportunities.

Finding Applicants on GitHub

This section discusses two ways to find applicants on GitHub.

Two Ways to Find Applicants

• The first way is to use the registry website, which is linked to your Ledger and GitHub. It allows you to see all the applications and assign them.

• The second way is to check GitHub yourself by sorting applications by region, industry, or date.

Notary Questions

This section addresses any questions notaries may have about the onboarding process.

Manual Collection of Access Requests

• Notaries who completed the fourth round but did not receive access to LDN V 3.1 or the new multi-sig will be manually added in a few days.

• Those who were missed were asked to leave a comment so they could be collected manually.

Data Caps Are Live

• New notaries have data caps and can distribute them as needed.

• If there are any questions about individual applications or processes, feel free to ask in the private notary channel.

Proposals for Feedback

This section covers four issues that require feedback from users.

Staking Structure and Trust & Transparency Issues

• These issues are looking for feedback on how staking should be structured and how trust and transparency should handle auto-closing applications that have been around for more than two weeks.

• TNT has been closing out many of these issues recently.

Code of Conduct Proposal

• There is a proposal for a code of conduct that users can comment on in GitHub.

SLA Feedback Requested

• Notaries who selected SLAs three, four, or five are encouraged to leave comments and provide feedback on shaping future projects.

Data Cap Removal Process Proposal

• There is an open issue (832) soliciting feedback on whether data sets with multiple aspects should have multiple applications or be grouped into one larger application.

Final Thoughts

This section provides a final opportunity for users to provide input on the open issues discussed in the previous section.

Data Cap Removal Process Proposal

• Users are encouraged to leave any final thoughts they may have on issue 832 before it is closed out.

Moving Away from Comments to Json Files

In this section, the speaker discusses how they plan to move away from using comments to store data about LDN applications and instead use Json files and code. They also discuss the specifics of how they plan to store LDN application data.

Storing LDN Application Data

• The team plans to move away from using comments to store data about LDN applications.

• Instead, they will use Json files and code to store information about LDN applications.

• The team is still figuring out the specifics of how they will store the LDN application data.

• They are considering whether to have one big file that stores all the LDN applications or multiple small files (one for each application).

• Another possibility is having many Json files but archiving old ones that haven't been used in two weeks.

Open Call for Contributions on Storing LDN Application Data

In this section, the speaker invites anyone who has thoughts or input on storing LDN application data using Json files and code.

Open Call for Contributions

• The speaker invites anyone who has thoughts or input on storing LDN application data using Json files and code.

• Before moving on, the speaker asks if anyone has any questions or input on open proposals.

Working Group Updates: E-Fill Plus Program

In this section, the speaker provides an update on the E-Fill Plus program's progress in onboarding private data.

Onboarding Private Data

• The E-Fill Plus program is focused on onboarding private data.

• KZ has been working on a survey and metrics to understand the data sets being submitted.

• There have been 22 applications since October, more than expected.

• Nine clients are actively being onboarded, representing over 100 petabytes of data.

• The team is looking at how to build trust in the onboarding process and streamline tooling to make it as quick as possible.

• KZ is putting together a client impact survey and looking at how to improve the 48-hour SLA for the process.

Trust and Transparency Working Group

This section covers the Trust and Transparency working group's proposals for building consensus around violations of the code of conduct, upfront KYC, and onboarding large amounts of data.

Code of Conduct Review

• The proposal outlines steps to be taken in case of a violation.

• Step one is to issue a public warning.

• Escalation includes blacklisting, removal from program, banning from Slack/GitHub/calls.

• No questions or feedback from the community.

Upfront KYC

• Looking at making this process mandatory before moving forward with more details.

• Closed out officially in GitHub. Final discussion at end of call.

Onboarding Large Amounts of Data

• Accelerator program by storage provider Greater Heat to onboard 100 petabytes within six months.

• New proposal issue coming from Tarot and RG.

Updates on Trust and Transparency

The speaker provides updates on the trust and transparency initiatives.

Trust and Transparency Updates

• Three updates were provided by RG this morning regarding the trust and transparency initiatives.

• The speaker turns it over to the audience for any questions or comments.

Discussion on Meeting Time Zones

The speaker discusses time zones and asks for feedback from the audience.

Meeting Time Zone Discussion

• The speaker brings up the issue of time zones, specifically in California after daylight savings.

• A survey will be sent out to ensure that meeting times are consistent with everyone's workload.

• The audience is asked to provide feedback on meeting times through Slack or during the call.

Closing Remarks

The speaker wraps up the call with closing remarks.

Closing Remarks

• No questions or comments were received, so the call ends early.

• The speaker thanks everyone for dialing in and wishes those still in the 14th time zone a happy Pi Day.

• Call ends.