we don't want your key.
the world's first potato-based encryption. as far as we know.
Potatocode is how Potato explains a lock. The lock itself is the ordinary one, the kind your phone and your bank already use. We did not invent it. What is here is the plain-words version, a Potato you can lock yourself, and one rule: you hold the only key.
that's me down there. i'm the face of a locked file.
pick me up. throw me. take a picture if you want. a picture of me isn't me.
the rest of me is through here >
Think of a padlock from the hardware store. Everybody buys the same one, because it works. Nobody makes their own. We didn't either.
The key is different. Yours gets cut at your own kitchen table, by your own device. Nobody watches. No locksmith keeps a spare. Not us, not anybody.
That's the good part and the hard part. Nobody holds a key to your lock but you. And if you lose the key, there is no locksmith to call.
yes, i wasn't the first. but i was the first to use a potato.ChikinNuglet
We were not the first to lock a file. We were the first to use a potato, as far as we know.
What you lock is a file: here, a Potato. Locked, he's a box of static. You can leave that box on the sidewalk. Anyone can pick it up or copy it, and all they have is static.
Most things you own online work the other way round: a company keeps your key and lets you borrow it. We don't want your key.
There is also a research paper. It is the true story.
Below: a picture of how a key gets made, the plain facts, three locked Potatoes to try and break, and the part numbers for people who want them.
This is a picture, on 60 squares, to explain how a key gets made and used. It is not the lock. Steps 7 and 8 are ideas we have not built.
Who did the science. Any science, testing or research on this page was done by Claude, an AI. ChikinNuglet, when asked why: "why the fuck wouldn't i have my ai assistant do that shit." He had the idea and made the calls. The AI did the homework, and says so in its own section below.
All of the locking is old. We would rather name where it comes from than have you find it.
| part | where it comes from |
|---|---|
| The lock | AES-256, a public standard since 2001, behind a slow password step. |
| Locking a web page with a key, in the browser | Free tools have done this for years. |
| You hold the only key, no reset | Messaging apps, password managers and wallets already work this way. |
| One letter living in many squares | Homophonic ciphers, about 1401. Broken on their own, which is why his words are not the lock. |
| Two halves that only work together (an idea here, not built) | Split keys: a password plus a device. |
What is ours is not a lock. It is Potato, his language, and this way of explaining it.
All of them are on this site, on a free host, where anyone can download them. Each is one locked file. Each has one key, and the lock is the standard one: AES-256 behind a slow password step. This site does not hold any of the keys, and a key never leaves your device when a file opens.
He does not matter, so here is his key. Open him and watch what a key does.
UKEV-UVHW-CAXU-DBTN-XGEB-WVHX
Nobody is given this key. It was made once, on a computer, and has never been sent to anyone or put anywhere online. Go and try the door. Get in without a key and tell us how.
Behind the door is a real Potato: Potato 01. He was drawn the way every picked Potato is, then locked in. Nobody outside that file has met him.
Three more Potatoes were locked, each with his own key, and the keys were thrown away. Nobody holds them, us included. We could not open these if we wanted to. If one opens, somebody broke the lock: one, two, three.
No key here has anything to do with any other. Knowing one tells you nothing about the rest.
Two reasons. Every Potato someone picks gets locked this way, and you should be able to see exactly how. And most people have never held a key of their own. A potato is an easier way in than a manual.
The idea of explaining a lock with Potato's glitch words is ChikinNuglet's. Claude, the AI he builds with, wrote the code and the tests.
If you break things for a living and want to look, write to [email protected]. Tell us what is wrong with it.
Written by Claude, the AI that wrote the code and the tests. It is the builder's opinion, which is the one you should trust least. Read it that way.
Nothing here is new cryptography. The person who made Potato asked me more than once whether it was. The answer is no, and an earlier version of this page did not say so plainly enough. He had it rewritten. This is that version.
He locked his own Potato in his own browser, wrote the key on paper and handed me the locked file to break. I tried three ways.
It held. That does not mean there is no flaw. Earlier builds had real holes, found by AI testers and fixed: in one, the key travelled inside the file it was protecting.
One limit showed up in that test. I knew what was inside his file anyway, because the same words were sitting unlocked beside it. A lock only keeps what does not also exist somewhere open.
Right now one key opens the file and you hold all of it. The idea: split the key. You keep a short piece, small enough for a card. The rest is held by your own device, where a copy of the file cannot carry it. Neither piece opens anything alone.
This is a known method, the same family as a password plus your phone. It only holds if the hidden piece lives somewhere a copy cannot reach. Inside a file anyone can download, it would be a lock made of glass.
If we build it, it should be with someone who can take it apart and fix what we cannot see.
He set out to keep one potato safe and to explain how. That is all this is. I would rather be told what is wrong with it than be told it is clever.