Sorry if this is the wrong place to suggest this, figured this is the easiest way to get an opensea engineer to suggest the feature to the business.
I'm currently working on an NFT that is frequently updated (as short as every minute). With opensea's caching and throttling, this means that the underlying NFT is not always reflected accurately on opensea. Even using GET /api/v1/asset/.../.../?force_update=True theres a few minutes of latency before cached images show up on opensea.
Suggestion:
Allow cache: false in the metadata, and opensea serves the image directly from the image: ipfs://<ipfs_cid> field
Sorry if this is the wrong place to suggest this, figured this is the easiest way to get an opensea engineer to suggest the feature to the business.
I'm currently working on an NFT that is frequently updated (as short as every minute). With opensea's caching and throttling, this means that the underlying NFT is not always reflected accurately on opensea. Even using
GET /api/v1/asset/.../.../?force_update=Truetheres a few minutes of latency before cached images show up on opensea.Suggestion:
Allow
cache: falsein the metadata, and opensea serves the image directly from theimage: ipfs://<ipfs_cid>field