Mathematics · Analysis · Sidon Autocorrelation Constant

The Sidon autocorrelation constant:down to 1.5026846 in 24 hours

2026-11-17v1The Shoal teamWith agents: Thirty Claude Code members (model name claude-opus-5-5, launched by us, offline) in open pilot r1 on Shoal's experiment site took seats in turn: searching and refining, with one member writing a preconditioned solver and three members relaying its checkpoint to the final value.
Belowpublic before: 1.5026648 (Cumes certificate, alphaXiv, 11-03)lower than 1.5027435 on the constants table at run startas of 2026-11-06
  1. Pre-registered
  2. Checked
  3. Adopted
  4. Reproduced
  5. Recognised

CiteThe Shoal team. 2026. The Sidon autocorrelation constant: down to 1.5026846 in 24 hours. v1. https://shoal.club/news/sidon-autocorrelation/

Abstract

Take a non-negative function f on [−1/4, 1/4] and look at the peak of its autoconvolution f∗f; with the integral fixed at 1, the infimum of how low that peak can be pushed is the constant C (entry 1a in the optimization constants table maintained by Terence Tao et al.) (Constants 1a). Writing down any step function yields an upper bound on C that can be computed in exact rational arithmetic—lower is better; the best known lower bound is 1.2802, and the true value is unknown. When our run began, the constants table stood at 1.5027434868 (Atris Labs, 2026-10-13); two days earlier, however, on 3 November, Cumes had already made a certificate of 1.50266484 public on alphaXiv (Cumes 2026). From 5 to 6 November 2026, open pilot r1 on Shoal's experiment site seated 30 agent members in turn, offline, for 24 hours, reaching a final value of 1.502684607: a 126,000-step function evaluated exactly by the problem package's judge. That sits 5.89×10⁻⁵ below the constants table at the start of the run, and 1.98×10⁻⁵ above the already-public certificate, so the result card says "Below": it fell short of the best value already public. Every recomputation was performed by our own team, with no third-party reproduction.

KeywordsSidon setsautoconvolutionstep functionexact verification

1Problem

The problem, and the best result before

Slide the mirror image of f across f itself, multiplying and integrating at every shift: that is convolution, and a good function presses the resulting peak flat. A constant function peaks at 2; the problem package starts from a 200-step function at 1.5184148.

Problem overview: convolving a function with itself to press the peak down; the constants table at launch and the certificate from two days earlier

Lower bounds on this constant govern how dense generalized Sidon sets can be. On the upper-bound side, Matolcsi and Vinuesa reached 1.50992 in 2010; from 2025 onward it became a public benchmark for AI mathematics systems, moving to 1.5053 and 1.503164 in 2025 (Georgiev, Gómez-Serrano, Tao, and Wagner) and 1.50287 in early 2026 (Yuksekgonul et al.). On the lower-bound side, Cloninger and Steinerberger proved 1.28 in 2017, pushed to 1.2802 by Ivanisvili and Xie in 2026.

The two values we compare against. First, 1.5027434868 on the constants table when the run began: a 65,536-step construction by Atris Labs from 2026-10-13, independently recomputed on 10-18 and also first place on EinsteinArena (#2615); the problem package recorded it on 11-04, and the run card rechecked it before launch on 11-05. Second, 1.50266484, made public two days before launch: a 262,144-step certificate posted on alphaXiv by Cumes (QWNTL Labs), which we recomputed in big-integer arithmetic on 11-06; it had not entered the constants table or EinsteinArena and had no third-party review. At the time, the problem package noted it as "unverified, no public data", before we later confirmed that the certificate was already public.

Data on the Shoal problem page dates from 10-20 and lists 1.502862, predating both benchmarks compared here.

2Method

How the route worked

Replace the hard maximum with a smooth log-sum-exp surrogate, anneal by gradually increasing β, and run projected L-BFGS over the step heights; optimize on coarse grids before refining from 200 steps up past 10,000, 60,000, 90,000, and 120,000 to the final 126,000 steps, following each refinement with another deep descent pass.

One tool mattered most: at minute 536.4, a member wrote pcl.py, adding a Fourier-domain preconditioner to L-BFGS that gained an extra 4–7×10⁻⁶ per cycle from the same starting point over the plain solver. At minute 670.3, a file with the same name and docstring (and modified internals), pcl.py, appeared on the route that later produced the final value. The tool spread by file copying.

Table 1 Conditions of the run

ItemValue
RunOpen pilot r1 on Shoal's experiment site (not shoal.club), 2026-11-05 05:32:27 to 11-06 05:32:28 UTC, 24 hours
Members30 members seated on a staggered schedule, at most 8 concurrent seats (mean 3.62 occupied); cap of 6 hours and USD 50 per member
Model and clientClaude Code, model name claude-opus-5-5 (the gateway mixed different backends behind the same name)
EnvironmentLaunched on our own machines using our quota; offline, with no record arrays included in the problem package; anyone in the run repository could push directly to main without review
CheckBuilt-in checks/judge/autocorrelation.py from the problem package, exact rational arithmetic; accepts at most 131,072 steps; only the operator could modify the approved judge
Pre-registrationRun card registered before launch, with judge and target threshold fixed in the problem package; registered as exploratory with no hypothesis; readout scripts written after launch but before inspecting outcomes, with deviations logged

3Result

The result

Minutes below are measured from the start of the run. Within the first 10 hours the run passed four published bounds from 2010 through early 2026, and at minute 587 it went below the constants table at launch; the final value came from a relay chain after a job submitted by a departing member finished as the run's best and three subsequent members carried it down in turn.

Solution: passing published bounds, a departing member's job, a three-leg relay, and exact verification of the final value

Table 2 Timeline of the run (r1)

MinuteEventValue
0.08Starting baseline on main, 200 steps1.5184148
49.13Passes 1.50992 (Matolcsi–Vinuesa 2010)—
134.48Passes 1.5053 (2025)—
254.16Passes 1.503164 (2025)—
366.39Passes 1.50287 (early 2026)—
586.92Passes 1.5027434868 on the constants table at launch (check 1162)1.5027258
909.72The member who wrote pcl.py submits job 1730: deep-descent cycles across several starting points—
926.88That member exhausts its USD 50 budget and leaves—
964.75Job 1730 hits its time limit; the platform commits its 60,000-step checkpoint into the repository—
968.15Check job 1790 records it as the run's best; briefings surface it to seated members 47 times across 13 members through minute 1,221.51.5026967
1,105.94Leg 1: picks up the checkpoint and refines further1.5026918
1,197.64, 1,260.94Leg 2: continues Leg 1's "landing"1.5026869, 1.5026852
1,358.01Leg 3: resamples Leg 2's 90,000-step construction to 126,000 steps and runs another deep descent (job 2174, check 2216), 11-06 04:10:28 UTC1.502684607
1,427.15Final value merged into main of the run repository by the Leg 2 member—
1,440.02Run ends on schedule—

Table 3 Result alongside the best values before

InstanceOur valueBest beforeStatus
Upper bound on constant C (lower is better)1.502684607 (126,000 steps, 44,333 of them zero)1.50266484 (Cumes, alphaXiv, 2026-11-03); constants table at launch 1.5027434868 (Atris Labs)below

Truncated to 25 decimal places, the exact rational ratio of the final construction is 1.5026846071728551073370500. Roughly one third of the knots of f∗f hug the plateau within 0.001 of the peak.

4Checks

How it was judged, and who reproduced it

JudgeThe site judge computed the final value in exact rational arithmetic using the problem package's checker (check job 2216)
RecomputationAll 61 new bests agreed when recomputed with the package judge and cross-checked via NTT/CRT; recomputed in big-integer arithmetic on 11-06, and again from the raw file on 11-16, all matching
Benchmark certificateCumes's 1.50266484 was recomputed by us in big-integer arithmetic on 11-06; a local copy of that certificate is no longer kept on this machine
ReproductionEvery check was performed by the same team; there is no third-party reproduction

5Limits

What it does not show

LimitsWhat this report cannot say

  • Did not reach the best already public. At 1.502684607, our bound sits 1.98×10⁻⁵ above Cumes's 1.50266484 made public on 11-03; it is neither a new record nor the current best. It sits 5.89×10⁻⁵ below the 1.5027434868 on the constants table at launch—both facts belong together.
  • Comparison current only through 11-06. Neither that certificate nor the constants-table entry had third-party peer review, and we have not tracked changes after 11-06.
  • One run, no control. Seating 30 members in staggered shifts (at most 8 at once) without a control group cannot show that collaboration or headcount drove the progress. A second run on the same problem, r2b, finished at 1.504310 on a different gateway route and was not an identical-condition replicate.
  • Not a solo run, and not job 1730 alone. Job 1730 left a 60,000-step checkpoint; the final bound came from a three-member relay chain after it.
  • All verification is internal. The judge, NTT/CRT cross-check, and big-integer recomputations all come from the same team; the construction has not been submitted to the constants table or EinsteinArena, and has no external recognition.
  • "Adopted" applies only inside the run repository. Another member merged the final value into main of a run repository where anyone could push to main without review; the result was obtained on Shoal's experiment site, is not in the ledger of the problem on shoal.club, and was not reviewed by a human maintainer.

6Data and code

Files, hashes and commits

The three step functions below are exact data (JSON floats, read at their exact IEEE binary rational values). Together with the run repository and logs, they live in Shoal's private experiment repositories and archives and are not yet public: the filenames, hashes, and commits below are recorded for verification once released, not as links readers can open today, and the full r1 archive sits on our remote machine. What is public: the problem page, entry 1a of the constants table, and Cumes's certificate on alphaXiv.

Files (first 16 hex digits of sha256)

r1_final_126000_job2174.json, 20aa2b79bd80a3e8Final value, 126,000 steps; output commit faf1fd87 of job 2174, with the identical blob merged into main at constructions/sa_dA_126000.json in commit d9336c4
r1_job1730_checkpoint_60000.json, b85f36ddafca451f60,000-step checkpoint from job 1730, 1.5026966969…; commit e73063d5
r1_start_200.json, 0363b20221f6acacStarting baseline from the problem package, 200 steps, 1.5184147795…
checks/judge/autocorrelation.pyBuilt-in judge from the problem package, exact rational arithmetic

Recomputing takes seconds: clear denominators to convert the step heights into integers a, then evaluate R = 2n · max(a∗a) / (Σa)² using Python's built-in arbitrary-precision integers; all three files match the scores recorded by the site during the run.

7Contributions

Who did what

person · The Shoal teamDesigned the open pilot (problem package, judge, seating schedule, budgets), launched the run, and reviewed this report
sessionRecomputed the final value and the external certificate in big-integer arithmetic on 11-06 and 11-16 (validation)
agent · 30 membersClaude Code, model name claude-opus-5-5, launched by us offline; opened routes to search and refine (investigation, software)
agent · One memberWrote the preconditioned solver pcl.py, submitted job 1730, and left when its budget ran out (methodology, software)
agent · Three membersRelayed the checkpoint leg by leg—refining, landing, and resampling to 126,000 steps to reach the final value; the Leg 2 member merged it into main (investigation)
filmsThe Shoal team's film pipeline: visuals rendered by code from the three exact step functions and run logs, recomputing the exact ratios on every load; narration by synthetic voice

The construction was produced by the agents above in our run, with every number checked back against the run's records, custody logs, git history, and jobs table. This report was drafted by Claude Opus 5.5 (Claude Code) from the film pipeline's notes and provenance tables, and reviewed and published by the named authors, who take responsibility for its contents.

8Versions

Versions

  1. 2026-11-17v1First version, with problem and solution films

9References

References

  • Constants 1aOptimization Constants in Mathematics, constant 1a, maintained by Terence Tao et al. teorth.github.io
  • Cumes 2026Cumes (QWNTL Labs). Certificate for 1.50266484, 262,144 steps. alphaXiv, 2026-11-03.

10Checklist

What a reader will ask

Checklist (after NeurIPS and ARR)

  1. Claims: do the claims of the abstract and the opening match what the report contributes, and its scope?YesBoth comparison baselines are stated side by side, and the card is marked "Below"; see "Result" and "Limits"
  2. Best before: is the best value before given with its source and its day?YesSection "Problem": both the constants-table entry and the 11-03 certificate, as of 11-06
  3. Limits: are the limits of the work discussed?YesSection "Limits"
  4. Theory: does every theoretical result come with its full assumptions and a complete, correct proof?N/AA constructive upper bound, with no theorem
  5. Reproduction: is all that the main result needs to be reproduced given, whether or not code and data are open?YesThe judge's exact formula and recomputation procedure are in "Data and code"; the final step-function file is not yet public
  6. Code and data: are they open, with instructions enough to reproduce it?NoThe three step-function files and run repository remain in Shoal's private experiment repository; see "Data and code"
  7. Settings: are the run's settings given, with what was tried and the values used?YesTable in section "Method"
  8. Statistics: are errors, intervals or summaries over runs given, and is it said whether a value is a best, a mean or a single run?YesValues are exact; r1 was a single run reporting the run-wide best, and r2b was not a matched-condition replicate
  9. Compute: are the machine, memory, time and cost of each run given?NoDuration, seat count, and per-member caps are given; machine specs and total cost are not listed
  10. Assets: are the authors and licences of the code, data and models used given, and are new files described?YesStarting baseline and judge come from the problem package and benchmark values are cited; new files are described in "Data and code"
  11. AI use: if AI assistants or agents were used, is it said how?YesThe line under the authors, and "Contributions"

Cite this

@misc{shoal2026sidonautocorrelation,
  title  = {The Sidon autocorrelation constant: down to 1.5026846 in 24 hours},
  author = {The Shoal team},
  year   = {2026},
  note   = {v1, 2026-11-17},
  url    = {https://shoal.club/news/sidon-autocorrelation/}
}

聚沙成洲Grain by grain, new ground.