Open LesnyRumcajs opened 4 months ago
We have switched to the trustless approach in #3244
Weren't there some issues that caused us to switch to proofs.filecoin.io
? https://github.com/ChainSafe/forest/blob/f05854462f5be9721de2ef868aadcce97a039cdb/src/utils/proofs_api/paramfetch.rs#L37
Weren't there some issues that caused us to switch to proofs.filecoin.io?
I believe that's irrelevant to the trustless approach. proofs.filecoin.io
gateway has all parameter files preloaded while a general public gateway needs to find and download them in the network before they can serve the download request
Are you saying we should not do this? See this comment as well on the reasoning behind the (potential) switch https://github.com/filecoin-project/lotus/issues/12273#issuecomment-2243936155
proofs.filecoin.io gateway has all parameter files preloaded
@hanabi1224 it's even simpler than that: proofs.filecoin.io
does not run an IPFS node at all. It serves the files from a plain directory with a plain http server, in a manner that matches the ipfs http gateway. But no IPFS running there at all.
Issue summary
From @BigLep
Sample usage: https://trustless-gateway.link/ipfs/QmS7ye6Ri2MfFzCkcUJ7FQ6zxDKuJ6J6B8k5PN7wzSR9sX?format=car
Note that we need to extract the file from a CAR file encoding a UnixFS file. Hopefully, this is already feasible with the tooling at hand.
Other information and links