@paraswap/dex-lib 3.2.5-return-amount-pos.7 → 3.3.0-v6-only

package/README.md

@@ -179,7 +179,6 @@ getDexParam(
       dexFuncHasRecipient: false,
       exchangeData: swapData,
       targetExchange: this.swETHAddress,
-      returnAmountPos: undefined,
     };
  }
 ```
@@ -217,10 +216,6 @@ getDexParam(
           exchangeData: swapData,
           targetExchange: this.config.wooPPV2Address,
           transferSrcTokenBeforeSwap: this.config.wooPPV2Address,
-          returnAmountPos:
-            side === SwapSide.SELL
-              ? extractReturnAmountPosition(ifaces.PPV2, 'swap', 'realToAmount')
-              : undefined,
         };
     }
 
@@ -238,13 +233,6 @@ In order to ensure correctness of encoding please make use of these parameters:
 - `transferSrcTokenBeforeSwap`: if your DEX requires a transfer before the swap happens, rather than encoding it within the `exchangeData`
 - `targetExchange`: the contract against which we swap
 - `spender`: a contract that we need to approve in order to swap against `targetExchange`. If not set, then the spender will be `targetExchange`
-- `returnAmountPos`: the offset position inside the return values from an external call to a dex where we expect our swap return value (output amount) to be.
-  There is a helper function `extractReturnAmountPosition` which could be used to automatically calculate return amount position.
-  If the DEX swap function doesn't support outputs then `undefined` should be passed.
-  For example:
-    1. swap(uint256,uint256) returns (uint256 returnAmount) -> return amount pos will be 0
-    2. swap2(uint256,uint256) returns (uint256 timestamp, uint256 returnAmount) -> return amount pos will be 32
-    3. swap3(uint256,uint256) -> return amount pos will be undefined
 
 To verify the validity of the encoding, we recommend looking at [this link](#writing-testing) and using Tenderly to validate transactions. If the encoding is done incorrectly at the Interface level, you will see errors in your testing logs.