@sentio/api 1.0.2-rc.22 → 1.0.2-rc.24

package/dist/src/apis/DebugAndSimulationApi.d.ts

@@ -10,75 +10,57 @@
  * Do not edit the class manually.
  */
 import * as runtime from '../runtime.js';
-import type { GoogleApiHttpBody, SolidityServiceGetSimulationBundleResponse, SolidityServiceGetSimulationResponse, SolidityServiceGetSimulationsResponse, SolidityServiceSimulateTransactionBundleResponse, SolidityServiceSimulateTransactionResponse, SolidityServiceSolidityAPIServiceSimulateTransactionBody, SolidityServiceSolidityAPIServiceSimulateTransactionBundleBody, TxindexEvmSearchTransactionsResponse } from '../models/index.js';
-export interface GetCallTraceRequest {
+import type { GoogleApiHttpBody, SolidityServiceGetSimulationBundleResponse, SolidityServiceGetSimulationResponse, SolidityServiceGetSimulationsResponse, SolidityServiceSimulateTransactionBundleResponse, SolidityServiceSimulateTransactionResponse, SolidityServiceSolidityAPIServiceSimulateTransactionBody, SolidityServiceSolidityAPIServiceSimulateTransactionBundleBody, SolidityServiceSolidityAPIServiceSimulateTransactionBundleByForkBody, SolidityServiceSolidityAPIServiceSimulateTransactionByForkBody, TxindexEvmSearchTransactionsResponse } from '../models/index.js';
+export interface GetCallTraceByBundleRequest {
     owner: string;
     slug: string;
     chainId: string;
-    txHash: string;
-    chainSpecForkId?: string;
-    txIdSimulationId?: string;
-    txIdBundleId?: string;
+    bundleId: string;
     withInternalCalls?: boolean;
     disableOptimizer?: boolean;
     ignoreGasCost?: boolean;
 }
-export interface GetCallTrace2Request {
+export interface GetCallTraceByForkBundleRequest {
     owner: string;
     slug: string;
-    chainId: string;
-    simulationId: string;
-    chainSpecForkId?: string;
-    txIdTxHash?: string;
-    txIdBundleId?: string;
+    forkId: string;
+    bundleId: string;
     withInternalCalls?: boolean;
     disableOptimizer?: boolean;
     ignoreGasCost?: boolean;
 }
-export interface GetCallTrace3Request {
+export interface GetCallTraceByForkSimulationRequest {
     owner: string;
     slug: string;
-    chainId: string;
-    bundleId: string;
-    chainSpecForkId?: string;
-    txIdTxHash?: string;
-    txIdSimulationId?: string;
+    forkId: string;
+    simulationId: string;
     withInternalCalls?: boolean;
     disableOptimizer?: boolean;
     ignoreGasCost?: boolean;
 }
-export interface GetCallTrace4Request {
+export interface GetCallTraceByForkTransactionRequest {
     owner: string;
     slug: string;
     forkId: string;
     txHash: string;
-    chainSpecChainId?: string;
-    txIdSimulationId?: string;
-    txIdBundleId?: string;
     withInternalCalls?: boolean;
     disableOptimizer?: boolean;
     ignoreGasCost?: boolean;
 }
-export interface GetCallTrace5Request {
+export interface GetCallTraceBySimulationRequest {
     owner: string;
     slug: string;
-    forkId: string;
+    chainId: string;
     simulationId: string;
-    chainSpecChainId?: string;
-    txIdTxHash?: string;
-    txIdBundleId?: string;
     withInternalCalls?: boolean;
     disableOptimizer?: boolean;
     ignoreGasCost?: boolean;
 }
-export interface GetCallTrace6Request {
+export interface GetCallTraceByTransactionRequest {
     owner: string;
     slug: string;
-    forkId: string;
-    bundleId: string;
-    chainSpecChainId?: string;
-    txIdTxHash?: string;
-    txIdSimulationId?: string;
+    chainId: string;
+    txHash: string;
     withInternalCalls?: boolean;
     disableOptimizer?: boolean;
     ignoreGasCost?: boolean;
@@ -124,158 +106,144 @@ export interface SimulateTransactionRequest {
     chainId: string;
     body: SolidityServiceSolidityAPIServiceSimulateTransactionBody;
 }
-export interface SimulateTransaction2Request {
-    owner: string;
-    slug: string;
-    forkId: string;
-    body: SolidityServiceSolidityAPIServiceSimulateTransactionBody;
-}
 export interface SimulateTransactionBundleRequest {
     owner: string;
     slug: string;
     chainId: string;
     body: SolidityServiceSolidityAPIServiceSimulateTransactionBundleBody;
 }
-export interface SimulateTransactionBundle2Request {
+export interface SimulateTransactionBundleByForkRequest {
     owner: string;
     slug: string;
     forkId: string;
-    body: SolidityServiceSolidityAPIServiceSimulateTransactionBundleBody;
+    body: SolidityServiceSolidityAPIServiceSimulateTransactionBundleByForkBody;
+}
+export interface SimulateTransactionByForkRequest {
+    owner: string;
+    slug: string;
+    forkId: string;
+    body: SolidityServiceSolidityAPIServiceSimulateTransactionByForkBody;
 }
 /**
  *
  */
 export declare class DebugAndSimulationApi extends runtime.BaseAPI {
     /**
-     * API to get Sentio call trace. It takes `txId.txHash` and `networkId` arguments, where the first is transaction hash, and the second is the numeric ethereum chain ID.  The results looks very similar to the normal [Ethereum call trace](https://raw.githubusercontent.com/sentioxyz/docs/main/.gitbook/assets/image%20(2)%20(1)%20(1)%20(1).png). But we have an additional `startIndex` and `startIndex` on each trace entry even for the LOG, representing the execution order in the trace.  This allows you to build chart that marks the order of fund flow.  ![screenshot](https://raw.githubusercontent.com/sentioxyz/docs/main/.gitbook/assets/image%20(2)%20(1)%20(1)%20(1).png)
-     * Get indexed call trace
+     * Get Call Trace by Bundle Simulation
      */
-    getCallTraceRaw(requestParameters: GetCallTraceRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<GoogleApiHttpBody>>;
+    getCallTraceByBundleRaw(requestParameters: GetCallTraceByBundleRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<GoogleApiHttpBody>>;
     /**
-     * API to get Sentio call trace. It takes `txId.txHash` and `networkId` arguments, where the first is transaction hash, and the second is the numeric ethereum chain ID.  The results looks very similar to the normal [Ethereum call trace](https://raw.githubusercontent.com/sentioxyz/docs/main/.gitbook/assets/image%20(2)%20(1)%20(1)%20(1).png). But we have an additional `startIndex` and `startIndex` on each trace entry even for the LOG, representing the execution order in the trace.  This allows you to build chart that marks the order of fund flow.  ![screenshot](https://raw.githubusercontent.com/sentioxyz/docs/main/.gitbook/assets/image%20(2)%20(1)%20(1)%20(1).png)
-     * Get indexed call trace
+     * Get Call Trace by Bundle Simulation
      */
-    getCallTrace(requestParameters: GetCallTraceRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<GoogleApiHttpBody>;
+    getCallTraceByBundle(requestParameters: GetCallTraceByBundleRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<GoogleApiHttpBody>;
     /**
-     * API to get Sentio call trace. It takes `txId.txHash` and `networkId` arguments, where the first is transaction hash, and the second is the numeric ethereum chain ID.  The results looks very similar to the normal [Ethereum call trace](https://raw.githubusercontent.com/sentioxyz/docs/main/.gitbook/assets/image%20(2)%20(1)%20(1)%20(1).png). But we have an additional `startIndex` and `startIndex` on each trace entry even for the LOG, representing the execution order in the trace.  This allows you to build chart that marks the order of fund flow.  ![screenshot](https://raw.githubusercontent.com/sentioxyz/docs/main/.gitbook/assets/image%20(2)%20(1)%20(1)%20(1).png)
-     * Get indexed call trace
+     * Get Call Trace by Bundle Simulation on Fork
      */
-    getCallTrace2Raw(requestParameters: GetCallTrace2Request, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<GoogleApiHttpBody>>;
+    getCallTraceByForkBundleRaw(requestParameters: GetCallTraceByForkBundleRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<GoogleApiHttpBody>>;
     /**
-     * API to get Sentio call trace. It takes `txId.txHash` and `networkId` arguments, where the first is transaction hash, and the second is the numeric ethereum chain ID.  The results looks very similar to the normal [Ethereum call trace](https://raw.githubusercontent.com/sentioxyz/docs/main/.gitbook/assets/image%20(2)%20(1)%20(1)%20(1).png). But we have an additional `startIndex` and `startIndex` on each trace entry even for the LOG, representing the execution order in the trace.  This allows you to build chart that marks the order of fund flow.  ![screenshot](https://raw.githubusercontent.com/sentioxyz/docs/main/.gitbook/assets/image%20(2)%20(1)%20(1)%20(1).png)
-     * Get indexed call trace
+     * Get Call Trace by Bundle Simulation on Fork
      */
-    getCallTrace2(requestParameters: GetCallTrace2Request, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<GoogleApiHttpBody>;
+    getCallTraceByForkBundle(requestParameters: GetCallTraceByForkBundleRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<GoogleApiHttpBody>;
     /**
-     * API to get Sentio call trace. It takes `txId.txHash` and `networkId` arguments, where the first is transaction hash, and the second is the numeric ethereum chain ID.  The results looks very similar to the normal [Ethereum call trace](https://raw.githubusercontent.com/sentioxyz/docs/main/.gitbook/assets/image%20(2)%20(1)%20(1)%20(1).png). But we have an additional `startIndex` and `startIndex` on each trace entry even for the LOG, representing the execution order in the trace.  This allows you to build chart that marks the order of fund flow.  ![screenshot](https://raw.githubusercontent.com/sentioxyz/docs/main/.gitbook/assets/image%20(2)%20(1)%20(1)%20(1).png)
-     * Get indexed call trace
+     * Get Call Trace by Simulation on Fork
      */
-    getCallTrace3Raw(requestParameters: GetCallTrace3Request, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<GoogleApiHttpBody>>;
+    getCallTraceByForkSimulationRaw(requestParameters: GetCallTraceByForkSimulationRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<GoogleApiHttpBody>>;
     /**
-     * API to get Sentio call trace. It takes `txId.txHash` and `networkId` arguments, where the first is transaction hash, and the second is the numeric ethereum chain ID.  The results looks very similar to the normal [Ethereum call trace](https://raw.githubusercontent.com/sentioxyz/docs/main/.gitbook/assets/image%20(2)%20(1)%20(1)%20(1).png). But we have an additional `startIndex` and `startIndex` on each trace entry even for the LOG, representing the execution order in the trace.  This allows you to build chart that marks the order of fund flow.  ![screenshot](https://raw.githubusercontent.com/sentioxyz/docs/main/.gitbook/assets/image%20(2)%20(1)%20(1)%20(1).png)
-     * Get indexed call trace
+     * Get Call Trace by Simulation on Fork
      */
-    getCallTrace3(requestParameters: GetCallTrace3Request, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<GoogleApiHttpBody>;
+    getCallTraceByForkSimulation(requestParameters: GetCallTraceByForkSimulationRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<GoogleApiHttpBody>;
     /**
-     * API to get Sentio call trace. It takes `txId.txHash` and `networkId` arguments, where the first is transaction hash, and the second is the numeric ethereum chain ID.  The results looks very similar to the normal [Ethereum call trace](https://raw.githubusercontent.com/sentioxyz/docs/main/.gitbook/assets/image%20(2)%20(1)%20(1)%20(1).png). But we have an additional `startIndex` and `startIndex` on each trace entry even for the LOG, representing the execution order in the trace.  This allows you to build chart that marks the order of fund flow.  ![screenshot](https://raw.githubusercontent.com/sentioxyz/docs/main/.gitbook/assets/image%20(2)%20(1)%20(1)%20(1).png)
-     * Get indexed call trace
+     * Get Call Trace by Transaction on Fork
      */
-    getCallTrace4Raw(requestParameters: GetCallTrace4Request, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<GoogleApiHttpBody>>;
+    getCallTraceByForkTransactionRaw(requestParameters: GetCallTraceByForkTransactionRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<GoogleApiHttpBody>>;
     /**
-     * API to get Sentio call trace. It takes `txId.txHash` and `networkId` arguments, where the first is transaction hash, and the second is the numeric ethereum chain ID.  The results looks very similar to the normal [Ethereum call trace](https://raw.githubusercontent.com/sentioxyz/docs/main/.gitbook/assets/image%20(2)%20(1)%20(1)%20(1).png). But we have an additional `startIndex` and `startIndex` on each trace entry even for the LOG, representing the execution order in the trace.  This allows you to build chart that marks the order of fund flow.  ![screenshot](https://raw.githubusercontent.com/sentioxyz/docs/main/.gitbook/assets/image%20(2)%20(1)%20(1)%20(1).png)
-     * Get indexed call trace
+     * Get Call Trace by Transaction on Fork
      */
-    getCallTrace4(requestParameters: GetCallTrace4Request, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<GoogleApiHttpBody>;
+    getCallTraceByForkTransaction(requestParameters: GetCallTraceByForkTransactionRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<GoogleApiHttpBody>;
     /**
-     * API to get Sentio call trace. It takes `txId.txHash` and `networkId` arguments, where the first is transaction hash, and the second is the numeric ethereum chain ID.  The results looks very similar to the normal [Ethereum call trace](https://raw.githubusercontent.com/sentioxyz/docs/main/.gitbook/assets/image%20(2)%20(1)%20(1)%20(1).png). But we have an additional `startIndex` and `startIndex` on each trace entry even for the LOG, representing the execution order in the trace.  This allows you to build chart that marks the order of fund flow.  ![screenshot](https://raw.githubusercontent.com/sentioxyz/docs/main/.gitbook/assets/image%20(2)%20(1)%20(1)%20(1).png)
-     * Get indexed call trace
+     * Get Call Trace by Simulation
      */
-    getCallTrace5Raw(requestParameters: GetCallTrace5Request, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<GoogleApiHttpBody>>;
+    getCallTraceBySimulationRaw(requestParameters: GetCallTraceBySimulationRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<GoogleApiHttpBody>>;
     /**
-     * API to get Sentio call trace. It takes `txId.txHash` and `networkId` arguments, where the first is transaction hash, and the second is the numeric ethereum chain ID.  The results looks very similar to the normal [Ethereum call trace](https://raw.githubusercontent.com/sentioxyz/docs/main/.gitbook/assets/image%20(2)%20(1)%20(1)%20(1).png). But we have an additional `startIndex` and `startIndex` on each trace entry even for the LOG, representing the execution order in the trace.  This allows you to build chart that marks the order of fund flow.  ![screenshot](https://raw.githubusercontent.com/sentioxyz/docs/main/.gitbook/assets/image%20(2)%20(1)%20(1)%20(1).png)
-     * Get indexed call trace
+     * Get Call Trace by Simulation
      */
-    getCallTrace5(requestParameters: GetCallTrace5Request, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<GoogleApiHttpBody>;
+    getCallTraceBySimulation(requestParameters: GetCallTraceBySimulationRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<GoogleApiHttpBody>;
     /**
-     * API to get Sentio call trace. It takes `txId.txHash` and `networkId` arguments, where the first is transaction hash, and the second is the numeric ethereum chain ID.  The results looks very similar to the normal [Ethereum call trace](https://raw.githubusercontent.com/sentioxyz/docs/main/.gitbook/assets/image%20(2)%20(1)%20(1)%20(1).png). But we have an additional `startIndex` and `startIndex` on each trace entry even for the LOG, representing the execution order in the trace.  This allows you to build chart that marks the order of fund flow.  ![screenshot](https://raw.githubusercontent.com/sentioxyz/docs/main/.gitbook/assets/image%20(2)%20(1)%20(1)%20(1).png)
-     * Get indexed call trace
+     * API to get Sentio call trace. It takes `txId.txHash` and `chainSpec.chainId` arguments, where the first is transaction hash, and the second is the numeric ethereum chain ID.  The results looks very similar to the normal [Ethereum call trace](https://raw.githubusercontent.com/sentioxyz/docs/main/.gitbook/assets/image%20(2)%20(1)%20(1)%20(1).png). But we have an additional `startIndex` and `startIndex` on each trace entry even for the LOG, representing the execution order in the trace.  This allows you to build chart that marks the order of fund flow.  ![screenshot](https://raw.githubusercontent.com/sentioxyz/docs/main/.gitbook/assets/image%20(2)%20(1)%20(1)%20(1).png)
+     * Get Call Trace by Transaction
      */
-    getCallTrace6Raw(requestParameters: GetCallTrace6Request, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<GoogleApiHttpBody>>;
+    getCallTraceByTransactionRaw(requestParameters: GetCallTraceByTransactionRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<GoogleApiHttpBody>>;
     /**
-     * API to get Sentio call trace. It takes `txId.txHash` and `networkId` arguments, where the first is transaction hash, and the second is the numeric ethereum chain ID.  The results looks very similar to the normal [Ethereum call trace](https://raw.githubusercontent.com/sentioxyz/docs/main/.gitbook/assets/image%20(2)%20(1)%20(1)%20(1).png). But we have an additional `startIndex` and `startIndex` on each trace entry even for the LOG, representing the execution order in the trace.  This allows you to build chart that marks the order of fund flow.  ![screenshot](https://raw.githubusercontent.com/sentioxyz/docs/main/.gitbook/assets/image%20(2)%20(1)%20(1)%20(1).png)
-     * Get indexed call trace
+     * API to get Sentio call trace. It takes `txId.txHash` and `chainSpec.chainId` arguments, where the first is transaction hash, and the second is the numeric ethereum chain ID.  The results looks very similar to the normal [Ethereum call trace](https://raw.githubusercontent.com/sentioxyz/docs/main/.gitbook/assets/image%20(2)%20(1)%20(1)%20(1).png). But we have an additional `startIndex` and `startIndex` on each trace entry even for the LOG, representing the execution order in the trace.  This allows you to build chart that marks the order of fund flow.  ![screenshot](https://raw.githubusercontent.com/sentioxyz/docs/main/.gitbook/assets/image%20(2)%20(1)%20(1)%20(1).png)
+     * Get Call Trace by Transaction
      */
-    getCallTrace6(requestParameters: GetCallTrace6Request, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<GoogleApiHttpBody>;
+    getCallTraceByTransaction(requestParameters: GetCallTraceByTransactionRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<GoogleApiHttpBody>;
     /**
-     * Get a simulation by id
+     * Get Simulation by ID
      */
     getSimulationRaw(requestParameters: GetSimulationRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<SolidityServiceGetSimulationResponse>>;
     /**
-     * Get a simulation by id
+     * Get Simulation by ID
      */
     getSimulation(requestParameters: GetSimulationRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<SolidityServiceGetSimulationResponse>;
     /**
-     * Get a bundle simulation by id
+     * Get Bundle Simulation by ID
      */
     getSimulationBundleInProjectRaw(requestParameters: GetSimulationBundleInProjectRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<SolidityServiceGetSimulationBundleResponse>>;
     /**
-     * Get a bundle simulation by id
+     * Get Bundle Simulation by ID
      */
     getSimulationBundleInProject(requestParameters: GetSimulationBundleInProjectRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<SolidityServiceGetSimulationBundleResponse>;
     /**
-     * Get existing transaction simulations
+     * Get Existied Simulations
      */
     getSimulationsRaw(requestParameters: GetSimulationsRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<SolidityServiceGetSimulationsResponse>>;
     /**
-     * Get existing transaction simulations
+     * Get Existied Simulations
      */
     getSimulations(requestParameters: GetSimulationsRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<SolidityServiceGetSimulationsResponse>;
     /**
-     * Search for transactions
+     * Search transactions
      */
     searchTransactionsRaw(requestParameters: SearchTransactionsRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<TxindexEvmSearchTransactionsResponse>>;
     /**
-     * Search for transactions
+     * Search transactions
      */
     searchTransactions(requestParameters: SearchTransactionsRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<TxindexEvmSearchTransactionsResponse>;
     /**
      * Create a new transaction simulation. The simulation body should be included in the request body. Your simulations will be saved, and a unique ID for each simulation is included in the response. It will be useful for fetching simulation details.
-     * Single simulation
+     * Run Simulation
      */
     simulateTransactionRaw(requestParameters: SimulateTransactionRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<SolidityServiceSimulateTransactionResponse>>;
     /**
      * Create a new transaction simulation. The simulation body should be included in the request body. Your simulations will be saved, and a unique ID for each simulation is included in the response. It will be useful for fetching simulation details.
-     * Single simulation
+     * Run Simulation
      */
     simulateTransaction(requestParameters: SimulateTransactionRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<SolidityServiceSimulateTransactionResponse>;
-    /**
-     * Create a new transaction simulation. The simulation body should be included in the request body. Your simulations will be saved, and a unique ID for each simulation is included in the response. It will be useful for fetching simulation details.
-     * Single simulation
-     */
-    simulateTransaction2Raw(requestParameters: SimulateTransaction2Request, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<SolidityServiceSimulateTransactionResponse>>;
-    /**
-     * Create a new transaction simulation. The simulation body should be included in the request body. Your simulations will be saved, and a unique ID for each simulation is included in the response. It will be useful for fetching simulation details.
-     * Single simulation
-     */
-    simulateTransaction2(requestParameters: SimulateTransaction2Request, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<SolidityServiceSimulateTransactionResponse>;
     /**
      * You could also create bundle simulations so that one transaction could be executed one after another. For `blockNumber` `transactionIndex` `networkId` `stateOverrides` and `blockOverrides` fields, only the first simulation takes effect.
-     * Bundle simulation
+     * Run Bundle simulation
      */
     simulateTransactionBundleRaw(requestParameters: SimulateTransactionBundleRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<SolidityServiceSimulateTransactionBundleResponse>>;
     /**
      * You could also create bundle simulations so that one transaction could be executed one after another. For `blockNumber` `transactionIndex` `networkId` `stateOverrides` and `blockOverrides` fields, only the first simulation takes effect.
-     * Bundle simulation
+     * Run Bundle simulation
      */
     simulateTransactionBundle(requestParameters: SimulateTransactionBundleRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<SolidityServiceSimulateTransactionBundleResponse>;
     /**
-     * You could also create bundle simulations so that one transaction could be executed one after another. For `blockNumber` `transactionIndex` `networkId` `stateOverrides` and `blockOverrides` fields, only the first simulation takes effect.
-     * Bundle simulation
+     * Run Bundle simulation on Fork
      */
-    simulateTransactionBundle2Raw(requestParameters: SimulateTransactionBundle2Request, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<SolidityServiceSimulateTransactionBundleResponse>>;
+    simulateTransactionBundleByForkRaw(requestParameters: SimulateTransactionBundleByForkRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<SolidityServiceSimulateTransactionBundleResponse>>;
     /**
-     * You could also create bundle simulations so that one transaction could be executed one after another. For `blockNumber` `transactionIndex` `networkId` `stateOverrides` and `blockOverrides` fields, only the first simulation takes effect.
-     * Bundle simulation
+     * Run Bundle simulation on Fork
+     */
+    simulateTransactionBundleByFork(requestParameters: SimulateTransactionBundleByForkRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<SolidityServiceSimulateTransactionBundleResponse>;
+    /**
+     * Run Simulation on Fork
+     */
+    simulateTransactionByForkRaw(requestParameters: SimulateTransactionByForkRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<SolidityServiceSimulateTransactionResponse>>;
+    /**
+     * Run Simulation on Fork
      */
-    simulateTransactionBundle2(requestParameters: SimulateTransactionBundle2Request, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<SolidityServiceSimulateTransactionBundleResponse>;
+    simulateTransactionByFork(requestParameters: SimulateTransactionByForkRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<SolidityServiceSimulateTransactionResponse>;
 }