> For the complete documentation index, see [llms.txt](https://nfd-gg.gitbook.io/main/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://nfd-gg.gitbook.io/main/eng-combine-software/modules/operation-and-launching-of-modules/linea-module/settings-and-launch/block-mode/preset-blocks.md).

# Preset Blocks

This mode allows you to interact with the Dapps available in the module. You can independently choose the protocols in which you want the software to perform transactions: swaps, adding and removing liquidity, etc.

Thanks to this mode, you can perform the required number of transactions, interactions with unique contracts, and various protocols on your wallets.

***

### Setting up and starting a session:

* In the **Mode** section, select **Block Mode**.
* In the **Run mode** section, choose the order in which the wallets will be launched:
  1. **Parallel** - parallel operation (multithreading) with or without proxies.
  2. **One-by-one** - wallets will be launched one after another with or without proxies.
  3. **One-by-one (mobile proxy)** - wallets will be launched one after another using mobile proxies. Mobile proxies must be added in **Settings ->** [**Proxies**](https://docs.nfd.gg/main/eng-combine-software/section-settings/proxies) and linked to accounts in **Account Manager** beforehand.
* To use a ready-made preset of software settings, click on the selection field in the **Select preset** section and choose the required preset.
* To launch a pre-prepared group of wallets, select the desired one in the **Select Accounts group to launch** section.
* In the **Select blocks** section, click **Select** to choose the protocols you want to interact with:
  * By clicking the **Select all** button, you will select all the protocols listed.
  * To select all block scenarios in a specific protocol, click **Select all** in that particular protocol.
  * To select individual protocols, click on the checkboxes next to the desired token pairs in the desired protocol.

<figure><img src="/files/6DL8dwuI1peIDubNtKkx" alt=""><figcaption></figcaption></figure>

If you select all the actions currently available in **Block mode**, the software will interact with any selected block scenarios from the list, but it may not necessarily cover all protocols in one session. This will depend on the number of transactions or volume you choose for a particular wallet.

Each block consists of a certain number of transactions. For example, the **ETH & USDC** block includes the following transactions:

1. Exchange ETH for USDC.
2. Approve USDC.
3. Exchange USDC for ETH.

In total, this makes 3 transactions. If you set **Amount of transactions** to 4, the software will likely take on another block if it was selected. For instance, the **Liquidity - ETH & USDC** block includes the following transactions:

1. Exchange ETH for USDC.
2. Approve USDC for adding to the ETH and USDC pool.
3. Add to the ETH and USDC pool.
4. Approve LP token, if issued.
5. Remove liquidity from the pool.
6. Approve USDC.
7. Exchange USDC for ETH.

If you set 4 transactions and only the first part (ETH & USDC block) is completed with 3 transactions, but the goal of 4 transactions is not reached, the software will proceed with the next block (Liquidity - ETH & USDC) and perform an additional 7 transactions. This will result in 10 transactions instead of 4.

This is designed to ensure that no tokens remain in pools or other tokens. Any block will end with ETH. A wallet will receive a **Success** status only after the block is fully completed and ETH is returned to the balance.

* In the **Delays** section, set delays between actions. There are two modes: **Standard** and **Pro**:
  1. **Wallet** - delay between wallet launches.
  2. **Block** - delay between block scenarios (protocols).
  3. **Step** - delay between actions in a block scenario.
* In **Pro mode**, there are three additional settings:
  1. **Approve** - delay between approval and bridge/swap.
  2. **Gas guard** - when activated, your wallet will go to sleep if several accounts in the same session are ready to work simultaneously after reaching the gas level you set for the software to operate. This ensures that all these wallets do not start sending transactions simultaneously after reaching your set gas level. The standard delay is set between 30 and 150 seconds.
  3. **Break** - delay between halves of steps in a block scenario.
* In the **Max gas price** section, set the maximum gas in the **Base** network for transactions. The software will wait for the gas price in the Base network to drop to the set value before starting transactions. After the session starts, you can change the upper Gwei level in the **Logs & Progress** tab by going to the **Sessions** section.
* In the **Amount of transactions** section, enter the number of transactions in a range that should be performed on each wallet during one session.
* In the **Work Amount Range** section, specify the percentage range of the amount that will be used in the session for each selected wallet. For instance, if your wallet balance is 1 $ETH and you set it to 40-50%, the software will work within the range of 0.4-0.5 $ETH. This rule will apply to all wallets selected for the session, and this percentage will be randomly chosen before each subsequent block scenario.
* If the **INFINITE** checkbox is activated, an infinite number of tokens will be approved so you do not have to reapprove your tokens before each subsequent swap/liquidity addition. If the checkbox is disabled, only the amount needed for the transaction will be approved.
* If you want wallets to start working in a random order, keep the **Randomize wallets** checkbox enabled.
* To save the session delay settings for use in other sessions, click the **Save this as preset** button, enter the preset name, and save it. You can later select this preset in the **Select preset** field.
* Click **Update Balances** to get the current token balances on the wallets.
* Select the wallets you want to launch and click **Launch**.

<figure><img src="/files/pNiKUtfUvOyotA7VpQaM" alt=""><figcaption></figcaption></figure>

* Your wallets are now operationa**l.** You can track the process of wallet operations in the [Logs & Progress](https://docs.nfd.gg/main/eng-combine-software/modules/operation-and-launching-of-modules/linea-module/logs-and-progress) section.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://nfd-gg.gitbook.io/main/eng-combine-software/modules/operation-and-launching-of-modules/linea-module/settings-and-launch/block-mode/preset-blocks.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.