Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Next Governance Call: Tues January 11 4pm UTC AND 12am UTC #364

Closed
Kevin-FF-USA opened this issue Dec 29, 2021 · 3 comments
Closed

Next Governance Call: Tues January 11 4pm UTC AND 12am UTC #364

Kevin-FF-USA opened this issue Dec 29, 2021 · 3 comments
Labels
Governance Call Notifications, agenda discussion, links to recordings

Comments

@Kevin-FF-USA
Copy link
Collaborator

The first Notary Governance Call of 2022 will take place on January 11th at 8am PT // 4pm UTC AND 4pm PT // 12am UTC

You are welcome to attend both! These will be recorded, and video links will be posted in this issue.
https://www.youtube.com/playlist?list=PL_0VrY55uV1-cwaAU8lcChONxYQ_Bj9hx

Agenda topics will include:

  • Updates around the Slingshot Restore Program
  • Check in on the LDN audit process
  • Notaries Discussion Topics
  • Community issues and input

To add to your schedule, the Fil+ Notary Governance calendar is available at
https://calendar.google.com/calendar/embed?src=c_k1gkfoom17g0j8c6bam6uf43j0%40group.calendar.google.com&ctz=America%2FLos_Angeles

If you have items to add to the agenda, please comment below!

@f8-ptrk
Copy link

f8-ptrk commented Jan 7, 2022

we'd like to discuss the possibilities of "2nd tier" / project-notaries that are given a datacap they are exclusively allowed to hand out to their projects users.

Problem: decentralized projects that store data want to offer filecoin backed data storage to their users. right now the project either centralizes the storage deals or each user has to apply for data caps continuously on their own. not only can datacap allocation take a long time - the experience of doing it might hinder the projects adaption and especially the adaption of the filecoin storage features a project might include/offer.

the project that triggered the thought process about this is: https://fx.land/ . I'd like to discuss the general possibility of a notary scheme like this and then, if necessary bring on the project to discuss their specific challenges they, we try to overcome with this scheme in a later call

@Kevin-FF-USA Kevin-FF-USA changed the title Next Governance Call: Tues January 11 4pm UTC AND Dec 07 12am UTC Next Governance Call: Tues January 11 4pm UTC AND 12am UTC Jan 7, 2022
@Kevin-FF-USA
Copy link
Collaborator Author

we'd like to discuss the possibilities of "2nd tier" / project-notaries that are given a datacap they are exclusively allowed to hand out to their projects users.

Problem: decentralized projects that store data want to offer filecoin backed data storage to their users. right now the project either centralizes the storage deals or each user has to apply for data caps continuously on their own. not only can datacap allocation take a long time - the experience of doing it might hinder the projects adaption and especially the adaption of the filecoin storage features a project might include/offer.

the project that triggered the thought process about this is: https://fx.land/ . I'd like to discuss the general possibility of a notary scheme like this and then, if necessary bring on the project to discuss their specific challenges they, we try to overcome with this scheme in a later call

Can do - thanks for flagging this. Sending a friendly confirmation its been added to the discussion agenda.

@Kevin-FF-USA
Copy link
Collaborator Author

@galen-mcandrew galen-mcandrew added Governance Call Notifications, agenda discussion, links to recordings and removed Governance Call Notifications, agenda discussion, links to recordings labels Jan 18, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Governance Call Notifications, agenda discussion, links to recordings
Projects
None yet
Development

No branches or pull requests

3 participants