hottakes

Base changed people's perception of NFTs and might be the biggest cause of backsliding to using regular server URLs for NFT metadata. I just ran through all of my Base NFTs and 38% of them use centralized web2 server URLs for token metadata.

Writer. Building @pinatacloud. Tinkering with a Farcaster native alternative to GoodReads: https://readcast.xyz \ https://polluterofminds.com

Basepaint

 /basepaint

prev: coinbase, zora, zapper

Fast retrieval is a solved problem though. And you can use IPFS. I honestly think it’s a messaging problem in web3. People think you can’t have both.

/basepaint NFT metadata uses a server for fast retrieval but anyone can verify the authenticity of the final img by rebuilding the it from all onchain paint events

Art, music, onchain data. Former Director of Research @coinmetrics

No, I mean that because the transaction cost is so cheap that people don’t care about preservation and open access as much. When an ETH project could cost you hundreds in gas to mint, you didn’t trust the NFT data to be on a traditional server because you could be rugged anytime

Interesting, what do you mean by Base changed the perception of NFTs? That they don’t need to be tied to the main chain?

realistically persistence is still a not fully solved problem with ipfs requiring (paying for) pinning and arweave unrealistic promise of pay once host forever. Given that both can fail you plus the additional centraized L2 point of failure probably make it not worth it for many, especially given that many are ephemeral mints