# Node Types

## Normal node

A normal node or non-validator node can sync the latest events from the network. Users can submit their transactions into a normal node. Transactions will be propagated to the other nodes of the network.&#x20;

A normal node is usually run locally, however if you want to expose blockchain data (transactions, balances, smart contract interactions). You can expose to the public via `--http` or `--ws` flag.

To enable Tracing Node, use `--enabletxtracer` flag.&#x20;

{% hint style="warning" %}
IMPORTANT: Do not enable TX Tracer along while running Validator Node
{% endhint %}

Please head to [run normal node](/network/run-normal-node.md).

## Validator node

A validator node has the ability to emit new consensus events and along with the other validators, their responsibilities are verify transactions and secure the consensus. Events are transmitted to the network through Peer-to-peer messaging service. Users can send transactions into their own validators, a normal node, or an API node, and those transactions will then be propagated throughout the network.

Please head to [run validator node](/network/run-validator-node.md).


---

# 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://docs.u2u.xyz/network/node-types.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.
