The scenarios where the current assertion method is deleted or replaced are not documented and are not reflected in the update algorithm.
e.g., if one wants to remove an old assertion method (used to sign previous event proofs) and add a new one, it is unclear how the transition should be handled. Should the update event be signed only with the old assertion method, or with both?
This needs to be clearly defined to avoid ambiguous or transitive transition flows (e.g., adding a new assertion, signing with the old one, then removing the old assertion and signing with the new one, etc.).
The scenarios where the current assertion method is deleted or replaced are not documented and are not reflected in the update algorithm.
e.g., if one wants to remove an old assertion method (used to sign previous event proofs) and add a new one, it is unclear how the transition should be handled. Should the update event be signed only with the old assertion method, or with both?
This needs to be clearly defined to avoid ambiguous or transitive transition flows (e.g., adding a new assertion, signing with the old one, then removing the old assertion and signing with the new one, etc.).