> For the complete documentation index, see [llms.txt](https://docs.nekodex.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nekodex.org/nekodex-playground/docs-for-devs/contracts/maker.md).

# Maker

Collection of contracts for each maker (liquidity framework) type. See the subpage for details.

[Oracle Maker](/nekodex-playground/docs-for-devs/contracts/maker/oracle-maker.md)

[Spot Hedge Maker](/nekodex-playground/docs-for-devs/contracts/maker/spot-hedge-maker.md)

## Key maker concepts

#### `minMarginRatio`

This is a minimum margin ratio set by a maker (LPs / pool participant). If this ratio is reached, the maker will stop providing more liquidity. In some Liquidity Strategies it is possible to LP with leverage (e.g. oracle pools), and in some Strategies leverage is not desirable (e.g. spot-hedge pools), and `minMarginRatio` controls the amount of leverage the maker allows.

#### `fillOrder`

Maker contracts provide a public fillOrder function to allow users to fill orders using pool liquidity.

#### Callback

Some maker types, such as spot hedge, may function best when funds can be removed from the vault for user in hedging or other functions. This ability is named `callback`, and is initially restricted to whitelisted LPs. This function will either be made permissionless or replaced by a more secure mechanism in the future.

#### Matching priority

Currently there is no prioritization. Orders will be filled using the maker with the best price including fees.

## Future

More maker types will be added to the liquidity framework as they are developed. Maker types can be developed by the Foundation team and by 3rd parties. The scope for maker types is very broad and can include JIT liquidity, off-chain orderbooks, and much more.

Please [Contact us](/nekodex-playground/all-about-perp/contact-us.md) if you are interested in developing novel liquidity framework strategies!


---

# 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://docs.nekodex.org/nekodex-playground/docs-for-devs/contracts/maker.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.