-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
verify failed #3289
Comments
I also tried the demo project in Solana tutorial(https://github.com/Unboxed-Software/anchor-counter-program.git), executing
|
To make the builds reproducable, set both Anchor and Solana versions (change it to whatever you used to build and deploy) [toolchain]
anchor_version = "0.30.1"
solana_version = "1.18.17" Add anchor build --verifiable && anchor deploy --verifiable Also worth noting that the Solana explorer currently uses Osec API to manage program verifications. You can find more information here. |
I have seen this warehouse, but its description is very confusing and complex. So I prefer to use simple instructions in the anchor. |
Although it was successful, the verification was not displayed as successful in the browser. |
I don't understand the difference between |
|
I think the version should be fine |
If entering the |
I want to give up, it's really puzzling. |
I deployed to devnet. It has been successfully deployed. https://explorer.solana.com/address/CirTw1apKgQHSveAvpMp3P283Z54XzJWTBy1LHVLz7E9?cluster=devnet
I haven't made any changes to the code.
I closed the previous program ID and rebuilt and deployed a new program ID.
I tried to re verify, but unfortunately.
anchor verify CirTw1apKgQHSveAvpMp3P283Z54XzJWTBy1LHVLz7E9 --skip-build
When I tried to verify again, it turned into various error. I have never even seen this pubkey before. I don't know which account it's referring to
The text was updated successfully, but these errors were encountered: