# Sending

![Transaction Batching with Etherspot](/files/-MgH8fLPC4IBTrCOzNqZ)

{% hint style="success" %}

Before we continue, please ensure that you have had a look at our [Supported Ethereum Chains](broken://pages/-MeAyzR2e2VKsOneDqAi), followed the steps in [Install Etherspot SDK](/getting-started/install-sdk.md) and how to [Bootstrap Etherspot SDK](/getting-started/bootstrap-etherspot-sdk.md). We're assuming that you have completed these steps before going forward.
{% endhint %}

## Getting started

The Etherspot SDK makes it really easy for you to send a transaction on any of our [Supported Ethereum Chains](broken://pages/-MeAyzR2e2VKsOneDqAi). The method call is the same for each chain.

{% hint style="danger" %}
**Do not send assets or native tokens from one chain (like xDai) to an address or contract address on another chain (like Polygon), it will not arrive and the transmitted funds will be lost. This requires the use of** [**Multi-chain Bridges**](/use-cases/multi-chain-bridges.md)**.**
{% endhint %}

First let's fetch our account object. The `state` object contains all the essential information for the instantiated SDK when we performed the steps at [Bootstrap Etherspot SDK](/getting-started/bootstrap-etherspot-sdk.md). You can see what else resides in.the account class [here](https://sdk.etherspot.dev/classes/account.html).

```typescript
const { account } = sdk.state;
```

## Optional: Setting up a notifications subscription

Next, set up a listener against the SDK's notification subscription method. This will allow us to receive an event when the transaction has been confirmed, or enters any other state for that matter.

```typescript
sdk
  .notifications$
  .subscribe(console.log);
```

## Adding your transaction to a batch

When using Etherspot to send transactions, we first add the transaction to a "batch". A batch can contain many transactions for a more gas-efficient operation, but in this example - we're just going to add one transaction to the batch. It will behave as if we are just sending a single transaction.

```typescript
await sdk.batchExecuteAccountTransaction({
  to: '0x0fd7508903376dab743a02743cadfdc2d92fceb8', // Destination Ethereum address
  value: 100, // This value is in wei
  data: null // Optional contract data payload
}).catch(console.error);
```

To see the full SDK reference for the `batchExecuteAccountTransaction`, click [here](https://sdk.etherspot.dev/classes/executeaccounttransactiondto.html).

Once the above method, `batchExecuteAccountTransaction` has been executed, the instruction to send 100 wer to the Ethereum address `0x0fd7508903376dab743a02743cadfdc2d92fceb8`.has been added into the batch. You can choose to continue adding more transactions to this batch.

## Estimating your batch

At this point, your batch is ready to have the gas cost estimated. This gives you, or your users, the opportunity to see how much this transaction may cost on the chain that you have instantiated the SDK on. You can read more about instantiating the Etherspot SDK on different chains here:[Supported Ethereum Chains](broken://pages/-MeAyzR2e2VKsOneDqAi). 

```typescript
const estimationResponse = await sdk
  .estimateGatewayBatch()
  .catch(console.error);
  
console.log('Gas estimated at:', estimationResponse);
```

If you're happy with the cost, proceed to the next and final step.

## Submitting your batch

The final step is to submit your batch, containing your one or more transactions, to the Etherspot gateway. The Etherspot gateway will queue and manage your batch, and endeavour to do everything it can to get your transaction onto your chosen blockchain.

```typescript
const submissionResponse = await sdk
  .submitGatewayBatch()
  .catch(console.error);
```

If you had previously set up a notification subscription [here](/use-cases/transactions.md#optional-setting-up-a-notifications-subscription), then this will fire with different events as your batch is queued, processed and eventually sent to the blockchain.

## :tada: Finished!


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://v1.etherspot.io/use-cases/transactions/sending.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.