> For the complete documentation index, see [llms.txt](https://docs.kotofi.fun/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kotofi.fun/core-concepts/nodes-and-discoverers.md).
# Nodes & Discoverers
Nodes and discoverers are the backbone of Kotofi's data layer. They power the protocol without relying on any centralized API.
***
### What Is a Node?
A **node** is your browser running the Kotofi extension while you browse X (formerly Twitter). When you have the extension installed and your node turned on, you're contributing to the network.
Think of it like this: instead of Kotofi asking X for permission to read data (which can be revoked anytime, like in the case of KaitoAI), Kotofi relies on *you*—and thousands of others—to see what's on the timeline. The information is already public. You're just helping the protocol understand what matters.
**Key points:**
* One node = one browser session with the extension active
* Your node only runs when you have X open and the power button is on
* No API keys, no permission from X—just you browsing as usual
***
### What Is a Discoverer (Founder)?
A **discoverer** (also called a **founder** in the system) is a node runner who has signed in with their X account. Once you sign in with X in the Kotofi extension, you become a discoverer and can earn rewards—no wallet connection required.
Discoverers earn rewards in two ways:
1. **Discovery rewards** — When you're among the first to see a post that gains traction, you earn based on your position and the post's mindshare.
2. **Presence rewards** — You earn points for time spent on X while your node is active.
***
### How Discovery Works
When you scroll X with your node on, the extension sends *which posts you see* to the Kotofi network. The protocol records:
* **Who saw what first** — The first discoverer to see a post gets the highest reward share if that post goes on to generate mindshare.
* **Node reach** — How many nodes saw the same post. More nodes seeing a post means it's getting more attention, which can boost rewards for early discoverers.
Positions matter. The first 10 discoverers to see a post share the discovery reward pie, with the earliest positions getting a larger share. Discoverers at position 11 and beyond get a smaller but still meaningful share.
***
### One Active Node Per User
To keep things fair, **only one active node per user** is allowed. If you start the extension on a second device or browser with the same account, the previous connection will be disconnected. This prevents gaming the system by running multiple nodes under one identity.
***
### Node Runners vs. Discoverers
* **Node Runner** — Anyone with the extension running. You're part of the network.
* **Discoverer** — A node runner who has signed in with their X account. You earn rewards as soon as you're signed in.
No wallet connection is required to become a discoverer.
***
### Why This Matters for InfoFi 2.0
The first generation of InfoFi platforms depended on X's API. When access was cut, they stopped working. Kotofi's node network is **API-independent**. As long as people browse X with the extension, the protocol keeps running. No single company or API gate can shut it down.
---
# 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.kotofi.fun/core-concepts/nodes-and-discoverers.md?ask=&goal=
```
`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.