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
Articulate Pinning Service Compliance
dpack/src/ipfs-util.ts
Line 7 in 830ce46
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
requestidthat can be later used for pin removal. When the samecidis pinned again, a differentrequestidis returned to differentiate between those pin requests.1Service implementation should use UUID,
hash(accessToken,Pin,PinStatus.created), or any other opaque identifier that provides equally strong protection against race conditions.1Footnotes
see https://ipfs.github.io/pinning-services-api-spec/ ↩ ↩2