storacha / content-claims

🦪 Implementation of the Content Claims Protocol.
Other
10 stars 1 forks source link

fix: add gateway URL to materialized location claims #62

Closed alanshaw closed 5 months ago

alanshaw commented 5 months ago

If carpath is already a URL, that is used. Otherwise, this adds https://w3s.link/ipfs/<SHARD_CID>?format=raw&origin=r2://auto/carpark-prod-0 as a URL in the generated location claims.

Also removes the generated relation claim which doesn't provide any further information than the offset of the block header within the shard (which is minus a few bytes from the actual block offset). This is not used by freeway anymore when a location claim with real block offset and length is present (as we are generating here).

seed-deploy[bot] commented 5 months ago
View stack outputs - **pr62-content-claims-API** Name | Value -- | -- cloudfrontUrl | https://d3nc1w40n1r4i7.cloudfront.net functionName | pr62-content-claims-API-fn5FF616E3-VgLfLxntFhMA functionUrl | https://wcbqu4zoe2idyeez2wt4dyyodq0vqnvy.lambda-url.us-east-2.on.aws/ url | https://pr62.claims.web3.storage - **pr62-content-claims-Bucket** - **pr62-content-claims-DB**