> For the complete documentation index, see [llms.txt](https://gitbook.mor.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gitbook.mor.org/smart-contracts/documentation/builders-protocol/v4-protocol/guides/required-mor-balance-on-the-treasury-contract.md).

# Required MOR balance on the treasury contract

## For all Subnets

Starting from v4, Subnet rewards are continuously accrued based on an emissions curve stored in the `RewardPool` contract. The emission is global and applies across all networks, with a network-specific multiplier determining how much reward is allocated per chain.

To ensure the system can fulfill all reward obligations at any time, the `BuildersTreasuryV2` contract must hold enough MOR tokens to cover all distributed but unclaimed rewards.

Call the function [`getCurrentSubnetsRewards()`](/smart-contracts/documentation/builders-protocol/v4-protocol/contracts/buildersv4.md#getcurrentsubnetsrewards). This function returns the total amount of rewards allocated to Subnets but not yet claimed. It accounts for the global reward rate and the time since the last update. This is the minimum MOR token amount that must be present on the treasury contract to pay out Subnet rewards at this point in time.

## For specific Subnet

To calculate the unclaimed rewards for a specific subnet, use [getCurrentSubnetRewards()](/smart-contracts/documentation/builders-protocol/v4-protocol/contracts/buildersv4.md#getcurrentsubnetrewards). This function computes the reward for the given Subnet, based on the updated global rate and the Subnet’s deposited amount.


---

# 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://gitbook.mor.org/smart-contracts/documentation/builders-protocol/v4-protocol/guides/required-mor-balance-on-the-treasury-contract.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.