Quick read · plain language
Using Prime Numbers as Computer Addresses
A plain-language version of “Prime-Indexed Addressing: Collision-Free Computational Units from the Prime Sequence, with Entropy and Physicality Bounds”
The short version
This paper proposes using prime numbers as memory addresses to avoid collisions. The scheme is sure to work in theory. No one has shown that computers can look up these addresses fast enough.
Why collisions matter
Computers store data at numbered addresses. Two items at the same address cause a clash. The system must spend extra work to fix this. Hash tables, distributed stores, and language models all waste time and energy here. A system with no collisions would remove this waste. The paper asks if prime numbers can provide such a system.
The core idea
Each stored item gets a unique counting number, called its index. The address is the prime number at that position in the prime list. The first item lives at address two. The second lives at address three. The third lives at address five. Each index points to exactly one prime. Each prime comes from exactly one index. No two items can ever share an address. This freedom from clashes is built into the definition. It is not achieved by luck or repair.
What the paper proves
The paper shows several things with full working. The extra address length needed, beyond ordinary tight numbering, grows very slowly. It grows like the count of digits in the count of digits of the index. For a million items, this means about four extra bits. This is roughly a fifth more length than tight numbering. For a billion items, the extra length drops to about fourteen percent. The paper also studies a two-step form where addresses are primes of primes. This form grows more slowly but needs longer addresses still. The energy cost of erasing an entire address table is tiny. A check against the limits of the whole universe finds that the scheme uses far less than one atom per bit. It passes easily.
A shortcut using many primes
The paper also explores a form using the Chinese Remainder Theorem. This is a rule about dividing by several primes and combining the remainders. With the first eight primes, this system can address nearly ten million values using twenty-seven bits. Tight coding needs twenty-four bits for the same range. This trades a small length increase for the ability to work in parallel. No digit carrying is needed between parts of the calculation.
What remains unproven
The entire practical value of the scheme rests on one open question. Can a computer find which index belongs to a given prime address as fast as it can look up an ordinary numbered slot? The paper calls this the task of turning a prime back into its position number. No source cited in the paper demonstrates this step at memory speed. Without it, the freedom from clashes is merely a math curiosity. The paper proposes the smallest test that could settle this. Build a software prototype with a billion keys. Measure lookup speed against ordinary indexing. Reject the scheme if the prime-based lookup is more than ten times slower with no fix in sight.
What the paper does not show
The paper does not claim that prime-based addressing is faster. It does not claim it is cheaper or ready to build. It does not prove that the two-step prime-of-prime structure has the same statistical pattern at all scales. This self-similar pattern is only checked for the first billion or so cases. It does not solve the slow rebuild problem in the many-prime form. This is the bottleneck where parts must be rebuilt one after another. It does not provide a direct formula that makes the next needed prime on demand without search. The physicality check only covers the address table itself. It does not cover the retrieval hardware, the stored data, or the control circuits. The paper sits at the earliest stage of technology readiness. Basic principles are stated. No hardware is built. No peer review is passed.
Words used here
- Collision
- two items trying to use the same address, like two people claiming the same parking spot.
- Prime number
- a whole number above one that cannot be split into equal smaller whole-number parts, like five or seven.
- Logarithm
- a measure of how many times you must double a starting number to reach a target; used here to describe how slowly the extra address length grows.
- Chinese Remainder Theorem
- a rule from arithmetic that lets you rebuild a large number from its leftovers after division by several smaller numbers.
Learn more in plain language
- Prime numberSimple English Wikipedia
- Hash tableWikipedia (English, more technical)
- Memory addressWikipedia (English, more technical)
- Landauer's principleWikipedia (English, more technical)
- Technology readiness levelWikipedia (English, more technical)
- CollisionSimple English Wikipedia
This plain-language version was written by an AI model from the text of the paper and checked against plain-language rules: everyday words, no mathematics, no unexplained names. It leaves details out and can still be wrong; the paper is the source of record. To report a problem, open the paper, select the passage and choose Report.
For specialists: the technical digest, quoted from the paper
In the paper's words
Large-scale computing systems spend substantial resources resolving address collisions: hash tables rehash, distributed key-value stores reconcile conflicting writes, and language models dedicate parameters to disambiguating positional encodings. A concrete gap is the absence of a deterministic, unbounded, collision-free addressing primitive whose resource cost can be bounded analytically before any hardware is built. This paper formalizes a candidate in which the address space itself is the sequence of prime numbers: each stored value is assigned a unique prime index N, so that the map from values to addresses is injective by construction and the address density follows the prime number theorem, π(x) ∼ x/ln x.
The abstract, verbatim; every line below is quoted from the text.
What it claims
The map v ↦ p_N(v) is injective, hence collision-free.
Numbers it reports
We compute the Landauer cost of address erasure, $k_B T \ln 2 \approx 2.87 \times 10^{-21}$ J per bit at $T = 300$ K, giving $6.89 \times 10^{-14}$ J to erase a full $N = 10^6$ address table and $1.00 \times 10^{-10}$ J at $N = 10^9$; a bounded-physicality check passes with margins of order $10^{66}$ in atoms.
from AbstractWe use the $\theta = 0.525$ result in Section 4 to bound the search cost of extending the address space, and the Hoheisel exponent as the historically first quantitative guarantee of the same form.
from 2. Background and Related WorkBounds on the least prime in an arithmetic progression govern how fast a modular address space can be extended. [6] records that Heath-Brown proved in 1992 the bound $p(k) \ll k^{5.5}$, where $p(k)$ is the maximum over coprime residues $l$ of the least prime $p \equiv l \pmod k$; [6] also gives a weakened form of Goldbach's conjecture (its Conjecture 1, concerning a prime $p_r$ coprime to $n$ with $2n - p_r$ coprime to all competing $2n - p$) and proves, under a weakened Chowla hypothesis, that every sufficiently large even integer is the sum of two distinct primes.
from 2. Background and Related WorkWe use the $k^{5.5}$ bound as the extension-cost datum for modular addressing.
from 2. Background and Related Work(A1) The prime number theorem holds in the form $\pi(x) \sim x/\ln x$; we additionally use the explicit bound of [3] that $[x, x + x^{0.525}]$ contains a prime for sufficiently large $x$.
from 3. Methods(A2) Address erasure is the only irreversible operation whose Landauer cost we account for; we assume Landauer's principle in the form $E_{\text{bit}} = k_B T \ln 2$ per erased bit, with $k_B = 1.380649 \times 10^{-23}$ J/K and $T = 300$ K taken as room temperature.
from 3. Methods
How it is done
This paper formalizes a candidate in which the address space itself is the sequence of prime numbers: each stored value is assigned a unique prime index $N$, so that the map from values to addresses is injective by construction and the address density follows the prime number theorem, $\pi(x) \sim x/\ln x$.
from AbstractOur contributions are: A formal definition of prime-indexed addressing and a proof that it is collision-free, with the address-space growth law $\pi(x) \sim x/\ln x$ and the address overhead $\log_2 \ln N$ bits derived in Section 4.
from 1. IntroductionThe distributional foundation is the prime number theorem, invoked throughout in the asymptotic form $\pi(x) \sim x/\ln x$.
from 2. Background and Related WorkThis paper is an analytic study: it derives properties of a formally defined encoding scheme and computes all quantitative claims from stated inputs.
from 3. Methods
What would falsify it
An assessment of readiness and the smallest falsifying experiment, in Sections 6 and 7.
from 1. IntroductionThe main quantitative claim — that the address overhead is $\log_2 \ln N$ bits and the scheme is collision-free — would be falsified by a single demonstrated collision (two distinct assigned indices mapping to one address), which the bijectivity proof rules out definitionally, or by a demonstration that $p_N$ grows asymptotically faster than $N \ln N$, which would contradict the prime number theorem.
from 6. DiscussionThe practical claim — that prime-indexed addressing is deployable — would be falsified by the experiment of Section 7 if prime-ranking inversion cannot be brought within a bounded factor of dense-index lookup latency.
from 6. Discussion
Where the claim stops
The result that does not follow from the analysis is viability as a retrieval mechanism, and the gap between the two is the honest center of this paper.
from 6. DiscussionThe scheme is therefore collision-free addressing , not yet collision-free retrieval : a deployment would need either a precomputed inverse table (which is itself a dense array of size $\pi(x)$, reintroducing the structure it was meant to replace) or dedicated hardware for prime-ranking.
from 6. DiscussionThis is the load-bearing unproven assumption, and every practical claim in Section 7 is conditional on it.
from 6. Discussion
Where to read
- Abstract258 words · 1 min
- 1. Introduction548 words · 2 min
- 2. Background and Related Work1,185 words · 5 min
- 3. Methods503 words · 2 min
- 4. Analysis1,645 words · 7 min
- 5. Results295 words · 1 min
- 6. Discussion996 words · 4 min
- 7. Practical Implications and Engineering Pathways721 words · 3 min
- 8. Conclusion318 words · 1 min
- Provenance and AI Involvement240 words · 1 min
Read from the paper itself: 19 sections, 6,844 words. Nothing in this digest is written by a model; a line that is not a sentence of the paper is not shown. Have a specific question? Ask this paper.
The full text · Ask the whole corpus
Keep exploring
One body of research, three doors.