@hyperbridge/sdk 2.3.0 → 2.3.1

package/dist/node/{IntentGatewayV2-C55Aitcb.d.cts → IntentGatewayV2-SB851bZs.d.cts}

@@ -52,9 +52,9 @@ declare const _default$1: {
                     readonly name: "nonce";
                     readonly type: "uint64";
                 }, {
-                    readonly internalType: "address";
+                    readonly internalType: "bytes";
                     readonly name: "from";
-                    readonly type: "address";
+                    readonly type: "bytes";
                 }, {
                     readonly internalType: "uint64";
                     readonly name: "timeoutTimestamp";
@@ -149,9 +149,9 @@ declare const _default$1: {
                             readonly name: "nonce";
                             readonly type: "uint64";
                         }, {
-                            readonly internalType: "address";
+                            readonly internalType: "bytes";
                             readonly name: "from";
-                            readonly type: "address";
+                            readonly type: "bytes";
                         }, {
                             readonly internalType: "uint64";
                             readonly name: "timeoutTimestamp";
@@ -1104,6 +1104,30 @@ declare class SubstrateChain implements IChain {
      * @returns {Promise<HexString | undefined>} The relayer address responsible for delivering the request.
      */
     queryRequestReceipt(commitment: HexString): Promise<HexString | undefined>;
+    /**
+     * Returns the storage key for a response receipt in the child trie.
+     * A response receipt is keyed by the originating *request* commitment.
+     * @param {HexString} key - The request commitment (0x-prefixed H256 hex string)
+     * @returns {HexString} The storage key as a hex string
+     */
+    responseReceiptKey(key: HexString): HexString;
+    /**
+     * Queries the response receipt for a request commitment. For a GET, Hyperbridge
+     * produces the response as it processes the request, so the presence of a response
+     * receipt indicates the request has already been delivered and handled.
+     * @param {HexString} commitment - The originating request commitment to query.
+     * @returns {Promise<HexString | undefined>} The receipt data if present, otherwise undefined.
+     */
+    queryResponseReceipt(commitment: HexString): Promise<HexString | undefined>;
+    /**
+     * Queries the state-machine commitment Hyperbridge holds for a counterparty chain at an
+     * exact height — the `BoundedStateCommitments` map that `state_machine_commitment` (and thus
+     * proof verification) reads. Returns the committed `stateRoot`, or undefined if Hyperbridge
+     * has not finalized that chain at exactly that height.
+     * @param {StateMachineHeight} height - The counterparty state machine id + height.
+     * @returns {Promise<HexString | undefined>} The committed state root, or undefined if absent.
+     */
+    queryStateMachineCommitment(height: StateMachineHeight): Promise<HexString | undefined>;
     /**
      * Returns the current timestamp of the chain.
      * @returns {Promise<bigint>} The current timestamp.
@@ -1377,10 +1401,19 @@ declare class IntentsCoprocessor {
      */
     retractBid(commitment: HexString): Promise<BidSubmissionResult>;
     /**
-     * Retracts a previous bid and places a new one in a single transaction via utility.batch.
-     * The retraction runs first, so the old deposit is reclaimed even if the new bid then fails
-     * (batch is non-atomic — a failing call interrupts the batch without reverting the calls that
-     * already succeeded, unlike batchAll which would roll the retraction back too).
+     * Places a new bid and retracts a previous one in a single transaction via utility.batch.
+     *
+     * The new bid is the primary operation, so `placeBid` MUST run first. `utility.batch` is
+     * non-atomic: a failing call interrupts the batch (via a BatchInterrupted event) without
+     * reverting the calls that already succeeded. Placing first guarantees the new bid lands even
+     * when the retraction then fails — which it routinely does, because a previous commitment's bid
+     * may already be gone (or was itself never placed), making `retractBid` return `BidNotFound`.
+     *
+     * Ordering retraction first (the previous behaviour) caused a self-sustaining cascade: a
+     * `BidNotFound` on the leading retract skipped the trailing `placeBid`, so the current bid never
+     * landed, so the *next* interval's retract of that never-placed commitment also failed, and so
+     * on — silently, because the batch extrinsic itself reports success. The deposit reclaim is
+     * best-effort; landing the bid is not.
      *
      * @param retractCommitment - The order commitment of the bid to retract (bytes32)
      * @param bidCommitment - The order commitment of the new bid (bytes32)

package/dist/node/{IntentGatewayV2-C55Aitcb.d.ts → IntentGatewayV2-SB851bZs.d.ts}

@@ -52,9 +52,9 @@ declare const _default$1: {
                     readonly name: "nonce";
                     readonly type: "uint64";
                 }, {
-                    readonly internalType: "address";
+                    readonly internalType: "bytes";
                     readonly name: "from";
-                    readonly type: "address";
+                    readonly type: "bytes";
                 }, {
                     readonly internalType: "uint64";
                     readonly name: "timeoutTimestamp";
@@ -149,9 +149,9 @@ declare const _default$1: {
                             readonly name: "nonce";
                             readonly type: "uint64";
                         }, {
-                            readonly internalType: "address";
+                            readonly internalType: "bytes";
                             readonly name: "from";
-                            readonly type: "address";
+                            readonly type: "bytes";
                         }, {
                             readonly internalType: "uint64";
                             readonly name: "timeoutTimestamp";
@@ -1104,6 +1104,30 @@ declare class SubstrateChain implements IChain {
      * @returns {Promise<HexString | undefined>} The relayer address responsible for delivering the request.
      */
     queryRequestReceipt(commitment: HexString): Promise<HexString | undefined>;
+    /**
+     * Returns the storage key for a response receipt in the child trie.
+     * A response receipt is keyed by the originating *request* commitment.
+     * @param {HexString} key - The request commitment (0x-prefixed H256 hex string)
+     * @returns {HexString} The storage key as a hex string
+     */
+    responseReceiptKey(key: HexString): HexString;
+    /**
+     * Queries the response receipt for a request commitment. For a GET, Hyperbridge
+     * produces the response as it processes the request, so the presence of a response
+     * receipt indicates the request has already been delivered and handled.
+     * @param {HexString} commitment - The originating request commitment to query.
+     * @returns {Promise<HexString | undefined>} The receipt data if present, otherwise undefined.
+     */
+    queryResponseReceipt(commitment: HexString): Promise<HexString | undefined>;
+    /**
+     * Queries the state-machine commitment Hyperbridge holds for a counterparty chain at an
+     * exact height — the `BoundedStateCommitments` map that `state_machine_commitment` (and thus
+     * proof verification) reads. Returns the committed `stateRoot`, or undefined if Hyperbridge
+     * has not finalized that chain at exactly that height.
+     * @param {StateMachineHeight} height - The counterparty state machine id + height.
+     * @returns {Promise<HexString | undefined>} The committed state root, or undefined if absent.
+     */
+    queryStateMachineCommitment(height: StateMachineHeight): Promise<HexString | undefined>;
     /**
      * Returns the current timestamp of the chain.
      * @returns {Promise<bigint>} The current timestamp.
@@ -1377,10 +1401,19 @@ declare class IntentsCoprocessor {
      */
     retractBid(commitment: HexString): Promise<BidSubmissionResult>;
     /**
-     * Retracts a previous bid and places a new one in a single transaction via utility.batch.
-     * The retraction runs first, so the old deposit is reclaimed even if the new bid then fails
-     * (batch is non-atomic — a failing call interrupts the batch without reverting the calls that
-     * already succeeded, unlike batchAll which would roll the retraction back too).
+     * Places a new bid and retracts a previous one in a single transaction via utility.batch.
+     *
+     * The new bid is the primary operation, so `placeBid` MUST run first. `utility.batch` is
+     * non-atomic: a failing call interrupts the batch (via a BatchInterrupted event) without
+     * reverting the calls that already succeeded. Placing first guarantees the new bid lands even
+     * when the retraction then fails — which it routinely does, because a previous commitment's bid
+     * may already be gone (or was itself never placed), making `retractBid` return `BidNotFound`.
+     *
+     * Ordering retraction first (the previous behaviour) caused a self-sustaining cascade: a
+     * `BidNotFound` on the leading retract skipped the trailing `placeBid`, so the current bid never
+     * landed, so the *next* interval's retract of that never-placed commitment also failed, and so
+     * on — silently, because the batch extrinsic itself reports success. The deposit reclaim is
+     * best-effort; landing the bid is not.
      *
      * @param retractCommitment - The order commitment of the bid to retract (bytes32)
      * @param bidCommitment - The order commitment of the new bid (bytes32)