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

# ERC404

<figure><img src="/files/aIyM8CVbepZD8hGabhqL" alt=""><figcaption><p><em>Visual Explainer of ERC404 (Tecnology Used by Sup Bears)</em></p></figcaption></figure>

### What is ERC-404?

ERC-404 is a new token standard for digital assets on the Ethereum blockchain developed by pseudonymous creators "ctrl" and "Acme."\
\
Token standards are formal sets of rules and protocols that determine the behavior of tokens on blockchain networks such as Ethereum.

The ERC-404 token standard combines features of ERC-20 and ERC-721, enabling the creation of "semi-fungible" tokens that employ features from fungible and non-fungible tokens.\
\
**How does ERC-404 work?**

NFTs are non-fungible, meaning that they are unique and indivisible; you can't own fractions of an NFT.

ERC-404 circumvents this limitation by using token mint and burn mechanics to enable fractional transfers of an NFT.

Issued tokens are linked to an NFT. If you buy a full token, the linked NFT is minted to your wallet. If you sell a fraction of the token, the linked NFT is burned. If a wallet holding fractions of a token purchases enough fractions to hold a complete token, a new NFT is minted automatically.

### What's so special about it?

The ERC-404 token standard enables native fractionalization of NFTs, creating new primitives and new mechanics built atop them. This, in turn, allows for experimentation with NFTs and the trading of them.


---

# 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://sup-bears.gitbook.io/sup-bears/erc404.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.