Anchor Verification Issue: Rustc Version Mismatch in Docker
Summary
A recent issue has been reported by users attempting to verify their Anchor accounts using the «anchor verify» command. The issue lies in the fact that this command requires access to a working Rust compiler, specifically version 1.75.0 or later. However, one user has discovered that they have an older version of Rustc installed on their system, which is causing the program to fail to build.
Issue
The anchor command «anchor verify» is used to validate and verify the authenticity of the anchor address received. To use this command, you must ensure that a working Rust compiler is available. The issue occurs when you try to build the «anchor verify» program using the built-in Rust compiler installed on your system.
Code
The code for the «anchor verify» program is as follows:
use anchor_lang::prelude::*;
#[program]
pub fn anchor_verify(
_owner: Id,
accounts: accounts<'_>,
) -> Result<()> {
//...
}
This code snippet shows the basic structure of a Rust function. It defines an Anchor program with a single function «anchor_verify» that takes multiple parameters.
User Solution
One user reported that they encountered this issue when trying to create and run the «anchor verify» command:
anchor verify 3MRKmmRZ6Fm4tvEEjBZcuGG7nxWVSYCJd83WzmAGqm8J
When they ran this command, they encountered an error message stating that their Rust compiler was incompatible with the required version.
Solution
To resolve this issue, the user installed a newer version of Rust (1.82.0) on their system, which allows them to build and run the «anchor-verify» program without causing compatibility issues:
rustc 1.82.0 -o anchor-verify --edition=2018
When installing Rustc on an older version (version 1.75.0), the user was unable to build and run the «anchor-verify» program, resulting in a failure with the given command.
Conclusion
This issue highlights the importance of having access to a working Rust compiler when attempting to verify anchor accounts using the «anchor-verify» command. Users can resolve this issue by upgrading their Rust version to a compatible installation (e.g. 1.82.0).