Skip to content

FIP Discussion: Remove Fplus Notary Process #203

Closed
@Fatman13

Description

@Fatman13

Summary

Remove centralized notary process and develop new decentrailized/algorithmic notary process

Motivation

Current datacap program not only disrupts a free storage market by creating manufactured demand but also hinders the actual adoption of filecoin as a viable alternative to traditional centralized storage services. Datacap program as it is implemented now is centralized, ineffective (at scale) and has no incentive/punitive framework in place for the governance body (i.e. notaries) rendering them unproductive in carrying out governance policies.

From the design of the filecoin storage market, SPs get portion of their revenue from providing retrieval services. As opposed to genuine market demand for storage, fabricated demand for storage won't incentivize SPs to optimize their retrieval capabilities as most data from datacap program has no commercial value at all. This stifles the development for building a competitive user experience (on-par with centralized services) for real-world storage use cases.

Ultimately, the program failed to align the interests of storage providers with the long-term goals of the network which is building a free storage market (free as in free market) over the span of a relatively long period of time (~1 year), during which 4PiB of datacap are sealed by storage providers according to fplus dashboard compared to 14EiB sealed by the whole network. I'd suggest cut the program loose or at least give it a thorough evaluation before it become "too big to fail" starting from removing centralized notary process.

As current LDN goes, verified deals basically made regular deals irrelavant. The network might as well just subsidize deal making directly on the protocol level instead of having applications go through a centralized and ineffective process.

Current Design

Current design of the notary process (centralized) fell short on the following

  • Most Notaries are both player and referee
  • Centrailized process either being slow and ineffective or fast with no audits (it doesn't scale well)
  • No dispute/audit that I am aware of (Please correct me if I am wrong)
  • Not helping real-world adoption as not many real-world clients would actually want to go through the datacap apllication process (It would be more useful for platform like nft.storage to get datacap and use it to subcidize storage but getting real world clients to do that is too ideal)
  • No way to verify private datasets
  • No way to determine if a dataset is useful or not
  • No content moderation (NSFW)
  • Rules around the centralised process that some may find hard to follow

Therefore, I propose allowing everyone any amount of datacap and maybe lowered the multiplier (10x right now), or develop other ways to subsidize datacap deals.

New Design

Premises

New design should adhere to the following premises...

  • Free market principles (as it was presented in here)
  • For real-world adoption
  • Decentralized process

Ideas

New design could incorporate the following ideas...

  • Remove current centralized datacap application process
  • Reward regular deal making with a multiplier
  • Reward "datacap" deal each time network successfully retrieve the deal data
    • something close to off-chain windowPost dispute logic but instead of slashing, it reward successful retrieve;
    • no slashing if fails;
    • facilitate for better user experience for storage client;

Consideration

Deal making is already bearing some extra cost associated with message gas and operation overhead. I think it is reasonable to remove current notary process and subsidize deal making directly until a decentralized process is developed, leaving most of it to the whim of the free market. If a dataset is useful then there should be a high market demand to retrieve such data as opposed to the usefulness of a dataset being determined by the personal preference of a notary.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions