You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At Sourcify we have a public repository of source-verified Solidity smart contracts https://ipfs.io/ipns/repo.sourcify.dev/ As contracts get verified we add the files to IPFS, and pin them on our node. Then, every 6 hours we update our IPNS to point to the latest version of the root CID of the repository. Also, every 6 hours we pin that new root CID on external pinning services. One of them is Estuary, thanks to your generous pinning offer.
However, recently our pins have been sitting queued for a while. I see other nodes pin these pins by checking ipfs dht pindprovs but I can't make sure if these are through Estuary.
Is there a way to troubleshoot this?
Additionally, we have been pinning since some time a good amount of pinned files have accumulated, which are actually not relevant anymore as they are old versions of the repo and the repo is append-only. I thought Estuary has been deduping across these pins but it doesn't seem to be the case
I have tried deleting the old pins through a simple script by getting the pins and deleting each one of them but for a good amount of them I am getting error {"error":{"reason":"Internal Server Error","details":"record not found"}}. Is there an easy way to do this? Once we've cleaned everything up, we'll be running this regularly to delete older pins, say older than 30 days.
At Sourcify we have a public repository of source-verified Solidity smart contracts https://ipfs.io/ipns/repo.sourcify.dev/ As contracts get verified we add the files to IPFS, and pin them on our node. Then, every 6 hours we update our IPNS to point to the latest version of the root CID of the repository. Also, every 6 hours we pin that new root CID on external pinning services. One of them is Estuary, thanks to your generous pinning offer.
However, recently our pins have been sitting queued for a while. I see other nodes pin these pins by checking
ipfs dht pindprovs
but I can't make sure if these are through Estuary.Is there a way to troubleshoot this?
Additionally, we have been pinning since some time a good amount of pinned files have accumulated, which are actually not relevant anymore as they are old versions of the repo and the repo is append-only. I thought Estuary has been deduping across these pins but it doesn't seem to be the case
I have tried deleting the old pins through a simple script by getting the pins and deleting each one of them but for a good amount of them I am getting error
{"error":{"reason":"Internal Server Error","details":"record not found"}}
. Is there an easy way to do this? Once we've cleaned everything up, we'll be running this regularly to delete older pins, say older than 30 days.And finally, I can't seem to be able to access the successfully pinned pins through the Estuary gateway https://gateway.estuary.tech/gw/ipfs/QmPRVtsK5eUounRpDkeHh7ZfjVpbQdzYVvC4p6pzujuVz1 whereas it works on others https://ipfs.io/ipfs/QmPRVtsK5eUounRpDkeHh7ZfjVpbQdzYVvC4p6pzujuVz1/
The text was updated successfully, but these errors were encountered: