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

Feat: Articulate IPFS Pinning Service Compliance #62

Open
sambacha opened this issue Jul 25, 2023 · 0 comments
Open

Feat: Articulate IPFS Pinning Service Compliance #62

sambacha opened this issue Jul 25, 2023 · 0 comments

Comments

@sambacha
Copy link
Contributor

Articulate Pinning Service Compliance

nodeAddress = process.env["IPFS_RPC_URL"] ?? '/ip4/127.0.0.1/tcp/5001'

Explicitly supporting pinning services that conform to the new pinning registry and compliance specification will ensure that pinned content can be migrated between pinning providers.

This is important because pinning services conforming to this spec ensure that:

  • When a pin is created, the service responds with unique requestid that can be later used for pin removal. When the same cid is pinned again, a different requestid is returned to differentiate between those pin requests.1

  • Service implementation should use UUID, hash(accessToken,Pin,PinStatus.created), or any other opaque identifier that provides equally strong protection against race conditions.1

Footnotes

  1. see https://ipfs.github.io/pinning-services-api-spec/ 2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant