• Public
  • Public/Protected
  • All

Interface AuthenticationTemplateScenarioOutput

An example output used to define a scenario for an authentication template.


  • AuthenticationTemplateScenarioOutput



Optional Readonly lockingBytecode

lockingBytecode: string | { overrides?: AuthenticationTemplateScenarioData; script?: string | null }

The bytecode used to encumber this transaction output for this scenario. This value is included in signing serializations, and therefore has an effect on the transaction context for this scenario.

This value may be provided as either a hexadecimal-encoded string or an object describing the required compilation.

If undefined, this defaults to {}, which uses the default values for script and overrides, respectively.

Optional Readonly satoshis

satoshis: number | string

The value of the output in satoshis, the smallest unit of bitcoin.

In a valid transaction, this is a positive integer, from 0 to the maximum number of satoshis available to the transaction.

The maximum number of satoshis in existence is about 1/4 of Number.MAX_SAFE_INTEGER (9007199254740991), so typically, this value is defined using a number. However, this value may also be defined using a 16-character, hexadecimal-encoded string, to allow for the full range of the 64-bit unsigned, little-endian integer used to serialize satoshis in the encoded output format, e.g. "ffffffffffffffff". This is useful for representing scenarios where intentionally excessive values are provided (to ensure an otherwise properly-signed transaction can never be included in the blockchain), e.g. transaction size estimations or off-chain Bitauth signatures.

If undefined, this defaults to: 0.

Generated using TypeDoc