Shared Prover
Shared proof-generation infrastructure for supported Layer 2 systems, with proof-system compatibility, capacity, privacy, operations, support, and commercial terms defined for each deployment.
- What it is
- Proof-generation service
- Current posture
- Available for supported proof systems
- What varies
- Architecture, providers, operating scope, and commitments
Proof demand changes. Dedicated operating burden does not.
Rollups can face uneven proving demand, specialised hardware, software-version dependencies, queueing, privacy requirements, and operational failure modes. Shared Prover makes capacity and responsibility a scoped service decision.
Keep the core authoritative.
- Rollup workload
- Proof requirements
- Operating policy
Change the capability at a controlled boundary.
Shared Prover changes the boundary, not the institution’s authority.
Capacity follows the workload
Scope shared or reserved proving capacity around supported proof systems and expected demand.
Dependencies become visible
Document software versions, hardware, queues, data handling, verification, and fallback assumptions.
Operations become contractual
Define monitoring, escalation, support, availability, privacy, and commercial terms in the service envelope.
What Shared Prover contributes. What still needs a decision.
Proof-system support
Confirm current software, version, input, output, and verification compatibility before integration.
Capacity model
Scope shared, burst, or reserved capacity and queue behaviour for the expected workload.
Integration API
Connect proof submission, status, retrieval, verification, retry, and failure workflows.
Data boundary
Document submitted data, logs, storage, access, retention, and privacy assumptions.
Operational telemetry
Review available queue, latency, error, capacity, and service-health evidence.
Service envelope
Define support, availability, response, capacity, commercial, and exit terms in the applicable agreement.
Continue from Shared Prover into the operating model.
Bring the requirement. Define the Shared Prover boundary.
A focused workshop maps the target capability, existing systems, providers, controls, and deployment variables.