> For the complete documentation index, see [llms.txt](https://trc404.gitbook.io/trc404-doc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://trc404.gitbook.io/trc404-doc/overview.md).

# Overview

[English](https://trc404.gitbook.io/trc404-doc)           [中文](https://trc404.gitbook.io/trc404-wen-dang)         [Русский](https://trc404.gitbook.io/trc404-dokumentaciya)

## What is TRC404 Protocol?

TRC-404 is an innovative, mixed Jetton and NFT implementation with native liquidity and fractionalization for semi-fungible tokens. **Inspired by the ERC-404 protocol, it's the first project to implement the ERC-404 protocol on TON.**

## Why TRC404 Protocol?

To address the “insufficient liquidity” and “indivisibility” issues of NFTs.Compared to other similar solutions, this standard would enable native support for the fragmentation and reassembly of NFTs (i.e., through wallet transfers of tokens) without the need for third-party platforms.

## What is T404?

T404 refers to the tokens minted based on the TRC404 protocol, fully compatible with Jetton/Token and NFT standards. One T404 represents the right of minting one TRC404 NFT.


---

# 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://trc404.gitbook.io/trc404-doc/overview.md?ask=<question>&goal=<endgoal>
```

`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.