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
Currently in both cm v2 and v3, the mint instruction always invokes the create_metadata_accounts_v2 with the Option<Uses> argument set to None. Would be great if you could (e.g. in cm v3) add a uses: Option<Uses> variable to the CandyMachine struct that would initialize all minted NFT metadata accounts with that same uses variable.
Even better would be to add an optional UseAuthority public key (or even a vector, but for my usecase, a single Use Authority Record Account is enough) to the CandyMachine struct that would get approved on mint.
Standard Change?
No
The text was updated successfully, but these errors were encountered:
Which package is this feature request for?
candy-machine
Feature
Currently in both cm v2 and v3, the mint instruction always invokes the
create_metadata_accounts_v2
with theOption<Uses>
argument set toNone
. Would be great if you could (e.g. in cm v3) add auses: Option<Uses>
variable to theCandyMachine
struct that would initialize all minted NFT metadata accounts with that sameuses
variable.Even better would be to add an optional UseAuthority public key (or even a vector, but for my usecase, a single Use Authority Record Account is enough) to the
CandyMachine
struct that would get approved on mint.Standard Change?
No
The text was updated successfully, but these errors were encountered: