Blockchain Transaction Rollback for Data Consistency

The patent applies preliminary action by locking transaction accounts before executing multiple transaction operations. This pre-locking mechanism prevents other operations from interfering with the locked accounts during the transaction process, ensuring that the accounts remain in a consistent state throughout the batch operation execution, thus maintaining reliability while enabling multiple operations.

The patent implements discarding and recovering through the rollback mechanism. When any transaction operation fails in a batch, the system discards all successful operations by rolling back to the pre-transaction state. This ensures that partial successes do not compromise data consistency, and the system recovers to a known good state, maintaining reliability.

The patent uses preliminary action by recording the state of transaction accounts before batch operations begin. This pre-recording of initial states enables rapid rollback by simply restoring to the recorded state rather than performing complex reverse operations, thereby reducing time consumption while maintaining accuracy through consistent state restoration.

The patent applies copying by creating a snapshot or copy of the transaction account states before operations are executed. This copy serves as the rollback target, allowing the system to quickly restore accuracy by replacing current states with the copied pre-transaction states, minimizing time loss while ensuring data integrity.

The patent applies preliminary action by locking all transaction accounts at the beginning of batch operations before any actual transactions are executed. This upfront locking ensures that no other operations can interfere with the locked accounts during the entire batch processing, maintaining consistency while allowing the batch operations to proceed without repeated locking/unlocking overhead, thus preserving throughput.

The patent implements continuity of useful action by maintaining the locked state throughout the entire batch operation execution without releasing locks between individual transactions. This continuous locking eliminates the need for repeated lock acquisition and release operations, reducing operational overhead and maintaining system throughput while ensuring consistency across all batch operations.