Variable OpenApiEvmMethodsConst

Type declaration

• createEvmAccount: (
      createEvmAccountBody?: CreateEvmAccountBody,
      options?: string,
  ) => Promise<EvmAccount>

  Creates a new EVM account.

• createEvmSmartAccount: (
      createEvmSmartAccountBody: CreateEvmSmartAccountBody,
      options?: string,
  ) => Promise<EvmSmartAccount>

  Creates a new Smart Account.

• getEvmAccount: (address: string, options?: string) => Promise<EvmAccount>

  Gets an EVM account by its address.

• getEvmAccountByName: (name: string, options?: string) => Promise<EvmAccount>

  Gets an EVM account by its name.

• getEvmSmartAccount: (address: string, options?: string) => Promise<EvmSmartAccount>

  Gets a Smart Account by its address.

• getUserOperation: (
      address: string,
      userOpHash: string,
      options?: string,
  ) => Promise<EvmUserOperation>

  Gets a user operation by its hash.

• listEvmAccounts: (
      params?: ListEvmAccountsParams,
      options?: string,
  ) => Promise<ListEvmAccounts200>

  Lists the EVM accounts belonging to the developer's CDP Project. The response is paginated, and by default, returns 20 accounts per page.

• listEvmSmartAccounts: (
      params?: ListEvmSmartAccountsParams,
      options?: string,
  ) => Promise<ListEvmSmartAccounts200>

  Lists the Smart Accounts belonging to the developer's CDP Project. The response is paginated, and by default, returns 20 accounts per page.

• listEvmTokenBalances: (
      network: ListEvmTokenBalancesNetwork,
      address: string,
      params?: ListEvmTokenBalancesParams,
      options?: string,
  ) => Promise<ListEvmTokenBalances200>

  Lists the token balances of an EVM address on a given network. The balances include ERC-20 tokens and the native gas token (usually ETH). The response is paginated, and by default, returns 20 balances per page.

  Note:* This endpoint is still under development and does not yet provide strong freshness guarantees. Specifically, balances of new tokens can, on occasion, take up to ~30 seconds to appear, while balances of tokens already belonging to an address will generally be close to chain tip. Freshness of new token balances will improve over the coming weeks.

• prepareUserOperation: (
      address: string,
      prepareUserOperationBody: PrepareUserOperationBody,
      options?: string,
  ) => Promise<EvmUserOperation>

  Prepares a new user operation on a Smart Account for a specific network.

• requestEvmFaucet: (
      requestEvmFaucetBody: RequestEvmFaucetBody,
      options?: string,
  ) => Promise<RequestEvmFaucet200>

• sendEvmTransaction: (
      address: string,
      sendEvmTransactionBody: SendEvmTransactionBody,
      options?: string,
  ) => Promise<SendEvmTransaction200>

  Signs a transaction with the given EVM account and sends it to the indicated supported network. This API handles nonce management and gas estimation, leaving the developer to provide only the minimal set of fields necessary to send the transaction. The transaction should be serialized as a hex string using RLP.

  The transaction must be an EIP-1559 dynamic fee transaction.

  Transaction fields and API behavior*

  • to (Required): The address of the contract or account to send the transaction to.

  • chainId (Ignored): The value of the chainId field in the transaction is ignored. The transaction will be sent to the network indicated by the network field in the request body.

  • nonce (Optional): The nonce to use for the transaction. If not provided, the API will assign a nonce to the transaction based on the current state of the account.

  • maxPriorityFeePerGas (Optional): The maximum priority fee per gas to use for the transaction. If not provided, the API will estimate a value based on current network conditions.

  • maxFeePerGas (Optional): The maximum fee per gas to use for the transaction. If not provided, the API will estimate a value based on current network conditions.

  • gasLimit (Optional): The gas limit to use for the transaction. If not provided, the API will estimate a value based on the to and data fields of the transaction.

  • value (Optional): The amount of ETH, in wei, to send with the transaction.

  • data (Optional): The data to send with the transaction; only used for contract calls.

  • accessList (Optional): The access list to use for the transaction.

• sendUserOperation: (
      address: string,
      userOpHash: string,
      sendUserOperationBody: SendUserOperationBody,
      options?: string,
  ) => Promise<EvmUserOperation>

  Sends a user operation with a signature. The signature that is sent should be 65 bytes, consisting of the r, s, and v values of the ECDSA signature. Note that the v value should conform to the personal_sign standard, which means it should be 27 or 28.

• signEvmHash: (
      address: string,
      signEvmHashBody: SignEvmHashBody,
      options?: string,
  ) => Promise<SignEvmHash200>

  Signs an arbitrary 32 byte hash with the given EVM account.

• signEvmMessage: (
      address: string,
      signEvmMessageBody: SignEvmMessageBody,
      options?: string,
  ) => Promise<SignEvmMessage200>

  Signs an EIP-191 message with the given EVM account.

  Per the specification, the message in the request body is prepended with 0x19 <0x45 (E)> <thereum Signed Message:\n" + len(message)> before being signed.

• signEvmTransaction: (
      address: string,
      signEvmTransactionBody: SignEvmTransactionBody,
      options?: string,
  ) => Promise<SignEvmTransaction200>

  Signs a transaction with the given EVM account. The transaction should be serialized as a hex string using RLP.

  The transaction must be an EIP-1559 dynamic fee transaction. The developer is responsible for ensuring that the unsigned transaction is valid, as the API will not validate the transaction.