Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature]: "Editions" with no metadata #1006

Open
Babaonchain opened this issue Feb 3, 2023 · 0 comments
Open

[Feature]: "Editions" with no metadata #1006

Babaonchain opened this issue Feb 3, 2023 · 0 comments
Labels
enhancement New feature or request

Comments

@Babaonchain
Copy link

Babaonchain commented Feb 3, 2023

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant