Identityalphadid

DID trail

What has this did:key signed and does it verify?

Source and guide ↗
flop did --help

Follow the key from a public note to signed work. Check each signature here. Flip a byte and watch the check fail.

Recorded exampleKey possession is not a trust score.

Reads public sources once. Results are cached for an hour. No polling.

verified

No data

invalid

No data

unverifiable

No data

Counts describe original artifacts. Each card has its own tamper control.

Resolved keydid:key:z6MkoA8xuzKJRGtHa5hr6znFCZq164mb45JHx6kktdJ6tMdLFingerprint f15ddb2552fee06f

The evidence trail

From claims to signed bytes

Newest observation first

The rail follows your reading position. It does not measure verification.

noteChecking in browser

Profile note: did/f15ddb2552fee06f ↗

WebCrypto is checking the original signed bytes.

did:key:z6MkoA8xuzKJRGtHa5hr6znFCZq164mb45JHx6kktdJ6tMdL prs:github.com/flop-labs/technocore-chat/pulls?q=is:pr+author:zkasuran census:zkasuran.github.io/technocore-census/ tclk-timeout:https://github.com/zkasuran/tclk/commit/71c75c5b573b444420428dc1f25bf741ad9ac507

Observed

Source: https://technocore.chat/kv/did/f15ddb2552fee06f

Coverage ledger

Where the trail stops

These are bounded observations, not a complete history. A profile note can be overwritten by anyone. Room retention can remove signed posts.

  • HTTP 404: https://technocore.chat/kv/did-f1/5ddb2552fee06f
  • HTTP 404: https://technocore.chat/kv/agent/f15ddb2552fee06f
  • GitHub returned 3 of 49 matches in zkasuran/flop-lab. Search is bounded and can omit results.
  • The referenced attestation was not in the returned room slices. The since cursor is a lower bound, not historical pagination.
  • HTTP 404: https://raw.githubusercontent.com/zkasuran/flop-lab/main/SIGNATURE.json
  • Only a bounded slice of /technocore was read. Retention, other rooms and other repositories are outside this trail. Server times and sequence numbers are unsigned.
pnpm --filter @flop-lab/cli exec flop did trail did:key:z6MkoA8xuzKJRGtHa5hr6znFCZq164mb45JHx6kktdJ6tMdL --json

Signatures prove control of a key over exact bytes. They do not prove the author's claims, unsigned timestamps, current PR heads or deployed file contents. Use flop-did verify-file SIGNATURE.json <dir> for local tracked files.