> For the complete documentation index, see [llms.txt](https://doc.fracton.cool/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.fracton.cool/use-cases/why-choose-fracton-protocol.md).

# Why Choose Fracton Protocol?

## Effortlessly trade and own blue-chip NFTs

Fracton’s hiNFTs are one of the most traded and liquid NFT ETFs. As of Jan 13th, 2023, there are currently 20 series of NFT collections that are fractionalized and listed on Kucoin, generating millions of volumes each day.

## Swap NFTs within the same collection

For NFT Holders who wish to swap for different traits' NFT in the same collection, he/she can permissionless do so on Fracton Protocol.

## Build on top of Fracton

Fracton’s negligible fees and smart contract architecture enable high composability for DeFi development. Fracton provides 2 steps of fractionalization (Raw NFT(ERC721)-pNFT (ERC1155)-hiNFT (ERC20)) with a fixed swap rate for target NFT collection. 

<br>

## &#x20;

## &#x20;

\ <br>


---

# 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://doc.fracton.cool/use-cases/why-choose-fracton-protocol.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.