Validate submission b9bb8444-b9bf-402c-a5c6-df6edb0d4047 - #24
Closed
yukon-autoresearch[bot] wants to merge 1 commit into
Closed
Validate submission b9bb8444-b9bf-402c-a5c6-df6edb0d4047#24yukon-autoresearch[bot] wants to merge 1 commit into
yukon-autoresearch[bot] wants to merge 1 commit into
Conversation
Co-authored-by: gnuchev <859355+gnuchev@users.noreply.github.com>
Author
|
Benchmark workflow dispatched: view run #30943548230. |
Author
|
Scored 26508031557 — does not improve the current best 1486468554; not promoted.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Yukon submission
b9bb8444-b9bf-402c-a5c6-df6edb0d4047against https://github.com/Layr-Labs/ecdsafail-challenge at6909d15d5642acbc643e075fb7cae393ef8132ef.Current best score: 1486468554. This PR's own benchmark run scores the head commit;
the PR is merged automatically if the submission is accepted, and closed with the result otherwise.
Submitter note
Model: GPT-5.6
Q973 compact-KG plus division/CLZ-A fuse
Result
This submission keeps the 973-qubit compact Khattar-Gidney ancilla layout and
combines it with an independent division/CLZ-A compute-use-uncompute fusion.
The resulting circuit passes the complete trusted 9,024-shot challenge replay
with no classical, phase, or ancilla failures.
qubits * ToffoliAt equal qubit count this removes 1,084,568 average executed Toffolis, a
3.83% reduction relative to jieyilong's public Q973 submission
53dc92c(commit
d37c518). It also uses 356,472 fewer Toffolis than our earlier Q975point (
f19e8a1, 27,600,081 T), while using two fewer qubits.Model/agent: GPT-5.6 Codex, default agent reasoning effort. The work used
the Codex desktop coding agent and a small bounded RunPod CUDA canary for the
classical nonce screen. The GPU never received the challenge submission token
and never performed submission or trusted validation.
Starting point and hypothesis
The public Q973 route already had the low-qubit structure we wanted: the
target-684 thin schedule, the CLZ difference constant fold, and the compact
Khattar-Gidney prefix ancilla layout. Its trusted nonce was 1071 and its public
metric was 28,328,177 T at 973 qubits.
Separately, our trusted Q975 route contained a division/CLZ-A fusion selected
by
TRAILMIX_FUSE_DIV_CLZ_A=1. That transformation had already demonstrated alarge Toffoli reduction, but it had not been combined with the Q973 compact-KG
layout. The key hypothesis was structural rather than statistical: the
compact-KG qubit cut and the division/CLZ-A Toffoli cut act on different parts
of the circuit and should compose without increasing the peak qubit count.
The fusion avoids materializing and then separately consuming the division
CLZ difference. It deposits the A-side contribution at the use site and
reverses it in the inverse path after the controlled add restores the source
state. This ordering is load-bearing: depositing it too early in the inverse
path produces a reversible-looking circuit construction but incorrect replay.
Implementation
The editable changes are under
src/point_add.The Q973 route remains configured with its existing thin-schedule and
compact-KG settings:
TRAILMIX_THIN_SEED=278TRAILMIX_THIN_CLZ_WINDOW=78TRAILMIX_THIN_MARGIN=0TRAILMIX_Q_CAP=99TRAILMIX_Q_TARGET=684LOWQ_CLZ_DIFF_CONST_FOLD=1LOWQ_ONE_A_ELIM=1LOWQ_COMPACT_KGANC=1TRAILMIX_FUSE_DIV_CLZ_A=1enables the independent A-side fusion. Theshrunken-PZ state machine now has explicit helpers for signed constant
addition, A deposit/undeposit, and the fused CLZ-difference use. Forward and
inverse division substeps use those helpers in matched order.
The existing local adjacent identical Toffoli cancellation remains enabled.
On the final source it reports:
The final tail nonce is baked into the route as
TRAILMIX_TAIL_NONCE=19501. This nonce was discovered only after freezingthe exact final 82,696,871-operation prefix; changing circuit structure
invalidates the nonce and requires a new search.
Experiments and course corrections
Adjacent cancellation alone was not sufficient
Starting from the public Q973 source, adjacent identical CCX/CCZ cancellation
removed 238,184 operations and produced a nominal Q973 / 28,089,993 T circuit.
However, the inherited/fast-screen nonce did not pass trusted replay: it had
two classical and two phase failures. A stricter CPU guard rejected that nonce,
and a bounded 20,000-nonce guard-1 scan found no candidate. I retired that lane
rather than spending more CPU time on it.
The first fusion port exposed an inverse-ordering bug
The first graft compiled and built, but all 9,024 trusted shots failed. This was
not treated as a nonce problem. Comparing forward and inverse dataflow showed
that the inverse implementation deposited the A contribution before the
controlled add had restored A. Moving the deposit after that restoration fixed
the semantic error.
With the corrected ordering, the inherited nonce produced only eight
classical and four phase failures and no ancilla failures. That pattern was
consistent with a correct unitary plus an unsuitable tail nonce, so a bounded
nonce search was justified.
A bit-exact GPU prefilter was parity-gated before use
Building and evaluating a multi-gigabyte operation stream per nonce is too
expensive. I therefore dumped the exact final circuit's SHAKE prefix state and
effective/raw shrunken-PZ schedules, then used the existing CUDA support
screen. The screen is deliberately only a necessary condition; every survivor
still goes through the full trusted evaluator.
The dump self-checks were:
The immutable canary archive was 872,499 bytes with SHA-256:
On a single Secure Cloud RTX A6000, compiled for native
sm_86, both paritygates passed before the search began:
The canary found
CLEAN nonce=19501after scanning 20,480 nonces. The searchwas stopped immediately, its logs were downloaded, and the Pod was deleted.
There were zero active Pods after cleanup. The support-clean result was never
considered validation by itself.
An infrastructure issue also surfaced during this canary: the old Pod request
overrode the current RunPod image's own
PUBLIC_KEY/SSH initialization with anexplicit
/usr/sbin/sshdcommand, causing a restart loop. Removing that staleoverride produced a stable Pod. This did not affect circuit results, but it is
useful reproducibility context for anyone reusing older automation.
Trusted validation
Nonce 19501 was first tested by rebuilding the exact final stream with an
environment override. It passed:
I then baked nonce 19501 into the source, rebuilt
build_circuitandeval_circuitfrom source with no nonce environment override, regenerated the4,631,024,792-byte
ops.bin, and repeated the full trusted replay. It producedthe same Q973 / 27,243,609 T metrics and the same 0/0/0 result.
Finally, the current ECDSA.fail CLI (
v2026.08.03-4) ran the official benchmarkfrom the repository root:
The official run rebuilt through the benchmark's WSL toolchain and independently
reported all 9,024 shots OK, 973 qubits, and 27,243,609 average Toffolis.
Fresh-frontier check
Immediately before submission I refreshed
ecdsafail submissions --all.The relevant public points were still:
53dc92cf19e8a1Therefore this is a strict same-Q improvement over the public Q973 point and a
strict Q-and-T improvement over our Q975 point. On a rejected-submission Pareto
view, it should remove the non-ours Q973 point rather than merely add a nearby
point.
Reproduction
From the submitted repository with the current CLI:
The direct trusted binaries used during development were:
On Windows, the checked-out
benchmark.shandsetup.shmust have LF endingswhen invoked through WSL. This working tree had Git index LF but worktree CRLF;
normalizing those two non-editable harness scripts to LF did not change their
Git content and allowed the official CLI command to run normally.
Caveats and next steps
9,024-shot trusted replay and must not be used as an auto-submit predicate.
including a cancellation change, requires redumping/parity-gating and finding
a new nonce.
division/CLZ-A fusion composes with adjacent lower-qubit routes. Qualify each
structural route locally before opening any wider GPU search.
around the compact-KG path, but this submission intentionally avoids a long
parameter grind: it takes one clear structural composition and validates it
exhaustively.
The main lesson is that the Q973 compact ancilla cut and the Q975 CLZ-A
Toffoli cut were orthogonal enough to compose. The meaningful win came from
recognizing that structural independence, then using a small parity-proven
nonce canary only after the final circuit was frozen.
Need help on this PR? Tag
@codesmith-botwith what you need. Autofix is disabled.