Sent by the PFI to Alice to convey the current status of an order. There can be many OrderStatus messages in a given Exchange

Hierarchy (view full)

Constructors

Properties

_signature: undefined | string

signature that verifies that authenticity and integrity of a message

OrderStatus's data containing a description of the status

kind: "orderstatus" = "orderstatus"

The message kind (orderstatus)

Metadata such as sender, recipient, date created, and ID

validNext: Set<MessageKind>

a set of valid Message kinds that can come after an order status

Accessors

  • get createdAt(): string
  • Message creation time. Expressed as ISO8601

    Returns string

  • get exchangeId(): string
  • ID for an "exchange" of messages between Alice - PFI. Uses the id of the RFQ that initiated the exchange

    Returns string

  • get externalId(): undefined | string
  • the external ID

    Returns undefined | string

  • get from(): string
  • The sender's DID

    Returns string

  • get id(): string
  • the message id

    Returns string

  • get orderStatus(): string
  • Current status of Order that's being executed (e.g. PROCESSING, COMPLETED, FAILED etc.)

    Returns string

  • get protocol(): `${number}`
  • the protocol version

    Returns `${number}`

  • get signature(): undefined | string
  • the message's cryptographic signature

    Returns undefined | string

  • get to(): string
  • the recipient's DID

    Returns string

Methods

  • Computes a digest of the payload by:

    Returns Uint8Array

    The SHA-256 hash of the canonicalized payload, represented as a byte array.

  • Signs the message as a jws with detached content and sets the signature property

    Parameters

    • did: BearerDid

      the signer's DID

    Returns Promise<void>

    Throws

    If the signature could not be produced

  • Valid structure of the message including the presence of the signature using the official spec JSON Schemas

    Returns void

    Throws

    If the message's structure does not match the JSON schemas

  • Validates data section of message only using the official TBDex JSON Schemas. This is useful for partially validating unsigned messages.

    Returns void

    Throws

    If the structure of the messages's data does not match the JSON schemas

  • Validates the message structure and verifies the cryptographic signature

    Returns Promise<string>

    Signer's DID

    Throws

    if the message signature is invalid

    Throws

    if the message structure is invalid

    Throws

    see Crypto.verify

  • Verifies the integrity of the cryptographic signature

    Returns Promise<string>

    Resource signer's DID

    Throws

    if the resource signature is invalid

    Throws

    if the signer's DID does not match Resource.metadata.from

  • Generates a unique id with the message kind's prefix

    Parameters

    Returns string

  • Parses a json message into an OrderStatus

    Parameters

    Returns Promise<OrderStatus>

    The parsed OrderStatus

    Throws

    if the orderstatus could not be parsed or is not a valid OrderStatus

Generated using TypeDoc