Manage reveal strategy
You can use this Phosphor feature when you want to create a different experience for your users. Reveal Strategy allows you to create items without necessarily revealing what are the actual NFTs visual components (and metadata) that the end-user is acquiring. Read more below about the goals one can achieve with this feature.
The Phosphor platform offers two ways to implement a drop using a Reveal Strategy setting:
| Reveal Strategy | Result |
|---|---|
INSTANT | Creates a drop that immediately reveals NFT's artwork and metadata. |
DELAYED | Creates a drop that displays a collection's preview artwork and metadata, until a reveal is issued at some later time. |
Selecting a reveal strategy
During the setup process for a new collection, you'll have an option to select the Reveal Strategy. Once set, it cannot be changed.
INSTANT strategy
When an item is minted, the item's metadata is immediately shown to the end-user.
DELAYED strategy
Goals of DELAYED
- Empower Phosphor developers to create a drop without initially revealing its artwork and metadata.
- Mitigate a risk known in the industry as the "rarity snipe" - in which insiders and/or end-users can inspect the secret content of NFT before the reveal and engage in unfair trading.
How DELAYED works
After the initial collection is created, you'll will be prompted to create the collection's preview artwork and metadata. The collection preview metadata is shown on all NFTs under the collection until the reveal is triggered, at which point, the platform:
- Randomly assigns all the NFTs its final artwork and metadata
- Makes the token data immutable
- Reveals the final artwork and metadata through
/metadata/{collection_id}/{token_id}endpoint - Notifies the smart contract of the metadata change, which in turn, causes the contract to emit an event
BaseURIUpdated()
Manage delayed reveal
During the setup process for a new collection, you’ll set reveal_strategy to DELAYED and add your preview_metadata for the collection preview display.
Both reveal strategies work with our FlexibleERC721, FlexibleERC1155, and SignatureERC721 platform contracts or your own custom smart contract that uses [capabilities]: SET_BASE_URI_PERMANENT and SET_BASE_URI. :::
After the initial collection is created, you’ll need to: