Proof Submission

Prerequisites

Before submitting a proof request, ensure you have:

• Installed Fermah Seek CLI (see Installation)
• Created your configuration file (see Configuration)
• Set up your ECDSA key (see Keys)

Basic Submission

Submit a Groth16 proof request:

CONFIG=groth16
KEY=ecdsa.seeker

fermah-seek proof send -k dev -n $CONFIG --key $KEY

Note: This assumes the configuration and key files are present in the ~/.fermah/config/Testnet directory.

After Submission

After sending a proof request:

1. Note the generated Proof ID
2. Use this ID to check proof status (see Status)

Valid for Testnet only.

Advanced Options

# Submit with custom parameters
fermah-seek proof send \
  --network dev \
  --config $CONFIG \
  --key $KEY \
  --timeout 3600 \
  --priority high \
  --callback "https://api.example.com/callback"

Request Lifecycle

1. Request submission
2. Configuration validation
3. Operator assignment
4. Proof generation
5. Result verification
6. Status update

Monitoring

After submission, you'll receive a Proof ID. Use this to:

• Check status (see Status Checking)
• Monitor progress
• Retrieve results

Error Handling

Common error codes:

• INVALID_CONFIG: Configuration validation failed
• INSUFFICIENT_BALANCE: Not enough funds
• NETWORK_ERROR: Network connectivity issues
• TIMEOUT: Request exceeded deadline