message: Update crypto-verify README.md
diff: @@ -12,13 +12,13 @@ Input formats are serialized byte slices for Message, Signature, and Public Key.
  - Message: A serialized message. It will be hashed by the contract using SHA-256, and the hashed value will be fed to the
  verification function.
  -- Signature: Serialized signature, in Cosmos format (64 bytes). Ethereum DER needs to be converted.
  -- Public Key: Compressed (33 bytes) or uncompressed (65 bytes) serialized public key.
  +- Signature: Serialized signature, in "compact" Cosmos format (64 bytes). Ethereum DER needs to be converted.
  +- Public Key: Compressed (33 bytes) or uncompressed (65 bytes) serialized public key, in SEC format.
  Output is a boolean value indicating if verification succeeded or not.
  ## Remarks
  -In case of an error (wrong or unsupported inputs), the current (mock) implementation panics. This can be easily debugged,
  -and optimizes for the production use case, where there is nothing the contract developer should or could handle.
  +In case of an error (wrong or unsupported inputs), the current implementation returns an error, which can be
  +easily handled by the contract, or returned to the client.
  