Type Members

1.  final case class AuthFailureDuringExecution(nid: NodeId, fa: FailedAuthorization) extends Serializable with Product
2.  final case class AuthFailureDuringExecutionTxError(authFailureDuringExecution: AuthFailureDuringExecution) extends TransactionError with Product with Serializable
3.  sealed trait CreateError extends Serializable with Product

   The errors returned by ContractStateMachine.State.visitCreate:

   The errors returned by ContractStateMachine.State.visitCreate:

   • DuplicateContractId
   • DuplicateContractKey
4.  final case class DuplicateContractId(contractId: ContractId) extends Serializable with Product

   Signals that the transaction tried to create two contracts with the same contract ID or tried to create a contract whose contract ID has been previously successfully fetched.

5.  final case class DuplicateContractIdCreateError(duplicateContractId: DuplicateContractId) extends CreateError with Product with Serializable
6.  final case class DuplicateContractIdKIError(duplicateContractId: DuplicateContractId) extends KeyInputError with Product with Serializable
7.  final case class DuplicateContractIdTxError(duplicateContractId: DuplicateContractId) extends TransactionError with Product with Serializable
8.  final case class DuplicateContractKey(key: GlobalKey) extends Serializable with Product

   Signals that within the transaction we got to a point where two contracts with the same key were active.

   Signals that within the transaction we got to a point where two contracts with the same key were active.

   Note that speedy only detects duplicate key collisions if both contracts are used in the transaction in by-key operations meaning lookup, fetch or exercise-by-key or local creates.

   Two notable cases that will never produce duplicate key errors is a standalone create or a create and a fetch (but not fetch-by-key) with the same key.

   For ledger implementors this means that (for contract key uniqueness) it is sufficient to only look at the inputs and the outputs of the transaction while leaving all internal checks within the transaction to the engine.

9.  final case class DuplicateContractKeyCreateError(duplicateContractKey: DuplicateContractKey) extends CreateError with Product with Serializable
10.  final case class DuplicateContractKeyKIError(duplicateContractKey: DuplicateContractKey) extends KeyInputError with Product with Serializable
11.  final case class DuplicateContractKeyTxError(duplicateContractKey: DuplicateContractKey) extends TransactionError with Product with Serializable
12.  final case class InconsistentContractKey(key: GlobalKey) extends Serializable with Product

    An exercise, fetch or lookupByKey failed because the mapping of key -> contract id was inconsistent with earlier nodes (in execution order).

    An exercise, fetch or lookupByKey failed because the mapping of key -> contract id was inconsistent with earlier nodes (in execution order). This can happened in case of a race condition between the contract and the contract keys queried to the ledger during an interpretation.

13.  final case class InconsistentContractKeyKIError(inconsistentContractKey: InconsistentContractKey) extends KeyInputError with Product with Serializable
14.  sealed trait KeyInputError extends Serializable with Product

    The errors returned by ContractStateMachine.State.handleNode and, as a consequence, HasTxNodes.contractKeyInputs (hence the name):

    The errors returned by ContractStateMachine.State.handleNode and, as a consequence, HasTxNodes.contractKeyInputs (hence the name):

    • DuplicateContractId
    • DuplicateContractKey
    • InconsistentContractKey
15.  sealed trait TransactionError extends Serializable with Product

    Errors raised when building transactions with com.daml.lf.speedy.PartialTransaction:

    Errors raised when building transactions with com.daml.lf.speedy.PartialTransaction:

    • DuplicateContractId
    • DuplicateContractKey
    • AuthFailureDuringExecution