9.1 Shadow ID
An identity that answers to no directory.
A second identity, derived and compartmented, that no directory ever links to your first. Unlocked with Shadow.
- Profile ID BLAKE3 derive-key
- Shadow derivation HKDF-SHA-512
- Domain qeryx.identity.profile.v1
01 / THE DERIVATION — LETTERED
Follow one secret through two one-way doors.
One secret. Two worlds. Neither door opens backwards.
9.1 / A
Derived, never registered
A Shadow ID is derived on your device from your own identity secret — a one-way derivation, not a registration. Nothing is filed, so nothing can be looked up.
BLAKE3 derive-key · qeryx.identity.profile.v1
HKDF-SHA-512 · channel-scoped derivation
9.1 / B
Lives only in RAM
The Shadow ID surface keeps every piece of view state in RAM — no persisted state, no app storage. Close it, and the surface forgets; the derivation can be repeated because the secret is yours.
01
bytes persisted on device by the Shadow ID surface
9.1 / C
Reached through the seal
Shadow ID renders as an overlay above the QSeal compartment — you reach it only through the sealed space, never from the regular app.
Nothing registers, so nothing can be looked up.
02 / THE VERDICT — CATEGORY COLUMNS
Set it against an alt-account and a second SIM.
| QERYX Shadow ID | Alt-account on classical E2E | Second SIM | |
|---|---|---|---|
| Real workloads | |||
| Linkability | Derivation — no registration | Same phone number or account graph | Carrier links both |
| Persistence on device | RAM-only surface | Second profile persisted | Physical artifact |
| Directory lookup | Nothing to query | Discoverable by identifier | Number is public |
| Setup trail | None — derived | Signup metadata | Purchase trail |
03 / ACCESS — THROUGH THE COMPARTMENT
Reach it through the Shadow compartment.
Shadow ID ships inside the Shadow tier, alongside QSeal and Ghost Serpent. Nothing in this build is purchasable; the tier ladder is set out on pricing.
Request an invite04 / THE HARD QUESTIONS
Ask what can still be linked.
Is a Shadow ID an account?
No. It is derived on your device from your own secret. Nothing registers, so nothing can be looked up.
Can the two identities be linked?
Not by the directory — there isn’t one. Derivation is one-way; the public handle never appears in the shadow context.
What persists on my phone?
The surface keeps its state in RAM only. Close it and it is gone from the view layer; the derivation can be repeated because the secret is yours.
What can be handed over under subpoena?
No shadow directory exists to query. Relay traffic is sealed blobs and opaque routing identifiers, like everything else — and Ghost Serpent is the pattern defense on the wire.
What is this for?
Work and relationships that must not join your visible graph — sources, casework, second lives that stay second.