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

# Run a full node

### Overview[​](https://docs.astar.network/docs/build/nodes/full-node#overview) <a href="#overview" id="overview"></a>

Running a full node on Uomi allows you to connect to the network, sync with a bootnode, obtain local access to RPC endpoints, author blocks, and more.

Different from archive node, a full node discards all finalized blocks older than configured number of blocks (256 blocks by default). A full node occupies less storage space than an archive node because of pruning.

A full node may eventually be able to rebuild the entire chain with no additional information, and become an archive node, but at the time of writing, this is not implemented. If you need to query historical blocks past what you pruned, you need to purge your database and resync your node starting in archive mode. Alternatively you can use a backup or snapshot of a trusted source to avoid needing to sync from genesis with the network, and only need the blocks past that snapshot. (reference: <https://wiki.polkadot.network/docs/maintain-sync#types-of-nodes>)

If your node need to provide old historical blocks' data, please consider to use Archive node instead.

### Requirements[​](https://docs.astar.network/docs/build/nodes/full-node#requirements) <a href="#requirements" id="requirements"></a>

Requirements for running any node are similar to what we recommend for archive node. Read more about this [here](/build/run-a-node/run-an-archive-node.md). Note that Full node requires less disk space. Hard Disk requirement for Archive node is not applied to Full nodes.

To set a full node, you need to specify the number of blocks to be pruned:

```
--pruning 1000 \
```

{% hint style="info" %}
INFO

Running a node for our testnet 'Finney' requires less resources. It's a perfect place to test your node infrastructure and costs.
{% endhint %}


---

# 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.uomi.ai/build/run-a-node/run-a-full-node.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.