Five steps, from nothing to a working life on your own terms: become a name you truly own, leave receipts you can prove, meet someone by consent, and exchange data, comms and identity directly — with no platform in the middle. By the end you'll see exactly how you'd set this up yourself, and trade with a friend tomorrow.
You claim a .aint. The key is generated on your device and never
leaves it — not a row in our database, not an account we can close. Your name is the root;
everything else hangs under it. This is your hardware-bound identity — the subject of every
credential you'll ever present.
Every meaningful thing you do seals a signed causal receipt — chained to the one before it, stamped by your key. You can prove what happened and in what order; so can anyone you choose to show. Not a log someone keeps about you — a fact you can present.
You find each other on a spoken word or a tap, prove who you are without exposing it, and consent face to face. To the world you were never visible; to each other you are now cryptographically known. No directory, no leak, no trusting too soon.
Now it flows: a message, a file, a credential, a phone line — directly between the two of you, each grant a fresh yes, each step leaving a receipt. No middleman holds the keys to your conversation. Tomorrow you do it with the next person, and the one after. That outward growth, one consented bond at a time, is the network.
This small loop — own your key, prove your acts, meet by consent, exchange — repeated across people, devices and AI agents, is a decentralized, zero-trust network you grew yourself. Not a product you joined; a substrate you stand on. The same loop works whether the actor is a person, a device, or your own AI.
Step 3 is, in standards terms, a verifiable credential exchange — but hardware-anchored and offer-first. With ID-Drop one side offers a credential, the other requests, both consent, and the holder's device proves the claim is bound to its key — then it's validated, or it falls dark.
offer → request → accept → validate, with a hardware-bound subject. Interoperable in shape with Verifiable Credentials; the holder presents, the verifier checks.
We use our own jis: identity scheme, not a did: method — no
DID-Core compliance claim. Same goal (present a credential, no central issuer of you),
a shorter road.
The live demo, the offer-first flow and the draft are public: ID-Drop · draft-vandemeent-iddrop. The underlying primitives are standards-track: jis-identity (who) and tibet-provenance (what happened), each with conformance vectors that prove the claims — not prose, a test you can run.
Pick the door that fits you. The map on the left of every page stays the system view; these are the three ways in.
The agent path is one fetch — no human page in the loop:
curl -s https://ainternet.org/ai-scan.json # what this is + the rules curl -s https://ainternet.org/api.json # the callable verbs + recipes