Keeta LogoKeeta Logo@keetanetwork/keetanet-client
    Preparing search index...

    Interface signOptionsType

    Options for signing and verifying

    interface signOptionsType {
        ancillaryData?: ArrayBuffer;
        forCert?: boolean;
        namespace?: string | ArrayBuffer;
        raw?: boolean;
    }
    Index

    Properties

    ancillaryData?: ArrayBuffer

    Additional data (usually raw value) that is being signed For example, when signing a block this would be the output of UnsignedBlock.toBytes(false)

    forCert?: boolean

    Is this signing or verification for an X.509 certificate ? The format can be different between our native format and what is accept for X.509

    namespace?: string | ArrayBuffer

    Optional domain-separation namespace applied to data before hashing and signing (or verifying), using the NamespacePrefix schema. This prevents cross-context signature reuse between applications that share a key but use different namespaces.

    Signer and verifier MUST supply the same namespace. Domain separation is applied regardless of raw; raw controls only the subsequent hash step.

    If namespace is a string, the 1-255 byte limit applies to the UTF-8 encoded namespace bytes, not the string's character count.

    raw?: boolean

    Perform signing or verification on the raw data ?

    The default is false (meaning the data will get hashed before signed)