A DID controller can mitigate some timing-related issues (e.g., some late publishing scenarios) by declaring their knowledge of the current anchor timings.
When the DID owner self-asserts their relative timing, a Sidetree-based implementation can compare the self-asserted timing with the timing of the actual anchoring. If the DID owner's timing does not match with the actual timing (within an acceptable range), the operation can be considered invalid - similar to an invalid signature. The concept of timing is implementation-specific. E.g., In implementations with blockchain-based anchoring, "timing" likely means block height. In other implementations, "timing" might mean timestamp. In either case, the "timing" can be represented numerically such that validation can be generically handled.
A DID controller can mitigate some timing-related issues (e.g., some late publishing scenarios) by declaring their knowledge of the current anchor timings.
When the DID owner self-asserts their relative timing, a Sidetree-based implementation can compare the self-asserted timing with the timing of the actual anchoring. If the DID owner's timing does not match with the actual timing (within an acceptable range), the operation can be considered invalid - similar to an invalid signature. The concept of timing is implementation-specific. E.g., In implementations with blockchain-based anchoring, "timing" likely means block height. In other implementations, "timing" might mean timestamp. In either case, the "timing" can be represented numerically such that validation can be generically handled.