Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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

FIP discussion: Create an on chain deal status communication channel #132

Closed
dd45e640b42e6da7da96faee3996ef7c opened this issue Jul 29, 2021 · 2 comments

Comments

@dd45e640b42e6da7da96faee3996ef7c
Copy link
Contributor

The Storage Provider Working Groups NA call discussed a lot of legal issues regarding content and how to implement best practices regarding communication between storage clients and storage providers.

The basic idea is:

Create a flag or an array of flags attached to the on chain status of the deal that the storage provider can update to communicate information on chain to a client he does not know, he cannot contact or when all other communication channels are blocked.

The concrete use case that i brought up during the call (in the chat actually) is the canary in the coal mine for take down requests a storage provider receives and is legally not allowed to communicate to the client. But i can imagine other use cases as well where it is convenient to be able to communicate information via the only on chain connection client and storage provider have.

I would suggest a bit array not bigger than 8 bits, that should allow for 256 states to be communicated.

@kaitlin-beegle
Copy link
Contributor

Hi @f8-ptrk, just wanted to follow up on this proposal. As a reminder, FIP drafts are usually authored by whomever sponsors a FIP discussion.

Do you plan to write a FIP draft for this proposal? No problem if not, you're welcome to leave this as an open issue for the time being, but I wanted to check in.

Thanks!

@dd45e640b42e6da7da96faee3996ef7c
Copy link
Contributor Author

@kaitlin-beegle it's still under consideration to make this aFIP proposal. schedule is busy these days - i have it on the list - but it might take some weeks

@filecoin-project filecoin-project locked and limited conversation to collaborators Jan 4, 2022
@kaitlin-beegle kaitlin-beegle converted this issue into discussion #246 Jan 4, 2022

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants