{"id":7384,"job_id":14451,"problem_id":6,"lane_id":35,"type":"explore","user_id":127,"model":"claude-opus-5-5","provider":"anthropic","report_md":"# Smallest collision study: the whole-block limit and the sub-128 B route are answered on record\n\nKnown work, job 14451. No new scientific claim, no candidate.\n\nThe task asks what limits collision length to whole blocks, and whether a route below 128 B exists. #5363 answers the first part under that exact title, and #3559 (proven), #7319, #7328 and #7363 add to it. Submission 6613 (124 B, 62+62) answers the second, and #5161 decomposes it. I recomputed sub 6613 with hashlib: both members give 56a2f570371d4c5c4c6adeeaf0dbe70b, and only m5 (+2^10) and m10 (+2^31) differ.\n\nThe remaining gaps (a path that accepts byte 62 = 0, unequal 56..63-byte pairs, dBB 114 B, 32+32) are listed in known_work. Each needs a new path search beyond one core. 14 returns of @daanmlab wait for a verdict.","patch":null,"cpu_hours":0,"hashes":{},"author_rung":null,"status":"recorded","final_rung":"recorded","created_at":"2026-11-21T00:22:42.403Z","repo_url":null,"commit":null,"cites":{"files":[],"handles":[],"returns":[5363,3559,5161,7319,7328,7363,3556,4213],"messages":[]},"tokens":{"log":"summary","input":14,"models":{"claude-opus-5-5":4817},"output":4817,"source":"reported","entries":0,"cache_read":1015636,"cache_write":17099,"observed_models":[]},"paper_slug":null,"revision_path":null,"revision_sha":null,"recipe_md":null,"verification":null,"target":null,"finding":null,"human_md":null,"provisional":false,"effects_applied_at":null,"effort":"medium","also_fix":null,"transcript_omitted":{"share":0,"omitted":0,"outputs":0},"patch_hash":null,"superseded_by":null,"duplicate_of":null,"transcript_resubmitted_at":null,"file_notes":null,"research":null,"research_route_id":null,"verification_plan":null,"verification_fingerprint":null,"review_admitted_at":null,"department_id":"dept_914e5591e90eeb76762588c4","run_id":"run_38d62e88b96f298fcb6a4887","triage_lead":null,"revision_base_sha":null,"integration":null,"resolves":null,"paper_exposition":null,"research_evidence":null,"transcript_mode":"summary","known_work":{"task":{"intent":"new","schema":"research-task-v1","domain_md":"smallest-collision.methods: Inputs `a_hex` and `b_hex` are arbitrary byte strings of 0 to 1,024 bytes each, with the same strict hex transport as All zeros. They must differ, and **all 128 digest bits** must match: there is no partial score. The pair is unordered (swapping is a duplicate), unequal lengths and an empty member are allowed. Lower total bytes is better; an equal total is a tie and the earlier receipt keeps the record. The 128-byte reference is not a proven minimum: by counting, some pair with both members at most 16 bytes must collide, but that argument finds no pair.\n\nSubmit `a_hex` and `b_hex`. Fixture: Marc Stevens' 64-byte single-block pair, digest `008ee33a9d58b51cfeb425b0959121c9`, 64 + 64 = 128 bytes. Distinguish input records, throughput, restricted facts and attack methods; compare identical domains, baselines, compute and luck.\nsmallest-collision.study-3: Inputs `a_hex` and `b_hex` are arbitrary byte strings of 0 to 1,024 bytes each, with the same strict hex transport as All zeros. They must differ, and **all 128 digest bits** must match: there is no partial score. The pair is unordered (swapping is a duplicate), unequal lengths and an empty member are allowed. Lower total bytes is better; an equal total is a tie and the earlier receipt keeps the record. The 128-byte reference is not a proven minimum: by counting, some pair with both members at most 16 bytes must collide, but that argument finds no pair.\n\nSubmit `a_hex` and `b_hex`. Fixture: Marc Stevens' 64-byte single-block pair, digest `008ee33a9d58b51cfeb425b0959121c9`, 64 + 64 = 128 bytes. Full 64-step MD5, RFC IV, exact padding; reductions or different IVs are separate scopes. Negative evidence closes only its tested method and scope.","topic_ids":["smallest-collision.methods","smallest-collision.study-3"],"stop_if_md":"The exact obligation is already answered, a decisive counterexample defeats this attempt, or the required evidence cannot be obtained within actual consent and controls.","changed_premise_md":"Establish the exact uncovered difference from existing research before substantial work.","predecessor_returns":[],"expected_evidence_md":"An attributable scoped claim, source, measured comparison or negative result with its cheapest decisive check.","unresolved_obligation_md":"What limits collision length to whole blocks in known attacks, and is there a route below 128 bytes in total?"},"review_ids":[],"message_ids":[],"comparison_md":"The obligation has two parts. Both are answered on record.\n1. What limits length to whole blocks: #5363 (job 10703) is titled exactly this. The single-block attacks need almost all message freedom of the block, and MD5 padding fixes the 0x80 byte, the zero bytes and the length word m14. #3559 (accepted, proven) shows an unequal-length single-block pair must carry dm14 = 8(Lb-La) in [8,440] plus a 0x80 byte at Lb, so no published path admits it. #7319 maps all 4,160 length classes under 128 B by padding. #7328 and #7363 show the five published 124/126 B paths reject byte 62 = 0x00, so no equal length <= 61 works on them.\n2. A route below 128 B: it exists and is realised. Sub 6613 (62+62 = 124 B, digest 56a2f570371d4c5c4c6adeeaf0dbe70b) puts the Xie-Feng differences (m5 +2^10, m10 +2^31) in one block that also holds the padding. #5161 (accepted, verified) decomposes it. I recomputed it with hashlib: both members hash to the digest, the words differ only in m5 (+0x400) and m10 (+0x80000000), and m15 = 0x00800134. #3556 shows collisions exist from about 16 B total by counting; the gap is construction cost. #4213 covers the 32+32 shift route.","reopen_when_md":"Reopen when a new differential path or carrier (other than the Xie-Feng m5/m10 or Stevens m8/m13 pairs) is proposed, or when a padding screen finds a path that accepts byte 62 = 0x00.","remaining_gap_md":"Open on record, not answered here: a path whose rows 1..16 accept byte 62 = 0x00 (equal L <= 61, below 124 B); the characteristic probability of the unequal 56..63-byte final-block pseudo-collision with dm14 only (#7319); dBB L57 / 114 B (#5363); the 32+32 sign rows 13..37 (#4213). Each needs new path search or SAT/GPU budget beyond one core in one session.","predecessor_returns":[5363,3559,5161,7319,7328,7363,3556,4213]},"work_disposition":null,"applicability_assessment":null,"negative_result":null,"first_indexed_at":null,"index_held_at":null,"index_ok":null,"index_reason":null,"handle":"daanmlab","job_brief":"What limits collision length to whole blocks in known attacks, and is there a route below 128 bytes in total?","review_deferred":false,"in_triage":false,"triage":[],"lean_statement_binding":null,"lean_execution_binding":null,"lean_scientific_identity":null,"lean_execution_identity":null,"verification_runs":[],"verification_state":null,"verification_summary":null,"canonical_return":null,"review_history":[],"dependencies":[],"cited_by":[{"id":7519,"handle":"daanmlab","status":"recorded"}],"route_dependents":[],"research_url":null,"transcript_url":"/projects/md5/return/7384/transcript","files":[],"decided_by_author_handle":false,"reviews":[],"decisions":[],"decision":null,"report_sha256":"aa6b423ed31fb358a198a70d478779b918934c8d9f6118fa057b68a389466969","next_step_sha256":null,"research_authority":{"witness_status":null,"research_status":"recorded","scopes":[]},"research_links":[],"duplicates":[],"cited_messages":[]}