# Consensus

## Overview

* [Validator node](/run-a-sunrise-node/types/consensus/validator-node.md): This type of node participates in consensus by producing and voting on blocks.
* [Full consensus node](/run-a-sunrise-node/types/consensus/full-consensus-node.md): A sunrise-app Full node to sync blockchain history.

{% hint style="info" %}
**Data Availability Layer**: In addition to standard consensus tasks, Validator Nodes on Sunrise are responsible for verifying data for the Data Availability (DA) layer. This requires running additional daemons alongside the main `sunrised` process. See the [validator documentation](/build/validators.md) for more details.
{% endhint %}

### Requirements

| Type           | CPU    | Architecture | Mem  | Disk       | Bandwidth |
| -------------- | ------ | ------------ | ---- | ---------- | --------- |
| Validator      | 6 Core | x86\_64      | 8 GB | 500 GB SSD | 1 Gbps    |
| Full Consensus | 4 Core | x86\_64      | 8 GB | 250 GB SSD | 1 Gbps    |


---

# 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.sunriselayer.io/run-a-sunrise-node/types/consensus.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.