feat: Add Verifier Server

[Bisht13]

feat: Add ProveKit Verifier Server

Overview

HTTP server that combines Rust (API) + Go (verifier binary) for WHIR-based proof verification.

Architecture

• Rust HTTP Server: Handles requests, downloads artifacts, orchestrates verification
• Go Verifier Binary: Performs WHIR proof verification using gnark

Key Features

• RESTful API: GET /health, POST /verify
• Artifact Caching: Downloads cached by URL hash
• Docker Support: Multi-stage build, docker-compose ready
• Config Management: Environment variables for deployment
• Service Architecture: Modular artifact/verification services
• Structured Logging: Comprehensive tracing and monitoring

API

# Health check
curl http://localhost:3000/health

# Verify proof
curl -X POST http://localhost:3000/verify \
  -H "Content-Type: application/json" \
  -d '{"npsUrl": "...", "r1csUrl": "...", "pkUrl": "...", "vkUrl": "...", "np": {...}}'

Deployment

# Docker (recommended)
cd tooling/verifier-server
docker-compose up --build

# Local development
cargo run --bin verifier-server

Environment Variables

• VERIFIER_HOST, VERIFIER_PORT - Server binding
• VERIFIER_BINARY_PATH - Go verifier path
• VERIFIER_ARTIFACTS_DIR - Cache directory
• VERIFIER_REQUEST_TIMEOUT - Request timeout

Dependencies

Added: chrono, reqwest, sha2, tokio, tower, tower-http

[codspeed-hq]

CodSpeed WallTime Performance Report

Merging #173 will not alter performance

_{Comparing px/verifier-server (fd0a512) with main (9a1f428)}

⚠️ Unknown Walltime execution environment detected

Using the Walltime instrument on standard Hosted Runners will lead to inconsistent data.

For the most accurate results, we recommend using CodSpeed Macro Runners: bare-metal machines fine-tuned for performance measurement consistency.

Summary

✅ 35 untouched

[piohei]

It would be nice to clear cache from time to time. :) It could be control by standard HTTP headers link.

[ashpect]

lgtm