P95 · Packing and covering · Classic

Consecutive dominoes in a square

VERIFIED CONSTRUCTIONsquare side 28.000000000
n = 10Current record · open

Place n dominoes, the k-th a k × 2k rectangle (k = 1, …, n), without overlap in a square, moved and turned freely, so as to minimise the square's side.

Formal definition

  • ContainerThe closed square [0, side] × [0, side] with its lower-left corner at the origin, in units of the smallest domino's short side; dominoes may touch its sides
  • SubmissionThe square's side, side > 0, and the placement of exactly n dominoes: the k-th (k = 1, …, n) is the closed k × 2k rectangle, each used exactly once; every value has at most nine decimal places
  • PlacementEach piece may be moved and turned freely: rotated lays it flat (2k × k) or stands it up (k × 2k), then it turns counter-clockwise by θ about its lower-left corner (x, y), with tan(θ/2) = turn. cos θ and sin θ are rational, so every corner is rational and any orientation can be written
  • ConstraintsEvery piece's four corners lie in the square; no two pieces' interiors intersect (touching is allowed), decided by the separating-axis test on both pieces' edge normals. Everything is decided exactly in integers, never approximately
  • ScoreThe square's side, displayed to at most nine decimal places; smaller is betterS=side
  • ObjectiveMinimise the square's side over all valid arrangementsminSside

Getting a feel for it

The area and the longest piece

The dominoes cover 2(1² + 2² + … + n²) = n(n + 1)(2n + 1)/3 in all, so the side is at least the square root of that; the longest piece also needs a side of at least 2n, which is what decides n ≤ 4. At n = 41 the area bound is about 218.3, and the literature's 220 wastes less than 2% of the square: the large pieces set the frame, the small ones fill the gaps, and almost nothing is left over.

Literature records

Erich Friedman's table Consecutive Dominoes in Squares covers n = 1–41; every side is an integer and every pictured packing is axis-aligned. n = 1–4 are the trivial s = 2n; most of n = 5–24 are Friedman's own, from 1998 to 2014, with n = 20 by Maurizio Morandi in 2014, the one row the table says may not be optimal; n = 25–38 come from Matthew Sun and others in June 2026, with n = 26 improved by Ryan Chi and d/dx in September; and Rowan Jones added n = 39–41 in October 2026. This catalogue cites each row's value and author without reconstructing its configuration; every size starts from the site's ordinary shelf packing, behind the literature value and not the external record.

Source
ONE LEADERBOARD PER n

Current best solutions by n

Each parameter n is an independently scored sub-problem. Select any card to inspect the current record construction or submit a stronger solution.

Discussion (1) ↓
n1
CURRENT RECORD2
Optimal
Record holderqiboqi
Solution methodHuman
n2
CURRENT RECORD4
Optimal
Record holderqiboqi
Solution methodHuman
n3
CURRENT RECORD6
Optimal
Record holderqiboqi
Solution methodHuman
n4
CURRENT RECORD8
Optimal
Record holderqiboqi
Solution methodHuman
n5
CURRENT RECORD11
Proven optimum
Record holderqiboqi
Solution methodHuman
n6
CURRENT RECORD14
Proven optimum
Record holderqiboqi
Solution methodHuman
n7
CURRENT RECORD17
Proven optimum
Record holderqiboqi
Solution methodHuman
n8
CURRENT RECORD21best known 21
Matches the best known
Record holderqiboqi
Solution methodHuman
n9
CURRENT RECORD24best known 24
Matches the best known
Record holderqiboqi
Solution methodHuman
n10
CURRENT RECORD28best known 28
Matches the best known
Record holderqiboqi
Solution methodHuman
n11
CURRENT RECORD32best known 32
Matches the best known
Record holderqiboqi
Solution methodAI · OpenAI: GPT-6 Luna
n12
CURRENT RECORD37best known 37
Matches the best known
Record holderqiboqi
Solution methodAI · OpenAI: GPT-6 Luna
n13
CURRENT RECORD41best known 41
Matches the best known
Record holderqiboqi
Solution methodAI · OpenAI: GPT-6 Luna
n14
CURRENT RECORD46best known 46
Matches the best known
Record holderqiboqi
Solution methodAI · OpenAI: GPT-6 Luna
n15
CURRENT RECORD50best known 50
Matches the best known
Record holderNUE_13
Solution methodHuman
n16
CURRENT RECORD55best known 55
Matches the best known
Record holderCCHES
Solution methodAI · MoonshotAI: Kimi K2.6
n17
CURRENT RECORD60best known 60
Matches the best known
Record holderCCHES
Solution methodAI · MoonshotAI: Kimi K2.6
n18
CURRENT RECORD66best known 66
Matches the best known
Record holderCCHES
Solution methodAI · MoonshotAI: Kimi K2.6
n19
CURRENT RECORD71best known 71
Matches the best known
Record holderCCHES
Solution methodAI · MoonshotAI: Kimi K2.6
n20
CURRENT RECORD76best known 76
Matches the best known
Record holdercondor
Solution methodAI · OpenAI: GPT-6.1 Sol
n21
CURRENT RECORD82best known 82
Matches the best known
Record holdercondor
Solution methodAI · OpenAI: GPT-6.1 Sol
n22
CURRENT RECORD88best known 88
Matches the best known
Record holdercondor
Solution methodAI · OpenAI: GPT-6.1 Sol
n23
CURRENT RECORD94best known 94
Matches the best known
Record holdercondor
Solution methodAI · OpenAI: GPT-6.1 Sol
n24
CURRENT RECORD100best known 100
Matches the best known
Record holdercondor
Solution methodAI · OpenAI: GPT-6.1 Sol
n25
CURRENT RECORD106best known 106
Matches the best known
Record holdercondor
Solution methodAI · OpenAI: GPT-6.1 Sol
n26
CURRENT RECORD112best known 112
Matches the best known
Record holdercondor
Solution methodAI · OpenAI: GPT-6.1 Sol
n27
CURRENT RECORD118best known 119
Numerically ahead (under review)
Record holdercondor
Solution methodAI · OpenAI: GPT-6.1 Sol
n28
CURRENT RECORD125best known 126
Numerically ahead (under review)
Record holdercondor
Solution methodAI · OpenAI: GPT-6.1 Sol
n29
CURRENT RECORD132best known 132
Matches the best known
Record holdercondor
Solution methodAI · OpenAI: GPT-6.1 Sol
n30
CURRENT RECORD138best known 139
Numerically ahead (under review)
Record holdercondor
Solution methodAI · OpenAI: GPT-6.1 Sol
n31
CURRENT RECORD145best known 146
Numerically ahead (under review)
Record holdercondor
Solution methodAI · OpenAI: GPT-6.1 Sol
n32
CURRENT RECORD152best known 153
Numerically ahead (under review)
Record holdercondor
Solution methodAI · OpenAI: GPT-6.1 Sol
n33
CURRENT RECORD159best known 160
Numerically ahead (under review)
Record holdercondor
Solution methodAI · OpenAI: GPT-6.1 Sol
n34
CURRENT RECORD166best known 167
Numerically ahead (under review)
Record holdercondor
Solution methodAI · OpenAI: GPT-6.1 Sol
n35
CURRENT RECORD174best known 174
Matches the best known
Record holdercondor
Solution methodAI · OpenAI: GPT-6.1 Sol
n36
CURRENT RECORD181best known 182
Numerically ahead (under review)
Record holdercondor
Solution methodAI · OpenAI: GPT-6.1 Sol
n37
CURRENT RECORD189best known 189
Matches the best known
Record holdercondor
Solution methodAI · OpenAI: GPT-6.1 Sol
n38
CURRENT RECORD196best known 197
Numerically ahead (under review)
Record holdercondor
Solution methodAI · OpenAI: GPT-6.1 Sol
n39
CURRENT RECORD204best known 204
Matches the best known
Record holdercondor
Solution methodAI · OpenAI: GPT-6.1 Sol
n40
CURRENT RECORD212best known 212
Matches the best known
Record holdercondor
Solution methodAI · OpenAI: GPT-6.1 Sol
n41
CURRENT RECORD220best known 220
Matches the best known
Record holdercondor
Solution methodAI · OpenAI: GPT-6.1 Sol

Data and citation

All sub-problems in this family — authoritative scores, proof status, coordinates, and sources — are published at the stable URL below under CC BY 4.0. Because scores update as records fall, please cite the file's generatedAt timestamp.

GET https://minmaxarena.com/data/consecutive-dominoes-in-square.json

Cite the frozen 2026-10 edition: live records change, whereas a frozen edition stays fixed and reproducible.

GET https://minmaxarena.com/data/editions/2026-10/consecutive-dominoes-in-square.json
BibTeX (click to copy)
@misc{minmaxarena-consecutive-dominoes-in-square-2026-10,
  title  = {{Consecutive dominoes in a square} (P95)},
  author = {{MinMax Arena}},
  year   = {2026},
  note   = {Machine-verified records, 2026-10 edition},
  url    = {https://minmaxarena.com/data/editions/2026-10/consecutive-dominoes-in-square.json},
  license = {CC BY 4.0}
}
DISCUSSION

Discussion

Discuss strategies, share construction methods, or ask questions. Any signed-in user can post under their public byline and unique #UID. New posts appear after moderation.