Collection Examples

To help illustrate how Capsule Collections work and their various customizable features, this page presents a few examples of how different Capsule Collections could be deployed.

Scenario A: Lockable, Private, User URI Owned Collection

Alice wants to create a fruit-based NFT collection, which contains artwork of different fruit. Alice doesn’t want anyone else to create NFTs in this collection, so she uses the Capsule Protocol to create a Capsule Collection and chooses the ‘private’ option on creation. She also passes in her own address as the URI Owner, meaning that she can change the attached metadata of any NFT in her collection at any time.

Once deployed, Alice mints some fruit as Simple Capsule NFTs, and others with a varying amount of wrapped Ethereum inside. For one Capsule NFT, she minted a banana NFT and stored it inside another apple NFT of the same collection, creating a sort of nesting doll situation.

After minting 10 fruit NFTs, Alice now decides to ensure the scarcity of her fruit-based Capsule Collection. She calls the ‘lock’ function with an upper bound of 10, which prohibits anyone (just herself in this case, since this was deemed a private collection) from minting any more NFTs to that collection. Existing NFTs are still redeemable for their underlying Capsule NFT value, but can never be created again.

At this point, Alice has created and fully customized her fruit-based Capsule Collection. While she can no longer add anymore NFTs to the collection, she may still choose to list her NFTs for sale on OpenSea. Alice can now sit back and watch her fruit NFTs be exchanged on the open market.

Scenario B: Lockable, Public, Zero Address URI Owned Collection

Bob decides to create a ‘community vault’ of sorts. He decides to create a public collection, where any user can mint.

Since it is a community vault, Bob wants to ensure that all users' metadata are immutably set. To do so, he uses the Capsule Protocol to create a Capsule Collection and passes the zero address (0x0000…) as the URI Owner. As a result, Bob or anyone else will never have the ability to alter any NFT metadata.

Since Bob knows beforehand how large he wants his collection to become, he calls the ‘lock’ method passing in 50 as the upper bound after deployment (he can do this before any NFT has even been minted). Once the collection mints its 50th NFT, it locks itself automatically - no one else may mint another NFT, not even Bob.

The functionality of these public Capsule NFTs remain the same - they are tradable and burnable by their respective owners. However, any holder may remain assured that Bob's collection will never grow in size - on the contrary - his collection size may only decrease from any Capsule NFTs being redeemed.

Last updated