On-line Signature Verification Based on Forward and Backward Variances of Signature

A signature is one of the characteristics of human behavior and can be used to identify individuals. Signatures are widely implemented in everyday life and are highly socially accepted \ reference {jain 1}. Signatures are mainly used to validate important documents such as bank checks. However, in many cases human eyes can not distinguish authenticity signatures, which is a serious problem in security systems. Therefore, the need for a high-accuracy automatic signature verification system is increasing.

In order to understand the importance of generalized signature verification, consider the use case of interblock communication. In this use case, the user MUST provide a Mercury certificate containing up to 128 sha256 operations and / or 14 signature verifications. All of these data and calculations are done only to show that a particular action is taking place in a particular block on the outer chain and / or that that particular block is being verified by the + 2/3 generator Thing. The business logic merely confirms that the block ID is valid and the operation is in the block. In addition to computing the public key derived from the signature, you do not need to use business logic to prove the operation of operations within the block.

Previously, we discussed encryption using asymmetric keys. One important use case for using asymmetric keys when creating and verifying digital signatures. Digital signatures are very similar to personal signatures on paper. As with paper signatures, digital signatures are useful for identifying individuals. It also helps to prevent messages from being tampered with during transmission. Let's use examples to understand digital signatures. Alice wishes to send a message to Tom. How does Tom recognize and confirm that the message is from Alice and that the message has not been changed or altered during transmission? Alice receives the message he wants to send to Tom, generates the hash, encrypts the hash with his private key (yes, secret key), and adds the resulting password data to the original message .