Network Verification
Quantum-network verification is the inference that a network delivered a declared quantum object or service with declared quality, under a declared trust model and finite-data error guarantee. The object may be an endpoint Bell pair, a multipartite graph state, a quantum channel, a remote operation, or a service transcript. The evidence may come from calibrated local measurements, state-verification tests, steering, Bell correlations, network-locality tests, challenge requests, or operational logs.
Verification is narrower than complete characterization and broader than measuring one fidelity. A useful certificate must say what was tested, which uses were eligible, what was trusted, which null model was rejected, how loss and postselection were handled, and what later use the result covers. A Bell pair measured for tomography no longer exists for an application. A certificate for retained pairs therefore needs a sampling argument connecting sacrificed test systems to unmeasured systems.
This page is the canonical home for the network-level verification contract: test-versus-use sampling, endpoint and multipartite state checks, source-independence tests, channel and heralding checks, service-level acceptance, route diagnosis, adversarial nodes, and continuous monitoring. Certification of Entanglement owns the general hierarchy of witnesses, steering, Bell tests, and self-testing. State Tomography and Process Tomography own reconstruction. Quantum Network Architectures owns services, layers, routing, inventory, and trust domains. Network Case Studies owns experiment-by-experiment evidence. Here those pieces are assembled into a decision about a delivered network service. Distributed Quantum Sensing owns the separate application-level question of whether a verified resource improves a calibrated weighted-field estimator under matched resources.
Begin with a Verifiable Claim
Section titled “Begin with a Verifiable Claim”“The network works” has no mathematical complement and therefore no test. A verification task should begin with a record such as
Here:
- is the delivered object and its endpoint identities;
- is the sample frame: eligible requests, routes, times, and exclusions;
- is the bad-service class to be controlled;
- is the intended good-service class;
- is the device, source, node, and causal trust model;
- is the randomized measurement or challenge design;
- is the acceptance rule fixed before seeing outcomes;
- bounds false certification under ;
- is a target bound on failing to certify a specified good alternative.
The two error probabilities answer different questions. A small protects against declaring a bad service good. A small gives the test power to recognize a useful service. Neither is the posterior probability that the network is good.
A threshold claim might be
where is the indifference margin used for power planning. Omitting can make the required sample size appear mysteriously large: no finite experiment reliably distinguishes parameters separated by an arbitrarily small amount.
A Ladder of Network Claims
Section titled “A Ladder of Network Claims”Different observations support different conclusions.
| Claim | Typical evidence | What it does not establish |
|---|---|---|
| component responds | source counts, detector tests, memory calibration | endpoint entanglement |
| elementary link delivers a state | endpoint correlations with a declared herald | multi-hop performance |
| endpoint state is entangled | witness, steering, or Bell test | target-state fidelity unless separately bounded |
| endpoint state is close to a target | fidelity test or state verification | arbitrary channel behavior |
| route implements a channel | process test or entangled-input test | sustained rate and availability |
| multipartite resource is present | stabilizer, witness, or network protocol | honesty of every party |
| source-independence model is violated | bilocal or network-locality statistic | unique physical topology |
| service meets its contract | joint quality, rate, latency, identity, and failure tests | cryptographic secrecy without a security proof |
A successful swap herald plus two bright detectors proves neither that the end memories are entangled nor that the application received the correct pair. A high reconstructed fidelity proves neither that requests are served on time nor that discarded attempts were independent of the settings. Conversely, a service can be useful for a restricted task without supporting complete state or process tomography.
Verification Consumes Quantum Systems
Section titled “Verification Consumes Quantum Systems”Most network tests are destructive. Measuring on a Bell pair consumes that pair. Verification therefore certifies a population, process, or future use only through a sampling theorem and its assumptions.
A certificate does not jump automatically from measured pairs to retained pairs. Random assignment, hidden test choices, authenticated identities, and a declared statistical or adversarial model provide that bridge. The audit ledger must include every eligible attempt, not only successful-looking records.
Suppose a batch contains eligible deliveries. A secret random subset is assigned to testing and the complement to use. A valid statement about requires conditions such as exchangeability, random sampling without replacement, an independent-use model, or a protocol proved against correlated and adversarial preparations. Choosing after looking at heralds, routes, or preliminary outcomes can destroy the guarantee.
The sampling unit must also be explicit. It might be an optical attempt, a heralded memory pair, an accepted end-to-end pair, a remote gate, or a complete application transaction. Changing the unit changes both the denominator and the claim.
Trust Models
Section titled “Trust Models”There is no universally strongest practical test. Reducing trust generally requires stronger correlations, more trials, tighter causal control, or a weaker conclusion.
| Model | Trusted elements | Typical conclusion |
|---|---|---|
| calibrated-device | state dimension, endpoint POVMs, labels, classical records | witness value, fidelity, or reconstructed state |
| untrusted source | endpoint measurements and randomness | target-state verification against a faulty or adversarial source |
| one-sided device-independent | one endpoint laboratory | steering or fidelity guarantee with the other side uncharacterized |
| device-independent | input choices, outputs, laboratory isolation, causal order | entanglement or state/measurement equivalence from Bell correlations |
| network-device-independent | the preceding interface plus a source-independence or causal graph assumption | incompatibility with a network-local model, sometimes network-assisted self-testing |
“Device-independent” never means assumption-free. Current inputs must be sufficiently private, every eligible trial needs a declared output, forbidden communication must be excluded during the trial, and the classical analysis must be trusted. A network-locality conclusion adds assumptions about which sources share common causes. If two nominally independent sources are pumped by one controller with hidden correlated state, a bilocal model is the wrong null.
Device-Independent QKD owns the stronger step from observed Bell data to composable secret key. A network Bell violation by itself is not a key-security proof.
Worked Bell-Pair Certificate
Section titled “Worked Bell-Pair Certificate”For the target
the projector has the Pauli expansion
For any two-qubit state , not merely a Bell-diagonal state,
where . If simultaneous one-sided confidence bounds give
then a conservative fidelity bound is
Every separable two-qubit state has overlap at most with a maximally entangled state. Thus certifies entanglement under the calibrated qubit-and-measurement model. A service requirement is stricter: an entanglement certificate can pass while the service-quality certificate fails.
Suppose the intervals are
Then
This certifies entanglement but does not certify a minimum. Rounding the point estimate upward would reverse a scientifically meaningful decision.
The target also depends on a frame convention. If a herald identifies and software records a Pauli-frame update to , the correlators must be interpreted using that exact record. Mixing uncorrected Bell labels can make individually good pairs look maximally mixed.
Quantum-State Verification Operators
Section titled “Quantum-State Verification Operators”Full tomography estimates many parameters that a pass/fail decision does not need. Quantum-state verification instead chooses local tests that accept an ideal target with certainty. Let setting be selected with probability and let be its pass operator. The verification operator is
Write its two largest eigenvalues as
and define the spectral gap
For any state satisfying
the one-trial pass probability obeys
Under the corresponding independent-product promise, the probability that bad systems all pass is at most
It is therefore sufficient to choose
to limit false acceptance to . Larger gap means better sample efficiency. Locality, available bases, dishonest parties, and noisy honest devices constrain which are implementable and change the gap.
The all-pass protocol is not appropriate when even an acceptable source has a nonzero fail probability. Then the protocol needs a threshold on the number of passes, an explicit good-state noise model, and finite-sample bounds for both errors. Correlated or adversarial batches require a theorem for that setting; blindly raising an IID binomial probability to the th power is not such a theorem.
Multipartite and Graph-State Resources
Section titled “Multipartite and Graph-State Resources”Let a graph define the graph-state stabilizer generators
For the ideal graph state, . Define
Because the generators commute and uniquely specify the graph state,
The operator inequality
gives the directly useful lower bound
This bound turns local Pauli correlators into a target-state guarantee. Graph coloring can group compatible stabilizer tests into fewer global settings. Specialized verification operators can have better sample complexity than this simple union bound.
A network adds a strategic problem absent from a trusted laboratory: some parties may lie about settings or outcomes, collude with the source, or exploit loss. Protocols for untrusted networks specify at least one honest verifier, private random challenges, authenticated classical communication, which parties may collude, and how untested copies are selected. Passing a trusted stabilizer test and passing an adversarial multipartite protocol are different claims even when both target the same .
Bilocality and Independent Sources
Section titled “Bilocality and Independent Sources”Ordinary Bell locality uses one shared hidden variable. An entanglement- swapping network has two nominally independent sources. In a three-node chain, a bilocal model factors as
The product is the source-independence assumption. A general Bell-local model may replace it with a correlated , so the bilocal set is smaller and generally nonconvex.
In one standard binary-setting formulation, the middle node returns two bits . Let and define
Bilocal correlations satisfy
A statistically valid violation rejects this bilocal null under the declared trial, independence, measurement-choice, communication, and loss assumptions. It does not by itself certify a particular Bell-state fidelity, identify which component is faulty, or prove that the sources are physically independent. Independence is an input to the null model, not an output conjured by the inequality.
Network nonlocality can reveal correlations that admit an ordinary Bell-local model but not a source-independent network-local model. That is a real and useful distinction, not a stronger synonym for every kind of nonclassicality.
Self-Testing and Topology Certification
Section titled “Self-Testing and Topology Certification”Self-testing infers that every compatible realization contains a target state and measurements, up to local isometries and irrelevant auxiliary systems. A robust statement has the schematic form
where is a chosen distance, is a product of local extraction maps, and as . The exact robustness function is protocol-specific. A statement of ideal self-testing without the finite-noise bound needed by the experiment is incomplete.
Network constraints can enable certifications unavailable in the same ordinary Bell scenario. They can also test candidate causal structures. Given observed , one may ask whether any states and measurements arranged on a proposed source graph can reproduce the data. Inflation and related relaxations generate necessary constraints on that model. Violating one excludes the candidate structure within the assumptions.
This conclusion is usually an equivalence-class statement, not a photograph of cables. Two physical networks can produce the same observable statistics, and finite tests rarely identify one unique internal realization. The certificate must state which candidate models were excluded and which alternatives remain.
Channels, Loss, and Heralding
Section titled “Channels, Loss, and Heralding”A network often promises a channel rather than a fixed state. For a trace-preserving map on dimension , define the normalized Choi state
with
Its entanglement fidelity relative to the identity is
For a trace-preserving channel, the Haar-average pure-state fidelity satisfies
This relation does not license silent conditioning on loss. A heralded branch is a completely positive trace-nonincreasing map . Its Choi operator is subnormalized:
The superscript reminds us that is the success probability for the maximally mixed input represented by the Choi experiment. If success depends strongly on the input, one number does not certify uniform transmission. A complete link certificate reports success behavior and conditional quality together, and includes failed trials in the sampling frame.
Herald timing matters. For an event-ready Bell test, the event definition and herald must be fixed before the endpoint settings are chosen. Otherwise the herald can become outcome- or setting-dependent postselection.
From State Quality to Service Conformance
Section titled “From State Quality to Service Conformance”An application consumes identified resources in time. A service claim can be written as the conjunction
Here counts accepted resources per wall-clock time, is request-to-delivery latency, is availability over a declared observation schedule, and includes endpoint, memory-slot, route, or Pauli-frame mismatch. A high conditional fidelity with a vanishing delivery rate does not satisfy this contract.
If component tests have false-certification probabilities , a simple simultaneous guarantee follows from the union bound:
This bound can be conservative, but it forces the error budget to be visible. Reporting five separate “99% confidence” intervals does not automatically give a 99% joint certificate.
Request classes must not be pooled indiscriminately. Fidelity, rate, and latency can depend on endpoints, route, requested threshold, priority, memory age, time of day, and competing traffic. A weighted average can pass while a contractually important class fails.
Route Diagnosis and Network Tomography
Section titled “Route Diagnosis and Network Tomography”End-to-end failure should be detected end to end. Component tests are then useful for localization. Testing only components can miss correlated phase errors, wrong Bell labels, timing mismatches, swap-feed-forward faults, and software identity errors that appear only after composition.
In a simplified additive model, route statistic depends on link parameters through
or in vector form
All link parameters are identifiable only if the probe-route matrix has the required rank. If has a nontrivial null space, several internal fault patterns produce the same end-to-end data. More trials reduce statistical noise but do not cure structural nonidentifiability.
The additive model itself must be validated. Coherent errors can interfere, memory noise depends on stochastic waiting time, swapping can correlate branches, and purification changes both state quality and selection. Network tomography is therefore model-based diagnosis, not a substitute for direct service verification.
Finite Statistics, Drift, and Repeated Monitoring
Section titled “Finite Statistics, Drift, and Repeated Monitoring”For independent bounded observations , Hoeffding’s inequality gives
It is useful for planning simple correlator tests, but its independence and stationarity assumptions are physical assumptions. Network records often have bursts, shared calibration drift, queue correlations, memory effects, and adaptive route selection. Treating every click as an independent sample can underestimate uncertainty by orders of magnitude.
The acquisition hierarchy should be retained:
Randomize test settings within relevant timescales, report between-epoch variation, and use block, hierarchical, martingale, or confidence-sequence methods when their assumptions match the protocol. If a dashboard is checked continuously, a fixed-horizon confidence interval recomputed after every event does not retain its nominal coverage. Time-uniform inference or a declared alpha-spending rule is needed.
Drift is also a property to test. A six-hour average above threshold can hide forty-minute outages. Report time-resolved bounds, change-point policy, data latency, and the recovery rule that returns a route to service.
Adversarial Nodes and Transcripts
Section titled “Adversarial Nodes and Transcripts”A faulty network can bias verification without changing the quantum state. It can omit inconvenient trials, relabel endpoints, replay heralds, announce a route different from the one used, delay messages until settings are known, or select calibration corrections after viewing outcomes.
A defensible transcript includes:
- a unique request and attempt identifier;
- endpoint and memory-slot identifiers;
- route and protocol versions;
- timestamps from declared clock domains;
- herald and swap outcomes in causal order;
- setting-generation records and commitment points;
- every no-click, timeout, abort, retry, and exclusion reason;
- Pauli-frame, reference-frame, and calibration versions;
- hashes or signatures that expose deletion and alteration;
- the preregistered test rule and analysis code version.
Authentication protects record integrity, not record truth. Independent cross-checks at endpoints, challenge traffic, causal timing, and physical tests are still required. Likewise, encrypting the transcript does not make a weak statistical test strong.
When some parties are dishonest, state what honest subset is guaranteed a useful state after acceptance. “At least one verifier is honest” and “all honest parties simultaneously receive a good state” are different security statements.
Logical and Application-Level Verification
Section titled “Logical and Application-Level Verification”A physical Bell-pair certificate does not automatically certify a logical Bell pair or remote logical gate. The logical object includes encoding, repeated syndrome extraction, decoder state, frame updates, leakage handling, accepted failure modes, and the time at which the application may safely consume it.
Distributed Quantum Computing owns teledata, telegates, partitioning, scheduling, and logical network-resource accounting. Network verification supplies testable acceptance conditions for the remote states or operations used there. A complete logical certificate should distinguish:
These probabilities need not be equal, and postselection at one layer changes the denominator seen by the next.
Cryptographic, sensing, and computing applications can require properties not captured by fidelity. QKD needs a security proof and authenticated transcript; sensing may need phase-reference stability and simultaneous delivery; distributed computation may need coherence-bound feed-forward latency. Verify the metric that the application theorem actually uses.
A Practical Verification Workflow
Section titled “A Practical Verification Workflow”- Name the service boundary. Identify endpoints, output system, success flag, deadline, and who controls each interface.
- Write the bad-service null. Include thresholds, dimensions, source graph, loss behavior, and allowed adversarial memory.
- Choose the least-trusting feasible protocol. Do not claim a stronger trust class than the implementation closes.
- Define all eligible trials before outcomes. Include no-clicks, timeouts, retries, and aborted transactions.
- Randomize test assignment and settings. Record when choices become knowable to sources, relays, and endpoints.
- Precompute power and error budgets. Include simultaneous metrics and planned subgroup analyses.
- Bind quantum and classical identities. Check route, slot, herald, correction, calibration, and clock records.
- Test end to end, then localize. Component certificates supplement but do not replace delivered-service tests.
- Stress the assumptions. Look for drift, source correlation, selective loss, setting leakage, and model nonidentifiability.
- Issue a scoped certificate. State the covered population, validity window, confidence, exclusions, and revocation triggers.
Reporting Standards owns the general artifact and provenance contract. The network-specific addition is that quantum-resource identity and causal ordering must be joined to the service transcript.
Evidence and Maturity
Section titled “Evidence and Maturity”Several layers are established. Trusted endpoint correlations and tomography are standard laboratory tools. Efficient local verification strategies are known for Bell, stabilizer, graph, and related states. Experiments have verified multipartite entanglement with untrusted sources or parties, and small networks have demonstrated service-layer entanglement delivery with state and latency measurements. Bilocal and larger network-locality violations have also been demonstrated under stated source-independence and sampling assumptions.
Other layers remain developing. Robust device-independent bounds can be experimentally demanding. Topology certification and network-assisted self-testing are active research areas. Continuous certification of a multiuser, rerouting, memory-bearing network under correlated faults and adversarial nodes is not yet a standardized solved problem. A simulation of such a monitor is evidence about a model; a small fixed-topology experiment is evidence about that implementation; neither alone establishes internet-scale operation.
Use Network Case Studies for detailed experimental ledgers and Claims, Hype, and Evidence Standards for classifying the resulting public claim.
Common Mistakes
Section titled “Common Mistakes”- Treating a herald as a certificate. A herald defines a candidate event; it does not establish the endpoint state.
- Reporting conditional fidelity alone. The herald probability, delivered rate, and all exclusions belong beside it.
- Using tested pairs as if they remain available. Destructive measurements require a sampling argument for retained systems.
- Calling a witness value tomography. A targeted test supports a targeted claim, not a complete reconstructed state.
- Calling tomography device-independent. Reconstruction inherits its state, measurement, dimension, and stationarity models.
- Ignoring source independence. Network-locality inequalities have a causal model different from ordinary Bell inequalities.
- Combining marginal confidence levels as a joint level. Allocate an error budget across all required service metrics.
- Dropping no-clicks or timeouts after seeing them. Outcome-dependent filtering can open a detection or selection loophole.
- Pooling routes and epochs. A passing average can conceal a failing route or outage window.
- Inferring components from unidentifiable path data. More samples cannot remove a null space in the probe design.
- Equating entanglement with usefulness. Target fidelity, latency, reference frames, logical error, and application security can impose stricter conditions.
- Letting the certificate outlive the system state. Firmware, calibration, topology, and maintenance changes need explicit invalidation rules.
References
Section titled “References”- N. Friis, G. Vitagliano, M. Malik, and M. Huber, “Entanglement certification from theory to experiment,” Nature Reviews Physics 1, 72–87 (2019), doi:10.1038/s42254-018-0003-5.
- S. Pallister, N. Linden, and A. Montanaro, “Optimal verification of entangled states with local measurements,” Physical Review Letters 120, 170502 (2018), doi:10.1103/PhysRevLett.120.170502.
- R. Blume-Kohout, J. O. S. Yin, and S. J. van Enk, “Entanglement verification with finite data,” Physical Review Letters 105, 170501 (2010), doi:10.1103/PhysRevLett.105.170501.
- B. Dirkse, M. Pompili, R. Hanson, M. Walter, and S. Wehner, “Witnessing entanglement in experiments with correlated noise,” Quantum Science and Technology 5, 035007 (2020), doi:10.1088/2058-9565/ab8d88.
- H. Zhu and M. Hayashi, “Optimal verification of stabilizer states,” Physical Review Research 2, 043323 (2020), doi:10.1103/PhysRevResearch.2.043323.
- H. Zhu and M. Hayashi, “Efficient verification of hypergraph states,” Physical Review Applied 12, 054047 (2019), doi:10.1103/PhysRevApplied.12.054047.
- A. Unnikrishnan and D. Markham, “Verification of graph states in an untrusted network,” Physical Review A 105, 052420 (2022), doi:10.1103/PhysRevA.105.052420.
- W. McCutcheon et al., “Experimental verification of multipartite entanglement in quantum networks,” Nature Communications 7, 13251 (2016), doi:10.1038/ncomms13251.
- Y.-G. Han et al., “Optimal verification of the Bell state and Greenberger–Horne–Zeilinger states in untrusted quantum networks,” npj Quantum Information 7, 164 (2021), doi:10.1038/s41534-021-00499-8.
- J. S. Bell, “On the Einstein Podolsky Rosen paradox,” Physics Physique Fizika 1, 195–200 (1964), doi:10.1103/PhysicsPhysiqueFizika.1.195.
- J. F. Clauser, M. A. Horne, A. Shimony, and R. A. Holt, “Proposed experiment to test local hidden-variable theories,” Physical Review Letters 23, 880–884 (1969), doi:10.1103/PhysRevLett.23.880.
- B. Hensen et al., “Loophole-free Bell inequality violation using electron spins separated by 1.3 kilometres,” Nature 526, 682–686 (2015), doi:10.1038/nature15759.
- C. Branciard, N. Gisin, and S. Pironio, “Characterizing the nonlocal correlations created via entanglement swapping,” Physical Review Letters 104, 170401 (2010), doi:10.1103/PhysRevLett.104.170401.
- C. Branciard, D. Rosset, N. Gisin, and S. Pironio, “Bilocal versus nonbilocal correlations in entanglement-swapping experiments,” Physical Review A 85, 032119 (2012), doi:10.1103/PhysRevA.85.032119.
- A. Tavakoli, A. Pozas-Kerstjens, M.-X. Luo, and M.-O. Renou, “Bell nonlocality in networks,” Reports on Progress in Physics 85, 056001 (2022), doi:10.1088/1361-6633/ac41bb.
- G. Carvacho et al., “Experimental violation of local causality in a quantum network,” Nature Communications 8, 14775 (2017), doi:10.1038/ncomms14775.
- D. J. Saunders, A. J. Bennet, C. Branciard, and G. J. Pryde, “Experimental demonstration of nonbilocal quantum correlations,” Science Advances 3, e1602743 (2017), doi:10.1126/sciadv.1602743.
- I. Šupić and J. Bowles, “Self-testing of quantum systems: a review,” Quantum 4, 337 (2020), doi:10.22331/q-2020-09-30-337.
- I. Šupić, J.-D. Bancal, Y. Cai, and N. Brunner, “Genuine network quantum nonlocality and self-testing,” Physical Review A 105, 022206 (2022), doi:10.1103/PhysRevA.105.022206.
- I. Šupić et al., “Quantum networks self-test all entangled states,” Nature Physics 19, 670–675 (2023), doi:10.1038/s41567-023-01945-4.
- M.-O. Renou et al., “Genuine quantum nonlocality in the triangle network,” Physical Review Letters 123, 140401 (2019), doi:10.1103/PhysRevLett.123.140401.
- Y.-L. Mao et al., “Certifying network topologies and nonlocalities of triangle quantum networks,” Physical Review Letters 132, 240801 (2024), doi:10.1103/PhysRevLett.132.240801.
- A. Ulibarrena et al., “Guarantees on the structure of experimental quantum networks,” npj Quantum Information 10, 117 (2024), doi:10.1038/s41534-024-00911-z.
- S. Neves et al., “Experimentally certified transmission of a quantum message through an untrusted and lossy quantum channel via Bell’s theorem,” PRX Quantum 6, 030312 (2025), doi:10.1103/PRXQuantum.6.030312.
- M. Pompili et al., “Experimental demonstration of entanglement delivery using a quantum network stack,” npj Quantum Information 8, 121 (2022), doi:10.1038/s41534-022-00631-2.
- M. A. Nielsen, “A simple formula for the average gate fidelity of a quantum dynamical operation,” Physics Letters A 303, 249–252 (2002), doi:10.1016/S0375-9601(02)01272-0.
- W. Hoeffding, “Probability inequalities for sums of bounded random variables,” Journal of the American Statistical Association 58, 13–30 (1963), doi:10.1080/01621459.1963.10500830.
- R. J. Serfling, “Probability inequalities for the sum in sampling without replacement,” The Annals of Statistics 2, 39–48 (1974), doi:10.1214/aos/1176342611.
- S. R. Howard, A. Ramdas, J. McAuliffe, and J. Sekhon, “Time-uniform, nonparametric, nonasymptotic confidence sequences,” The Annals of Statistics 49, 1055–1080 (2021), doi:10.1214/20-AOS1991.
- M. Guedes de Andrade et al., “Quantum network tomography with multiparty state distribution,” arXiv:2206.02920 (2022), doi:10.48550/arXiv.2206.02920.
Exercises
Section titled “Exercises”1. Bell-pair lower bound
Section titled “1. Bell-pair lower bound”Simultaneous confidence intervals give
Find a lower bound on . Does it certify entanglement? Does it certify a service threshold ?
Solution
Use the lower bounds for the positive terms and the upper bound for , because it enters with a minus sign:
Since , the result certifies entanglement under the trusted two-qubit measurement model. It does not certify .
2. Verification sample size
Section titled “2. Verification sample size”A verification operator has gap . How many all-pass trials are sufficient, using the exponential bound, to reject states with infidelity at least at false-acceptance probability ?
Solution
The sufficient bound is
Thus trials suffice. This calculation assumes the all-pass protocol and the product or conditional bad-state promise used in its proof.
3. Conditional quality versus delivery
Section titled “3. Conditional quality versus delivery”A link makes attempts in one hour, heralds pairs, and estimates conditional Bell-state fidelity . State the delivery probability and explain why the fidelity alone does not certify an application requiring at least one pair per ten seconds.
Solution
The empirical herald probability is
The delivered rate is , before any additional application rejection. The average rate is therefore below one pair per ten seconds. The conditional fidelity concerns states given a herald; it does not guarantee rate, latency quantiles, or availability.
4. Why independence changes the null
Section titled “4. Why independence changes the null”Show how a bilocal model becomes an ordinary Bell-local model if the two hidden variables are allowed a joint distribution . Why can a bilocality violation coexist with an ordinary Bell-local explanation?
Solution
Replace by an arbitrary joint distribution and define one shared hidden variable . Then
after allowing each response to ignore whichever component it does not need. The ordinary local set therefore permits source correlations forbidden by the bilocal model. Data can lie outside the smaller bilocal set while remaining inside the ordinary Bell-local set.
5. Graph-state fidelity bound
Section titled “5. Graph-state fidelity bound”Four stabilizer generators have measured expectations
Use the generator union bound to lower-bound the graph-state fidelity.
Solution
The total generator failure bound is
Therefore
This is a conservative target-state bound under the trusted stabilizer measurement model, not a device-independent statement.
6. Identifiability of three links
Section titled “6. Identifiability of three links”Three unknown link-error parameters are . Two route probes give
Are all links identifiable? What additional route makes the linear system identifiable?
Solution
The first probe matrix is
which has rank . The vector lies in its null space, so the three errors are not identifiable. Adding
gives
whose determinant is , so the linearized parameters are identifiable.
7. A joint error budget
Section titled “7. A joint error budget”A service certificate requires fidelity, delivered rate, latency, and identity tests to pass. Give a simple allocation that guarantees total false certification probability at most .
Solution
Assign each of the four component tests
Then the union bound gives
Other allocations are valid and may give more power by assigning more error budget to the hardest metric, but they should be fixed before inspecting the data.
8. Design a drift-aware route test
Section titled “8. Design a drift-aware route test”A three-node network alternates between two routes and recalibrates every hour. Sketch a verification design that can certify a daily fidelity threshold without hiding a forty-minute failure.
Solution
A defensible design would stratify by route and calibration epoch, randomly interleave destructive test requests with application requests inside each stratum, and retain attempt-level timestamps, heralds, no-clicks, frame data, and exclusions. It would set both a daily aggregate threshold and a shorter window or change-point rule, with a simultaneous error budget. A route is removed from service when its time-uniform lower bound crosses the failure threshold and is reinstated only after a preregistered recovery test. This design can identify a forty-minute failure instead of averaging it into the rest of the day.