TMBR: December 2025: Difference between revisions

From BusyBeaverWiki
Jump to navigation Jump to search
Move TYBR to it's own article
Fixed link. Add lede.
Line 3: Line 3:
''This edition of TMBR is in progress and has not yet been released. Please add any notes you think may be relevant (including in the form a of a TODO with a link to any relevant Discord discussion).''
''This edition of TMBR is in progress and has not yet been released. Please add any notes you think may be relevant (including in the form a of a TODO with a link to any relevant Discord discussion).''


This is the last edition of TMBR this year. 2025 was a very productive year for [[Busy Beaver Challenge|BBChallenge]]: about 60% of the next domain, [[BB(6)]], was solved. Furthermore, new champions were discovered for BB(6), [[BB(7)]] and [[BB(4,3)]]. Many models of computation other than Turing Machines were also explored - most notably [[Fractran]] and [[Instruction-Limited Busy Beaver]]. Some new methods were developed, such as [https://discord.com/channels/960643023006490684/1028746861395316776/1442964185599447152 mxdys's new version of FAR.]
[[:Category:This Month in Beaver Research|This Month in Beaver Research]] for December 2025. In commemoration of the end of the year, we've summarized some of the major accomplishments into This Year in Beaver Research: [[TYBR: 2025]]. This month saw a lot of exploration into BB-adjacent models with the introduction of BB for [[General Recursive Function|General Recursive Functions]] and [[Register machine|Register machines]] and new champions for many previously introduced variants.
 
This year, [[TMBR: November 2025#Themed Months|Themed Months]] were introduced - first, for [[BB(3,3)]], then for [[BB(2,5)]] - and the result is the clarification and verification of some of the results and techniques on the [https://discord.com/channels/960643023006490684/1259770474897080380 Discord] and [https://wiki.bbchallenge.org/wiki/BB(3,3) wiki]. See [[TMBR: November 2025#Themed Months]] for more information.
 
An annotated spreadsheet of [[BB(6)]] holdouts was also shared by [[User:RobinCodes|Robin Rovenszky]], which includes links to Discord discussions, classification of machines and is almost always up-to-date. See [https://docs.google.com/spreadsheets/d/1mMp8bAcTFT91j7azn72liX8NSTwc2E_ozKnOGTfRCfw/edit?gid=1330361301#gid=1330361301 Google Sheets]
 
== Misc ==
 
* Azerty [https://azertywastaken.github.io/TuringMachinesSimulator/bb_champions.html shared a website] with champions for many BB-Adjacent functions and original BB.


== In the News ==
== In the News ==
Line 27: Line 19:
* Patcail and [https://github.com/tromp/AIT/blob/master/fast_growing_and_conjectures/melo.lam Gustavo Melo] discovered a new [[Busy Beaver for lambda calculus|BBλ(63)]] champion, running for more than <math>f_{\omega^3}\left(2\right)</math> steps and <code>50_ft_lock</code> discovered a new [[Busy Beaver for lambda calculus|BBλ(91)]] champion, running for over <math>f_{\varepsilon_0 + 1}\left(3\right)</math> steps. f represents the [[Fast-Growing Hierarchy]].
* Patcail and [https://github.com/tromp/AIT/blob/master/fast_growing_and_conjectures/melo.lam Gustavo Melo] discovered a new [[Busy Beaver for lambda calculus|BBλ(63)]] champion, running for more than <math>f_{\omega^3}\left(2\right)</math> steps and <code>50_ft_lock</code> discovered a new [[Busy Beaver for lambda calculus|BBλ(91)]] champion, running for over <math>f_{\varepsilon_0 + 1}\left(3\right)</math> steps. f represents the [[Fast-Growing Hierarchy]].
* On 18 Dec, Azerty discovered the new [[TT]](2) champion <code>1TB---_1PA0PB</code> with a runtime of 13 steps. This was followed by new champions a day later: <code>1PB0PA_1TA0PC_1PA---</code> for TT(3) with a runtime of 82 steps, <code>1TB---_0PD1PB_1PA1TA_0PC0PD</code> for TT(4) with a runtime of 758 steps, <code>1TB0PA2PA_2PA---1PA</code> for TT(2,3) with a runtime of 223 steps and <code>1TB3TB2PB---_2TB1PA0PA2TB</code> for TT(2,4) with a runtime of 1,068 steps. On 21 Dec Azerty also discovered the new TT(3,3) champion with a runtime of 427 steps <code>1TB2TA2PA_1TA0TC1PC_---2PA0PA</code>, this champion was surpassed on 22 Dec by <code>1TB2PB1PB_2TA0TA2PC_2TA---2PA</code> with a runtime of 1,072 steps, on 23 Dec by <code>1PB2PC1PB_2TC0TA---_1PA1PC0PC</code> with a runtime of 3,786 steps and again on 28 Dec by <code>1PB1PA1TA_2TB2PB2PC_---2PA1TC</code> with a runtime of 45,153 steps.
* On 18 Dec, Azerty discovered the new [[TT]](2) champion <code>1TB---_1PA0PB</code> with a runtime of 13 steps. This was followed by new champions a day later: <code>1PB0PA_1TA0PC_1PA---</code> for TT(3) with a runtime of 82 steps, <code>1TB---_0PD1PB_1PA1TA_0PC0PD</code> for TT(4) with a runtime of 758 steps, <code>1TB0PA2PA_2PA---1PA</code> for TT(2,3) with a runtime of 223 steps and <code>1TB3TB2PB---_2TB1PA0PA2TB</code> for TT(2,4) with a runtime of 1,068 steps. On 21 Dec Azerty also discovered the new TT(3,3) champion with a runtime of 427 steps <code>1TB2TA2PA_1TA0TC1PC_---2PA0PA</code>, this champion was surpassed on 22 Dec by <code>1TB2PB1PB_2TA0TA2PC_2TA---2PA</code> with a runtime of 1,072 steps, on 23 Dec by <code>1PB2PC1PB_2TC0TA---_1PA1PC0PC</code> with a runtime of 3,786 steps and again on 28 Dec by <code>1PB1PA1TA_2TB2PB2PC_---2PA1TC</code> with a runtime of 45,153 steps.
* Azerty [https://azertywastaken.github.io/Website/Champions/index.html shared a website] with champions for many BB-Adjacent functions and original BB.


== BB Adjacent ==
== BB Adjacent ==

Revision as of 16:07, 8 February 2026

Prev: November 2025 This Month in Beaver Research Next: January 2026

This edition of TMBR is in progress and has not yet been released. Please add any notes you think may be relevant (including in the form a of a TODO with a link to any relevant Discord discussion).

This Month in Beaver Research for December 2025. In commemoration of the end of the year, we've summarized some of the major accomplishments into This Year in Beaver Research: TYBR: 2025. This month saw a lot of exploration into BB-adjacent models with the introduction of BB for General Recursive Functions and Register machines and new champions for many previously introduced variants.

In the News

Blog Posts

Champions

  • A new BBS(4,3) champion (1RB1RD1LC_2LB1RB1LC_1LB1LA1LD_0RB2RA2RD (bbch)) was discovered by changing the C0 transition of the BB(4,3) champion 1RB1RD1LC_2LB1RB1LC_1RZ1LA1LD_0RB2RA2RD (bbch) from C0 --> 1RZ to C0 --> 1LB.
  • Azerty discovered a series of Blanking Busy Beaver 3x3 champions, culminating in 1RB2LC2LA_1LC---2RA_2RC2LB0LC (bbch) which blanks the tape after 329 steps on 31 Dec 2025.
  • On 25 Dec 2025, Azerty discovered 1RB2RC1LC_0RC0RB1LA_2LA2RC1LB (bbch) which is a Translated cycler and new BBP(3,3) champion with a new record period length of 1195 steps.
  • Patcail and Gustavo Melo discovered a new BBλ(63) champion, running for more than fω3(2) steps and 50_ft_lock discovered a new BBλ(91) champion, running for over fε0+1(3) steps. f represents the Fast-Growing Hierarchy.
  • On 18 Dec, Azerty discovered the new TT(2) champion 1TB---_1PA0PB with a runtime of 13 steps. This was followed by new champions a day later: 1PB0PA_1TA0PC_1PA--- for TT(3) with a runtime of 82 steps, 1TB---_0PD1PB_1PA1TA_0PC0PD for TT(4) with a runtime of 758 steps, 1TB0PA2PA_2PA---1PA for TT(2,3) with a runtime of 223 steps and 1TB3TB2PB---_2TB1PA0PA2TB for TT(2,4) with a runtime of 1,068 steps. On 21 Dec Azerty also discovered the new TT(3,3) champion with a runtime of 427 steps 1TB2TA2PA_1TA0TC1PC_---2PA0PA, this champion was surpassed on 22 Dec by 1TB2PB1PB_2TA0TA2PC_2TA---2PA with a runtime of 1,072 steps, on 23 Dec by 1PB2PC1PB_2TC0TA---_1PA1PC0PC with a runtime of 3,786 steps and again on 28 Dec by 1PB1PA1TA_2TB2PB2PC_---2PA1TC with a runtime of 45,153 steps.
  • Azerty shared a website with champions for many BB-Adjacent functions and original BB.

BB Adjacent

TODO. Fractran progress, Semi-infinite tape Busy Beaver

Holdouts

BB Holdout Reduction by Domain
Domain New Holdout Count Previous Holdout Count Holdout Reduction % Reduction
BB(6) 1326 1416 90 6.36%
BB(7) 20,387,509 20,405,295 17,786 0.09%
BB(3,4) 12,435,284 15,136,283 2,700,999 17.84%
  • BB(6): 90 machines solved, a 6.36% reduction.
    • There are 14 holdouts left to simulate up to 1e12 steps, and 288 to simulate up to 1e13 steps[1]. Later, at the end of the year, all 14 machines were simulated up to 1e12 machines, which means that now, all holdouts TMs must have a score >1e12. 278 machines are left to simulate up to 1e13. A dynamic list can be found here. (See results on Discord, plus [2], [3] and [4])
    • The possibility of simulating computationally tractable machines which nonetheless has large time and memory requirements was discussed. List
    • mxdys shared a new holdouts list, consisting of 1343 machines, which means 73 solved TMs. This is a 5.4% reduction. There is one extra machine that is solved formally, but unverified. (That is, not verified in Rocq.)
    • The old spreadsheet was replaced with a newer one, see Google Sheets
    • At the end of the year, mxdys shared the latest holdouts list, which consisted of 1326 machines, that is, 17 TMs solved and a 1.27% reduction.
  • BB(7):
    • Further enumeration by Andrew Ducharme has reduced the number of holdouts from 20,405,295 to 20,387,509, a 0.09% reduction.
  • BB(3,4):
    • XnoobSpeakable and Lúkos ran stages 8, 9, 10A, 10B & 10C of Phase 2, reducing the number of holdouts from 15,136,283 TMs to 12,435,284 holdouts. This is a 17.84% reduction.
  • BB(2,7):
    • Terry Ligocki enumerated 60K more subtasks, increasing the number of holdouts to 309,868,865. A total of 100K subtasks out of the 1 million subtasks (or 10%) have been enumerated.