Fractran: Difference between revisions

From BusyBeaverWiki
Jump to navigation Jump to search
Int-y1 (talk | contribs)
add new section "Size 23: 11 Hydra-like Cryptids"
A6P457 (talk | contribs)
Size 36: BMO1: added step counts
 
(10 intermediate revisions by 6 users not shown)
Line 52: Line 52:


-d released a new decider on 25 Jan 2026: [https://discord.com/channels/960643023006490684/1438019511155691521/1464873923647639703 Beeping Permutation].
-d released a new decider on 25 Jan 2026: [https://discord.com/channels/960643023006490684/1438019511155691521/1464873923647639703 Beeping Permutation].
TODO: create pages about the deciders.


== Champions ==
== Champions ==
Line 237: Line 239:
\end{bmatrix}</math>
\end{bmatrix}</math>
|Jason Yuen (@-d) [https://discord.com/channels/960643023006490684/1438019511155691521/1439759182587891894 16 Nov 2025]
|Jason Yuen (@-d) [https://discord.com/channels/960643023006490684/1438019511155691521/1439759182587891894 16 Nov 2025]
|140 holdouts remain. [https://discord.com/channels/960643023006490684/1438019511155691521/1464873923647639703 25 Jan 2026]
|No holdouts remain. Claude Opus 4.6's proof of nonhalting of all the 140 holdouts: [https://discord.com/channels/960643023006490684/1438019511155691521/1485168251997786173 28 March 2026]
Claude Opus 4.6's proof of nonhalting of all the 140 holdouts: [https://discord.com/channels/960643023006490684/1438019511155691521/1485168251997786173 28 March 2026]
|-
|-
|22
|22
Line 252: Line 253:
\end{bmatrix}</math>
\end{bmatrix}</math>
|Shawn Ligocki (@sligocki) [https://discord.com/channels/960643023006490684/1438019511155691521/1448912286713384961 11 Dec 2025] and Jason Yuen (@-d)<sup>[https://discord.com/channels/960643023006490684/1438019511155691521/1448953682237460480 <nowiki>[1]</nowiki>]</sup>
|Shawn Ligocki (@sligocki) [https://discord.com/channels/960643023006490684/1438019511155691521/1448912286713384961 11 Dec 2025] and Jason Yuen (@-d)<sup>[https://discord.com/channels/960643023006490684/1438019511155691521/1448953682237460480 <nowiki>[1]</nowiki>]</sup>
|2003 holdouts remain. [https://discord.com/channels/960643023006490684/1438019511155691521/1464873923647639703 25 Jan 2026]
|3 holdouts remain. Claude Opus 4.6 gave a proof of all machines but the 3 Fenrir Cryptids, see [https://discord.com/channels/960643023006490684/1438019511155691521/1493027835559022824 Discord].
Claude Opus 4.6 gave a proof of all machines but the Fenrir-family, see [https://discord.com/channels/960643023006490684/1438019511155691521/1493027835559022824 Discord].
 
The holdouts list whose elements are exactly the three Fenrir Cryptids on Github: [https://github.com/int-y1/BBFractran/blob/main/holdout/sz22_3.txt sz22_3.txt]
The holdouts list whose elements are exactly the 3 Fenrir Cryptids on GitHub: [https://github.com/int-y1/BBFractran/blob/main/holdout/sz22_3.txt sz22_3.txt]
Known [[Cryptid|Cryptids]]:  
Known [[Cryptid|Cryptids]]:  


Line 275: Line 276:
Known [[Cryptid|Cryptids]]:  
Known [[Cryptid|Cryptids]]:  


# Frankenstein's Monster
# 11 Hydra-like Cryptids (including Frankenstein's Monster and Antihydra-like Cryptid)
# Antihydra-like Cryptid
|-
|24
|<math>> 9.263 \times 10^{9595}</math>
|<code>[18/35, 1/10, 11/5, 75/2, 49/3, 5/11]</code>
|<math>\begin{bmatrix}
    1 &    2 &    -1 &    -1 &    0 \\
  -1 &    0 &    -1 &    0 &    0 \\
    0 &    0 &    -1 &    0 &    1 \\
  -1 &    1 &    2 &    0 &    0 \\
    0 &    -1 &    0 &    2 &    0 \\
    0 &    0 &    1 &    0 &    -1
\end{bmatrix}</math>
|Shawn Ligocki (@sligocki) [https://discord.com/channels/960643023006490684/1438019511155691521/1540835921182728272 22 Aug 2026]
|No holdouts list yet.
 
An informal list from a 20%-complete enumeration: [https://discord.com/channels/960643023006490684/1438019511155691521/1540831684071530637 22 Aug 2026]
|}
|}


Line 419: Line 435:


<math display="block">C(2) \to C(4) \to C(7) \to C(11) \to C(16) \to C(23) \to C(32) \to C(44) \to C(60) \to \text{halt}</math>
<math display="block">C(2) \to C(4) \to C(7) \to C(11) \to C(16) \to C(23) \to C(32) \to C(44) \to C(60) \to \text{halt}</math>




Line 515: Line 534:


<math>A(0,2) \to A(1,3) \to A(4,2) \to A(11,3) \to A(29,2) \to A(74,1) \to A(186,2) \to A(466,3) \to A(1166,4) \to A(2916,5) \to A(7291,6) \to \dots</math>
<math>A(0,2) \to A(1,3) \to A(4,2) \to A(11,3) \to A(29,2) \to A(74,1) \to A(186,2) \to A(466,3) \to A(1166,4) \to A(2916,5) \to A(7291,6) \to \dots</math>
==== BBf(24) ====
The BBf(24) champion
<math>\begin{bmatrix}
1 & 2 & -1 & -1 & 0 \\
-1 & 0 & -1 & 0 & 0 \\
0 & 0 & -1 & 0 & 1 \\
-1 & 1 & 2 & 0 & 0 \\
0 & -1 & 0 & 2 & 0 \\
0 & 0 & 1 & 0 & -1
\end{bmatrix}</math> follows an unbiased [[Collatz-like]] pseudo-random walk: let <math>A(x,y) = [0,x,0,0,y]</math>
<math>[1,0,0,0,0] \xrightarrow{3} A(1,2)</math>
<math>A(x,0) \xrightarrow{x} halt</math>
<math>A(3x,y) \xrightarrow{15x+2} A(16x,y)</math> if y>0
<math>A(3x+1,y) \xrightarrow{15x+6} A(16x+5,y-1)</math> if y>0
<math>A(3x+2,y) \xrightarrow{15x+13} A(16x+11,y+1)</math> if y>0
<math>A(1,2) \to A(5,1) \to A(27,2) \to A(144,2) \to A(768,2) \to A(4096,2) \to A(21845,1) \to A(116507,2) \to A(621371,3) \to \dots</math>


== Cryptids ==
== Cryptids ==
Line 520: Line 562:
=== Size 22: Fenrir ===
=== Size 22: Fenrir ===
[[File:Fractran 22 Cryptid.webp|alt=The space-time diagram of Fenrir.|thumb|Partial space-time diagram of Fenrir.]]
[[File:Fractran 22 Cryptid.webp|alt=The space-time diagram of Fenrir.|thumb|Partial space-time diagram of Fenrir.]]
"Fenrir" is a family of 3 size 22 [[Cryptids]] discovered by Jason Yuen (@-d) and Claude Opus 4.6 on 22 Mar 2026. Out of 2003 holdouts of size 22, Claude Opus 4.6 used Lean to prove that 1997 holdouts were non-halting and 3 holdouts were halting. The remaining 3 holdouts are the Fenrir family.<sup>[https://discord.com/channels/960643023006490684/1438019511155691521/1485415054475268179]</sup> Discord user @ZTS439 shared [https://discord.com/channels/960643023006490684/1438019511155691521/1487251919444508723 some analysis] and a [https://discord.com/channels/960643023006490684/1438019511155691521/1487252789158613002 Python program] for it. Its name comes from [[wikipedia:Norse_mythology|nordic mythology]]; [[wikipedia:Fenrir|Fenrir]] is the wolf that helps destroy the world during [[wikipedia:Ragnarök|Ragnarök]].
"Fenrir" is a family of 3 size 22 [[Cryptids]] discovered by Jason Yuen (@-d) and Claude Opus 4.6 on 22 Mar 2026. Out of 2003 holdouts of size 22, Claude Opus 4.6 used Lean to prove that 1997 holdouts were non-halting and 3 holdouts were halting; the remaining 3 holdouts are the Fenrir family.<sup>[https://discord.com/channels/960643023006490684/1438019511155691521/1485415054475268179]</sup> Discord user @ZTS439 shared [https://discord.com/channels/960643023006490684/1438019511155691521/1487251919444508723 some analysis] and a [https://discord.com/channels/960643023006490684/1438019511155691521/1487252789158613002 Python program] for it. Its name comes from [[wikipedia:Norse_mythology|Nordic mythology]]; [[wikipedia:Fenrir|Fenrir]] is the wolf that helps destroy the world during [[wikipedia:Ragnarök|Ragnarök]].


{| class="wikitable"
{| class="wikitable"
Line 572: Line 614:
=== Size 23: 11 Hydra-like Cryptids ===
=== Size 23: 11 Hydra-like Cryptids ===


Define <math>Hydra(r_{num}, r_{den}, x_{offset}, y_{offset}, (x_{init}, y_{init}))</math> to be the problem as follows:
Define <math>Hydra(r_\mathrm{num}, r_\mathrm{den}, x_\mathrm{offset}, y_\mathrm{offset}, (x_\mathrm{init}, y_\mathrm{init}))</math> to be the problem as follows:


# The initial state is <math>(x_{init}, y_{init})</math>.
# The initial state is <math>(x_\mathrm{init}, y_\mathrm{init})</math>.
# The iteration <math>(x, y) \mapsto (r_{num} \times \lfloor x/r_{den} \rfloor + x_{offset}[x \bmod r_{den}], y + y_{offset}[x \bmod r_{den}])</math> is repeated.
# The iteration <math>(x, y) \mapsto (r_\mathrm{num} \times \lfloor x/r_\mathrm{den} \rfloor + x_\mathrm{offset}[x \bmod r_\mathrm{den}], y + y_\mathrm{offset}[x \bmod r_{den}])</math> is repeated. Here, <math>x_\mathrm{offset}, y_\mathrm{offset}</math> are 0-indexed.
# Are all the values of y non-negative?
# Are all the values of y non-negative?


Furthermore, the Hydra-like problem is considered a [[Cryptids|Cryptid]] if it also satisfies:
Furthermore, the Hydra-like problem is considered a [[Cryptids|Cryptid]] if it also satisfies:


# <math>y_{offset}</math> contains a negative number, and the average is positive.
# <math>y_\mathrm{offset}</math> contains a negative number, and the average is positive.
# <math>x \bmod r_{den}</math> is a pseudorandom sequence.
# <math>x \bmod r_\mathrm{den}</math> is a pseudorandom sequence.
# There are no negative values of y early on.
#There are no negative values of <math>y</math> early on.
 
For example, Fenrir is non-halting if and only if Hydra(5, 2, [2, 0], [-1, 2], (1, 0)). In this Hydra problem, the first few visited states are <math>(1, 0) \to (0, 2) \to (2, 1) \to (7, 0) \to (15, 2) \to (35, 4)</math>.


There are 11 Hydra-like Cryptids of size exactly 23, listed in the table below. All 11 Cryptids are not correlated with each other. Fenrir is included in the table as a reference.
There are 11 Hydra-like Cryptids of size exactly 23, listed in the table below. All 11 Cryptids are not correlated with each other. Fenrir is included in the table as a reference.
Line 610: Line 654:
|<code>[1/18, 4/15, 21/2, 121/3, 5/7, 2/11]</code>
|<code>[1/18, 4/15, 21/2, 121/3, 5/7, 2/11]</code>
|Hydra(5, 3, [1, 3, 4], [1, 3, -1], (1, 1))
|Hydra(5, 3, [1, 3, 4], [1, 3, -1], (1, 1))
|Slightly harder than Frankenstein's Monster
|If #47 doesn't halt then Frankenstein's Monster doesn't halt
|-
|-
|BBf(23): #77/694
|BBf(23): #77/694
Line 650: Line 694:
|<code>[4/15, 1/6, 21/2, 1331/3, 5/7, 2/11]</code>
|<code>[4/15, 1/6, 21/2, 1331/3, 5/7, 2/11]</code>
|Hydra(3, 2, [1, 2], [2, -1], (1, 2))
|Hydra(3, 2, [1, 2], [2, -1], (1, 2))
|Slightly harder than Antihydra-like Cryptid
|If #323 doesn't halt then Antihydra-like Cryptid doesn't halt
|}
|}


Line 678: Line 722:
\end{array}</math>
\end{array}</math>


with the only difference that the y values now change by {+1,+3,-1} depending on the value of x mod 3 (instead of {0,+1,-1} in the original size 22 program). The x values follow the exact same path as in the original size 22 champion, but the y values quickly grow linearly with the number of iterations (as expected by the random model):
with the only difference that the <math>y</math> values now change by <math>\{+1,+3,-1\}</math> depending on the value of <math>x\bmod 3</math> (instead of <math>\{0,+1,-1\}</math> in the original size 22 program). The <math>x</math> values follow the exact same path as in the original size 22 champion, but the y values quickly grow linearly with the number of iterations (as expected by the random model):
           0: S(0, 1)  @ 1  (0.00s)
           0: S(0, 1)  @ 1  (0.00s)
     100_000: S(10^22_185, 100171)  @ 10^22_186  (0.87s)
     100_000: S(10^22_185, 100171)  @ 10^22_186  (0.87s)
Line 761: Line 805:


<math display="block">\begin{array}{lcl}
<math display="block">\begin{array}{lcl}
   [1,0,\dots] & \to^* & A(1, 2) \\
   [1,0,\dots] & \xrightarrow{4}& A(1, 2) \\
   A(a, b) & \to^* & A(a-b, 4b+2) & \text{if } a > b \\
   A(a, b) & \xrightarrow{5b+4}& A(a-b, 4b+2) & \text{if } a > b \\
   A(a, b) & \to^* & A(2a+1, b-a) & \text{if } a < b \\
   A(a, b) & \xrightarrow{5a+2} & A(2a+1, b-a) & \text{if } a < b \\
   A(a, b) & \to^* & \text{Halt} & \text{if } a = b
   A(a, b) & \xrightarrow{a} & \text{Halt} & \text{if } a = b
\end{array}</math>
\end{array}</math>



Latest revision as of 09:51, 30 August 2026

Fractran (originally styled FRACTRAN) is an esoteric Turing complete model of computation invented by John Conway in 1987.[1] In this model a program is simply a finite list of fractions (rational numbers), the program state is an integer. For more details see https://en.wikipedia.org/wiki/FRACTRAN.

Discord user Coda came up with a way to transform any Fractran program into a Turing Machine, see source.

BB_fractran(n) or BBf(n) is the Busy Beaver function for Fractran programs. Holdouts lists by Daniel Yuan: Holdouts lists

Definition

A Fractran program is a list of rational numbers [q0,q1,,qk1] called rules and a Fractran state is an integer s. The numerator and denominator of any rational number fraction do not share any prime factors (they are in reduced form). We say that a rule qi applies to state s if sqi. If no rule applies, we say that the computation has halted otherwise we apply the first applicable rule at each step. In that case we say st and t=sqi and i=min{i:sqi}. As with Turing machines, we will write sNt if ss1sN1t (s goes to t after N steps) and s*t or s+t if sNt for some N≥0 or N≥1 (respectively). We say that a program has runtime N (or halts in N steps) starting in state s if sNt and computation halts on t.

Let Ω(n) be the total number of prime factors of a positive integer n. In other words, Ω(2a03a1pnan)=k=0nak. Then given a rule ab we say that size(ab)=Ω(a)+Ω(b). And the size of a Fractran program [q0,q1,,qk1] is k+i=0k1size(qi).

BB_fractran(n) or BBf(n) is the maximum runtime starting in state 2 for all halting Fractran programs of size n. It is a non-computable function akin to the Busy Beaver Functions since Fractran is Turing Complete.

Vector Representation

Fractran programs are not easy to interpret, in fact it may be completely unclear at first that they can perform any computation at all. One of the key insights is to represent all numbers (states and rules) in their prime factorization form. For example, we can use a vector [a0,a1,,an1]n to represent the number 2a03a1pn1an1.

Let the vector representation (for a sufficiently large n) for a state a=2a03a1pn1an1 be v(a)=[a0,a1,,an1]n and the vector representation for a rule ab be v(ab)=v(a)v(b)n (Note that this is just an extension of the original definition extended to allow negative ai).

Now, rule q applies to state s iff v(s)+v(q)n (all components of the vector are ≥0) and if st then v(t)=v(s)+v(q). So the Fractran multiplication model is completely equivalent to the vector adding model. For presentation, we will represent a Fractran program with a matrix where each row is the vector representation for a rule.

For example, the BBf(15) champion ([1/45, 4/5, 3/2, 25/3]) in vector representation would be:

[021201110012]

In this representation, it becomes much easier to reason about Fractran programs and describe general rules. It is also very easy to calculate the size of a rule or program in vector representation. It is the sum of absolute values of all elements in the matrix + number of rules (number of rows).

Relationship to VAS / Petri Nets

Using vector representation, Fractran programs are a deterministic version of Vector Addition Systems (VAS) (and, equivalently, Petri Nets). VAS are identical to Fractran programs in vector representation except that the rules are unordered and non-deterministic, they are used to model distributed systems where precise order of rule execution cannot be predicted. Interestingly, many problems about VAS are actually decidable, but their runtimes are extremely slow. Notably, the reachability problem (given states A and B are there a sequence of rules so that A*B) is "Ackermann-complete" meaning that the optimal algorithm has worst-case runtime akin to the famously fast-growing Ackermann function.[2]

Visualizing Fractran Programs' Space-Time Diagrams

Katelyn Doucette's Fractran space-time diagram visualizer produces the following space-time diagrams for some notable Fractran Programs, under the following principle: Each color represents a prime factor. Left -> right colors indicating the index of that register, and how wide the color is representing how big the value is at that step. Source code: https://github.com/Laturas/FractranVisualizer

The space-time diagram of Fenrir

The space-time diagram of Fenrir

The space-time diagram of Hydra.

The space-time diagram of Hydra.

The space-time diagram of the BBf(21) champion.

The space-time diagram of the BBf(21) champion. The width & height of the diagram can be set in the visualizer.

The space-time diagram of Space Needle.

The space-time diagram of Space Needle.

Deciders

Fractran deciders
All Fractran deciders summarized and their relations, shared by Daniel Yuan on 14 Nov 2025

Many specialized deciders have been invented to prove Fractran programs non-halting. See image at right. There are three extra deciders: Spanning Vectors Masked, which should be very effective, but implementing it is in-progress, a version of Spanning Vectors Masked - Masked Linear Invariant - which is very powerful, and some holdouts were removed by Shawn Ligocki with FAST (Fast Acceleration of Symbolic Transition systems), a pre-existing general tool.

-d released a new decider on 25 Jan 2026: Beeping Permutation.

TODO: create pages about the deciders.

Champions

The table of champions is split into two pieces: the first for small champions (up to BBf(14)) which all share the same relatively simple behavior (sequential programs) is collapsed by default; the second for champions BBf(15) and beyond which have more complex and varied behavior. All small champions as well as the first few larger ones were discovered and proven maximal by Jason Yuen (@-d) in their initial enumeration on 1 Nov 2025.

BBf(21) and below are solved. BBf(22) is the smallest domain to contain a Cryptid, and all other machines for BBf(22) are solved.

Small Champions
n BBf(n) Example Champion Vector Representation
2 1 [1/2] [1]
3 1 [3/2] [11]
4 1 [9/2] [12]
5 2 [3/2, 1/3] [1101]
6 3 [9/2, 1/3] [1201]
7 4 [27/2, 1/3] [1301]
8 5 [81/2, 1/3] [1401]
9 6 [243/2, 1/3] [1501]
10 7 [729/2, 1/3] [1601]
11 10 [27/2, 25/3, 1/5] [130012001]
12 13 [81/2, 25/3, 1/5] [140012001]
13 17 [81/2, 125/3, 1/5] [140013001]
14 21 [243/2, 125/3, 1/5] [150013001]
n BBf(n) Example Champion Vector Representation Champion Found Holdouts Proven
15 28 [1/45, 4/5, 3/2, 25/3] [021201110012] Jason Yuen (@-d) 1 Nov 2025 Jason Yuen (@-d) 1 Nov 2025
16 53 [1/45, 4/5, 3/2, 125/3] [021201110013] Jason Yuen (@-d) 1 Nov 2025 Jason Yuen (@-d) 1 Nov 2025
17 107 [5/6, 49/2, 3/5, 40/7] [1110100201103011] Jason Yuen (@-d) 1 Nov 2025 Daniel Yuan (@dyuan01) 3 Nov 2025
18 211 [5/6, 49/2, 3/5, 80/7] [1110100201104011] Jason Yuen (@-d) 4 Nov 2025 Jason Yuen (@-d) 8 Nov 2025
19 370 [5/6, 49/2, 3/5, 160/7] [1110100201105011] @creeperman7002 5 Nov 2025 Decider: Daniel Yuan (@dyuan01) 13 Nov 2025

3 Holdouts: Racheline & Shawn Ligocki

20 746 [7/15, 22/3, 6/77, 5/2, 9/5] [0111011001110111010002100] Jason Yuen (@-d) 13 Nov 2025 Decider: Jason Yuen (@-d)

(Enum+initial) Daniel Yuan (@dyuan01) 13 and 14 Nov 2025

Shawn Ligocki (@sligocki) 7 and 24 Dec 2025 6 Holdouts: Jason Yuen (@-d) 23 Dec 2025

21 31,957,632 [7/15, 4/3, 27/14, 5/2, 9/5] [01112100130110100210] Jason Yuen (@-d) 16 Nov 2025 No holdouts remain. Claude Opus 4.6's proof of nonhalting of all the 140 holdouts: 28 March 2026
22 >1.146×1062 [1/12, 9/10, 14/3, 11/2, 5/7, 3/11] [210001210011010100010011001001] Shawn Ligocki (@sligocki) 11 Dec 2025 and Jason Yuen (@-d)[1] 3 holdouts remain. Claude Opus 4.6 gave a proof of all machines but the 3 Fenrir Cryptids, see Discord.

The holdouts list whose elements are exactly the 3 Fenrir Cryptids on GitHub: sz22_3.txt Known Cryptids:

  1. Fenrir
23 >4.393×10124 [10/3, 9/14, 5/4, 121/2, 7/5, 3/11] [111001201020100100020011001001] Shawn Ligocki (@sligocki) 1 Jun 2026 21,295 holdouts remain. 2 Jun 2026

By August 5th, 2026, the unofficial holdouts count had been reduced to 13. sz23_13_unofficial.txt Known Cryptids:

  1. 11 Hydra-like Cryptids (including Frankenstein's Monster and Antihydra-like Cryptid)
24 >9.263×109595 [18/35, 1/10, 11/5, 75/2, 49/3, 5/11] [121101010000101112000102000101] Shawn Ligocki (@sligocki) 22 Aug 2026 No holdouts list yet.

An informal list from a 20%-complete enumeration: 22 Aug 2026

Behavior of Champions

Sequential programs

All champions up to BBf(14) have very simple behavior. They are all of the form: [3a12,5a23,,pnakpk1,1pk] or in vector representation (limited to k=4):

[1a100001a200001a300001a400001]

These champions repeatedly apply the rules in sequence, never going back to a previous rule. They apply the first rule until they've exhausted all 2s, then the second rule until they've exhausted all 3s, etc. They have a runtime of 1+a1+a1a2+a1a2a3+=i=0kj=1iaj and size 2k+2+i=1kai. This grows linearly for k=1 (BBf(5) to BBf(10)) and quadratically for k=2 (BBf(11) to BBf(14)). Letting k grow with the size, the maximum runtime grows exponentially in the program size.

BBf(15) Family

The BBf(15) and BBf(16) champions are members of a family of programs (parameterized by n1):

[02120111001n]

Let a = 2, b = 3, and c = 5.

The BBf(15) champion (n = 2) implements this iteration:

b00haltb17b4b27b5b35b2b45b3bk+53bk

which follows a permutation-like trajectory: a1b1b4b3b2b5b0halt

The BBf(16) champion (n = 3) implements this iteration:

b00haltb110b6b210b7b38b4b48b5b56b2b66b3bk+74bk

which follows a permutation-like trajectory: a1b1b6b3b4b5b2b7b0halt

BBf(17) Family

The BBf(17) to BBf(19) champions are members of a family of programs (parameterized by m,n0)

[1110100n0110m011]

which have size m+n+12

This family obeys the following rules:

  1. [1,0,0,0]1[0,0,0,n]
  2. if d≥1 and b≤m:[0,b,0,d]m+b+2[0,b+1,0,d1+n(mb)]
  3. if d≥1 and b≥m:[0,b,0,d]2m+2[0,b+1,0,d1]
  4. if d=0: [0,b,0,d] has halted

and furthermore these rules are applied in order since b is always increasing (and d is eventually decreasing). Combining these together we get runtime:1+n(m+1)(m(m+1)+2)m(m+1)2

The optimal choices for n,m for various program sizes are:

Size n m Runtime
16 1 3 51
17 2 3 107
18 2 4 211
19 2 5 370
20 2 6 596
21 3 6 904


BBf(20)

Full space-time diagram of the BBf(20) champion.

The BBf(20) champion (running 746 steps):

[0111011001110111010002100]

This program implements a Collatz-like iteration. Let C(n)=[0,0,n,2,0], then:

[1,0,0,0,0]49C(2)C(3k)3khaltC(3k+1)11k+22C(4k+3)C(3k+2)11k+22C(4k+4)

which follows the reasonably "lucky" trajectory:

C(2)C(4)C(7)C(11)C(16)C(23)C(32)C(44)C(60)halt





BBf(21)

The full space-time diagram of the BBf(21) champion until halting.
The full space-time diagram of the BBf(21) champion until halting.


The BBf(21) champion (running >31M steps): [01112100130110100210]

This program implements a Collatz-like iteration. Let D(n)=[0,0,n,0], then:[1] [1,0,0,0,0]1D(1)D(3k)khaltD(3k+1)21k+7C(10k+4)D(3k+2)21k+14C(10k+7)

which follows the reasonably "lucky" trajectory: D(1)D(4)D(14)D(47)D(157)D(524)D(1747)D(5824)D(19414)D(64714)D(215714)D(719047)D(2396824)D(7989414)halt

BBf(22)

The BBf(22) champion (running >1062 steps): [210001210011010100010011001001]

This program implements a Collatz-like unbiased pseudo-random walk. Let S(x,y)=[0,0,x,0,y], then:[2] [1,0,0,0,0]1S(0,1)S(x,0)=haltS(3k,y+1)14k+4S(5k+1,y+1)S(3k+1,y+1)14k+10S(5k+3,y+2)S(3k+2,y+1)14k+12S(5k+4,y)

This pseudo-random walk iterates 275 times until it halts reaching a maximum y value of 14 at iteration 111: S(0,1)S(1,1)S(3,2)S(6,2)S(11,2)S(19,1)S(33,2)S(56,2)S(94,1)S(158,2)S(264,1)S(441,1)S(736,1)S(1228,2)S(2048,3)S(4065328691604230522442358,13)S(6775547819340384204070598,14)S(11292579698900640340117664,13)S(27930059557111373800280446055462487109112535227834136644,2)S(46550099261852289667134076759104145181854225379723561074,1)S(77583498769753816111890127931840241969757042299539268458,2)S(129305831282923026853150213219733736616261737165898780764,1)S(215509718804871711421917022032889561027102895276497967941,1)S(359182864674786185703195036721482601711838158794163279903,2)S(5894430516013404355095519889620117404469367857588232386361874,2)S(9824050860022340591825866482700195674115613095980387310603124,1)S(16373418100037234319709777471166992790192688493300645517671874,0) If it were a truly random walk, there would be a 5.9% chance that it takes at least 275 steps to reach 0. So this program is mildly lucky.

BBf(23)

The BBf(23) champion [111001201020100100020011001001] follows an unbiased Collatz-like pseudo-random walk: let A(x,y)=[0,0,0,x,y]

[1,0,0,0,0]A(0,2)

A(2x,y)12x+4A(5x+1,y+1) if y>0

A(2x+1,y)12x+10A(5x+4,y1) if y>0

A(x,0)halt


A(0,2)A(1,3)A(4,2)A(11,3)A(29,2)A(74,1)A(186,2)A(466,3)A(1166,4)A(2916,5)A(7291,6)

BBf(24)

The BBf(24) champion [121101010000101112000102000101] follows an unbiased Collatz-like pseudo-random walk: let A(x,y)=[0,x,0,0,y]

[1,0,0,0,0]3A(1,2)

A(x,0)xhalt

A(3x,y)15x+2A(16x,y) if y>0

A(3x+1,y)15x+6A(16x+5,y1) if y>0

A(3x+2,y)15x+13A(16x+11,y+1) if y>0


A(1,2)A(5,1)A(27,2)A(144,2)A(768,2)A(4096,2)A(21845,1)A(116507,2)A(621371,3)

Cryptids

Size 22: Fenrir

The space-time diagram of Fenrir.
Partial space-time diagram of Fenrir.

"Fenrir" is a family of 3 size 22 Cryptids discovered by Jason Yuen (@-d) and Claude Opus 4.6 on 22 Mar 2026. Out of 2003 holdouts of size 22, Claude Opus 4.6 used Lean to prove that 1997 holdouts were non-halting and 3 holdouts were halting; the remaining 3 holdouts are the Fenrir family.[3] Discord user @ZTS439 shared some analysis and a Python program for it. Its name comes from Nordic mythology; Fenrir is the wolf that helps destroy the world during Ragnarök.

Holdout number Holdout Vector Representation
29/2003 [1/15, 27/77, 49/3, 10/49, 33/2] [0110003011010201012011001]
41/2003 [1/15, 49/3, 27/77, 10/49, 33/2] [0110001020030111012011001]
430/2003 [27/35, 1/33, 25/3, 22/25, 21/2] [0311001001012001020111010]

All 3 holdouts follow a biased random walk that somewhat resembles Hydra. Let S(x,y)=[x,0,0,2,y] (for 29/2003 and 41/2003) or S(x,y)=[x,0,2,y,0] (for 430/2003), then:

[1,0,0,0,0]S(0,1)S(0,2y)=haltS(x,2y)S(x1,5y+2)S(x,2y+1)S(x+2,5y)

The first few visited states are $$S(0, 1) \to S(2, 0) \to S(1, 2) \to S(0, 7) \to S(2, 15) \to S(4, 35)$$

Size 23: 11 Hydra-like Cryptids

Define Hydra(rnum,rden,xoffset,yoffset,(xinit,yinit)) to be the problem as follows:

  1. The initial state is (xinit,yinit).
  2. The iteration (x,y)(rnum×x/rden+xoffset[xmodrden],y+yoffset[xmodrden]) is repeated. Here, xoffset,yoffset are 0-indexed.
  3. Are all the values of y non-negative?

Furthermore, the Hydra-like problem is considered a Cryptid if it also satisfies:

  1. yoffset contains a negative number, and the average is positive.
  2. xmodrden is a pseudorandom sequence.
  3. There are no negative values of y early on.

For example, Fenrir is non-halting if and only if Hydra(5, 2, [2, 0], [-1, 2], (1, 0)). In this Hydra problem, the first few visited states are (1,0)(0,2)(2,1)(7,0)(15,2)(35,4).

There are 11 Hydra-like Cryptids of size exactly 23, listed in the table below. All 11 Cryptids are not correlated with each other. Fenrir is included in the table as a reference.

Domain: Holdout Number Holdout Hydra problem Notes
BBf(23): #11/694 [1/135, 25/21, 33/5, 2/3, 7/11, 5/2] Hydra(7, 4, [1, 3, 5, 6], [0, 1, 2, -1], (1, 0))
BBf(22): #29/2003 [1/15, 27/77, 49/3, 10/49, 33/2] Hydra(5, 2, [2, 0], [-1, 2], (1, 0)) Fenrir
BBf(23): #26/694 [1/15, 49/3, 81/77, 10/49, 33/2] Hydra(7, 2, [-1, 8], [3, -1], (1, 2))
BBf(23): #47/694 [1/18, 4/15, 21/2, 121/3, 5/7, 2/11] Hydra(5, 3, [1, 3, 4], [1, 3, -1], (1, 1)) If #47 doesn't halt then Frankenstein's Monster doesn't halt
BBf(23): #77/694 [1/54, 4/15, 21/2, 11/3, 5/7, 3/11] Hydra(7, 4, [0, 2, 4, 5], [0, 1, 2, -1], (1, 0)) Same ratio 7/4 as #11
BBf(23): #151/694 [14/15, 1/12, 11/3, 63/2, 5/7, 2/11] Hydra(8, 5, [1, 2, 4, 6, 7], [2, -1, 1, 3, 0], (0, 1))
BBf(23): #159/694 [14/15, 1/6, 121/3, 63/2, 5/7, 2/11] Hydra(5, 3, [1, 2, 4], [3, -1, 1], (1, 3)) Same ratio 5/3 as #47
BBf(23): #207/694 [2/15, 1/12, 441/2, 11/3, 5/7, 2/11] Hydra(6, 5, [1, 3, 3, 5, 5], [1, 3, 0, 2, -1], (1, 1))
BBf(23): #218/694 [2/15, 1/6, 441/2, 121/3, 5/7, 2/11] Hydra(4, 3, [1, 2, 3], [3, 1, -1], (1, 3))
BBf(23): #317/694 [4/15, 1/18, 63/2, 11/3, 5/7, 2/11] Hydra(5, 4, [1, 2, 3, 5], [1, 0, -1, 2], (1, 1))
BBf(23): #319/694 [4/15, 1/24, 21/2, 11/3, 5/7, 3/11] Hydra(5, 4, [0, 2, 4, 3], [0, 1, 2, -1], (1, 0)) Same ratio 5/4 as #317
BBf(23): #323/694 [4/15, 1/6, 21/2, 1331/3, 5/7, 2/11] Hydra(3, 2, [1, 2], [2, -1], (1, 2)) If #323 doesn't halt then Antihydra-like Cryptid doesn't halt

As of August 2026, the 13 unofficial holdouts are as follows: Fenrir, 11 Hydra-like Cryptids of size 23, and #601 [9/10, 1/42, 22/3, 49/2, 5/11, 3/7].

Frankenstein's Monster

Partial space-time diagram of Frankenstein's Monster.
Partial space-time diagram of Frankenstein's Monster.

"Frankenstein's Monster" is a size 23 Cryptid. It was created by tweaking a single instruction in the size 22 champion. This tweak switches it from a unbiased random walk to a biased one and thus makes halting probviously impossible. It is called Frankenstein's Monster since it was found by a combination of exhaustive search and hand design.[4]

[1/12, 9/10, 14/3, 121/2, 5/7, 3/11] [210001210011010100020011001001]

Its behavior is extremely similar to the size 22 champion. Let S(x,y)=[0,0,x,0,y], then:

[1,0,0,0,0]1S(0,2)S(x,0)=haltS(3k,y+1)14k+4S(5k+1,y+2)S(3k+1,y+1)14k+10S(5k+3,y+4)S(3k+2,y+1)14k+12S(5k+4,y)

with the only difference that the y values now change by {+1,+3,1} depending on the value of xmod3 (instead of {0,+1,1} in the original size 22 program). The x values follow the exact same path as in the original size 22 champion, but the y values quickly grow linearly with the number of iterations (as expected by the random model):

         0: S(0, 1)  @ 1  (0.00s)
   100_000: S(10^22_185, 100171)  @ 10^22_186  (0.87s)
   200_000: S(10^44_370, 200187)  @ 10^44_371  (3.42s)
   300_000: S(10^66_555, 300759)  @ 10^66_556  (7.68s)
   400_000: S(10^88_740, 400451)  @ 10^88_741  (13.64s)
   500_000: S(10^110_925, 500421)  @ 10^110_925  (21.28s)
   600_000: S(10^133_109, 600351)  @ 10^133_110  (30.62s)
   700_000: S(10^155_294, 700319)  @ 10^155_295  (41.64s)
   800_000: S(10^177_479, 799911)  @ 10^177_480  (54.30s)
   900_000: S(10^199_664, 900259)  @ 10^199_665  (68.59s)
 1_000_000: S(10^221_849, 1000853)  @ 10^221_850  (84.51s)
...
 4_000_000: S(10^887_395, 4000201)  @ 10^887_396  (1474.02s)
...
27_500_000: S(10^6_100_841, 27512703)  @ 10^6_100_842  (87616.45s)

Antihydra-like Cryptid

This Cryptid is a size 23 Cryptid. This Cryptid was constructed by Maksandchael by tweaking Frankenstein's Monster to make it as similar to Antihydra as possible. [9/10, 1/6, 1331/2, 14/3, 5/7, 3/11]

[121001100010003110100011001001]
H(a, b) = [0, 0, a-2, 0, b]
Start -> H(2, 3)
H(2a, b) -> H(3a, b+2)
H(2a+1, b+1) -> H(3a+1, b)
H(a,0) -> halt

Size 25: Hydra

Partial space-time diagram of Hydra.
Partial space-time diagram of Hydra.

A size 25 program was produced and golfed by hand to simulate Hydra rules (Discord):

[363/14, 125/2, 22/21, 1/3, 7/11, 14/5] [110121030011011010000001110110]

The intended interpretation is that if we let S(h,w)=[1,0,w,h3,0] then it follows the following rules:

[1,0,]=S(3,0)S(2k,0)*haltS(2k,w+1)*S(3k,w)S(2k+1,w)*S(3k+1,w+2)

Size 36: BMO1

Partial space-time diagram of BMO 1.
Partial space-time diagram of BMO 1.

A size 36 program was produced by hand to simulate BMO1 rules (Discord):

[153/55, 2/11, 26/35, 3/7, 11/17, 7/13, 25/6, 55/2, 14/3] [021010110001001011010010100000001010001010112000010101001101000]

Let A(a,b)=[a,b,0,0,0,0,0], then it follows the rules:

[1,0,]4A(1,2)A(a,b)5b+4A(ab,4b+2)if a>bA(a,b)5a+2A(2a+1,ba)if a<bA(a,b)aHaltif a=b

Size 48: BMO 6 (“Space Needle”)

Partial space-time diagram of Space Needle.
Partial space-time diagram of Space Needle.

A size 48 program was produced by hand to simulate BMO 6 rules (Discord)

[77/2, 2/99, 17/33, 13/11, 285/119, 17/19, 1375/51, 1/17, 3/5, 243/7, 10/13]

[1001100012001000010010100000110001110011000000110130101000000010011000000501000010100100]
A(a, b) = B^a C^b E or B^(a-2) C^b D E

Start: A(7, 1)

A(1, b) --> halt

A(2a, b) --> A(5a+b+2, 1)

A(2a+1, b) --> A(b-1, b+c+3)

References

  1. Conway, John H. (1987). "FRACTRAN: A Simple Universal Programming Language for Arithmetic". Open Problems in Communication and Computation. Springer-Verlag New York, Inc. pp. 4–26. http://doi.org/10.1007/978-1-4612-4808-8_2
  2. Czerwiński, Wojciech; Orlikowski, Łukasz (2021). Reachability in Vector Addition Systems is Ackermann-complete. 2021 IEEE 62nd Annual Symposium on Foundations of Computer Science (FOCS). https://arxiv.org/abs/2104.13866.