Every algorithm estimates a = sin θ ∼ U(0.1, 0.9) from Grover-depth-n measurements with p = cos²((2n+1)θ). The score is a constant: the error percentile times the resources used. Lower is better, and the frontier is what counts, not a single number.
| # | Algorithm | Track | Rounds | Deepest rung | Seq. depth | Total queries CQ | Sequential depth C̃ | Pareto | ||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| C68 | C95 | C99 | C̃68 | C̃95 | C̃99 | |||||||
An entry is Pareto-optimal in a frontier when no other entry is at least as good on all three percentiles and strictly better on one. A method can win on tails (C99) while losing on the bulk (C68), so a single rank hides most of the story.
Why C̃ and not ε · depth: multiplying every shot count by k divides ε by √k and multiplies queries by k, so ε · depth can be driven down at will while ε · queries goes up. The product ε² · depth · queries does not move. The depth that enters is the sequential one, the Grover depth a single processor must run in series: a non-adaptive schedule runs all its circuits in one parallel round, so its sequential depth is its deepest rung, while an adaptive method waits for each round before choosing the next and pays the sum. (The paper's parallel constant ε95 nmax ≈ 0.21 is the same idea at one shot on the deepest rung.)
The dashed green lines are the Cramér–Rao floor of the flagship ladder itself, , averaged over the scales. They bound what any estimator can do on that schedule (the paper's exact ML sits within a few percent of them) and say nothing about other schedules: an adaptive method that spends fewer queries on disambiguation can legitimately go below them. No universal floor for the query constant is drawn.
Depth is capped at nmax for every track, so a method cannot lower its query constant by running deeper circuits than the schedules it is compared with. Sequential rounds are not capped; they show up in C̃.
Two kinds of rows. Literature baselines are reference methods from published papers, regenerated by leaderboard/populate_baselines.py on the public holdout seed. Challenge submissions arrive as pull requests under leaderboard/submissions/, pass the sandboxed verifier, and are certified by CI on a blind HMAC-derived seed, . Both kinds compete on the same frontier; the Source filter and the tag under each name tell them apart.