Polynomial Multiproofs: Multi-Claim Verification
- Polynomial Multiproofs (PMP) are proof systems that aggregate multiple claims into one concise verification protocol, with applications in quantum complexity, batch evaluation, and blockchain data availability.
- A key insight is that PMP constructions compress many outputs into a single univariate polynomial proof, reducing verification complexity and lowering computational and communication overhead.
- The research highlights trade-offs and open questions regarding soundness, proof-length efficiency, and the potential for multiprover advantages across diverse application domains.
Searching arXiv for recent and foundational papers on “Polynomial Multiproofs” and closely related usages. Polynomial Multiproofs (PMP) is a term used in several technically distinct lines of research to denote proof-system constructions that handle multiple claims in a single formal framework. In one usage, PMP refers to the landscape of quantum Merlin–Arthur variants with polynomially many unentangled proofs, as studied under the heading of “polynomially many provers” and summarized as “QMA variants with polynomially many Merlins” (Gharibian et al., 2011). In a second usage, PMP denotes a non-interactive Merlin–Arthur proof for batch evaluation of an arithmetic circuit on many inputs, where a single univariate polynomial “sketch” certifies evaluations at once (Williams, 2016). In a third usage, PMP designates aggregated polynomial-opening proofs for Kate–Zaverucha–Goldberg commitments in blockchain light clients, where multiple sampled cell evaluations are verified using a single aggregated proof over a shared evaluation micro-domain (Srivastava et al., 17 Apr 2026). The common theme is multiplicity: many witnesses, many evaluation claims, or many data-availability samples are compressed into a verifier-efficient proof structure.
1. Terminological scope and research contexts
The term does not denote a single universally standardized primitive. Rather, the arXiv literature represented here uses it in at least three settings: complexity theory of unentangled quantum proofs, Merlin–Arthur proofs for multipoint arithmetic circuit evaluation, and polynomial-commitment aggregation for data availability sampling (Gharibian et al., 2011, Williams, 2016, Srivastava et al., 17 Apr 2026).
In the quantum-complexity setting, the central object is the class , where a verifier receives polynomially many unentangled quantum proofs. The terminology “polynomial multiproofs” is used to organize subclasses such as , , and , together with collapse and repetition theorems that delimit their expressive power (Gharibian et al., 2011).
In the batch-evaluation setting, PMP is explicitly formulated as a one-message protocol for Multipoint Arithmetic Circuit Evaluation. Merlin sends a proof string of length , and Arthur verifies all claimed evaluations in time with soundness error at most (Williams, 2016). Here “multiproof” means that one proof string certifies many outputs.
In the blockchain setting, PMP is a mechanism for reducing the cost of attaching one proof to each sampled cell in data availability sampling. The construction replaces many independent KZG openings by one aggregated proof 0 over a shared micro-domain, with the stated goal of lowering proof bytes, verifier CPU and memory usage, and deployment-level infrastructure cost (Srivastava et al., 17 Apr 2026).
A common misconception is that PMP always refers to cryptographic polynomial-opening aggregation. The literature here shows that the same phrase also names a complexity-theoretic program around polynomially many Merlins and an unconditional MA proof system for batch evaluation. This suggests that the most precise interpretation of PMP is context-dependent rather than canonical.
2. Polynomially many quantum proofs
The quantum-complexity formulation begins with promise problems 1 and completeness–soundness parameters 2 such that 3. For functions 4, a promise problem lies in 5 if there is a uniform family of quantum circuits 6 such that 7 takes input 8 together with 9 unentangled quantum proofs 0, each on 1 qubits, and satisfies the usual completeness and soundness conditions. Writing 2, one has 3 (Gharibian et al., 2011).
Several subclasses are singled out. 4 (also called 5) replaces the quantum witness by a single classical string 6. 7 restricts each of the polynomially many proofs to length 8 qubits. 9 is defined by a verifier that first performs local, nonadaptive POVMs 0, one per proof register, obtaining classical outcomes 1, and then runs an efficient quantum circuit on 2. 3 is the subclass in which the verifier’s accept-POVM element 4 is fully separable across the 5 proof registers (Gharibian et al., 2011).
Three structural theorems organize this PMP landscape. First, 6. The proof sketch states that a classical proof can be embedded bitwise into one-qubit states, while in the reverse direction a classical witness can describe each 7-qubit state to inverse-exponential precision, after which the verifier uses Solovay–Kitaev to prepare the states and relies on trace-norm continuity to preserve the 8 completeness–soundness gap (Gharibian et al., 2011). The key continuity lemma is
9
Second, for polynomially bounded 0 and 1, 2, and since 3, one concludes 4. The stated simulation uses a single-prover QMA witness composed of a classical consistency-check register 5, encoding the alleged measurement distributions 6, together with a quantum register 7 holding polynomially many copies of each original proof 8. The verifier measures 9 in the computational basis, checks normalization, performs random local checks against the empirical frequencies in 0 using a Chernoff bound, and then simulates Stage 2 of the original BellQMA protocol (Gharibian et al., 2011).
Third, 1 satisfies perfect parallel repetition: if a protocol has accept-probability 2, then its 3-fold parallel repetition has acceptance probability exactly 4, even if the proofs across the 5 copies are globally entangled. The argument is presented via cone programming duality. The primal optimization is
6
with dual
7
The proof uses strong duality and the tensor-product closure property
8
to show multiplicativity of the optimum under repetition (Gharibian et al., 2011).
The complexity-theoretic significance is stated explicitly: short quantum proofs collapse to the classical-proof class 9; Bell-style local unentangled measurements with polynomially many outcomes do not exceed 0; and separable-accept protocols admit exact multiplicative repetition (Gharibian et al., 2011). A plausible implication is that any genuine multiprover advantage inside 1 must lie outside these natural subclasses.
3. Non-interactive batch-evaluation PMP
In the Merlin–Arthur setting, PMP is formulated for Multipoint Arithmetic Circuit Evaluation. Let 2 be a finite field, let
3
be an arithmetic circuit of size 4 and total degree at most 5, and let 6. The main theorem states that there is a one-message protocol in which Merlin sends a proof string of length 7, Arthur tosses 8 coins, runs in time 9, and outputs the vector 0 with completeness 1 and soundness error at most 2 (Williams, 2016).
The prover’s construction begins by choosing an extension field 3, where
4
A set 5 of size 6 is fixed and put in bijection with the evaluation points 7, written 8. For each coordinate 9, Merlin interpolates a univariate polynomial 0 of degree at most 1 such that 2. He then defines
3
Because 4 and each 5 has degree at most 6, the resulting degree bound is 7, and by construction 8 for all 9. Merlin sends the coefficient vector of a polynomial
0
claimed to equal 1, so the proof string is
2
This is why the protocol is characterized as a non-interactive PMP: a single polynomial of degree 3 certifies 4 output claims at once (Williams, 2016).
Arthur reconstructs the extension field, recomputes the interpolants 5, samples a random 6, evaluates 7 by Horner’s method, evaluates 8, and rejects if the two values differ. If the test passes, Arthur outputs 9 by fast multipoint evaluation. Soundness follows from polynomial identity testing: if 00, then 01, so
02
The cost breakdown listed for verification is: interpolating 03 in 04, evaluating the 05 in 06, evaluating the circuit in 07, Horner evaluation of 08 in 09, and multipoint evaluation in 10, yielding overall 11 (Williams, 2016).
The authors contrast this PMP with several prior directions: classical multipoint evaluation algorithms for restricted circuit classes, multi-round sum-check interactive proofs, Aaronson–Wigderson protocols for inner products, and cryptographic verifiable computation using heavy PCP machinery or cryptographic assumptions. The stated distinguishing features are that the protocol is unconditionally secure, one-round, applies to all low-degree arithmetic circuits, and attains proof length 12 with verification time 13 (Williams, 2016).
The same framework is then applied to the Permanent, 14Circuit-SAT, counting Hamiltonian cycles, orthogonal vectors, Hamming nearest neighbors, and 15-cliques, using standard arithmetization or inclusion–exclusion reductions spelled out in the source summary (Williams, 2016). This suggests that, in this usage, PMP functions less as a standalone cryptographic primitive than as a general-purpose certification method for batch algebraic computation.
4. KZG-based polynomial multiproofs for data availability sampling
In blockchain light clients, PMP is studied as an optimization for data availability sampling based on Kate–Zaverucha–Goldberg polynomial commitments. The underlying KZG commitment scheme is specified by an SRS generated from a secret 16, publishing
17
For a polynomial 18 of degree at most 19, the commitment is
20
A single-point opening at 21 with claimed value 22 uses witness polynomial
23
proof 24, and verification equation
25
These details provide the baseline against which PMP is introduced (Srivastava et al., 17 Apr 2026).
The stated bottleneck is that in data availability sampling, a client samples 26 random cells from an erasure-coded 27 grid to gain at least 28 assurance that the full block is available, and modern schemes attach one KZG proof per sampled cell. If 29–30, this yields 31–32 independent proofs per block, with costs summarized as bandwidth and storage 33 bytes34, verification cost 35 pairings and scalar multiplications, and DHT object explosion from many small objects (Srivastava et al., 17 Apr 2026).
The PMP construction aggregates multiple opening claims 36 into a single proof 37. In the random-linear-combination approach, a challenge
38
is derived via Fiat–Shamir, and the aggregate witness polynomial is defined as
39
The aggregated proof is
40
The description then gives a corresponding aggregated verification equation and notes an equivalent derivation using bilinearity and linearity of exponents (Srivastava et al., 17 Apr 2026).
For data availability sampling, the critical specialization is the evaluation micro-domain 41, a small subset of row or column positions. Its vanishing polynomial is
42
Under the “shared-point specialization (Boneh et al. first scheme),” all openings use 43, causing the denominators to collapse to 44. If 45 interpolates the 46 evaluations of 47 in block 48 over 49, then the specialized witness is
50
The source emphasizes that this avoids per-row interpolation at the prover: compute a weighted sum of commitments minus weighted evaluations, then divide once by 51 (Srivastava et al., 17 Apr 2026).
The light-client verification algorithm takes as input commitment identifiers 52, an 53, the micro-domain 54, and sampled coordinates 55. The verifier derives 56, interpolates each row polynomial 57 of degree 58, computes
59
forms
60
and checks whether
61
satisfies 62. The reported verification cost per block is one interpolation of degree 63, 64 scalar multiplications in 65, and 66 pairings (Srivastava et al., 17 Apr 2026).
5. Systems architecture, complexity, and empirical trade-offs
The system design in the blockchain use case is described end-to-end. Full nodes choose a micro-domain size 67 such as 68, partition each row or column domain into blocks 69, compute the 70 evaluation values 71 for each of 72 nearby rows, form the proof transcript
73
derive 74 via Fiat–Shamir, compute
75
and exponentiate via multiexp on the SRS to obtain 76 (Srivastava et al., 17 Apr 2026).
On the dissemination side, the baseline stores each sampled cell under a DHT key equal to its coordinate, with value 77, or approximately 78 bytes per object. The PMP design introduces two structures:
- 79
- 80
A fat client constructs an 81 for each block 82 and republishes it under one DHT key per block. A light client maps each sampled coordinate to its 83, fetches one 84, and extracts the relevant scalar or scalars together with the single aggregated proof 85 (Srivastava et al., 17 Apr 2026).
The theoretical comparison between the baseline and PMP is concise and explicit.
| Scheme | Proof size | Verifier cost |
|---|---|---|
| Per-cell proofs | 86 group elements 87 bytes | 88 pairings + 89 scalar muls |
| PMP with blocks of size 90 | 91 group elements 92 bytes | 93 scalar ops + 94 pairings |
The same section states that PMP memory usage is “store 95 proofs + interpolation buffers,” whereas the baseline stores 96 proofs (Srivastava et al., 17 Apr 2026).
The empirical case study in Avail reports the following values.
| Metric | Vanilla | PMP |
|---|---|---|
| Verifier CPU @1 000 | 110 units | 60 units |
| Peak memory (GB) | 1.2 | 0.7 |
| DHT hit rate (1 KB) | 78% | 100% |
| DHT hit rate (1.5–2 MB) | 12% | 98% |
| Fats to meet SLO (1 KB) | 40 | 10 |
| Capacity @2 MB (B/fat) | 16 | 80 |
The “Relative” column in the source gives 97 verifier CPU, 98 peak memory, 99 DHT hit rate at 00 KB, 01 DHT hit rate at 02–03 MB, 04 “Fats to meet SLO (1 KB),” 05 capacity at 06 MB, and infrastructure compute cost reduction “07” (Srivastava et al., 17 Apr 2026).
The paper also states several trade-offs. Grouping introduces soundness considerations because worst-case correlation inside groups of size 08 reduces effectively independent events by 09; preserving a target failure probability may therefore require sampling 10 more blocks or ensuring 11 distinct groups. Grouping also affects privacy or unlinkability because per-cell retrieval hides the exact neighborhood, whereas grouped retrieval leaks the full 12-block region to peers. Larger group objects improve DHT hit rates and lower latency, but a failed block forces re-request of all 13 scalars. The stated engineering conclusion is that Avail found 14 minimized end-to-end latency under their workload (Srivastava et al., 17 Apr 2026).
6. Comparative interpretation and open questions
Across these three usages, PMP has a shared structural motif but different formal semantics. In 15, multiplicity lies in the witness space: there are polynomially many unentangled Merlins, and the question is how verifier restrictions change expressive power (Gharibian et al., 2011). In the MA batch-evaluation protocol, multiplicity lies in the claim set: one proof polynomial certifies 16 outputs of an arithmetic circuit (Williams, 2016). In the KZG setting, multiplicity lies in the opening set: one aggregated proof certifies several sampled evaluations under a shared micro-domain (Srivastava et al., 17 Apr 2026). This suggests that “multiproof” is best understood operationally—as a proof artifact for many claims—rather than as a single syntactic object common to all subfields.
The three settings also differ sharply in what counts as efficiency. In the quantum-complexity paper, the key outcomes are class collapses and exact repetition theorems, not concrete runtime benchmarks. In the MA batch-evaluation paper, efficiency is measured by proof length, verifier randomness, and nearly linear-time algebraic verification. In the blockchain paper, efficiency is measured both asymptotically and at the deployment level, including proof bytes, verifier CPU, peak memory, DHT hit rates, and infrastructure cost (Gharibian et al., 2011, Williams, 2016, Srivastava et al., 17 Apr 2026).
The most explicit open question appears in the complexity-theoretic PMP literature: “whether 17 strictly contains 18” remains unresolved (Gharibian et al., 2011). The same source states that its theorems suggest any genuine “multiprover advantage” must either employ longer proofs than 19 or exploit richer joint measurements beyond the 20 style. In the MA batch-evaluation line, the authors ask whether proof length or verification time can be reduced below 21 by using more interaction or more randomness, and specifically whether there is an 22-time MA protocol for 23 (Williams, 2016). In the blockchain line, the unresolved issues are not posed as a single theorem-level open problem, but the trade-off analysis identifies tension among proof amortization, verifier interpolation cost, soundness under grouped retrieval, latency, and privacy leakage (Srivastava et al., 17 Apr 2026).
A recurring misconception is that aggregation automatically yields an unconditional advantage. The sources are more precise. In the quantum setting, several natural polynomial-multiproof classes collapse to already known classes. In the MA setting, the benefit depends on low degree and batch structure. In the blockchain setting, proof aggregation lowers proof bytes and verifier cost but introduces grouped-retrieval trade-offs. The literature therefore supports a narrower conclusion: PMP is a family of techniques for organizing many claims under one verification framework, and its value depends on the exact proof model, verifier restrictions, and application-level cost structure.