> 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.md). # v4 Protocol Protocol v4 is a redesigned staking and reward distribution system built around the concept of Subnets. Each Subnet represents a distinct staking pool that users can join by depositing MOR tokens. The administrator of a Subnet can later claim MOR rewards proportionally to the total staked amount in that Subnet relative to the global network. The rewards are calculated in real time based on a global emission curve, which simulates MOR token distribution over time for the Builders bucket. Unlike earlier versions that relied on manual reward injections, v4 ensures continuous and fair distribution as long as the `BuildersTreasuryV2` contract holds sufficient MOR balance. Subnet identifiers now incorporate the blockchain’s chain ID alongside the Subnet name, enabling Subnets with identical names to exist across multiple networks. Each Subnet also has its own metadata and allows specifying a separate claim administrator who is authorized to collect rewards on its behalf. ### --- # 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.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.