Closed k666-bit closed 2 years ago
Can you provide the full command you're running so I can try to duplicate the issue?
Can you provide the full command you're running so I can try to duplicate the issue?
metaboss -r https://ssc-dao.genesysgo.net snapshot holders --candy-machine-id EUXHWUyfFSXYuvei9oQxsVZ27H9iQN9WU1wKdwvRR3pP --v2
metaboss -r https://ssc-dao.genesysgo.net snapshot holders --update-authority God1GnHPzNrhWrbPTcv41YJAkra5GKQbqJkZuJeqkatZ --v2
EUXHWUyfFSXYuvei9oQxsVZ27H9iQN9WU1wKdwvRR3pP
doesn't look like it's actually a candy machine id: https://solscan.io/account/EUXHWUyfFSXYuvei9oQxsVZ27H9iQN9WU1wKdwvRR3pP
metaboss -r https://ssc-dao.genesysgo.net/ snapshot holders --update-authority God1GnHPzNrhWrbPTcv41YJAkra5GKQbqJkZuJeqkatZ --v2
The --v2
flag is only for candy machine ids, not update authority.
EUXHWUyfFSXYuvei9oQxsVZ27H9iQN9WU1wKdwvRR3pP
doesn't look like it's actually a candy machine id: https://solscan.io/account/EUXHWUyfFSXYuvei9oQxsVZ27H9iQN9WU1wKdwvRR3pPmetaboss -r https://ssc-dao.genesysgo.net/ snapshot holders --update-authority God1GnHPzNrhWrbPTcv41YJAkra5GKQbqJkZuJeqkatZ --v2
The
--v2
flag is only for candy machine ids, not update authority.
I'm confused. That is the candy machine ID.
{"program":{"uuid":"EUXHWU","candyMachine":"EUXHWUyfFSXYuvei9oQxsVZ27H9iQN9WU1wKdwvRR3pP"}
I've been successfully snapshotting holders until today with the first command and it always worked correctly
EUXHWUyfFSXYuvei9oQxsVZ27H9iQN9WU1wKdwvRR3pP
Yeah, that's my bad, it is a candy machine ID. It wasn't showing up earlier when I looked it up. Not sure if I was doing something wrong or what was going on. I just tried the command on a different RPC and it worked so looks like the issue is with the GeneSysGo node and their new rate-limits. The error message is misleading, so I need to fix that. I'll have to research later why my rate limits aren't sufficient for their node.
Edit: I figured it out and am fixing in 0.4.1. You'll be able to use the GeneSysGo node but it will be significantly slower than you are used to due to the rate-limiting, just FYI.
Curious if this would have anything to do with this error I'm getting today?
@k666-bit update metaboss to 0.4.1 and it should work now
Curious if this would have anything to do with this error I'm getting today?
It says can't find key file
so make sure you're giving it the correct path to your key.
Curious if this would have anything to do with this error I'm getting today?
It says
can't find key file
so make sure you're giving it the correct path to your key.
Yes, got that part just had to double check docs. It successfully ran, but returned No unverified metadata for this creator and candy machine. Done!
. When I go to check my creator address for the NFT in Solscan, it still reads as unverified even 15 minutes later. Any ideas?
Sorry if this isn't the best place to ask this question!
Curious if this would have anything to do with this error I'm getting today?
It says
can't find key file
so make sure you're giving it the correct path to your key.Yes, got that part just had to double check docs. It successfully ran, but returned
No unverified metadata for this creator and candy machine. Done!
. When I go to check my creator address for the NFT in Solscan, it still reads as unverified even 15 minutes later. Any ideas?Sorry if this isn't the best place to ask this question!
Is your creator address the same one as the keypair?
It's not, how would that happen? I definitely didn't change it at any point somehow.
It's not, how would that happen? I definitely didn't change it at any point somehow.
You can only sign a creator with the creator keypair.
I'll do another full run through with a brand new candy machine on devnet and make sure I mark everything down this time. Thanks for answering my questions.
@k666-bit update metaboss to 0.4.1 and it should work now
This has fixed it :)
Thank you!
It's not, how would that happen? I definitely didn't change it at any point somehow.
You can only sign a creator with the creator keypair.
I figured it out awhile ago.... you were right! When I generated the art, I forgot to change my creator address to my new address. That's why we always do multiple devnet tests folks ;)
Thanks for following up so I can close the issue! I appreciate it.
Hi!
I just started getting this error today, whereas yesterday was working fine. Doesn't matter if you use the CMID or Update Authority
Any ideas? This happens for ALL accounts.