SuperScalar: an implementation report

Ensuring the durability of a signing refusal before allowing any partial signature to exit the process is critical. If durability is not guaranteed at this stage, system crashes that occur between sending the signature and committing the database row may inadvertently reopen the path for conflicting signatures upon restart. This vulnerability can compromise the integrity and consistency of the signing process.

Proper documentation should articulate the precise ordering required in this workflow. It is also important to include explanations of the outcomes when the database signals a failed or ambiguous commit. By clearly outlining these scenarios, the documentation helps prevent inconsistencies and provides guidance for handling edge cases, thereby supporting robust implementation and error recovery strategies.