Prototype — simulated data, not embedded yet
For the curious
No blockchain. No tokens. No account.
Dibs runs on decentralized identifiers — but not the kind you're thinking of. Here's exactly how the machine works.
Not us
Web3 DIDs
- Anchored to blockchains
- Managed in crypto wallets
- Entangled with tokens and speculation
- Identity as an asset you trade
Dibs
Us
Industrial DIDs
- The kind supply chains use to track pharmaceuticals and aircraft parts
- A serial number plus signed custody records
- No chain, no token, nothing to buy
- Identity as a receipt, not an investment
DIDs like shipping manifests, not like crypto wallets.
The mechanics
Plain language, then the machine note.
Your root lives in your phone's secure hardware
The same chip that guards Face ID and Apple Pay generates a master identifier that never touches the internet.
hardware enclave · biometric-bound · never transmitted
Every dib is a disposable child identity
Minted from your root, unique to one store, one task. The store sees a serial number, never you.
one child DID per relationship · unlinkable
Your place is yours alone, enforced in the database
One device root can hold exactly one place per drop. Not by policy — by constraint. A second claim from the same device is rejected before it exists.
unique(line, credential) · 3 registrations per IP per hour
Every action leaves a signed receipt
A custody chain of everything done under that authority, held by you. Burning the dib revokes the authority; the receipts survive.
signed custody chain · revocation ≠ deletion of history
What they get
Proof of one live human, and a place in line.
What they never get
Your name, your history, your device, your other dibs, anything to profile or resell.
Enough reading. Watch it run.