w3s-project
Assert equivalence claims for submitted filecoin pieces
Context
Currently system seems to issue equivalence claims after piece is submitted, which ensures that when SPs access piece via roundabout they will be redirected to the location from which they can read corresponding car.
What
With blob API we no longer using CARs and will change equivalence claims to extends support for blobs https://github.com/w3s-project/content-claims/issues/60
We need to ensure that issued equivalence claims is aligned with ☝️
@vasco-santos I think you could help fill this out with more details as I'm getting bit lost
Sure @Gozala . I think we need to align on https://github.com/w3s-project/content-claims/issues/60#issuecomment-2075786891 + https://github.com/w3s-project/w3up/issues/1408#issuecomment-2075818557 first.
Either we need to provide the digest instead of the CAR CID, or swap to provide RAW CID for content instead
(we agreed we can do this as follow up) Equivalency claim issued by filecoin pipeline can pick the digest of the received raw CID
I believe the equivalence claim is now issued by the pipeline as a "raw" codec CID. @vasco-santos please correct me if wrong!
