MintAccount can't be found

Question

I want to create an NFT using the Metaplex SDK with react. But when i execute this function, it throws following error:

AccountNotFoundError: 
The account of type [MintAccount] was not found at the provided address 
[7SYH47nGcK5fnMmf6zoW75BWpdxDAyq8DBRbagMdsPKJ].

This is the function i'm trying to execute:

  async function mint() {
    const links = await uploadMetadata();
    console.log("Cover: " + links.cover);
    console.log("Text: " + links.text);
    console.log("Metadata: " + links.metadata);
    const { nft } = await metaplex.nfts().create({
      uri: links.metadata,
      name: title,
      sellerFeeBasisPoints: 500, // Represents 5.00%.
    });
    console.log(nft);
  }```

@FerhatMousavi probably because he's writing software that does many things beyond just creating NFTs. — mikemaccana, Dec 30 '22 at 23:39

Jimii · Accepted Answer · 2022-12-30T15:30:25.057

7

This is a metaplex SDK error.

The issues is that metaplex sdk is trying to read after writing to solana. The issues with that is obviously that the changes have yet to be propagated throughout the chain.

To fix this add the optional commitment argument { commitment: "finalized" }

Your code will now look like this


async function mint() {
    const links = await uploadMetadata();
    console.log("Cover: " + links.cover);
    console.log("Text: " + links.text);
    console.log("Metadata: " + links.metadata);
    const { nft } = await metaplex.nfts().create(
        {
            uri: links.metadata,
            name: title,
            sellerFeeBasisPoints: 500, // Represents 5.00%.
        },
        { commitment: "finalized" }
    );
    console.log(nft);
}

edited Dec 30 '22 at 15:30

answered Dec 30 '22 at 15:12

Jimii

294
2
5

6

I did add `{commitment: "finalized"}`, but still got same error. – Alchemist Feb 01 '23 at 01:18
could you share the code for this? – Jimii Feb 03 '23 at 08:52
I am also getting the same issue even after adding {commitment: "finalized"} @Jimmy . Has anyone able to resolve this ? – user2179059 Mar 03 '23 at 10:28

score 2 · Answer 2 · edited Apr 04 '23 at 12:16

The way I "solved" this was to not use the methods like nfts().create({}) directly; instead, use them with the transaction builder module.

So this example would look like this:

const createNftBuilder = await metaplex.nfts().builders().create({
  uri: links.metadata,
  name: title,
  sellerFeeBasisPoints: 500, // Represents 5.00%.
});

// Get the data that you don't know in advance from getContext()
const { mintAddress } = transactionBuilder.getContext();

// Submit the tx
await metaplex
    .rpc()
    .sendAndConfirmTransaction(createNftBuilder, { commitment: "confirmed" });

This way, the SDK doesn't try to fetch the on-chain data too early. The problem is that you end up writing a lot more code and you can't get the nft object in the same way as above.

score 0 · Answer 3 · answered Jun 06 '23 at 21:06

This worked for me:

const transactionBuilder = await metaplex.nfts().builders().create({ ... });
const { mintAddress } = transactionBuilder.getContext();
await metaplex.rpc().sendAndConfirmTransaction(transactionBuilder);

// Then, optionally fetch the NFT afterwards after sleeping for 2 seconds. 
await new Promise(resolve => setTimeout(resolve, 2000))
const nft = await metaplex.nfts().findByMint({ mintAddress });

From https://github.com/metaplex-foundation/js/issues/344#issuecomment-1325265657

MintAccount can't be found

3 Answers3