> 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/mrc/closed/mrc46.md). # MRC 46: 90 Day Delay on MOR Claims for Capital Contributors **Status: IMPLEMENTED** **Discord Thread:** ## Smart Contract Functions To Be Added Add two new variables by updating the smart contract. * \#1. claimLockPeriodAfterStake = 90 Days * \#2. claimLockPeriodAfterClaim = 90 Days It will be set every time the user deposits stETH, will be counted as current time + 90 days (or other value that can be changed on the contract). It will be set every time the user claims MOR, will be counted as current time + 90 days (or other value that can be changed on the contract). ## Purpose To prevent farmers from depositing stETH and immediately claiming / dumping the MOR tokens earned as there is currently no MOR claim delay function. Those depositing stETH over a longer period of time are adding value to the Protocol Owned Liquidity. Those only depositing stETH to immediately sell MOR are just preforming an arbitrage and providing less to the community then they get in MOR rewards. [Analysis of the onchain data](https://docs.google.com/spreadsheets/d/1RrE3tnByYoy_oieJkq5CJ3tFWvENgo6RYT9sepWaeCY/edit?usp=sharing) indicates this change will not effect 90% of the Morpheus Capital Contributors. * Only 10% of people Claim MOR more often than once every 90 days. * Only 3.4% of the Capital Contributors claim more than once a month. ## Implementation Can be coded up by the Smart Contract developers that worked on the Capital Smart Contracts. ## Proposed Code --- # 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/mrc/closed/mrc46.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.