Skip to main content

r/ipfs


IPFS wasn't the weak link: in a survey of 250 NFT collections, 2% of IPFS ones were broken against 56% on their own servers
IPFS wasn't the weak link: in a survey of 250 NFT collections, 2% of IPFS ones were broken against 56% on their own servers

I surveyed the 250 biggest NFT collections on Stacks to see whether their art is still reachable from the contract. The headline is good news for IPFS: 4 of 203 IPFS collections were broken, against 9 of 16 on projects' own servers.

The catch is who's pinning:

- 9 collections hardcoded Cloudflare's gateway into their URIs. When it closed in August 2024, some survived through other gateways and some didn't.

- The marketplace's copies for 214 of 241 collections sit in one Pinata account.

- One 2,500-image collection exists, as far as I can find, in one folder held by one pinning account.

Content addressing did its job. What fails is the arrangement that keeps a copy alive after the team moves on. What's the most durable setup you've seen for that?

Full write-up (I build an on-chain storage layer on Stacks, for disclosure): https://xtrata.xyz/a/3654


Advertisement: Plants take time. Your internet shouldn’t. That’s just one reason to try T-Mobile 5G Home Internet.
Plants take time. Your internet shouldn’t. That’s just one reason to try T-Mobile 5G Home Internet.
media poster


Kubo Defunct
Kubo Defunct

I tried to start Kubo a few minutes ago & kept getting the error:

ERROR
autotls.renew certmagic@v0.25.3/config.go:977 could not get certificate from issuer {"identifier": "*.k51qzi5uqu5dib71dwmielsxiew9mefrghdsbincj4gs03794yvdmpdsrpkev1.libp2p.direct", "issuer": "acme-v02.api.letsencrypt.org-directory", "error": "[*.k51qzi5uqu5dib71dwmielsxiew9mefrghdsbincj4gs03794yvdmpdsrpkev1.libp2p.direct] solving challenges: presenting for challenge: no public address found (order=https://acme-v02.api.letsencrypt.org/acme/order/3430357256/577068260762) (ca=https://acme-v02.api.letsencrypt.org/directory)"}

As best I could tell the server was unresponsive.

I poked around a bit & it turns out register.libp2p.direct doesn't exist anymore. It used to be part of the AutoTLS which gave each IPFS node a valid TLS certificate.

I went into the config & changed "AutoTLS": {} to "AutoTLS": { "Enabled": false }, rebooted, & it worked.


IPFS is a bad idea.
IPFS is a bad idea.

IPFS doesn't solve any issue at all, i think someone just wanted to sell and dump their filecoins when they were 100 euros each in 2021.

  • Anonymous file sharing? No.

  • Faster file sharing than HTTP or BitTorrent (DHT)? No.

  • Do i pay less than a traditional cloud subscription for storage? Absolutely not.

  • Does it solve centralized architecture (SPOF)? No, a centralized service must keep existing or even being paid to keep the content pinned inside the network.