> For the complete documentation index, see [llms.txt](https://elements-organization-2.gitbook.io/ift/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://elements-organization-2.gitbook.io/ift/introduction-to-ift/core-concept.md).

# Core Concept

The IFT Protocol aims to monetize information by associating tokens with specific words, enabling market-driven valuation of concepts, ideas, or topics. As a topic such as "longevity" gains traction — driven by social engagement, cultural relevance, or investment in its corresponding IFT — the token’s price may rise, reflecting its societal or viral impact. The IFT Protocol enforces uniqueness through two core constraints:

1. **Unique Subnames**: Each IFT is linked to a distinct subname under ift.eth, such as longevity.ift.eth.
2. **ENS Guarantees**: The ENS prevents duplicate token names and addresses.

<figure><img src="/files/HWwt7tGvTYvAN5htnRNb" alt=""><figcaption></figcaption></figure>

These constraints foster a transparent and decentralized ecosystem where IFT market caps can be compared to identify trending topics and ideas, serving as a public good for tracking information trends.


---

# 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:

```
GET https://elements-organization-2.gitbook.io/ift/introduction-to-ift/core-concept.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.