@escro/sdk 0.4.0 → 0.4.1

package/dist/index.cjs

@@ -779,7 +779,16 @@ async function signAndSend(base64Tx, wallet, connection, cluster) {
   const signature = await connection.sendRawTransaction(raw, {
     skipPreflight: false
   });
-  await connection.confirmTransaction({ signature, blockhash, lastValidBlockHeight }, "confirmed");
+  const { value } = await connection.confirmTransaction(
+    { signature, blockhash, lastValidBlockHeight },
+    "confirmed"
+  );
+  if (value.err !== null) {
+    throw new EscroError(
+      `Transaction ${signature} failed at execution: ${JSON.stringify(value.err)}`,
+      "TX_FAILED"
+    );
+  }
   return signature;
 }
 async function buildReleasePaymentTx(params) {
@@ -904,9 +913,11 @@ var Escro = class {
    * {@link Escro.releasePayment}, reporting whether the API recorded the release.
    * `ESCROW_NOT_SETTLED` (the API's RPC does not yet show the escrow closed), the codes
    * {@link Escro.confirm} retries and a network failure are retried for about 30 s. A
-   * failure never throws: the release already landed, so the signature is returned with
-   * `confirm.landed: false` and an `EscroConfirmError` (the API's code, or
-   * `NETWORK_ERROR` when the last call never reached it).
+   * failed record never throws: the release already landed, so the signature is returned
+   * with `confirm.landed: false` and an `EscroConfirmError` (the API's code, or
+   * `NETWORK_ERROR` when the last call never reached it). A release that failed at
+   * execution on chain throws an {@link EscroError} with code `TX_FAILED`, and the API is
+   * never asked to record it.
    *
    * @returns `{ signature, confirm }`.
    */