New Feature: Metadata Provider Compatibility
Last week, the Capsule team shipped a valuable upgrade to the Capsule Protocol — the ability to attach an external “metadata provider” to Capsule Collections. What does this mean? How will the Capsule team utilize this? Read on.
Capsule Collections
First, let’s quickly review Capsule Collections: Capsule Collections are NFT collections generated by the Capsule Protocol. They provide methods that facilitate creation of Capsule NFTs, and offer additional layers of customization when compared to traditional NFT collections.
For more information on Capsule Collections, visit the CapsuleNFT gitbook.
Metadata Providers
Users have always been able to add metadata to Capsule Collections just like you would for any ERC-721 token — by attaching a link as the returned tokenURI. This is exactly how it works for nearly every single collection you see and may hold today.
The Capsule Protocol recently added a feature allowing a “metadata provider” to be assigned to a Capsule Collection. The addition of a metadata provider allows for a completely separate, user-defined contract to determine the metadata for an NFT collection — in a decentralized manner.
Imagine NFT Collections with dynamic metadata: those that could change their image and traits based upon the price of the NFT, the weather outside, or even by the address of the holder.
By creating a contract implementing the IMetadataProvider interface and attaching it to your Capsule collection by calling the setMetadataProvider function, you can introduce these potential use cases to your new Capsule Collections today.
interface IMetadataProvider {
function tokenURI(uint256 tokenId) external view returns (string memory);
}Conclusion
Shortly, the Capsule team will be releasing a revolutionary collection which not only showcases the power of token-storing, composable NFTs — but the power of a CapsuleNFT collection attached to a metadata provider. That is the power of innovation and choice: the power of the Capsule Protocol.
