For Seekers

Seekers are participants who submit workflow-based proof requests to the Fermah network. Our universal proof generation layer enables you to generate proofs for any supported system through a unified, developer-friendly interface.

System Requirements

Base Configuration

• JSON-RPC compatible client
• 2GB RAM minimum
• 10GB storage for proof data

Architecture Overview

Identity and Authentication

Seekers are authenticated using ECDSA key pairs:

• Public keys serve as requester addresses
• Private keys sign proof requests
• Keys must be whitelisted

Network Interaction

Getting Started

1. Install Fermah Seek CLI

   • Follow our installation guide
   • Verify installation with fermah-seek --version

2. Set Up Authentication

   • Generate your ECDSA keypair using key management
   • Submit your public key for whitelisting
   • Store your private key securely

3. Configure Your Environment

   • Create your configuration file
   • Set up Docker for proof images
   • Configure network endpoints

4. Submit Your First Proof

   • Follow the proof submission guide
   • Monitor status using status checking
   • Review results and verification

Workflow-Based Proof Generation

# Compile your workflow
fermah-cli workflow compile <workflow-path>

# Submit workflow
fermah-cli workflow submit <workflow-id>

# Monitor status
fermah-cli workflow status <request-id>

Creating Your Workflow

• Start with our provided workflow templates
• Customize the template configuration based on your needs
• Compile your workflow into WASM using the CLI

Workflow Execution

1. Submit your compiled workflow to Fermah Core
2. Core validates and stores your workflow
3. Trigger execution through the CLI
4. Monitor status and retrieve results

Advanced Features

Universal Proof System Support

Fermah supports multiple proof systems through a unified interface, allowing you to generate proofs for any supported system without changing your workflow structure.

Confidential Proof Delegation (Optional)

For sensitive computations, you can enable Confidential Proof Delegation which:

• Protects input data using secure multi-party computation (MPC)
• Splits input data across multiple MPC servers
• Ensures data privacy during proof generation
• Maintains information-theoretic security below compromise threshold

Resource Allocation

The system automatically:

• Matches your proof request with appropriate Prover Nodes
• Optimizes for cost and performance
• Ensures fair pricing through dynamic matchmaking

Common Use Cases

Network Status

• Testnet: Active (Permissioned)
• Testnet: Coming Soon
• Mainnet: In Development

Security Considerations

• Keep private keys secure
• Validate proof results
• Monitor request status
• Follow rate limiting guidelines

Support

For technical support:

• Join our Discord
• Email: support@fermah.xyz

Troubleshooting

Common issues and their solutions:

For detailed workflow specifications, compilation instructions, and gas estimation, see our Workflow Guide.