# LP Account

* Due to TON’s asynchronous nature, when depositing assets, separate transactions are required to transfer assets into the Vault.
* When users deposit assets in batches, the LP Account acts like a **delivery service**, waiting until all items have been checked out and packed before making a single delivery to the user's home (Pool) for asset exchange or liquidity provision.
* If the user deposits only one type of asset, the LP Account is not needed – the Vault sends the asset directly to the Pool for processing, streamlining the transaction.

***

## **Example**

Imagine you are shopping at a supermarket and purchasing multiple items, each checked out at a different counter:

* After each checkout, the items are handed to the delivery service (LP Account) for temporary storage.
* Once all items are checked out, the delivery service **delivers everything to your home (Pool) in one go**, ensuring complete delivery.
* If you purchase only one item, it is sent directly from the checkout counter to your home, skipping the delivery service step.

This design ensures flexibility in the transaction process – even if assets are deposited in batches, the final transaction can be completed once all assets are ready.


---

# 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://doc.torch.finance/dex/getting-started/architecture/core-components/lp-account.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.