> 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:** <https://discord.com/channels/1151741790408429580/1283805259730255884>

## 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

<https://github.com/MorpheusAIs/SmartContracts/pull/44>


---

# 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/mrc/closed/mrc46.md?ask=<question>&goal=<user_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.
