The FRI Protocol (Fast Reed-Solomon Interactive Oracle Proof of Proximity) is a probabilistic proof system that establishes whether a committed vector corresponds to the evaluation of a polynomial of a bounded degree. Unlike polynomial commitment schemes such as KZG commitments, FRI does not rely on bilinear pairings or a trusted setup; it operates purely on hash functions and Merkle trees, making it transparent and plausibly post-quantum secure. The protocol uses a recursive, interactive process of folding and random linear combination to reduce the degree of the tested polynomial, culminating in a trivial check that a constant polynomial is correct.
Glossary
FRI Protocol

What is FRI Protocol?
The FRI protocol is a cryptographic primitive that enables a prover to convince a verifier that a committed function is close to a low-degree polynomial, serving as the foundational proximity test within ZK-STARK systems.
The protocol's efficiency derives from its use of Reed-Solomon encoding and the Fast Fourier Transform (FFT) to perform proximity testing with logarithmic communication complexity. In each round, the verifier sends a random challenge, and the prover folds the current polynomial into a new one of half the degree, committing to it via a Merkle root. This process repeats until the polynomial degree is zero. FRI is the core low-degree test in ZK-STARKs, enabling verifiable computation without the need for a trusted setup ceremony, and is implemented in systems like RISC Zero and StarkWare's STARK prover.
Key Features of FRI Protocol
The FRI protocol is the cryptographic engine behind modern STARKs, enabling succinct proofs about the structure of committed data. These core features define its efficiency and security model.
Low-Degree Polynomial Testing
The core primitive of FRI is proving that a committed function corresponds to a polynomial of a specific low degree. The protocol uses a split-and-fold technique: in each round, the prover combines evaluations from pairs of points using a random challenge, reducing the polynomial's degree by half. After a logarithmic number of rounds, the polynomial is reduced to a constant, which the verifier checks directly. This interactive oracle proof is made non-interactive via the Fiat-Shamir heuristic, using a Merkle tree as the commitment scheme.
Logarithmic Proof Size and Verification
FRI achieves polylogarithmic proof size relative to the computation being verified. Key efficiency characteristics:
- Prover complexity: O(N log N) field operations, dominated by FFTs
- Verifier complexity: O(log² N) operations, making verification extremely fast
- Proof size: O(log² N) hash values, typically tens of kilobytes for real-world computations
- Round complexity: log₂(N) rounds of interaction, each halving the instance size This logarithmic scaling is what makes STARKs practical for proving large computations on resource-constrained verifiers.
Proximity Parameter and Soundness
FRI proves that a committed function is δ-close to a low-degree polynomial in Reed-Solomon code space. The proximity parameter δ determines the protocol's soundness error:
- A function that is δ-far from all low-degree polynomials will be rejected with high probability
- The soundness error is bounded by a function of δ, the number of queries, and the field size
- Increasing the number of query repetitions reduces soundness error exponentially
- Typical configurations use 30-80 queries to achieve 80-128 bits of security This relaxed notion of correctness (proximity rather than exact equality) is sufficient for all STARK applications.
Transparent Setup and Post-Quantum Security
Unlike pairing-based proof systems, FRI requires no trusted setup ceremony. The protocol relies solely on:
- Collision-resistant hash functions (typically SHA-256 or BLAKE3)
- Reed-Solomon codes over finite fields
- Merkle trees for polynomial commitments This transparency eliminates the toxic waste problem inherent in structured reference strings. Additionally, the reliance on symmetric cryptography rather than bilinear pairings or discrete log assumptions provides conjectured post-quantum security, making FRI-based STARKs resistant to attacks by large-scale quantum computers.
DEEP-FRI: Enhancing Security via Out-of-Domain Sampling
Standard FRI only queries points within the evaluation domain. DEEP-FRI (Domain Extension for Eliminating Pretenders) adds a crucial security enhancement:
- The verifier samples a random point outside the original evaluation domain
- The prover must open the polynomial at this out-of-domain point
- This prevents a class of algebraic attacks where a malicious prover constructs a function that passes in-domain tests but is not actually close to a low-degree polynomial
- Combined with quotienting (proving the polynomial satisfies specific constraints at the random point), DEEP-FRI achieves tighter soundness bounds Most production STARK implementations, including StarkWare's Stone prover, use DEEP-FRI.
Batch Verification and Proof Composition
FRI supports efficient batch verification of multiple polynomial proximity claims:
- Multiple polynomials can be combined into a single random linear combination
- A single FRI proof then attests to the low-degree property of all polynomials simultaneously
- This batching reduces amortized proof size and verification cost Furthermore, FRI proofs can be recursively composed: a STARK proof attesting to the validity of another STARK proof. This recursion enables:
- Proof compression: Multiple proofs collapsed into one constant-size proof
- Incremental verifiable computation: Long computations broken into steps, each proven incrementally
- L3 scaling solutions: Recursive proof aggregation for rollup ecosystems
FRI Protocol vs. Other Polynomial Commitment Schemes
A technical comparison of the Fast Reed-Solomon Interactive Oracle Proof of Proximity (FRI) against other dominant polynomial commitment schemes used in zero-knowledge proof systems.
| Feature | FRI Protocol | KZG Commitments | IPA (Inner Product Arguments) |
|---|---|---|---|
Cryptographic Assumption | Collision-resistant hash functions only | Bilinear pairings (pairing-based elliptic curves) | Discrete logarithm problem |
Trusted Setup Required | |||
Post-Quantum Security | |||
Proof Size | O(log² n) — logarithmic, larger than KZG | O(1) — constant size (single group element) | O(log n) — logarithmic, smaller than FRI |
Verifier Complexity | O(log² n) — polylogarithmic | O(1) — constant time (pairing check) | O(log n) — logarithmic |
Prover Complexity | O(n log n) — dominated by FFTs | O(n) — linear in polynomial degree | O(n) — linear in polynomial degree |
Primary Use Case | STARKs, zkVMs (RISC Zero, StarkWare) | SNARKs, Ethereum Proto-Danksharding (EIP-4844) | Bulletproofs, Halo 2, range proofs |
Enabling Efficiency, Speed & Accuracy
Intelligent Analysis, Decision & Execution
We build AI systems for teams that need search across company data, workflow automation across tools, or AI features inside products and internal software.
Talk to Us
Search across company data
Give teams answers from docs, tickets, runbooks, and product data with sources and permissions.
Useful when people spend too long searching or get different answers from different systems.

Automate internal workflows
Use AI to route work, draft outputs, trigger actions, and keep approvals and logs in place.
Useful when repetitive work moves across multiple tools and teams.

Add AI to products and internal tools
Build assistants, guided actions, or decision support into the software your team or customers already use.
Useful when AI needs to be part of the product, not a separate tool.
Frequently Asked Questions
Technical answers to the most common questions about the Fast Reed-Solomon Interactive Oracle Proof of Proximity (FRI), its cryptographic mechanics, and its role in modern ZK-STARK systems.
The Fast Reed-Solomon Interactive Oracle Proof of Proximity (FRI) is a cryptographic protocol that proves a committed function is close to a low-degree polynomial. It works through an interactive process of successive folding: the prover commits to a function, the verifier sends a random challenge, and the prover applies a random linear combination to fold the function into one of half the original degree. This process repeats logarithmically until the polynomial is reduced to a constant, which the verifier checks directly. The protocol achieves logarithmic proof size and verification time relative to the original domain size, making it the primary polynomial commitment scheme used in ZK-STARKs. Unlike KZG commitments, FRI relies solely on collision-resistant hash functions, requiring no trusted setup and offering post-quantum security.
Related Terms
The FRI protocol is a core component of modern STARK-based proving systems. Understanding its relationship to these adjacent cryptographic primitives is essential for architects designing verifiable compute pipelines.

About the author
Prasad Kumkar
CEO & MD, Inference Systems
Prasad Kumkar is the CEO & MD of Inference Systems and writes about AI systems architecture, LLM infrastructure, model serving, evaluation, and production deployment. Over 5+ years, he has worked across computer vision models, L5 autonomous vehicle systems, and LLM research, with a focus on taking complex AI ideas into real-world engineering systems.
His work and writing cover AI systems, large language models, AI agents, multimodal systems, autonomous systems, inference optimization, RAG, evaluation, and production AI engineering.
Partnered with leading AI, data, and software stack.
How We Work
Custom AI workflows for your Business
One-fit-all AI don't work for modern businesses. At Inferensys, we aim to understand your business & custom requirements; which we use to define most efficient agentic workflows, the data, and the tools for your business.
01
Review the use case
We understand the task, the users, and where AI can actually help.
Read more02
Pick the right approach
We define what needs search, automation, or product integration.
Read more03
Build the first useful version
We implement the part that proves the value first.
Read more04
Improve from there
We add the checks and visibility needed to keep it useful.
Read moreThe first call is a practical review of your use case and the right next step.
Talk to Us