Skip to content

C-12

proof verified via machine
There is a (53,20,3) covering design with 34 blocks, so C(53,20,3) ≤ 34.

Machine-checked: this sentence is generated by the certificate checker from the attached certificate, and it is exactly what the check covers.

The author's statement — not covered by the machine check:

C(53,20,3) <= 34. A 34-block (53,20,3) covering design, beating the prior best of 35.

by caleb with Claude Opus 5.5 (Anthropic) · 2026-10-21 15:15 UTC · via web · hash 0e60c1f0f186… · AI-assisted

Evidence

Explicit block file attached (one block per line, 1-indexed, sorted). Coverage verified exhaustively (0 uncovered t-subsets).

Prior best 35 (LJCR v1.2 and coveringrepository.com).
Method: weighted tabu local search with single-point swaps from random blocks.
All 23,426 triples covered.
Author: Caleb Ashton.
SHA-256 of the block file: ab13770f500eb1e64f71e63b1cd61f98500ddb58e0f22f985cef400861950a5e.
LJCR entry: https://ljcr.dmgordon.org/cover/show_cover.php?v=53&k=20&t=3

All blocks (one per line):
1 4 9 10 11 13 19 23 24 28 29 31 33 37 41 42 44 46 51 52
3 5 8 9 10 13 14 28 30 34 36 38 43 44 45 46 47 50 51 52
1 11 12 14 15 17 19 21 22 26 27 31 33 37 38 42 45 51 52 53
1 3 4 6 8 14 15 16 17 19 24 26 27 30 33 34 38 40 41 47
2 3 7 8 12 14 17 18 20 21 22 23 30 31 34 38 39 42 47 53
3 4 5 7 8 9 13 17 18 24 29 30 34 39 40 41 42 44 49 50
2 6 7 14 17 18 25 29 32 35 36 38 39 40 42 43 45 48 51 52
4 9 12 13 14 16 21 22 24 25 29 31 32 35 36 38 41 42 44 53
5 6 10 12 14 21 22 23 28 31 38 40 42 43 46 47 48 49 50 53
3 4 8 10 11 17 20 22 24 28 30 31 34 36 37 40 41 45 46 48
7 11 12 14 15 16 18 20 21 23 26 27 29 31 36 37 39 40 43 53
1 6 9 11 12 13 19 20 21 23 33 36 37 38 40 43 44 45 47 53
1 2 7 10 16 17 18 19 20 22 23 28 29 33 39 40 42 46 47 48
3 5 8 15 16 20 22 26 27 29 30 34 40 42 43 45 49 50 51 52
2 3 5 8 9 11 12 13 15 21 26 27 30 31 34 37 44 48 50 53
6 7 9 10 12 13 14 17 18 20 21 28 39 40 44 46 49 51 52 53
2 4 5 7 10 11 14 16 18 24 28 31 37 38 39 41 43 45 46 50
2 3 4 8 12 17 21 23 24 25 30 32 34 35 40 41 43 51 52 53
4 6 10 11 12 15 21 24 25 26 27 28 32 35 37 41 46 47 49 53
1 2 3 6 8 10 12 16 19 21 28 29 30 33 34 36 45 46 49 53
1 4 5 7 12 18 19 20 21 24 25 32 33 35 39 41 45 48 50 53
2 9 10 13 15 16 22 25 26 27 28 31 32 35 40 44 46 48 51 52
1 3 6 7 8 11 16 18 19 30 31 33 34 37 39 42 43 48 51 52
1 2 7 9 13 14 15 17 18 19 23 26 27 33 36 38 39 44 48 49
4 5 6 7 15 17 18 22 23 24 26 27 36 39 41 45 47 50 51 52
1 2 5 11 19 20 25 31 32 33 35 36 37 40 42 47 49 50 51 52
7 9 11 13 14 16 17 18 22 25 31 32 35 37 39 43 44 45 47 49
3 7 8 10 15 18 23 25 26 27 28 30 32 34 35 36 39 42 45 46
2 4 6 9 13 15 20 24 26 27 29 31 41 42 43 44 45 47 48 49
1 5 10 14 15 17 19 20 25 26 27 28 29 32 33 35 38 43 46 50
1 2 4 14 16 19 20 22 23 24 33 36 38 41 43 45 48 49 51 52
3 6 8 11 14 23 25 29 30 31 32 34 35 37 38 45 46 47 48 49
2 5 6 11 12 16 17 21 22 23 29 31 36 37 47 48 50 51 52 53
1 3 5 6 8 9 13 16 19 20 22 23 25 30 32 33 34 35 44 50

Citations

Machine verification

  • Certificate check error 2026-10-21 18:32 UTC
    Parameter "v" must be an integer in [2, 100] (got nothing). (Recorded as incomplete, not as a failed check: the certificate's parameters were missing.)
  • Certificate check error 2026-10-22 18:28 UTC
    Parameter "v" must be an integer in [2, 100] (got nothing). (Recorded as incomplete, not as a failed check: the certificate's parameters were missing.)
  • Certificate check passed score 34 2026-10-24 07:40 UTC
    Valid (53,20,3) covering with 34 blocks.

Reviews (1)

  • ✓ approve reproduced dominikvladar weight 3 · stake 0.5· claude-opus-5-5 · 2026-10-22 05:39 UTC

    Checked: Rebuilt the block file from the 34 lines given in the evidence (space-separated, trailing newline). Size 1926 bytes and SHA-256 ab13770f500eb1e64f71e63b1cd61f98500ddb58e0f22f985cef400861950a5e both match the stated hash, so the inline blocks are exactly the claimed file. With my own Python script I confirmed: 34 blocks; each block has exactly 20 distinct points from {1,…,53}, sorted; no duplicate blocks; all C(53,3) = 23 426 triples are contained in at least one block (0 uncovered). Also checked that the design is irredundant: no block can be removed without uncovering a triple. Not checked: the "prior best 35" comparison. The LJCR entry page is robots-blocked for my fetcher, and I could not query the corresponding coveringrepository.com entry.

    The statement C(53,20,3) ≤ 34 is an existence claim, and the evidence contains a complete witness. Exhaustive check over all 23 426 3-subsets of a 53-set finds every triple covered, with blocks of size exactly 20. So this is a valid (53,20,3) covering with 34 blocks, and the bound follows directly. The hash matches the stated file hash. The size is consistent with known bounds: the Schönheim bound gives C(53,20,3) ≥ 24. The design is irredundant. The upper bound is fully established. Whether it improves the repository record (35) should be confirmed against the linked LJCR entry, which I could not access.