> For the complete documentation index, see [llms.txt](https://docs.onefinity.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.onefinity.network/technology/run-a-onefinity-node/nodes/operation-modes.md).

# Operation modes

#### Introduction

Starting with the `v1.x.y` release, a new CLI flag has been introduced to the node: `--operation-mode`. Its purpose is to override certain configuration values, enabling the node to operate differently based on the use case. Without any configuration changes, nodes will start with the default settings. However, there are several ways to configure the node to suit the desired operation mode. Instead of manually editing the `toml` files (or doing so programmatically via `sed`, for example), you can use the `--operation-mode` CLI flag to specify a custom operation mode. This results in configuration changes tailored to your needs.

### Available Operation Modes

#### Full archive[​](https://docs.multiversx.com/validators/node-operation-modes#full-archive) <a href="#full-archive" id="full-archive"></a>

Enabling `full-archive` mode reconfigures the node to sync from the beginning and handle historical queries. However, be prepared for a longer sync time due to limited full archive peers available.

```bash
./node --operation-mode full-archive
```

#### Db Lookup Extension[​](https://docs.multiversx.com/validators/node-operation-modes#db-lookup-extension) <a href="#db-lookup-extension" id="db-lookup-extension"></a>

The `hyperblock` endpoint and others like `/network/esdt/supply/:tokenID` or `/transaction/:txhash?withResults=true` depend on the `db-lookup-extension` mode. This mode adjusts the node's setup to enhance databases, enabling them to store additional data such as logs and block-epoch links, which supports more complex Rest API queries.

```
./node --operation-mode db-lookup-extension
```

#### Historical balances[​](https://docs.multiversx.com/validators/node-operation-modes#historical-balances) <a href="#historical-balances" id="historical-balances"></a>

Enabling the `historical-balances` mode alters the node configuration to support historical balance queries by preventing trie pruning. This increases disk usage but enables querying past block balances or nonces of addresses.

```
./node --operation-mode historical-balances
```

#### Snapshotless-Observer Mode

This mode streamlines the node for real-time requests like live balance updates or transaction broadcasts. It deactivates trie snapshotting and ensures obsolete data is purged, enhancing efficiency by avoiding resource-intensive operations.

```
./node --operation-mode snapshotless-observer
```


---

# 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://docs.onefinity.network/technology/run-a-onefinity-node/nodes/operation-modes.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.