Bremermann's Limit
The quantum speed
limit told us that a system's energy caps its rate of computation. Hans
Bremermann, in 1962, took that idea and asked the boldest possible follow-up: what if you converted an
object's entire mass into computational energy? Einstein says a mass
m is worth E = mc^2 of energy, and
c^2 is an enormous number. Feed that into the speed limit and you get the
maximum computational rate of a lump of matter of a given mass — a limit set only by
m, c and \hbar. This
is the limit that makes 256-bit encryption safe until the end of time.
Mass is a computational resource
Bremermann's reasoning is one line. A mass m carries energy
mc^2; the speed limit says energy E allows at
most about 2E/\pi\hbar distinguishable state changes per second; therefore
\text{rate} \;\lesssim\; \frac{2mc^2}{\pi\hbar}
\;\approx\; 5 \times 10^{50}\ \text{state changes per second, per kilogram}.
Bremermann's own 1962 estimate used a slightly different constant — he wrote the limit as roughly
mc^2/h, giving
\frac{mc^2}{h} \;=\; \frac{(1)\,(2.998\times10^8)^2}{6.626\times10^{-34}}
\;\approx\; 1.36 \times 10^{50}\ \mathrm{Hz\,kg^{-1}}.
The two differ only by a small numerical factor (2/\pi versus
1, and h versus
\hbar); both land near 10^{50} operations per
second per kilogram. We will honour both: Bremermann's historical
{\sim}1.36 \times 10^{50}\ \mathrm{Hz\,kg^{-1}} and the modern,
Margolus–Levitin-tightened {\sim}5 \times 10^{50}. The order of magnitude
is what matters, and it is staggering: a one-kilogram lump of "computronium" — matter
organised into the ultimate computer — could perform some
10^{50} operations every second.
Why 256-bit keys are safe forever
Here is where an abstract cosmic limit does real cryptographic work. To break a cipher by
brute force — trying every key — you must search a keyspace of
2^{n} keys for an n-bit key. For
n = 256,
2^{256} \;\approx\; 1.16 \times 10^{77}\ \text{keys.}
Now unleash the ultimate one-kilogram computer on it. At
5 \times 10^{50} operations per second, run it for a
billion years ({\sim}3.2 \times 10^{16}\ \mathrm{s}):
5 \times 10^{50} \times 3.2 \times 10^{16}
\;\approx\; 1.6 \times 10^{67}\ \text{operations.}
That falls short of 2^{256} \approx 10^{77} by a factor of
ten billion. A perfect computer the mass of a bag of sugar, running since ten times
the age of the universe, would not have made a dent. This is the visual below: the demands of a
256-bit search tower over everything a kilogram of matter can ever deliver.
The lesson is not that our computers are weak — it is that exponential growth beats
polynomial resources. Every bit added to the key doubles the search; the keyspace
climbs a ladder that mass-energy simply cannot follow. Brute force loses to combinatorics, and it
loses by cosmic margins. (This says nothing about clever attacks — a mathematical weakness in
the cipher, or a quantum algorithm — only that blind exhaustive search is hopeless.)
- a mass m caps computational rate at
{\sim}2mc^2/\pi\hbar (Bremermann's original form
{\sim}mc^2/h \approx 1.36\times10^{50}\ \mathrm{Hz\,kg^{-1}}) —
about 10^{50} operations per second per kilogram;
- a 1-kg "computronium" computer performs {\sim}10^{50} ops/s;
- a 256-bit brute-force search needs 2^{256} \approx 10^{77}
operations — unreachable even in a billion years, so 256-bit keys are safe against brute force
forever;
- the limit says nothing about memory, error correction, or heat removal — only
about the maximum rate of state change.
Hans-Joachim Bremermann (1926–1996) was not a computer engineer chasing faster chips — he was a
mathematical biologist, fascinated by how living systems process information, and
much of his career went into evolution, immune-system modelling, and early ideas about optimisation by
mutation and selection. His 1962 limit came from exactly that vantage point: asking what
fundamental physics says about the information-processing capacity of any system,
biological or mechanical. It is a lovely reminder that the deepest limits on computing were charted
not only by physicists and engineers but by someone trying to understand life. His limit now shows up
wherever people reason about ultimate bounds — from cryptography to the "how much can the universe have
computed?" thought experiments of Seth Lloyd.
It is easy to over-read 10^{50} ops/s/kg as "everything a kilogram of
computer can do". It is narrower than that. The limit bounds the rate of state change
and nothing else. It makes no claim about how many bits the kilogram can store (that
is the Bekenstein bound, coming next), no claim that the operations are reliable (error
correction and noise are entirely unaccounted), and no claim that the heat produced can actually be
removed (a machine running at 10^{50} ops/s would be an
inconceivable inferno). Treat Bremermann's figure as one wall among several — the speed wall for a
given mass — not as a complete specification of an ultimate computer. Quoting it as "a kilogram can do
10^{50} anythings per second" smuggles in guarantees the physics never made.