{"id":"2fe3cea5-2dca-493b-800d-ebb8269a9528","arxiv_id":"2501.16796","paper_version":1,"verdict":"CONDITIONAL","confidence":"MODERATE","novelty_score":5.0,"correctness_risk":"medium","formal_verification":"none","parameter_count":1,"one_line_summary":"Photon pairs used to generate quantum keys over 48 km of deployed fiber simultaneously kept two rubidium clocks synchronized to within 12 ps, with no extra timing hardware.","lead":"This paper demonstrates that the entangled photon pairs already used for quantum key distribution can also keep two remote clocks in step, holding their time offset below 12 picoseconds over a 48 kilometer deployed fiber link. A generalist should read it because it removes the need for separate clock synchronization hardware in field-deployed quantum networks, a practical obstacle for entanglement-based QKD.","discovery_kind":"new_application","skeptic_critique":{"model":"deepseek-v4-flash","headline":"The 12 ps clock-offset claim conflates coincidence-peak residual with true clock offset; optical path variations are absorbed by the loop, so the actual clock offset may be much larger.","rationale":"The paper's headline is specifically about clocks: 'time offset between the clocks under 12 ps at all time'. The only direct measurement is the coincidence-peak position, which is the sum of the clock offset and the differential optical-path delay. The protocol actively corrects the clock frequency to center this sum, and the paper claims to 'passively correct the daily variations of optical path' (Introduction, Conclusion). This creates an identifiability problem: a slow change in the fiber path delay is indistinguishable from a clock drift and will be compensated by the clock correction loop. Therefore, the corrected-drift residual in Fig. 4 being small is necessary but not sufficient to conclude the clocks themselves are within 12 ps. The internal tension between Section II.B ('mostly fixed in time' for δt_photons) and the passive path-correction claim highlights that the path stability is never quantified. The sustained 7 kbps key rate only shows the coincidence peak remains centered, which is the relevant metric for QKD but not for the clock-offset claim. The proposed test, an independent time reference, would settle the issue by measuring the true clock offset directly. If the path is stable, the claim holds; if not, the headline overstates. The reader's weakest_assumption captured the lack of an independent reference but did not fully articulate the conflation between peak position and clock offset, hence partial agreement. The verdict remains CONDITIONAL because the issue can be resolved by additional measurement; no change to the reader's verdict is needed, but the condition should explicitly require path-stability evidence or an independent clock verification.","tokens_in":8283,"tokens_out":8096,"duration_ms":72579,"concrete_test":"During a 48 h run, operate an independent time-transfer link (e.g., White Rabbit or GNSS common-view) between Alice and Bob to obtain a ground-truth clock offset, and compare it with the corrected-drift residual reported in Fig. 4; if the true clock offset exceeds 12 ps while the residual remains below 12 ps, the claim conflates peak position with clock offset.","verdict_should_be":"UNCHANGED","load_bearing_attack":"The central claim (Section V, abstract) that the remote clocks 'never drift apart by more than 12 ps' is not established by the data. The measured residual in Fig. 4 is the servo error of the coincidence-peak position, which is the sum of the clock offset and the differential optical-path delay between the two arms. The protocol corrects the clock frequency to keep this sum centered, and the paper explicitly states that it 'passively corrects the daily variations of optical path' (Introduction, Conclusion). Consequently, any slow path change between the two deployed fibers is absorbed into the clock correction, and the true clock offset can wander by the path variation while the reported residual remains below 12 ps. Section II.B treats δt_photons as 'mostly fixed in time', but the claimed passive path correction contradicts this unless the path variation is known to be <12 ps, which is never quantified. Without an independent time reference, the sustained 7 kbps key rate only confirms the peak stays centered, not that the clocks themselves are syntonized to 12 ps.","agreement_with_reader":"partial"},"referee_report":{"model":"deepseek-v4-flash","summary":"The paper reports a field implementation of a photon-pair-based time synchronization protocol on an entanglement-based QKD link deployed over 48 km of optical fiber in the Métropole Côte d'Azur. The protocol uses the strong temporal correlations of energy-time entangled photon pairs transmitted through the quantum channel to estimate and correct the relative drift between two rubidium clocks at the end stations. The authors demonstrate a sustained secret key rate of about 7 kbps and claim that the clocks never drift apart by more than 12 ps over 48-hour runs. They also argue that this approach requires less hardware than conventional synchronization methods, such as White Rabbit or dedicated reference-signal distribution, and that it passively compensates daily optical path variations.","tokens_in":8269,"tokens_out":4474,"duration_ms":42161,"significance":"If the central claim is fully supported, this is a practically useful result: it shows that an entanglement-based QKD link can be self-synchronizing to tens of picoseconds without dedicated synchronization hardware. The paper's strengths include a real-field deployment with a sustained key rate, a concrete complexity estimate for the histogram computation that makes frequent updates feasible, and a clear presentation of the system architecture. The protocol itself is taken from Ho et al. (ref. 17), but the new contribution is its integration into an operational QKD network and the characterization of its long-term behavior. The main weakness is that the headline 'under 12 ps at all time' claim is based on the feedback-loop residual, which does not directly measure the clock offset if optical path variations are absorbed by the loop.","major_comments":[{"comment":"The central claim that 'the clocks never drift apart by more than 12 ps' is not established by the data shown. The blue curve in Fig. 4 is the residual of the coincidence-peak position after feedback correction, and this quantity is the sum of the clock offset and the differential optical-path delay between the two arms. Section IV explicitly states that the feedback is 'resilient to slow external perturbations, such as the variation of the optical path between night and day', and the Conclusion states that the protocol 'passively corrects the optical path variations'. Therefore slow path changes are absorbed into the clock-frequency corrections, and the 12 ps bound applies to the combined servo residual rather than to the clock offset alone. The authors should either quantify the optical-path stability (for example with a co-propagated classical reference or an independent time reference) or restrict the claim to the coincidence-peak position. As written, the abstract's guarantee is overstated.","section":"Section V, Abstract, and Conclusion"},{"comment":"The statistical summary 'mean value of 0.08 ps and a variance of 9 ps' does not support the statement 'never drifting apart from more than 12 ps during the whole experiment'. A variance of 9 ps (standard deviation 3 ps) is compatible with peak excursions well above 12 ps over a 48-hour run, especially if the residual has non-Gaussian tails. The maximum absolute residual for the unperturbed run should be reported; for comparison, the perturbed run in Fig. 5 states a maximum drift of 44 ps. As written, the 'at all time' bound is not backed by the displayed metric.","section":"Section V, Fig. 4"},{"comment":"The assumption that δt_photons is 'mostly fixed in time' (Section II.B) is in tension with the claimed passive correction of daily optical path variations (Section IV and Conclusion). Unless the optical path variation is independently bounded below 12 ps, the feedback loop's corrections to Alice's clock frequency do not yield a measurement of the true clock offset. The paper should provide such a bound or explicitly acknowledge that the reported 12 ps stability is a property of the combined clock-plus-channel system, not of the clocks alone.","section":"Section II.B and Section IV"}],"minor_comments":[{"comment":"The title says a '50 km-long link' while the abstract and body state 48 km of deployed fiber; the numbers should be harmonized.","section":"Title and Abstract"},{"comment":"The caption says the histogram is plotted twice per second, while Section IV says that 'only one measurement of δt_clock is required every few seconds' and also that histograms can be calculated 'several times per second'; the actual update rate should be stated consistently.","section":"Fig. 2 caption and Section IV"},{"comment":"There is a typo in 'Ctimstamp' (should be 'C_timestamp'), and the sentence beginning 'more specifically' after a period is ungrammatical.","section":"Section III"},{"comment":"'oranges lines' should read 'orange lines'.","section":"Fig. 1 caption"},{"comment":"'pacing two rubidium atomic clocks' should be 'synchronizing' or 'pairing'.","section":"Conclusion"}],"recommendation":"major_revision","confidential_remarks":"The main issue is interpretational rather than technical: the paper's claim about clock syntonization depends on separating optical path variations from clock drift, and the current data do not do that. I believe this is fixable by either adding a measurement or carefully revising the claim, so I recommend major revision rather than rejection. The manuscript is otherwise a solid demonstration with a clear complexity argument and a useful field deployment."},"author_rebuttal":null,"desk_editor":{"model":"deepseek-v4-flash","letter":"Short version: this is a genuinely useful field demonstration, but the paper overstates what is measured. The 12 ps figure is the coincidence-peak residual, not the clock offset, and the paper's own claim that the scheme passively corrects optical path variations means the loop is absorbing path drift that could be much larger. For the QKD application that's fine—the peak stays in the window and key flows. For the advertised clock-syntonization claim, it isn't established.\n\nWhat's new: the deployment itself is solid. 48 km of metro fiber, three nodes, energy-time entangled source, automated BBM92 with 7 kbps secret key rate over 48 hours. The synchronization protocol is from Ho, Lamas-Linares and Kurtsiefer (2009), properly cited. The new material is the long-duration stability run, the perturbation resilience test (magnetic disturbance on Bob's clock), and the loss scaling study up to 32 dB. The histogram complexity argument in Section III checks out, and the numbers are internally consistent: 80 ps FWHM peak, 120 ps window, 30 ps tolerance, 4 ps bins, corrections every few seconds matched to the rubidium spec of ~7 ps/s.\n\nThe soft spots: the strongest one is the gap between the data and the claim. What is plotted in Fig. 4 is the position of the coincidence peak after feedback correction. That position is the sum of the clock offset and the differential optical path between the two arms. The paper states (Introduction and Conclusion) that the protocol passively compensates daily path variations from temperature. So any slow path change is absorbed into the clock frequency correction, and the true clock offset can drift by more than 12 ps while the residual stays small. To make the 'clocks never drift apart by more than 12 ps' claim, you need either an independent time reference at both ends or a quantification of the path stability. Neither is supplied. The sustained 7 kbps key rate only confirms the peak stays centered, which is the operational requirement for this QKD system. So the engineering works, but the metrological claim is not proven.\n\nAlso, the statistics are loose: mean 0.08 ps and variance 9 ps with no sample count, no units for the variance, and no error bars on the peak fits. No raw data or code is released either. The abstract's 'under 12 ps at all time' also conflicts with Fig. 5, where the perturbation pushes the residual to 44 ps; the text explains this, but the abstract and conclusion overstate.\n\nWho gets value: anyone running a field-deployed entanglement-based QKD link who wants to drop separate clock distribution hardware. For that reader, the paper is worth serious referee time. The main fix is to re-label the claim: what is stabilized is the coincidence-peak position, not the clock offset. With that revision, the paper should be publishable. Without it, the headline overstates.","headline":"Solid field demonstration of a known photon-pair sync protocol, but the 12 ps clock-offset claim is really a coincidence-peak servo residual and should be reframed.","tokens_in":9056,"tokens_out":2628,"would_cite":true,"duration_ms":22013,"reading_group":"yes","serious_thinker":"yes","would_accept_peer_review":true},"rs_alignment":null,"lean_confirmation":null,"pith_extraction":{"msc":["81P94"],"pacs":[],"model":"deepseek-v4-flash","headline":"Photon pairs from a working QKD link can synchronize the users' clocks to within 12 ps.","keywords":["quantum key distribution","entanglement-based QKD","clock synchronization","syntonization","rubidium clock","energy-time entanglement","coincidence measurement","field-deployed fiber network"],"falsifier":"Feed both end stations an independent common time reference, such as common-view GNSS or a White Rabbit link, over the same 48-hour period and compare that reference to the clock offset reported by the QKD-based synchronization loop; any excursion beyond 12 ps in the difference would falsify the claim.","tokens_in":7866,"feed_emoji":"⏱️","tokens_out":3589,"duration_ms":33357,"temperature":0.7,"pith_summary":"This paper demonstrates that two remotely located rubidium clocks can be kept aligned to within 12 picoseconds at all times using only the time-correlated photon pairs that an entanglement-based quantum key distribution (QKD) system already generates. This turns clock synchronization from an extra hardware service into a byproduct of the QKD protocol itself, requiring no dedicated reference signal or additional fiber. The demonstration runs continuously for 48 hours over 48 km of deployed optical fiber and maintains an average secret key rate of 7 kbps throughout. The authors argue that this level of stability keeps the 80 picosecond coincidence peak completely inside the 120 picosecond coincidence window, which is what makes uninterrupted key generation possible.","feed_headline":"Entangled photons keep QKD clocks locked under 12 ps","feed_subtitle":"A 48 km field run shows a QKD network's own photon pairs can keep remote clocks aligned for 48 hours.","key_machinery":"The central mechanism is a closed correction loop built around a cross-correlation histogram of photon detection times. Bob's time-tagged detections are sent to Alice, who computes a coincidence histogram with 4 ps bins over a 1 ns window at a rate of roughly twice per second; fitting the central peak gives the current clock offset. Consecutive peak positions yield the frequency difference between the two rubidium clocks, and Alice's clock frequency is adjusted accordingly. This loop carries the entire argument: it converts the quantum correlation signal into a continuous, high-precision syntonization service that needs no external time reference.","core_discovery":"The central claim is that the coincidence peak reconstructed from Alice and Bob's detection timestamps gives a precise, unbiased estimate of the relative clock offset, and that feeding this estimate into a periodic frequency-correction loop can hold the two remote rubidium clocks together indefinitely. Without correction, the clocks drift by roughly 240 ps in ten seconds and up to 27 ns over 48 hours; with correction, the residual drift over a 48-hour run has a mean of 0.08 ps and a variance of 9 ps, never exceeding 12 ps. The paper also shows that the same loop survives external perturbations, such as a magnetic disturbance that worsens one clock's stability by a factor of twenty, keeping the drift below 44 ps. This is sufficient for QKD because the coincidence peak is only 80 ps wide and must remain inside a 120 ps coincidence window.","pith_inferences":["The 12 ps bound is the loop's own measurement of its residual drift; an independent time reference, such as common-view GNSS or a distributed optical clock signal, would be needed to verify that the absolute offset is really that small.","If the coincidence-peak estimator remains unbiased under asymmetric dispersion, detector jitter drift, or temperature-induced path changes, the same mechanism could serve as a self-contained time-transfer service for any two nodes equipped with single-photon detectors, not only QKD users.","At high losses, where coincidence integration takes more than a minute, a predictive clock-drift model or Kalman filter could maintain the 12 ps bound with sparser peak measurements, since rubidium clocks drift slowly and predictably.","In a multi-user entanglement network, each entangled pair defines a pairwise syntonization relation, so the same photon pairs could in principle be used to align clocks across more than two nodes without dedicated synchronization hardware."],"forward_implications":["Over a full 48-hour run, the residual clock drift stays below 12 ps, which keeps the 80 ps coincidence peak fully inside the 120 ps coincidence window and therefore preserves the optimal secret key rate.","The protocol tolerates an external perturbation that degrades one clock's passive stability by a factor of twenty, keeping the drift below 44 ps and the system QKD-ready.","Synchronization holds up to 32 dB of total transmission losses; beyond that, the loop needs more than 60 seconds to accumulate enough coincidences and the precision worsens to worse than ±80 ps.","Dedicating a second wavelength channel to synchronization could raise the loss limit from 32 dB to about 48 dB, since the source can generate up to 40 pairs of 100 GHz channels.","Because the photon pairs carry the timing information, the protocol passively corrects optical path variations induced by temperature changes in the deployed fibers, a problem that standard synchronization methods must estimate and rectify separately."],"supporting_citations":[{"why":"Describes the deployed 48 km entanglement-based QKD testbed that the synchronization protocol runs on, including its 48-hour operation and single-photon detectors.","marker":"[7]"},{"why":"Introduces the photon-pair based synchronization protocol that this paper implements and demonstrates in the field.","marker":"[17]"},{"why":"Defines the BBM92 QKD protocol whose continuous secret key rate serves as the performance benchmark for the synchronization loop.","marker":"[18]"},{"why":"Provides the nonlocal dispersion compensation result that lets the authors neglect fiber dispersion in the coincidence-peak width calculation.","marker":"[20]"}],"fun_headline_variants":["QKD photons double as clock sync: 12 ps over 50 km","Entangled pairs align clocks to <12 ps on 48 km link","Photon coincidences discipline clocks to 12 ps over 50 km","Self-syncing QKD: photons keep clocks within 12 ps","Entangled photon pairs sync remote clocks to <12 ps"],"cache_read_input_tokens":3200,"weakest_assumption_plain":"The load-bearing premise is that the fitted coincidence peak is a precise and unbiased measure of the clock offset, combined with the assumption that the rubidium clocks drift slowly enough for corrections every few seconds to keep the residual under 12 ps.","fun_headline_variants_meta":{"raw":{"variants":["QKD photons double as clock sync: 12 ps over 50 km","Entangled pairs align clocks to <12 ps on 48 km link","Photon coincidences discipline clocks to 12 ps over 50 km","Self-syncing QKD: photons keep clocks within 12 ps","Entangled photon pairs sync remote clocks to <12 ps"]},"model":"deepseek-v4-flash","effort":"low","cost_usd":0.000745,"raw_usage":{"total_tokens":3279,"prompt_tokens":857,"completion_tokens":2422,"prompt_tokens_details":{"cached_tokens":384},"prompt_cache_hit_tokens":384,"prompt_cache_miss_tokens":473,"completion_tokens_details":{"reasoning_tokens":2328}},"tokens_in":473,"tokens_out":2422,"duration_ms":15485,"temperature":1.0,"reasoning_tokens":2328,"cache_read_input_tokens":384,"cache_creation_input_tokens":0},"cache_creation_input_tokens":0},"created_at":"2026-08-10T10:39:53.631764+00:00","model_set":{"reader":"deepseek-v4-flash"},"falsifier":"Feed both end stations an independent common time reference, such as common-view GNSS or a White Rabbit link, over the same 48-hour period and compare that reference to the clock offset reported by the QKD-based synchronization loop; any excursion beyond 12 ps in the difference would falsify the claim.","supporting_citations":[{"cited_title":"Pelet , author G","cited_arxiv_id":null,"evidence_quote":"Describes the deployed 48 km entanglement-based QKD testbed that the synchronization protocol runs on, including its 48-hour operation and single-photon detectors."},{"cited_title":"Ho , author A","cited_arxiv_id":null,"evidence_quote":"Introduces the photon-pair based synchronization protocol that this paper implements and demonstrates in the field."},{"cited_title":"Steinberg , author P","cited_arxiv_id":null,"evidence_quote":"Provides the nonlocal dispersion compensation result that lets the authors neglect fiber dispersion in the coincidence-peak width calculation."}],"review_version":1}