Skip to main content

Troubleshooting

Common problems and solutions when requesting proofs on the Succinct Network.

Insufficient Funds​

When requesting proofs, you may encounter errors related to insufficient funds. This happens when your account doesn't have enough balance to pay for the proof generation.

Error: Insufficient funds for proof request

Solution:

  1. Check your balance in the Explorer
  2. If it's too low, deposit more $PROVE to your account using the Account UI. If your network balance is not too low, contact the Succinct team for assistance.
  3. Wait for the deposit transaction to complete before retrying

Invalid Private Key​

If you see an error about an invalid private key, ensure that:

  • Your private key is properly formatted (starts with "0x" and is 64 characters long)
  • The environment variable is correctly set: export NETWORK_PRIVATE_KEY=0x...
  • The account associated with this private key has funds

Network Connection Issues​

If you encounter RPC connection errors:

Error: Failed to connect to RPC endpoint

Try the following:

  1. Verify your internet connection
  2. Ensure the NETWORK_RPC_URL is correct
  3. Check if the Succinct Network status page reports any outages
  4. Try using a different RPC endpoint if available

Program Registration Failures​

When registering your program, you might see:

Error: Failed to register program

Common causes include:

  • Invalid ELF binary format
  • Program size exceeds limits
  • Network connectivity issues
  • Insufficient funds for registration

Try rebuilding your project with cargo clean && cargo build --release before retrying.

No Reservation Found​

If you see an error like:

no reservation found for requester (The caller does not have permission to execute the specified operation)

This means you are trying to use reserved capacity but your account does not have a corresponding reservation.

  • Ensure you're using the correct private key
  • Ensure Succinct has setup a reservation for your account
  • Confirm with Succinct that your account is supposed to be using the Reserved strategy (.prove().strategy(FulfillmentStrategy::Reserved))