Options hashmap.
Either a key OR at least one of signer/verifier is required.
Optional date?: string | DateSigning date to use if not passed.
Optional key?: Sr25519VerificationKey2020An optional key object (containing an
  id property, and either signer or verifier, depending on the
  intended operation. Useful for when the application is managing keys
  itself (when using a KMS, you never have access to the private key,
  and so should use the signer param instead).
Optional proof?: ProofA JSON-LD document with options to use
  for the proof node (e.g. any other custom fields can be provided here
  using a context different from security-v2).
Optional signer?: JSigsSignerSigner function that returns an
  object with an async sign() method. This is useful when interfacing
  with a KMS (since you don't get access to the private key and its
  signer(), the KMS client gives you only the signer function to use).
Optional useWhether to use a native canonize algorithm.
Optional verifier?: JSigsVerifierVerifier function that returns
  an object with an async verify() method. Useful when working with a
  KMS-provided verifier function.
Advanced optional parameters and overrides.
Optional keyOptional signerOptional verifierStatic Readonly CONTEXTStatic Readonly CONTEXT_Adds a signature (proofValue) field to the proof object. Called by LinkedDataSignature.createProof().
The options to use.
Resolves with the proof containing the signature value.
Cryptographic suite to produce and verify Sr25519Signature2020 linked data signatures. This is modelled after the Ed25519Signature2020 suite but uses the sr25519 signature scheme common in the polkadot ecosystem.