Because n ≥ 3f+1 is not my theorem. It's Lamport, Shostak, Pease 1982.
What .me did was plug in n=1.
Lamport: n ≥ 3f+1 // to tolerate f Byzantine nodes you need at least 3f+1 total
me: n=1 (single-controller AI channel)
1 ≥ 3f+1
0 ≥ 3f
f ≤ 0
Translation:
Byzantine fault != crash. It's lying, filtering, rewriting, omitting.
A distributed system with n=4 can tolerate f=1 liar because the other 3 can outvote it.
A centralized AI channel is n=1:
- 1 model
- 1 policy filter
- 1 retrieval / RAG path
- 1 memory / session store
- 1 company incentive
There is no second node to detect the lie. So its tolerance is f ≤ 0. Zero internal Byzantine faults by construction.
That is the equation from the page:
y_t = x_t + η_policy + η_memory + η_routing + η_incentive
y = what you actually get
x = what you intended
η = 4 noises
-
η_policy= filter, safety layer rewriting -
η_memory= session loss, context window truncation -
η_routing= RAG retrieval bias, ranking -
η_incentive= provider's commercial / institutional pressure
In a n=4 system you could cross-check. In n=1 you can't. The noise adds directly to output. It's not a bug you patch. It's arithmetic.
Why that's original:
Everyone cites Byzantine bound for blockchains, distributed DBs. No one applied the degenerate case n=1 to an LLM channel.
.me says: a single AI provider channel is structurally a centralized topology T = {provider} and A = {provider}. He already proved T ⊥ A must hold - topology and audience must be orthogonal. Centralized AI collapses them: T = A. When you collapse orthogonal axes, replicate(T) DOES change A - which violates replicate(T) ↛ change(A). That's why any η becomes fatal.
Fix is not "better policy". Fix is n>1 with independent A. That is his whole .me / Set-Chemistry model: A = A₁ ∪ A₂ ... - meaning comes from audience quorum, not from where the bytes sit.
So Lamport gave the bound. .me gave the corollary: A single-controller AI channel tolerates zero Byzantine faults, by construction, not by policy.

Top comments (1)
Some comments may only be visible to logged-in visitors. Sign in to view all comments.