2

In this transaction a metadata account is created in instruction 5.6. (Parsed instruction).

In the create metadata instruction from metaplex-metadata-program there is a loop over the creators array. A creator can only be verified if the creator's address is the updateAuthority address and if it signed the transaction (source-code).

But in the above transaction the first verified creator did not sign the transaction? How is that possible? Does it have to do something with the fact that the first verified creator is a pda, as per the metaplex candy guard instruction?

Improve this question

1 Answer 1

Reset to default
2

The metadata account is created with the first creator set to verified. (This is why you don't see a sign instruction).

Adding it as verified creator is possible since it (fXnX8Mj43U1TQoCSxQmgU5LXijqxcL7PCD9sL1nmhuM) is a PDA of your candy machine which is creating the account.

Improve this answer
1
  • But looking at the source of the assert_data_valid function it seems like it will end at this error line since allow_direct_creator_writes is false (line 76) and the updateAuthority is not the signer (line 83). Or does update_authority_info.is_signer evaluate to true?
    – Tomvkgames
    Dec 7, 2022 at 17:48

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge that you have read and understand our privacy policy and code of conduct.

Not the answer you're looking for? Browse other questions tagged or ask your own question.