{"id":"7219eb70-abad-441d-ba97-8025944cdd09","arxiv_id":"2508.12173","paper_version":1,"verdict":"REJECT","confidence":"HIGH","novelty_score":6.0,"correctness_risk":"high","formal_verification":"none","parameter_count":0,"one_line_summary":"The abstract promises a new consensus protocol called Carry-the-Tail, but the full text is an unrelated paper about robot energy efficiency, so the protocol claims are unsupported.","lead":"This submission's abstract announces a new consensus protocol, Carry-the-Tail, claimed to defend against tail-forking attacks with linear steady-state communication. The provided full text, however, is an unrelated systematic review of robotics software energy efficiency, so the protocol and its proof never appear in the paper.","discovery_kind":"new_method","skeptic_critique":{"model":"deepseek-v4-flash","headline":"Provided full text is an unrelated robotics SLR; the abstract's consensus-protocol claims have no specification, pseudocode, or proofs in the manuscript body.","rationale":"The reader's verdict of REJECT with HIGH confidence is well-founded. The weakest assumption identified is that the full text is the body of the paper described by the abstract; this is empirically false. My independent reading confirms the mismatch: the provided text is an unrelated robotics SLR. There is no technical error to find in a protocol that is absent. The robotics SLR may have its own merits (e.g., a replication package, transparent LLM-assisted methodology, acknowledged limitations), but it cannot substantiate the consensus-protocol claims. The central claim therefore fails at the most basic level of support. My proposed string-search check would conclusively demonstrate this mismatch and is quick to run. No other concern is more load-bearing: if the correct paper were supplied, the analysis might change, but as submitted there is nothing to evaluate. Thus the appropriate verdict is REJECT, unchanged from the reader's assessment.","tokens_in":18553,"tokens_out":3065,"duration_ms":29959,"concrete_test":"Run a string search over the entire full text for: 'Carry', 'tail-fork', 'HotStuff', 'atomic broadcast', 'partial synchrony', 'GST', 'Byzantine', 'quorum', 'leader'. If fewer than three of these terms appear outside the abstract, and if no section contains pseudocode or a theorem/proof environment proposing the protocol, then the manuscript body does not implement the abstract. A stronger confirmation is to fetch the actual arXiv record for 2508.12173; if its source differs, the submission is a corrupted/wrong file and the review should be redone with the true paper.","verdict_should_be":"REJECT","load_bearing_attack":"Central claim: 'Carry-the-Tail, the first deterministic atomic broadcast protocol in partial synchrony that, after GST, guarantees a constant fraction of commits by non-faulty leaders against tail-forking attacks, and maintains optimal, worst-case quadratic communication under a cascade of faulty leaders.' For this to be true, the manuscript must contain a precise protocol definition, a partial-synchrony/GST model, leader and quorum rules, correctness proofs for the commit-fraction and communication guarantees, and ideally an evaluation. The provided full text is 'Energy Efficiency in Robotics Software: A Systematic Literature Review (2020-2024)' by Aryan Gupta. It describes an SLR methodology, 79 primary studies, energy models, and technique families; it never mentions consensus, HotStuff, tail-forking, Byzantine faults, GST, or atomic broadcast. Therefore the central claim has zero derivational support in the submission. This is not a subtle technical flaw but an internal inconsistency between the abstract's promises and the body. The title, author list, and abstract describe one paper; the full text is another. This mismatch makes the claim unverifiable as submitted and is the single most load-bearing concern.","agreement_with_reader":"agree"},"referee_report":{"model":"deepseek-v4-flash","summary":"The arXiv submission (2508.12173) is presented as a computer science systems paper titled 'Carry the Tail in Consensus Protocols'. The abstract claims a deterministic atomic broadcast protocol for partial-synchrony systems that, after GST, guarantees a constant fraction of commits by non-faulty leaders against tail-forking attacks, maintains optimal worst-case quadratic communication under cascades of faulty leaders, and provides linear amortized communication as a drop-in mechanism for HotStuff-family protocols. The full text, however, is an unrelated systematic literature review titled 'Energy Efficiency in Robotics Software: A Systematic Literature Review (2020-2024)' by Aryan Gupta. The body contains no protocol specification, no pseudocode, no model definitions, no theorems, no proofs, no complexity analysis, and no evaluation of any consensus protocol. The terms 'consensus', 'atomic broadcast', 'HotStuff', 'tail-forking', 'Byzantine', and 'GST' do not appear in the full text. The manuscript therefore does not support its abstract claims at all.","tokens_in":18735,"tokens_out":2573,"duration_ms":28238,"significance":"If the abstract claims were true, the work would be a meaningful contribution to Byzantine fault-tolerant consensus: a protocol that mitigates tail-forking attacks while preserving linear steady-state communication and quadratic worst-case complexity would improve on known trade-offs that require SNARKs or quadratic communication steps. However, because the manuscript body is a different paper on robotics software energy efficiency, the substantive consensus claims cannot be evaluated. The robotics SLR itself appears methodologically careful, with a documented LLM-assisted pipeline, human audits, and a replication package, but it is out of scope for this submission's title and abstract and provides no evidence for the consensus claims. The 'first' claim in the abstract is unverifiable from the submitted text.","major_comments":[{"comment":"The abstract promises a deterministic atomic broadcast protocol called Carry-the-Tail, with specific guarantees against tail-forking attacks, but the full text is a systematic literature review on energy efficiency in robotics software. No protocol, algorithm, or mechanism named 'Carry' is defined anywhere in the body. The central claim therefore has zero derivational support in the submitted manuscript.","section":"Abstract / Full Text"},{"comment":"The core guarantees—'constant fraction of commits by non-faulty leaders', 'optimal worst-case quadratic communication', and 'linear amortized communication'—are asserted without any formal model of partial synchrony, GST, adversary structure, leader election, quorum intersection, or complexity measure. The full text contains no equations, theorems, or proofs relevant to these guarantees. This is a load-bearing omission: the paper cannot be reviewed as a technical consensus paper in its current form.","section":"Abstract"},{"comment":"The claim that Carry-the-Tail is 'the first' deterministic atomic broadcast protocol with these properties cannot be checked because the manuscript contains no related-work discussion of consensus protocols. The reference list [1]–[95] covers only robotics energy efficiency, and the body never mentions prior atomic broadcast solutions, tail-forking attacks, or SNARK-based approaches. The novelty assertion is therefore unverifiable.","section":"Entire manuscript"}],"minor_comments":[{"comment":"The full-text author (Aryan Gupta) and title differ from the arXiv metadata for this submission. If this is a file-upload error, the correct manuscript should be provided; otherwise the submission is internally inconsistent.","section":"Metadata vs. full text"},{"comment":"The limitations listed in the robotics SLR apply to that review and are irrelevant to the consensus-protocol claims. This further confirms that the body and abstract describe different works.","section":"Section 4.5"}],"recommendation":"reject","confidential_remarks":"This is not a standard technical-review situation: the submitted full text is an entirely different paper. The mismatch between the abstract and the body cannot be fixed through revision; it requires the authors to submit the correct manuscript. I recommend rejection, or desk rejection, and an invitation to resubmit the actual Carry-the-Tail paper if it exists."},"author_rebuttal":null,"desk_editor":{"model":"deepseek-v4-flash","letter":"Two things to know up front. (1) The abstract and title describe a consensus protocol paper, but the full text is an unrelated systematic literature review on energy efficiency in robotics software. (2) As a result, the paper's central claims have no support anywhere in the manuscript. This is not a subtle technical weakness; it's a complete mismatch between the content and the metadata.\n\nWhat the paper does well: the SLR that actually constitutes the body is a competent secondary study. It has a transparent methodology, a replication package, LLM-assisted screening with human audits, and it honestly reports its limitations. In isolation, it is a credible piece of work, though it belongs in a different venue and under a different title.\n\nWhere it falls apart: none of the abstract's claims about Carry the Tail appear in the body. There is no protocol specification, no partial-synchrony model, no theorem statements, no proofs, no complexity argument, no evaluation. The phrase 'tail-forking' never appears. The reader's stress-test is accurate: the central claim is asserted and then the paper moves on to an unrelated subject. The author mismatch—the abstract lists Suyash Gupta, Dakai Kang, Dahlia Malkhi, and Mohammad Sadoghi, while the full text is by Aryan Gupta—reinforces that this is likely a submission error, but a reviewer can only judge the artifact as submitted. It is internally incoherent.\n\nWill this paper deserve a serious referee? Only if the authors resubmit the actual Carry-the-Tail paper. On the current submission, the answer is no: there is nothing to referee. The SLR portion might merit a separate review in the right setting, but it cannot carry the consensus-protocol claims. Recommendation: desk reject and invite the authors to resubmit with the correct full text if they have one.","headline":"The submission is two different papers: an abstract about a consensus protocol and a full text about robotics energy efficiency; the consensus claims have zero support in the manuscript.","tokens_in":19276,"tokens_out":2379,"would_cite":false,"duration_ms":26933,"reading_group":"no","serious_thinker":"no","would_accept_peer_review":false},"rs_alignment":null,"lean_confirmation":null,"pith_extraction":{"msc":[],"pacs":[],"model":"deepseek-v4-flash","headline":"The submission claims a new consensus protocol, Carry-the-Tail, that defeats tail-forking attacks with linear steady-state communication, but the supplied manuscript contains none of the protocol's specification or proofs.","keywords":["atomic broadcast","consensus protocols","partial synchrony","tail-forking attacks","HotStuff family","communication complexity","Byzantine faults"],"falsifier":"Search the supplied full text for the terms 'Carry', 'tail-forking', or 'atomic broadcast': none occur; the body is a robotics-energy literature review. That absence is decisive for the submission as given. For the underlying claim, the decisive check would be a simulation under partial synchrony where an adversary tail-forks honest leaders after GST: if the honest-leader commit fraction fails to stay constant, or if a cascade of faulty leaders drives communication beyond quadratic, the claimed guarantees fail.","tokens_in":18370,"feed_emoji":"⚠️","tokens_out":6532,"duration_ms":73861,"temperature":0.7,"pith_summary":"The submission sets out to prove that a mechanism named Carry-the-Tail can be inserted into HotStuff-family consensus protocols to neutralize tail-forking attacks: after the network reaches global stabilization time, non-faulty leaders would keep committing a constant fraction of proposals, with optimal quadratic worst-case communication and linear amortized traffic, and without the SNARK-based machinery of earlier defenses. That would matter because current atomic-broadcast protocols either suffer throughput collapse under tail-forking or pay quadratic communication steps or expensive zero-knowledge proofs to resist it. The manuscript as supplied does not support this aim: its full text is an unrelated systematic literature review about energy-efficient robotics software, and it never mentions, specifies, or proves the Carry mechanism. A sympathetic reader can see the intended contribution in the abstract, but the presented text provides no derivational content for it.","feed_headline":"Tail-forking fix claimed, but manuscript holds a different paper","feed_subtitle":"Abstract promises constant-fraction commits; the supplied body is an unrelated robotics survey with no proof.","key_machinery":"Carry is the named mechanism: described in the abstract as a practical, drop-in addition to streamlined protocols in the HotStuff family, meant to protect honest leaders' commits against tail-forking and to remove most leader-induced stalls. It is the load-bearing object of the claimed result—retrofitting it should yield the constant-fraction commit guarantee and the linear/quadratic communication bounds. No description of how Carry achieves this appears in the supplied text; the mechanism is named and claimed, not defined or analyzed.","core_discovery":"On its face, the paper claims to introduce Carry-the-Tail, the first deterministic atomic broadcast protocol for partial synchrony that, after a global stabilization time (GST), guarantees a constant fraction of commits by non-faulty leaders even under tail-forking attacks, while keeping worst-case communication quadratic under cascades of faulty leaders and linear in steady state. The payoff would be a drop-in defense for HotStuff-family protocols that avoids the quadratic communication steps or prohibitive SNARK generation of prior fixes. The supplied full text, however, is not this protocol: it is a systematic literature review on energy efficiency in robotics software, and it contains no","pith_inferences":["A reader should treat the abstract's numbers as unverified: the supplied body is a different study, so there is no evidence in this submission that the constant-fraction or communication guarantees hold.","If a full specification of Carry is provided later, the natural experiment is to run HotStuff-family implementations under a tail-forking adversary and measure honest-leader commit fraction and message complexity before and after GST; the paper supplies no such data.","The drop-in framing suggests that, if realized, the mechanism could also be adapted to other streamlined BFT protocols built on rotating leaders and chained certificates; this extension is not argued in the abstract."],"forward_implications":["HotStuff-family implementations could adopt Carry without changing their quorum structure or steady-state message pattern, keeping amortized communication linear.","Tail-forking resistance would become available without SNARKs, removing a computationally prohibitive component from existing defenses.","A cascade of faulty leaders would cost at most quadratic communication, so the protocol remains within the optimal worst-case bound while sustaining commits.","After GST, any stretch of non-faulty leaders would contribute a constant fraction of committed proposals, bounding the throughput damage a tail-forking adversary can inflict.","Because Carry is presented as drop-in, the defense would generalize across streamlined protocols rather than requiring a new consensus core."],"supporting_citations":[],"fun_headline_variants":["Consensus paper's body: robotics survey, no proof","Atomic broadcast abstract, robotics survey inside","Abstract promises protocol, body delivers literature review","Carry-the-Tail: abstract mismatch, no protocol in paper"],"cache_read_input_tokens":2816,"weakest_assumption_plain":"The load-bearing premise is that the submission actually contains the Carry-the-Tail protocol—its precise rule, pseudocode, and proofs—so the abstract's guarantees can be checked; the supplied text contains none of this, so as presented the central claim has nothing to rest on.","fun_headline_variants_meta":{"raw":{"variants":["Consensus paper's body: robotics survey, no proof","Atomic broadcast abstract, robotics survey inside","Abstract promises protocol, body delivers literature review","Carry-the-Tail: abstract mismatch, no protocol in paper"]},"model":"deepseek-v4-flash","effort":"low","cost_usd":0.000366,"raw_usage":{"total_tokens":1758,"prompt_tokens":654,"completion_tokens":1104,"prompt_tokens_details":{"cached_tokens":256},"prompt_cache_hit_tokens":256,"prompt_cache_miss_tokens":398,"completion_tokens_details":{"reasoning_tokens":1051}},"tokens_in":398,"tokens_out":1104,"duration_ms":10885,"temperature":1.0,"reasoning_tokens":1051,"cache_read_input_tokens":256,"cache_creation_input_tokens":0},"cache_creation_input_tokens":0},"created_at":"2026-08-05T19:35:46.903737+00:00","model_set":{"reader":"deepseek-v4-flash"},"falsifier":"Search the supplied full text for the terms 'Carry', 'tail-forking', or 'atomic broadcast': none occur; the body is a robotics-energy literature review. That absence is decisive for the submission as given. For the underlying claim, the decisive check would be a simulation under partial synchrony where an adversary tail-forks honest leaders after GST: if the honest-leader commit fraction fails to stay constant, or if a cascade of faulty leaders drives communication beyond quadratic, the claimed guarantees fail.","supporting_citations":[],"review_version":1}