You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On every edition mint, a new metadata account is created. This account is a copy of the same information from the master token’s metadata account.
Issues with the Current Flow
Wasteful
A collection with 10k editions creates 10k identical Metadata accounts, bloating the chain with 10,000 copies of the same data.
Expensive
The metadata account holds around 706 bytes. This requires around .006 SOL in rent, which represents about 50% of the mint cost. Eliminating this account would drop the cost of a mint in half.
Complex
Updating the metadata for an NFT with editions requires updating every single token in the collection.
Standard Change?
No
Ideal solution or implementation
Each “Edition” token has a reference to the “parent” (the “Master Edition”.) This should provide a path for obtaining the Metadata information from the master token (meaning the Edition Token can be omitted entirely).
This should reduce waste, reduce mint cost by 50%, and decrease complexity (the token metadata can be updated in one place).
Implementation might be as easy as skipping the line of code which creates the token metadata in this case.
Hurdles
Client Updates
Clients will need to update their code to support this new protocol.
Fraud Prevention
The system must prevent a malicious user from creating an “Edition” who’s “parent” points to a master Token they do not own.
The Token Metadata program should enforce this is not possible (probably already does).
Alternative solutions or implementations
No response
Other context
No response
The text was updated successfully, but these errors were encountered:
Which package is this feature request for?
Candy machine
Feature
Current “Edition” Flow
On every edition mint, a new metadata account is created. This account is a copy of the same information from the master token’s metadata account.
Issues with the Current Flow
Wasteful
A collection with 10k editions creates 10k identical Metadata accounts, bloating the chain with 10,000 copies of the same data.
Expensive
The metadata account holds around 706 bytes. This requires around .006 SOL in rent, which represents about 50% of the mint cost. Eliminating this account would drop the cost of a mint in half.
Complex
Updating the metadata for an NFT with editions requires updating every single token in the collection.
Standard Change?
No
Ideal solution or implementation
Each “Edition” token has a reference to the “parent” (the “Master Edition”.) This should provide a path for obtaining the Metadata information from the master token (meaning the Edition Token can be omitted entirely).
This should reduce waste, reduce mint cost by 50%, and decrease complexity (the token metadata can be updated in one place).
Implementation might be as easy as skipping the line of code which creates the token metadata in this case.
Hurdles
Client Updates
Clients will need to update their code to support this new protocol.
Fraud Prevention
The system must prevent a malicious user from creating an “Edition” who’s “parent” points to a master Token they do not own.
The Token Metadata program should enforce this is not possible (probably already does).
Alternative solutions or implementations
No response
Other context
No response
The text was updated successfully, but these errors were encountered: