Skip to content

Introduction to zkVerify Network course – Top 5 FAQs

zkVerify FAQ

Hey zkVerify learners, we hear you! To make your learning journey smoother, we’ve compiled the 5 most frequently asked questions for our Introduction to zkVerify Network course.

1. I accidentally submitted the wrong wallet address for my assignment. How can I resubmit the correct one?

If you’ve submitted an incorrect wallet address, please follow these steps:

Details you need to provide:

  • The old (incorrect) wallet address that was submitted
  • Correct wallet address

The support team will help you update your submission accordingly.

2. Should I submit my Talisman wallet address, and Metamask address, on Galxe for the quest?

For any galxe quest, you should submit your Metamask wallet address. This is the same wallet address connected with your Metaschool profile. Also, ensure that the email used to sign up for Metaschool and Galxe is the same.
For the Metamask Wallet, please ensure:

  • The address is an Ethereum (ETH) address
  • You have full access to this wallet
  • The wallet is properly connected to the Ethereum network
  • The same wallet is connected to Metaschool and Galxe

3. In which network should the NFT from Metaschool arrive?

The NFT from Metaschool will be delivered on the Polygon.
Please ensure:

  • Your wallet is configured to view Polygon network assets
  • You have the correct NFT contract address added to your wallet
  • You’re checking the correct wallet address where you completed the course requirements.

4. Should I submit my Polkadot zkVerify address or the ETH address I used to claim the faucet?

You should submit the Polkadot zkVerify address as we are using the Polkadot address to claim the test tokens.

5. I’m getting an error 

<code>"bash: path_to_verification_key.json: No such file or directory" when running the <strong>node snarkjs2zkv convert-vk <path_to_verification_key.json> -o verification_key_zkv.json</strong> </code>command.

This error occurs when the system cannot find the verification key file.
To resolve this:

  • Check the file location: Ensure you’re in the correct directory containing the verification key file
  • Verify the exact filename of your verification key
  • node snarkjs2zkv convert-vk ./verification_key.json -o verification_key_zkv.json
    Replace ./verification_key.json with the actual path to your verification key file
  • Common fixes:
    • Use the correct file path relative to your current directory
    • Check for typos in the filename
    • Ensure the verification key file exists and has the correct permissions