HOW IT WORKS

The journey of a proof.

Six moments, from a key being born inside your phone to a receipt only you hold. No jargon. Nothing hidden in the middle.

Watch it happen.

IN BUILD · P1

This is the whole thing. Every step is a real step, and every step says how far it has actually been built.

Six moments, in order.

A key is born inside your phone.

The first time you set up, your phone builds a key for you inside its own locked chip, the same guarded corner that holds your fingerprint. Nobody mails it to you. Nobody keeps a spare.

IN BUILD · P1 the part that does this is not finished
For engineers

The key pair is generated in the device secure element; the private half is marked non-exportable and every use is gated behind a device unlock. The public half is the subject key of everything you are later issued, named by its RFC 7638 thumbprint (did:jwk style).

Status: no wallet exists in the xORBIS platform today. See the register.

Someone you already trust gives you a document.

Your bank, your city, your employer signs a document and hands it to your phone. It arrives looking like a card. It is bound to the key from step one, so only your phone can use it: a copy on someone else's device is worthless.

IN BUILD · P1
For engineers

SD-JWT VC signed by the organisation's own key, delivered over OpenID4VCI, bound to the device key so a stolen copy cannot be presented. The signing domain is the organisation's own, a DNS record they can delete to fire us.

Status: the platform ships storage, secrets and health seams; the issuing path is the next build.

GIVEN BY · your city
Proof of age
Held byyou, on your phone
Statusvalid
Renewsyearly

A website asks one question.

Not "who are you". One question, with a reason attached, from a name your phone can look up on a public list of who is allowed to ask. If they are not on the list, you find out before you decide anything.

IN BUILD · P1
For engineers

An OpenID4VP request carrying a DCQL query that names exactly the claims wanted. The requesting party is resolved against a public register before the sheet renders, and an over-broad query demotes the sheet to its warning state.

Bottle & Vine — checkout
Are you over 18?
This shop must check your age. It does not need to know who you are.
waiting for your proof…

You see the same sheet, every time.

A shop, a bank, a government office — the sheet looks the same. One fact per row. What they keep, declared on the sheet. And the ring around their name is drawn open at exactly one point: the boundary is closed except where you approve.

IN BUILD · P1
For engineers

The sheet is one component with one anatomy across every request type: typed action, requesting party, per-claim rows, declared retention, deliberate approval gesture. Field-level choice is real selective disclosure over SD-JWT, not a filter applied after the fact.

PROVE
Bottle & Vine on the public register
Name stays on phone
Date of birth stays on phone
Address stays on phone
Bottle & Vine keeps: nothing. This proof expires in 60 seconds.

One answer crosses. Nothing else moves.

You approve with a deliberate slide — never a stray tap. One answer leaves your phone: yes. The rows you kept were never sent and then held back. They simply never went.

IN BUILD · P1
For engineers

Only the selected disclosures travel; the rest stay inside the document, which never leaves the device. The answer is a derived claim (over-18 rather than a birth date), so the shop cannot recompute anything it was not given.

WHAT CROSSES THE GAP
Age over 18yes → crossed
Namenever sent
Date of birthnever sent
Photonever sent
Addressnever sent

One row of five. That is the whole product.

A receipt lands that only you hold.

Your phone writes down what you shared, with whom, and when. It is yours. We do not get a copy, which also means we can never be asked for one.

PLANNED not built yet, and the register says so
For engineers

A local, signed record per disclosure, stored on device only, exportable by the person and by nobody else. No server-side log of who proved what to whom exists, because building one would recreate the database this whole design removes.

YOUR RECORD
Shared "age over 18" with Bottle & Vine.

Kept on this phone. Not on ours.

What that adds up to.

Three things are true of every step you just walked.

Try the ceremony yourself