> 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/~/revisions/3ulU7lsttK8DsMz9IH4e/smart-contracts/documentation/distribution-protocol/v5-protocol.md). # v5 Protocol ## Introduction The primary goal of the v5 protocol is to ensure accurate distribution of MOR tokens among stakers of various buckets based on their staked stETH. Capital stakers (Capital bucket) deposit stETH on the Ethereum network through this protocol for a some period of time, in exchange for receiving yield in the form of MOR tokens on the Arbitrum One network utilizing LayerZero for cross-chain messaging. The yield is calculated based on the user’s stake, the total stake across all users, and the overall reward pool. A user’s yield can be increased through participation in the referral program or by utilizing a power factor. Other buckets **do not** stake stETH directly into the smart contract. Instead, the contract owner allocates reward shares to specific addresses. These addresses, following a similar logic to capital stakers, can claim MOR tokens based on their assigned share. In turn, the Morpheus protocol earns yield from the stETH deposited by users. This yield is transferred to Arbitrum using the Arbitrum Bridge. On L2, the yield can optionally be converted into MOR tokens to increase liquidity in the Uniswap pool. Each bucket has its own separate reward pool, and these do not overlap. This ensures that capital stakers are not mixed with other participant groups, maintaining clear reward boundaries and fair distribution within each category. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://gitbook.mor.org/~/revisions/3ulU7lsttK8DsMz9IH4e/smart-contracts/documentation/distribution-protocol/v5-protocol.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.