> For the complete documentation index, see [llms.txt](https://doc.magport.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.magport.io/product-guides/develop-coretime-ready-chain-with-magnet-stack/using-magnet-stack-functional-models.md).

# Using Magnet Stack : Functional Models

**Profit Distribution:**

   \- Define the target address and distribution ratios for profit.

   \- If left empty, profit distribution will be disabled, and profits will remain in the system account.

{% hint style="info" %}
If DOT is selected as the gas token in the coretime configuration, any price difference between the coretime orders and the gas fees collected per block will be calculated as profit and automatically allocated to the designated address.

If you choose your native token as the gas token, all gas fees collected will be allocated directly, without involving DOT.
{% endhint %}

\
For more infortmaion about profit calcuation, please refer to this section:

{% content-ref url="/pages/2XPTGohNYeLHLpsze7KN" %}
[Profit Calcuation and Distribution](/overview/magnet-network-features/profit-calcuation-and-distribution.md)
{% endcontent-ref %}

 **Assurance:**

This function ensures that coretime order placement is forced and block production continues if the order control mechanisms (Price Limit & Price Threshold) halt order placement for longer than the defined bid threshold.

The bid threshold is specified by the number of relay chain blocks. For example, if the bid threshold is set to 8, on-demand order placement can be halted for up to 8 relay chain blocks if the Price Limit and Price Threshold conditions are not met.

You may define bid threshold in this section.

For more information about assurance function, please refer to this section:

{% content-ref url="/pages/VseMU5RZs6cxJppJufdS" %}
[Coretime Order Control and Assurance](/overview/magnet-network-features/coretime-order-control-and-assurance.md)
{% endcontent-ref %}

**Other Functions:**

   \- [XCM](https://wiki.polkadot.network/docs/learn-xcm-index): Facilitates communication and data transfer between different blockchains within the Polkadot and Kusama ecosystems.

   \- [Proxy](https://wiki.polkadot.network/docs/learn-guides-accounts-proxy): Proxies enable users to engage less frequently with an account while still actively contributing to the network with the token weight of that account. Proxies have the authority to execute a limited set of actions pertaining to certain substrate pallets on behalf of another account.

   \- [Multisig](https://wiki.polkadot.network/docs/learn-guides-accounts-multisig): Enables joint account control by requiring multiple signatures for transaction approval.

   \- OpenGov: Provides a framework for decentralized governance, allowing stakeholders to propose and vote on network changes.

<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.magport.io/product-guides/develop-coretime-ready-chain-with-magnet-stack/using-magnet-stack-functional-models.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.