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

# Sats MarketPlace

The MarketPlace is one of the core features of Neko swap and will be the most important core feature in the later stage. Neko swap will be the first native Layer2 cross-chain BTC rune trading platform on bitlayer. Users can mint Layer1 BRC-20 (ARC-20 and more) tokens on Layer2 through Neko swap, and can choose to pay with a variety of on-chain assets such as BRC-20, BTC, ETH, and so on. Users will receive stToken, which can be traded or exchanged for Layer2 ERC-20 tokens in the Unicross market.

All BTC inscriptions on Layer2 can be bridged back to BTC Layer1 at any time. When BTC inscriptions are bridged from Layer2 to Layer1, users will receive BTC inscriptions on Layer1. At the same time, the inscriptions on the second layer will also be burned.

<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://nekoswap.gitbook.io/nekoswap/product-features/sats-marketplace.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.