Summary

The studio pass is an ERC721 token that will be airdropped to a set of dedicated gm. studio collectors, allowing them access to exclusive studio content. This could for example consist of curated 1/1 pieces, supplementary material launched alongside studio collections, and additional technical features such as re-rolling tokens, etc.

A given pass will only be active, if they are placed within a wallet that also contains one token of each studio collection (bunch) per pass. Active tokens will have an additional tag in their metadata, and show a different image as compared to inactive ones.

Issuance

This is still in discussion.

Issuing tokens based on studio bunches (1 of each collection → 1 pass), we would end up with 57 passes.

We might choose to issue pieces again.

In any way, the token receivers will be identified off-chain, providing a list of receiving addresses.

Contract

Pass Collection

• Standard ERC721 (+ Enumerable for token activation logic)
• Owner mint to a list of receiving addresses
• Interface to check if a given token is active
  • Logic is upgradeable
  • This method will be called by outside redeemer contracts
• Tokens activate based on studio collection ownership
  • Fetches all collections from the gm studio code repo
• On-chain metadata rendering
  • Logic is upgradeable
  • Metadata entries: Active/Inactive, Last refreshed: timestamp
  • Points to different image hosted on IPFS depending on the activation
• Allow internal approval for claims

Redeemer

This depends heavily on the content that we want to provide, and must in most case be integrated with other contracts. E.g. in the case of token seed rerolling, the redeeming functionality must be implemented in the respective collection contract.

Each redeemer must fulfill the following feature (from a standardized interface):

• Check if the content was already claimed by a given pass