-
Notifications
You must be signed in to change notification settings - Fork 69
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
IncorrectOwner: Incorrect account owner #73
Comments
Program Logs: |
Same issue found any fix? Been struggling with this for 2 days. Thank in advance |
The document is incorrect,I adopted another approach. Create tokens using "@solana/spl-token" and upload metadata using @metaplex-foundation/mpl-token-metadata CreateMetadataAccountV3InstructionAccounts |
Still trying to figure this ut still. This is what I have, I have gone with your method of spl-tokens but still having quite a hard time: This is m code: `** import { createUmi } from '@metaplex-foundation/umi-bundle-defaults' let secretKey = bs58.decode(process.env.SECRET_KEY!) const umi = createUmi('https://api.devnet.solana.com').use(mplTokenMetadata()) const connection = new Connection(clusterApiUrl('devnet'), 'confirmed'); const authorityKeyPair = umi.eddsa.createKeypairFromSecretKey(secretKey); const createToken = async()=>{ const fromAirdropSignature = await connection.requestAirdrop(fromWallet.publicKey, LAMPORTS_PER_SOL); // Get the token account of the fromWallet address, and if it does not exist, create it // const UploadMetadata = async()=>{ const getIrys = async () => {
}; const fundNode = async () => { const uploadFile = async () => {
}; async function mintToken() { // const CreateAccount = async()=>{ // console.log(mintAccount.result) const CreateAccount = async()=>{
} const MintTokens = async () => {
await mintV1(umi, { }; MintTokens().catch(console.error); **` |
I'm not sure if it's the case here, but sometimes this error happens if you are trying to use Token-2022 and not specifically deriving the token account with that program id and passing it in. |
I had this problem too. Just retried 4 times and it worked randomly. |
I also retried 4 times and it worked randomly. I don't know why |
I have this problem too. What about using createFungible helper method? |
hey all! I had the same issue, shout out to @MarkSackerberg from Metaplex for solving it: // See https://developers.metaplex.com/token-metadata/collections
await verifyCollectionV1(umi, {
// The metadata PDA for the NFT we want to verify inside the collection.
metadata: findMetadataPda(umi, { mint: publicKey(nftAddress) }),
// The Collection NFT that is already set on the Metadata account of the NFT but not yet verified.
collectionMint: publicKey(collectionAddress),
// The Update Authority of the Collection NFT as a signer, in this case the umiKeypair
authority: umi.identity,
}).sendAndConfirm(umi);
console.log(`Collection verified!`); |
The text was updated successfully, but these errors were encountered: