They are doing both key rotation AND if your key leaks then it requires a human intervention to decide what is the correct state!!! Also I didn't read to the end, but as soon as this is worth fucking with I will spam the shit out of their registeries to see how would they survive without a Blockchain countering Sybil and pruning history of updates.

All just to say "we don't use Blockchain"... Well Pkarr doesn't either and it definitely can do this retarded form of key rotation if you insist.

Why is no one serious?

> Equivocation
Because did:dfos has no global consensus layer, an identity holder could theoretically sign two different operations at the same chain position (same previousOperationCID, different payloads). This creates a fork — two valid chain branches.

Equivocation is detectable: a verifier who encounters two valid operations sharing a previousOperationCID can identify the conflict. Resolution policy for equivocation (reject both branches, prefer one, flag for human review) is an application-level concern and is deliberately outside the scope of this method specification.

In practice, equivocation requires the identity holder to act against themselves — no external party can extend an identity chain, since all operations must be signed by a current controller key.