> 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/fractonxs-solutions/key-innovations.md).
# Key Innovations
## Pool-less Liquidity
Traditional swap relays on dedicated liquidity pools for swapping tokens. This requires initial liquidity and LPs for building the liquidity pool. Fracton Swap creates pool-less liquidity based on a “Left-Right-Exchange” mechanism. The swap always hold\&send tokens on the Left side of ERC721/ERC1155/ERC20 token pairs, and Mint\&Burn tokens on the Right side.
## Stateless System
By reducing the frequency and the volume of adding data to the Ethereum state, Fracton tackles the state explosion problem by creating a “stateless system” that runs on the Ethereum mainnet with absolute cost efficiency.
Fracton protocol does not add any state variables to be updated for user actions. Furthermore, Fracton protocol reduces traditional token contract \_balance state variable updates which:
* Reduce >25% gas in token exchange compared to traditional swap, by its pool-less liquidity design, by mint/burn user address tokens instead of transferring between user address and swap.
* Reduce >50% gas compared to traditional swap in converting BlindBox into People’s NFT, by embedding BlindBox business logic into People’s NFT ERC1155 contract.
---
# 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/fractonxs-solutions/key-innovations.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.
