# 1. Founder Nodes Intro

#### 1. First Generation Founder Nodes

The Cashtap network features **two types of nodes**, both serving the primary purpose of maintaining and securing the ecosystem. While their core functions are similar, they differ in their reward mechanisms. Cashtap Nodes operate as a decentralized oracle Foundernode infrastructure, playing a crucial role in the growth and security of the Cashtap ecosystem.

**Key Functionality**

The main purpose of these nodes is to ensure data validation for the platform. This includes verifying the accuracy and reliability of critical information essential for tokenized debt and equity markets. This function is vital to the integrity and transparency of the ecosystem, making Cashtap Nodes a cornerstone of its operations.

**Staking and Rewards**

By staking **$vCASH**, participants can join the network and contribute to its stability while earning rewards. The staking mechanism incentivizes participation and ensures that the platform remains decentralized and secure.

**User Perspective**

Cashtap Nodes are designed to be accessible and rewarding for users. Whether operating a node directly or delegating stakes to an existing node, participants play a significant role in securing the network. The dual reward mechanisms provide opportunities for both active and passive involvement, creating a dynamic and inclusive ecosystem


---

# 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://cashtap.gitbook.io/cashtap-whitepaper/~/changes/RzPXwU8vxnveFbiZocnN/1.-first-generation-founder-nodes/1.-founder-nodes-intro.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.
