Personal Identity Protocol

Your identity,
shaped to the moment.

PIP is a self-sovereign identity protocol. Reveal nothing, prove one thing, or sign with your legal name - and switch between them in a tap. The keys never leave your device.

0
Keys we hold
15s
Proof lifetime
3
Identity modes
PIP · Anon
live

Anonymity mode

Unnamed citizen

  • Unique personhood
  • Not a bot
  • Ephemeral noise only
Zero PIIzkp · ed25519 · enclave

Prove you are human and unique without revealing a single attribute. The default posture.

The Chameleon

One protocol.
Three faces you control.

Most identity systems are all-or-nothing: hand over everything or prove nothing. PIP lets you dial disclosure to the exact line a situation needs. Switch the mode and watch every surface - cards, proofs, telemetry, the QR - recolour and re-scope in real time.

What “Anonymity” discloseslive scope
  • Unique personhood shared
  • Human, not a bot shared
  • Over 18 hidden
  • Region of residence hidden
  • Membership status hidden
  • Legal name hidden
  • Document number hidden
  • Issuing authority hidden
Matrix protocol · core backbone

Built on Matrix,
not reinvented.

PIP rides on the open Matrix protocol for decentralized, end-to-end-encrypted sync. Your identity store replicates across your own devices using Matrix cross-signing and device verification - the same primitives that secure matrix-org clients, applied to identity instead of chat.

decentralized identity storesyncing
E2EE room-key sync82%

Cross-signing

Trusted

Megolm sessions

14 active

device verification

  • Pixel 9 ProDAQRSTUV verified
  • MacBook AirGHIJKLMN verified
  • iPad miniWXYZ1234pending
federated homeserver routing
matrix · federated routing
■ homeserver● deviceolm·megolm

Identity claims hop between independent homeservers over Olm and Megolm double-ratchet encryption. No central server can read, link, or withhold them.

9:41

PIP · identity sync

Securing your account

Open sliding sync streamclient.syncService().start()
Restore encryption storeencryptionService.restore()
Bootstrap cross-signingcrossSigning.bootstrap()
Verify this deviceverification.requestSelf()
Replicate identity roomroom.syncStateEvents()
end-to-end encrypted
Element X · mobile SDK

Mobile sync that
feels instant.

PIP's mobile client mirrors the architecture of Element X: a Rust core, sliding-sync for sub-second state, and the same hardened cross-signing flow. The screen on the left maps directly to the SDK calls that run under it.

SDK API mapping
  • MatrixClientsession lifecycle + sliding sync
  • EncryptionServiceOlm / Megolm key store
  • VerificationServiceSAS device verification
  • SyncServiceincremental room-state replication
Live-Pulse credential

A proof that
expires before it leaks.

Every PIP handshake mints a fresh ephemeral hash, signed inside the secure enclave and valid for exactly fifteen seconds. The credential adapts to your active identity: blinded when anonymous, certified when legal. A screenshot is worthless the moment the ring completes.

Cipher
X25519 + ChaCha20
Rotation
Every 15s
Binding
Enclave attested
Replay window
None
ephemeral15.0s
Blinded credentialUnlinkable
blinded

Pattern is blinded - it proves personhood but carries no identifier.

current hash

790df5b97242cb4534b702bbc860f945b93b27af96c1822f881ab8ce2ebd965a

bound · pk:ded6ead36bce8929a6

Zero-knowledge prover

Prove it
without showing it.

Pick the attributes you want to attest. PIP blinds the underlying data and emits a succinct proof - the verifier learns the claim is true and nothing more. Your birth date, address, and account number never leave the device.

1 · select attributes to prove

2 · proof output

Select claims and generate a proof. Private values stay on-device.

Government gateway

Federal-grade proof,
zero disclosure.

PIP bridges to European public-sector identity - itsme and the eIDAS framework - to verify claims against the federal registry. A government-signed hash proves you are a citizen or of age without ever exposing your national number, birth date, or address.

attest a federal claim

registry response

The registry will return a signed yes/no. It never receives your national number.

The Seal

Consent you can
feel.

A tap is too easy to fake and too easy to regret. Every signature in PIP is a deliberate press-and-hold: the enclave only releases a proof once the ring completes. On a phone it buzzes under your thumb - intent, made physical.

Gesture
Press · hold · sign
Signature
Ed25519
Key custody
Never exported
Haptics
On-device buzz

Press and hold the seal

Fuzzy Buckets

Telemetry that
forgets the details.

Apps still need signal to work - is this a real device, roughly where, roughly when. PIP coarsens every data point into a privacy bucket before it ever leaves you, so observers see a crowd, never a person. Toggle the lens to see raw versus bucketed.

outbound telemetry · liveprotected
IP address

82.146.x.x · AS-block

Location

Bay Area · 25 km grid

Device

Mobile · current-gen

Network

Residential · broadband

Timestamp

Afternoon · ±1 h

Behaviour

Active · k-anon ≥ 50

Anonymity set1 in 48,000

Each signal is generalised until at least 50 other people share it. Buckets are computed on-device; raw values never transmit.

Hardware enclave monitor

Keys that live
in silicon.

Every private key is born and dies inside dedicated security hardware. This monitor streams the live state of the enclave - attestation, key generation, and vault encryption - for the device you are on.

Apple Secure Enclave

SEP · A/M-series

online
ok

Attestation

device proof valid

ok

Key generation

non-extractable

ok

Vault encryption

AES-256 · sealed

SEP coprocessorkSecAttrTokenIDSecureEnclaveFace ID bound0 keys exported
Technical architecture

The protocol,
under the hood.

Three pillars carry the whole system. Expand each to see how encryption, hardware, and cryptographic proofs combine into an identity only you can wield.

Identity claims travel over the federated Matrix protocol, end-to-end encrypted and homeserver-agnostic.

PIP rides on Matrix - an open, federated messaging fabric - so identity proofs move peer-to-peer across independent homeservers with no central authority to compromise or subpoena.

Each exchange is wrapped in Olm and Megolm double-ratchet encryption: forward secrecy per message, with keys derived and held only on participating devices. Servers route ciphertext they can never read.

  • Olm 1:1 + Megolm group double ratchet
  • Cross-signed device trust, no central PKI
  • Federated relays · no single point of failure
  • Metadata minimized · sealed-sender routing
matrix · federated routing
■ homeserver● deviceolm·megolm
Open source by design

Standing on
open shoulders.

Identity is too important to trust to a black box. PIP composes audited, open protocols - Matrix for transport, eIDAS for public trust, zero-knowledge circuits for disclosure. Every dependency is public, inspectable, and replaceable.

Verified open sourceAGPL-3.0 · reproducible builds
Emergency

When it has to be gone,
it is gone.

The panic switch wipes every key, proof, and route from the device in seconds - an irreversible cryptographic erase with no backdoor and no recovery. Try the simulation; nothing real is destroyed here.

Arm the panic switch to begin the self-destruct sequence.

irreversible · no recovery

Hold your own keys

Identity that answers
to you alone.

No central database, no silent profiling, no company standing between you and proof of who you are. Just cryptography you control, on hardware you trust.