artist | collector | sustainability | rektguy 

           🔗: https://seemore.tv/hustletrees

PSA

You're collecting the cast, not the image / video / URL, etc.

The collectible (NFT) rendering makes that clear.

Don't overthink it.

great question! I don't believe there is anything in the auction or NFT contracts related to that, so it would have to be an update to the snapchain/hub logic.

it looks like the NFT metadata is currently stored offchain on merkle servers, and one of the metadata properties is the link to the cast itself hosted on farcaster[.]xyz

here is an example: https://api.farcaster.xyz/v2/cast-collectibles/metadata?id=0x0000000000000000000000008002dad4b2cb75b9d9f838d5aec5e330e72383d9

as is, I believe this would result in metadata rot if the cast gets dropped for storage reasons. I hope this is just the first iteration and that the team will make use of the modular metadata feature of the NFT contract to upgrade the metadata to more decentralized and persistent storage

question, what happens if the cast goes stale because we don't renew storage and it's an old one?

question, what happens if the cast goes stale because we don't renew storage and it's an old one? https://farcaster.xyz/spengrah.eth/0xd41f3d19

planting causal loops; harvesting reflexivity

the cast itself is affected by storage and deleted. The rendering of the cast you’re buying is onchain and stays. The link between the collectable stops when the original cast is deleted. You’re essentially buying a screenshot of the cast, not the actual cast.

Founder of @rune-online & /rune || /gameplay & /futurama

could you point me to where the cast is rendered onchain?

admittedly I didn't look *super* hard at the contracts, but the only onchain metadata I could find was a url to an offchain api

I work at the posts office

terminally.online

building /hatsprotocol | 
proudly mid-curving it since 1995

cc @horsefacts.eth 

We have a v1 and then are thinking about a future iteration.

I'm guessing this is what the metadata module feature is for, yes?

maybe something like screenshot of the cast/embedded media as ipfs would suffice, users can always self-pin in the future