NFT collections of PHP images exist as separate files, mostly on IPFS. Slow.
So, part of the "album cover" is the single file spritesheet of the collection. These spritesheets will contain low resolution renderings of the entire collection. These are what tink.js will use to map overview visualizations including, say, 3D animations via WebGL or a 2D grid list.
The structure of the spritesheet needs to be in the metadata: file size, sprite dimensions, numbering order, all the info needed for actually processing it for client use.
NFT collections of PHP images exist as separate files, mostly on IPFS. Slow.
So, part of the "album cover" is the single file spritesheet of the collection. These spritesheets will contain low resolution renderings of the entire collection. These are what tink.js will use to map overview visualizations including, say, 3D animations via WebGL or a 2D grid list.