@sentio/api 1.0.2-rc.17 → 1.0.2-rc.18

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

@@ -10,38 +10,99 @@
  * Do not edit the class manually.
  */
 import * as runtime from '../runtime.js';
-import type { GoogleApiHttpBody, SolidityServiceGetSimulationBundleResponse, SolidityServiceGetSimulationResponse, SolidityServiceGetSimulationsResponse, SolidityServiceSimulateTransactionBundleRequest, SolidityServiceSimulateTransactionBundleResponse, SolidityServiceSimulateTransactionRequest, SolidityServiceSimulateTransactionResponse, TxindexEvmSearchTransactionsResponse } from '../models/index.js';
+import type { GoogleApiHttpBody, SolidityServiceGetSimulationBundleResponse, SolidityServiceGetSimulationResponse, SolidityServiceGetSimulationsResponse, SolidityServiceSimulateTransactionBundleResponse, SolidityServiceSimulateTransactionResponse, SolidityServiceSolidityAPIServiceSimulateTransactionBody, SolidityServiceSolidityAPIServiceSimulateTransactionBundleBody, TxindexEvmSearchTransactionsResponse } from '../models/index.js';
 export interface GetCallTraceRequest {
-    projectOwner?: string;
-    projectSlug?: string;
-    networkId?: string;
-    chainSpecChainId?: string;
+    projectOwner: string;
+    projectSlug: string;
+    chainSpecChainId: string;
+    txIdTxHash: string;
+    chainSpecForkId?: string;
+    txIdSimulationId?: string;
+    txIdBundleId?: string;
+    withInternalCalls?: boolean;
+    disableOptimizer?: boolean;
+    ignoreGasCost?: boolean;
+}
+export interface GetCallTrace2Request {
+    projectOwner: string;
+    projectSlug: string;
+    chainSpecChainId: string;
+    txIdSimulationId: string;
+    chainSpecForkId?: string;
+    txIdTxHash?: string;
+    txIdBundleId?: string;
+    withInternalCalls?: boolean;
+    disableOptimizer?: boolean;
+    ignoreGasCost?: boolean;
+}
+export interface GetCallTrace3Request {
+    projectOwner: string;
+    projectSlug: string;
+    chainSpecChainId: string;
+    txIdBundleId: string;
     chainSpecForkId?: string;
     txIdTxHash?: string;
     txIdSimulationId?: string;
+    withInternalCalls?: boolean;
+    disableOptimizer?: boolean;
+    ignoreGasCost?: boolean;
+}
+export interface GetCallTrace4Request {
+    projectOwner: string;
+    projectSlug: string;
+    chainSpecForkId: string;
+    txIdTxHash: string;
+    chainSpecChainId?: string;
+    txIdSimulationId?: string;
     txIdBundleId?: string;
+    withInternalCalls?: boolean;
     disableOptimizer?: boolean;
+    ignoreGasCost?: boolean;
+}
+export interface GetCallTrace5Request {
+    projectOwner: string;
+    projectSlug: string;
+    chainSpecForkId: string;
+    txIdSimulationId: string;
+    chainSpecChainId?: string;
+    txIdTxHash?: string;
+    txIdBundleId?: string;
+    withInternalCalls?: boolean;
+    disableOptimizer?: boolean;
+    ignoreGasCost?: boolean;
+}
+export interface GetCallTrace6Request {
+    projectOwner: string;
+    projectSlug: string;
+    chainSpecForkId: string;
+    txIdBundleId: string;
+    chainSpecChainId?: string;
+    txIdTxHash?: string;
+    txIdSimulationId?: string;
     withInternalCalls?: boolean;
+    disableOptimizer?: boolean;
     ignoreGasCost?: boolean;
 }
 export interface GetSimulationRequest {
+    projectOwner: string;
+    projectSlug: string;
     simulationId: string;
-    projectOwner?: string;
-    projectSlug?: string;
 }
-export interface GetSimulationBundleRequest {
+export interface GetSimulationBundleInProjectRequest {
+    projectOwner: string;
+    projectSlug: string;
     bundleId: string;
-    projectOwner?: string;
-    projectSlug?: string;
 }
 export interface GetSimulationsRequest {
-    projectOwner?: string;
-    projectSlug?: string;
+    projectOwner: string;
+    projectSlug: string;
     labelContains?: string;
     page?: number;
     pageSize?: number;
 }
 export interface SearchTransactionsRequest {
+    projectOwner: string;
+    projectSlug: string;
     chainId?: Array<string>;
     address?: Array<string>;
     includeDirect?: boolean;
@@ -58,10 +119,28 @@ export interface SearchTransactionsRequest {
     pageToken?: string;
 }
 export interface SimulateTransactionRequest {
-    body: SolidityServiceSimulateTransactionRequest;
+    projectOwner: string;
+    projectSlug: string;
+    chainSpecChainId: string;
+    body: SolidityServiceSolidityAPIServiceSimulateTransactionBody;
+}
+export interface SimulateTransaction2Request {
+    projectOwner: string;
+    projectSlug: string;
+    chainSpecForkId: string;
+    body: SolidityServiceSolidityAPIServiceSimulateTransactionBody;
 }
 export interface SimulateTransactionBundleRequest {
-    body: SolidityServiceSimulateTransactionBundleRequest;
+    projectOwner: string;
+    projectSlug: string;
+    chainSpecChainId: string;
+    body: SolidityServiceSolidityAPIServiceSimulateTransactionBundleBody;
+}
+export interface SimulateTransactionBundle2Request {
+    projectOwner: string;
+    projectSlug: string;
+    chainSpecForkId: string;
+    body: SolidityServiceSolidityAPIServiceSimulateTransactionBundleBody;
 }
 /**
  *
@@ -76,7 +155,57 @@ 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
      */
-    getCallTrace(requestParameters?: GetCallTraceRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<GoogleApiHttpBody>;
+    getCallTrace(requestParameters: GetCallTraceRequest, 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
+     */
+    getCallTrace2Raw(requestParameters: GetCallTrace2Request, 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
+     */
+    getCallTrace2(requestParameters: GetCallTrace2Request, 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
+     */
+    getCallTrace3Raw(requestParameters: GetCallTrace3Request, 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
+     */
+    getCallTrace3(requestParameters: GetCallTrace3Request, 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
+     */
+    getCallTrace4Raw(requestParameters: GetCallTrace4Request, 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
+     */
+    getCallTrace4(requestParameters: GetCallTrace4Request, 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
+     */
+    getCallTrace5Raw(requestParameters: GetCallTrace5Request, 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
+     */
+    getCallTrace5(requestParameters: GetCallTrace5Request, 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
+     */
+    getCallTrace6Raw(requestParameters: GetCallTrace6Request, 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
+     */
+    getCallTrace6(requestParameters: GetCallTrace6Request, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<GoogleApiHttpBody>;
     /**
      * Get a simulation by id
      */
@@ -88,11 +217,11 @@ export declare class DebugAndSimulationApi extends runtime.BaseAPI {
     /**
      * Get a bundle simulation by id
      */
-    getSimulationBundleRaw(requestParameters: GetSimulationBundleRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<SolidityServiceGetSimulationBundleResponse>>;
+    getSimulationBundleInProjectRaw(requestParameters: GetSimulationBundleInProjectRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<SolidityServiceGetSimulationBundleResponse>>;
     /**
      * Get a bundle simulation by id
      */
-    getSimulationBundle(requestParameters: GetSimulationBundleRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<SolidityServiceGetSimulationBundleResponse>;
+    getSimulationBundleInProject(requestParameters: GetSimulationBundleInProjectRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<SolidityServiceGetSimulationBundleResponse>;
     /**
      * Get existing transaction simulations
      */
@@ -100,7 +229,7 @@ export declare class DebugAndSimulationApi extends runtime.BaseAPI {
     /**
      * Get existing transaction simulations
      */
-    getSimulations(requestParameters?: GetSimulationsRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<SolidityServiceGetSimulationsResponse>;
+    getSimulations(requestParameters: GetSimulationsRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<SolidityServiceGetSimulationsResponse>;
     /**
      * Search for transactions
      */
@@ -108,7 +237,7 @@ export declare class DebugAndSimulationApi extends runtime.BaseAPI {
     /**
      * Search for transactions
      */
-    searchTransactions(requestParameters?: SearchTransactionsRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<TxindexEvmSearchTransactionsResponse>;
+    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
@@ -119,6 +248,16 @@ export declare class DebugAndSimulationApi extends runtime.BaseAPI {
      * Single 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
@@ -129,4 +268,14 @@ export declare class DebugAndSimulationApi extends runtime.BaseAPI {
      * 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
+     */
+    simulateTransactionBundle2Raw(requestParameters: SimulateTransactionBundle2Request, 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
+     */
+    simulateTransactionBundle2(requestParameters: SimulateTransactionBundle2Request, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<SolidityServiceSimulateTransactionBundleResponse>;
 }