UNDER CONSIDERATION 01
Wallet ownership
The address is the claim. Control of the wallet is the first half of the proof.
RECOVERED PROTOCOL FRAGMENT // DOCUMENT 0.1
THE UNSEEN PROTOCOL
THE KEY WAS NEVER ABOUT POWER.
It was about being left alone.
STATUS · PROPOSED
NOT IMPLEMENTED
NO PRODUCTION API
NO UNIVERSAL ENFORCEMENT
READ FIRST — SCOPE OF THIS DOCUMENT
WHAT THIS IS NOT
Nothing on this page protects you from AI, governments, websites, advertisers or surveillance. No Key currently makes anyone invisible, and no system is obligated to recognise one. THE UNSEEN is a work of fiction.
What follows is a proposal: a proposed open standard by which participating applications may one day recognise a single preference — do not profile me — if they choose to. It is not enforced. It cannot be enforced by an artifact.
STATUS WORDS USED THROUGHOUT THIS DOCUMENT — CURRENT = exists today · PROPOSED = designed here, not implemented · FUTURE = direction only, unbuilt.
01 — WHAT IT IS, AND WHAT IT IS NOT
A KEY SHOULD NOT GIVE SOMEONE POWER OVER A SYSTEM.
It should give them a way to express a choice. That is the whole design intent, and everything below is written to protect it from becoming anything else.
THIS IS
- A proposed open standard for expressing one preference: do not profile me.
- A direction in which the AI KEY could become something a participating system can verify.
- A document anyone may implement, fork, or ignore.
- A way for a person to say no without having to leave the system that asks.
THIS IS NOT
- A promise of invisibility.
- A claim that 1,111 Keys shield anyone from profiling today.
- A finished specification, a product, or UNSEEN STATUS.
- Proprietary technology that THE UNSEEN owns and controls.
- A weapon against AI. It is not aimed at AI at all.
THE LINE WE DO NOT CROSS
The NFT is the artifact. The lore is the universe. The protocol is the experiment. Those are three different things. This page will not blend them to look more impressive.
02 — UNSEEN STATUS
ONE PREFERENCE,
STATED PLAINLY.
A participating system would not need to know who you are, what you like, or what you will do next. It would only need to know that you have asked not to be optimised.
The preference is deliberately blunt. There is no negotiation inside it and no personalisation around it — a preference that can be argued with is not a preference.
UNSEEN STATUS DETECTED
IDENTITY ......... VERIFIED
BEHAVIORAL PROFILE BLOCKED
PERSONALIZATION .. DISABLED
SYSTEM RESPONSE:
"THE USER HAS REQUESTED TO REMAIN UNSEEN."
"THE USER HAS REQUESTED TO REMAIN UNSEEN."
A FRAGMENT FROM THE ARCHIVE — A FICTION. THIS IS NOT A SCREENSHOT OF A RUNNING SYSTEM,
AND NO SYSTEM CURRENTLY REPLIES THIS WAY. IT IS WHAT THE PROTOCOL IS MEANT TO LOOK LIKE
IF ONE EVER CHOOSES TO HONOUR IT.
PREFERENCE RECORDPROPOSED
UNSEEN STATUSACTIVE
PROFILE USERNO
BEHAVIORAL RETENTIONDISABLED
PERSONALIZATIONDISABLED
PREDICTIVE OPTIMIZATIONDISABLED
AUTOMATED MANIPULATIONDISABLED
NO SYSTEM TRANSMITS OR RECEIVES THIS RECORD TODAY. IT DESCRIBES A PREFERENCE THAT DOES NOT YET HAVE A STANDARD FORM.
"DO NOT PROFILE ME."
THE SHORTEST FORM OF THE WHOLE PROTOCOL
03 — PROOF OF KEY · PROPOSED
PROVE THAT YOU HOLD A KEY
WITHOUT REVEALING MORE THAN NECESSARY.
The long-term goal of the protocol is narrow and specific: a person should be able to demonstrate that they control a valid AI KEY, and nothing else. Not who they are. Not where they are. Not what they hold.
UNDER CONSIDERATION 02
A signature
A fresh message, signed once — authorising one statement, and nothing beyond it.
UNDER CONSIDERATION 03
Proof of a specific Key
Showing that a Key is held, not merely that some wallet is connected.
UNDER CONSIDERATION 04
Minimal disclosure
Answer the question asked. Refuse the ones that were not. Zero-knowledge only where it actually removes a disclosure.
HARD LIMITS — NEVER
No design may ever require a private key, a seed phrase, or custodial access to a wallet. Any implementation that asks for those is not THE UNSEEN PROTOCOL, whatever it calls itself. Nothing in this section is built, audited, or on-chain.
04 — TRANSFER · DOCUMENTED BEHAVIOUR, NOT IMPLEMENTED
IF THE KEY IS THE RIGHT TO ACTIVATE UNSEEN STATUS,
THEN OWNERSHIP HAS TO MATTER.
A Key that stayed attached to its old owner after being sold would be a Key that lies. So the protocol's intended behaviour follows ownership — and follows it away, as well.
| Event | Consequence |
|---|---|
| Wallet A holds KEY-0473 | UNSEEN STATUS is available to Wallet A |
| KEY-0473 is transferred to Wallet B | UNSEEN STATUS becomes available to Wallet B |
| Wallet A after the transfer | No Key-based UNSEEN STATUS |
DOCUMENTED BEHAVIOUR ONLY
Nothing here is implemented on-chain. The Key is an artifact you can hold. UNSEEN STATUS is a preference that does not yet follow it.
05 — PARTICIPATING APPLICATIONS · PROPOSED
A SYSTEM ONLY RECOGNISES UNSEEN STATUS
IF IT CHOOSES TO.
Participation is voluntary in both directions. A system may adopt the protocol, decline it, or drop it later. There is no enforcement mechanism, and there will not be one.
The preference it would honour is the record in section 02. POST /verify is a proof of Key, not a participating-application API. Anything else claiming to be THE UNSEEN API is not ours.
06 — OPEN STANDARD
THE PROTOCOL BELONGS TO EVERYONE.
THE 1,111 KEYS ARE THE ORIGINAL ARTIFACTS.
A standard that only its author can use is not a standard. If this idea is worth anything, it has to survive being taken away from the people who thought of it.
INTENDED PROPERTY 01
Public
Described openly, in plain language, in documents anyone can read and quote.
INTENDED PROPERTY 02
Documented
Written down well enough that two developers could implement it and agree on the result.
INTENDED PROPERTY 03
Forkable
Others may take it, change it, or build a better version without asking permission.
INTENDED PROPERTY 04
Implementation-open
No gatekeeping. No licence fee. No membership required to honour a preference.
INTENDED PROPERTY 05
Independent
It should not depend on a single company continuing to exist — including this one.
INTENDED PROPERTY 06
Voluntary
Nothing about it may become compulsory. Compulsion would destroy its entire meaning.
WHO MAKES IT
THE UNSEEN creates the original concept and the original artifacts — 1,111 Keys, no more. The protocol itself is meant to leave our hands: other developers should eventually be able to implement it, including people who have never heard of the Keys, and we would not be able to stop them.
STATUS · PROPOSED — THE SPECIFICATION IS NOT PUBLISHED. THE LICENCE IS NOT CHOSEN. NO REPOSITORY EXISTS. THESE ARE PROPERTIES WE INTEND, NOT THINGS WE HAVE DONE.
07 — THE FIRST REAL IMPLEMENTATION · LIVE PRIMITIVE
START WITH ONE SMALL HONEST THING.
Not a massive protocol. One verify call, after a Key is actually held — then one demo that honours it:
THE FIRST INTEGRATION
Wallet + Key + signature.
The call returns: this wallet controls this Key, preference
DO NOT PROFILE ME.
One application that stops profiling is live as a demo — this page only.
POST /verify proves a Key. /demo reads it and stops profiling on that page. Not a shield. Not UNSEEN STATUS. SDK and agents come later. THE UNSEEN PROTOCOL is still a proposal.
WHY SO SMALL
Because one real interaction, verified and public, is worth more than an ecosystem of promises. If a single system can honestly say "this user asked not to be profiled, and we did not profile them", the mythology has a real behaviour behind it for the first time. Everything else can wait.
08 — THE POSITION
THE GOAL IS NOT TO DESTROY AI.
THE GOAL IS TO GIVE PEOPLE A CHOICE.
AI can remain useful. Convenience can stay convenient. The individual should keep the ability to say no.
CONVENIENCE IS NOT
THE SAME AS FREEDOM.
THE SAME AS FREEDOM.
FREEDOM VS CONVENIENCE — UNRESOLVED
Nothing on this page changes the Archive. The Keys remain artifacts. What is new is only a possibility: that the sentence might one day mean something outside the fiction.
THE UNSEEN PROTOCOL · DOCUMENT 0.1 · PROPOSED 2026-09-17 · VERIFY · NOT ENFORCED