The busy beaver game asks, for a Turing machine limited to a fixed number of internal states, how many steps it can run before halting, or how many symbols it can write, given that it is required to eventually stop rather than loop forever. The mathematician Tibor Rado introduced the problem in his 1962 paper On Non-Computable Functions, defining two functions, one for the maximum output and one for the maximum running time, both measured across every possible halting machine of a given size. Both functions grow faster than any function that can itself be computed by an algorithm, which makes them impossible to compute in general, and this connects the busy beaver problem directly to the halting problem at the foundation of computability theory. Because the functions grow so explosively, finding the exact value for even a modestly sized busy beaver machine can, in principle, require settling open mathematical questions such as Goldbach's conjecture or the Riemann hypothesis.
Facts
Connections
Associated With
Source Wikipedia: Busy beaver
Is Kind Of Object
Entity-backed identity for the object-kind enum value this mathematical object already carries, resolved to a mathematics concept by an explicit value-to-entity map (phase 3 bucket conversion, docs\design_entity_backed_browse_buckets_20260928.md). The object-kind fact itself stays on the object unchanged.
Sources
1. Wikipedia: Busy beaver
Lead section
The concept of a busy beaver was first introduced by Tibor Rado in his 1962 paper, 'On Non-Computable Functions'.
Definitions section
The score function gives the maximum number of 1s an n-state Turing machine can output before halting, while the shifts function gives the maximum number of shifts that an n-state Turing machine can undergo before halting.
Associated With: Turing Machine, Technical Definition section
The n-state busy beaver game (or BB-n game), introduced in Tibor Rado's 1962 paper, involves a class of Turing machines, each member of which is required to meet the following design specifications
View the SourceReader Challenges (0)
No disputes yet. Spotted an error or a better source? Open the first one.
Sign in to dispute this or suggest a correction.