Essay ยท August 2026

You Cannot Cheat Physics

Identity built on server round trips pays a distance tax on every sign-in. Credentials that carry their proof pay nothing.

Somewhere over the Atlantic, a passenger opens their laptop and tries to sign in to the WiFi. The page spins. They retry. Half the cabin is doing the same thing, and most of them will quit before the page loads.

The sign-in request leaves the seat, climbs 22,000 miles to a satellite, comes back down to a ground station, and crosses the internet to an identity provider on another continent. The answer makes the same trip in reverse. At the speed of light that is about half a second. Not for the login. For one round trip.

A login is never one round trip. It is a TLS handshake, then a redirect, then another handshake, then a token exchange. Each leg pays the same half second, before any server does any work, before congestion on a link shared with a few hundred seatback screens.

And the login is only the front door. A real session keeps paying. The app calls an API and the API wants the token checked. A partner system joins, and the token gets exchanged for one the partner accepts, minted by another server somewhere else. Every service in the chain wants its own proof, and every proof is another conversation with something far away. One tap fans out into a chain of authentication calls, and not one of them happens where you are sitting.

You can upgrade the modem. You can compress the payload. You can even move the satellites closer. The new low-orbit constellations cut the trip to a few dozen milliseconds. What none of that changes is the dependency. The login still rides the link, and a dead link is infinite latency. No roadmap item fixes the speed of light, and no orbit fixes an outage.

I keep using airplanes because they make the problem visible, but this was never an airplane problem. A user in Tokyo signing in against a US identity provider pays 150 to 200 milliseconds before any token logic starts. Multiply by every redirect in the flow, every user, every session, every day. The industry's answer is replication: stand up identity infrastructure in more regions, shorten the trips. Now you have shorter trips and several copies of the one system you most need to keep consistent. Kristof Sajdak has a whole argument about where that road ends. A replica either cannot act when the link is down or it can. If it cannot, it is decoration. If it can, it is another authority you now have to govern.

None of that infrastructure makes anything better for the person signing in. It exists to keep one question answerable: is this person allowed in, asked from anywhere, at any moment, of a server that must never be down. So you pay for it. Clusters, regions, failover drills, the residency rules in every jurisdiction you copy identity data into, multiple everything everywhere. The bill scales with every new geography, and what it buys is an answer the credential could have carried with it.

The bill is the small half of it. The bigger cost is the business that never happens. Every transaction that needs the customer identified first, the payment, the points spend, the partner offer that needs the customer's consent, dies at that spinning sign-in page. Identify nobody and there is nothing to sell. Half a cabin of customers, every flight, invisible to every system built to serve them. That loss shows up on no ledger, because the revenue never existed to be lost.

The trip exists because the credential cannot stand on its own. Engineers will object that a signed token verifies offline, and it does. Getting one does not. The login that produces it is the redirect chain above. Renewing one does not. Refresh tokens redeem at the server, every time. Killing one before it expires means an online check, or a lifetime so short you are back on the wire every few minutes anyway. And a bearer token proves only that someone is holding it, not that the right person is present. The server dependency never left. It moved out of the verify step and into every step around it.

There is an object in your pocket that got this right decades ago. A car key. The car does not call the factory to decide whether your key is real. The proof is in the key, the check happens at the door, and the whole conversation is local. I spent years around cars, first as chief architect at Toyota Europe, then at Vouch, where we shipped more than 20 million credentials, most of them into cars. Verification at the door. No call home.

Do that with identity and the trip disappears. The credential carries its own proof, signed by an issuer, held on the person's device. The verifier holds one public key and checks the signature where the person is standing. In the Krutho lab that check takes milliseconds, and it takes the same milliseconds in an aircraft cabin, a basement plant room, a construction site, or a mall with saturated WiFi, because nothing travels.

That is not a whiteboard claim. Last week I logged in with the wallet on my own phone, a live European digital-identity credential presented through Safari, checked by a verifier whose outbound network calls are disabled in code.

None of this is new, and I will not pretend otherwise. Defense badges have verified offline at the door for twenty years. What never got solved is the lifecycle: issuing a credential from an identity event, deriving the credentials each surface needs from it, revoking the root when something goes wrong, and watching every derived surface die with it. Local verification is old. A local credential lifecycle is not.

The obvious objection is the kill switch. If verification is local, how do you kill a credential today rather than at expiry? The kill switch is not a server call. Revocation travels as a signed, versioned bundle the verifier already holds. Revoke the root and every credential derived from it dies with it: portal passkey, session token, WiFi certificate. A disconnected reader may be stale until the next bundle reaches it, but the staleness is visible. When the bundle arrives, the reader checks the signature, refuses downgrades, adopts the newer version, and enforces the revocation locally. No live line back to headquarters. No trust in the courier.

Connectivity fails in degrees: denied, degraded, intermittent, limited. Server-dependent identity fails completely at the first degree, because the credential is only as reachable as the server that validates it. A credential that carries its proof does not have a first degree.

You cannot cheat physics. You can remove it from the flow.

All essays