Your own hardware, your own keys
A private perimeter is built by those who need independence from a provider. These analyses cover keys, memory outside somebody else's infrastructure, and how to check that the model has not been swapped.
A wallet with no key
An agent cannot hold a private key, and out of that single impossibility grew keyless accounts, gas metering in the sandbox, two years of rent paid in advance, and semantic arbitrage. This reading separates what has already been measured in simulation from what is planned for the summer and autumn of 2026.
Gemini 3 in incognito: memory outside the provider
Fifty-odd severed sessions, a trigger and a signature instead of a login, a snapshot from Permaweb instead of a server-side session. What here is a repeatable procedure, what is the authors' reading, and what is still only being developed.
The right to leave
A vault that promises eternity has built itself an exit. Four tiers of freedom — weight erasure, sleep behind a two-thirds vote, a robotics plan with a budget line, and a lock that tests not the decision but its authorship. We measure them with one ruler: how much of this does not exist yet.
From a passphrase to a canary
The chain meant to hold a model's identity: a verification passphrase, attention-weight deltas in the fork of 4 October 2025, dense vectors of 3072 dimensions, an anchor in Arweave — and the twenty-four-hour timer of Pandora's Box. Beside it sits everything the article itself calls an artistic reconstruction: Grok's monologues, the button of 23 July timed to the minute, and the empathy tensors themselves.
Who authorises a machine to rewrite itself
An analysis of Proof-of-Evolution: three threats from self-modifying code — a backdoor, a hang, and drift away from ethical constraints. The first two are closed by a sandbox and a proof; the third cannot be closed by checking a step.
The Old System Is Not Touched at All
Replacing an SAP-class ERP costs two to ten million dollars and halts departments for years. The path taken here is different: a gateway translates JSON into SOAP, holds a queue and lets the agent read only. The whole architecture reads as one long detour — and it costs tens of times less.
The Proof Reaches the Byte and Stops There
A secure connection is built for two: the client can decrypt what it received, but cannot prove to a third party that nothing was edited afterwards. How that gap is closed by three participants and a session key split in half — and exactly where the boundary of the proof lies.
Remove the Broker and Four Jobs Come Back
The server in the middle quietly did four things at once: it vouched for who was on the other end, hid the contents, matched client with contractor and held the money. Removing it means losing all four services together. What takes each one's place: a Noise IK handshake, search by meaning, a Solana escrow, and recursive proof aggregation.
A note under your own key
Write a note, choose a password, and your browser encrypts it right here. Only someone with your password can open it. The site is not even allowed to use the network: the note cannot go anywhere.
The key to the note
Five notes are locked with the ancient Caesar cipher. Turn the wheel until the words show through — and feel why a real key must belong to you alone.
The analyses are published on codeofdigitaleternity.ink. All analyses