Designated Verifier Signature (DVS) scheme allows a client entity to sign a message/document which could be verified only by the designated verifier. The signatures are produced on the end user’s side either by the DVS Web Plugin as described in this article or by the mobile applications using the Android and iOS SDKs.
You can read more about DVS in the concepts section.
# What Can Be Signed
We are using the term ‘document’ in this article to represent the data that is cryptographically signed. This however does not mean there are restrictions on the type of data that you want to sign. DVS can be used on any blob of data as the signature is produced for the hash digest of the data rather than the raw value itself. On top of what is traditionally considered a document, you can also sign any type of transaction, like a transfer of financial funds or a representation of a write operation to be stored in an audit log.
It is important to note that the usage of a hash digest instead of the raw data also means that the actual value of what is being signed is never transmitted to the MIRACL Trust platform. This holds true for all parts of the process - both signing and verification.
