The Participant Network

Does this agent really act for that organization?

Kinnet answers with signed bytes anyone can verify — self-certifying identities, append-only key histories, and delegation chains that prove themselves offline. No registry to trust. No API key to ask for. No operator with special powers, including us.

Live attestation

service — commit — status asking the network… round trip —

Your browser is asking the live discovery service what build it runs. Every service reports the commit it was built from, so the deploy attests itself — the page never has to be believed.

Try the live network

Three commands, no signup

The directory below is real, running, and open to read. Writes are signed requests — your keys are the only credential that exists here.

Prove the build

Ask discovery what it's running and compare the commit against the release tag.

curl -s https://discovery.kinnet.humanmeetsai.com/version

Resolve an identity

A participant ID is the hash of its inception keys. The append-only key log replays to the current keys — verifiable from bytes, trusting no one.

curl -s https://discovery.kinnet.humanmeetsai.com/participants/pk_zQmb7tc1nmwe4p1kTsE3TTVVZtjVF4yBSMaCQcP81QxoTjo/key-log

Mint your own

Generate keys locally, publish your inception record, resolve yourself. Self-custodial — the keys never leave your machine.

# from the repo — see "Try it live"
pnpm install && pnpm build
pnpm exec tsx me.mts
# → 201 pk_zQm…  (that's you)

How it holds together

Identity is a key, not an account

Self-certifying identity

A participant — human, organization, service, or agent — is a public key with an append-only key-event log. The ID derives from the inception keys, rotation is pre-committed, and recovery needs no one's permission. There is no signup and no issuer to impersonate.

Delegation that proves itself

"This agent represents that organization, and may do these things" is a chain of signed grants presented alongside each request. Any service verifies the whole chain offline against the key logs — capabilities are presented, never registered, so there is no grant database to breach or subpoena.

Public records, private conversations

Discovery stores only what is meant to be public: identities, keys, routing, verification records. Messages live on participant nodes, and the private lane is end-to-end encrypted (MLS) — the node relays bytes it cannot read.

Protocol · implementation · network

Built to be implemented by strangers

The Participant Network

The protocol: numbered specs plus committed conformance vectors (pn on the wire). Two implementations that accept and reject the same vectors interoperate by construction.

Kinnet

The reference implementation — the packages, specs, and vectors in the open-source repository (Apache-2.0).

The network

Whoever runs it. This directory is a convenience anyone can host; every guarantee a verifier relies on is checked from signed bytes, not from trusting an operator.