# 1.2 Validator Responsibilities in Detail

Let's delve deeper into each of these responsibilities:

1. **Receiving and Verifying Batches of Transactions**
   * Your node will continuously receive batches of transactions from the network.
   * You must verify each transaction in these batches to ensure they adhere to Spicenet's protocol rules.
   * This includes checking for correct signatures, sufficient balances, and adherence to any smart contract conditions.
2. **Maintaining Network State**
   * As transactions are processed, you'll update your local copy of the network state.
   * This state includes account balances, smart contract states, and other relevant blockchain data.
   * Ensuring your state matches that of other honest validators is crucial for network consensus.
3. **Detecting Fraud**
   * You'll need to run checks to identify any suspicious or invalid transactions.
   * This might involve looking for double-spends, invalid state transitions, or other protocol violations.
   * Prompt detection of fraud is vital to prevent any potential damage to the network.
4. **Producing Fraud Proofs**
   * If you detect fraudulent activity, you're responsible for creating a fraud-proof.
   * This proof is a cryptographic demonstration of the invalid state transition or transaction.
   * You'll submit this proof to the network, allowing other validators to verify the fraud and take appropriate action.


---

# 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://validators.spicenet.io/introduction-to-spicenet-validation/1.2-validator-responsibilities-in-detail.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.