# When will developers implement 200% MP cap boost

**URL:** <https://gov.gmx.io/t/when-will-developers-implement-200-mp-cap-boost/2434>\
**Category:** Uncategorized\
**Created:** [September 22, 2023, 10:52am UTC](https://gov.gmx.io/t/when-will-developers-implement-200-mp-cap-boost/2434 "2023-09-22T10:52:01Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![george](https://avatars.discourse-cdn.com/v4/letter/g/71e660/32.png) [@george](https://gov.gmx.io/u/george)\
**Post date:** [September 22, 2023, 10:52am UTC](https://gov.gmx.io/t/when-will-developers-implement-200-mp-cap-boost/2434/1 "2023-09-22T10:52:01Z")

</div>

There are dozens of addresses over the 200% boost.

Hundreds of thousands of MP’s accruing rewards beyond the cap.

When is the team implementing what the community voted on.

---

<div class="post-metadata">

**Author:** ![Saulius](https://sea2.discourse-cdn.com/flex020/user_avatar/gov.gmx.io/saulius/32/455_2.png) [@Saulius](https://gov.gmx.io/u/Saulius)\
**Post date:** [September 24, 2023, 10:17am UTC](https://gov.gmx.io/t/when-will-developers-implement-200-mp-cap-boost/2434/2 "2023-09-24T10:17:00Z")

</div>

Not “hundreds of thousands” but only 8160 MP should be passive atm. Implementing cap is quite difficult per my understanding. It needs reward distributor contract upgrade and potential audits before deployment. To partly tackle this problem we need reduce MP APR rate asap. We were promised will have vote on it but still waiting.

 ![Capture](https://us1.discourse-cdn.com/flex020/uploads/gmx/original/1X/d06e21dd9a9e9e1d91ef332495de84ab11c4c5a5.png)

---

<div class="post-metadata">

**Author:** ![ImmieV](https://avatars.discourse-cdn.com/v4/letter/i/f05b48/32.png) [@ImmieV](https://gov.gmx.io/u/ImmieV)\
**Post date:** [November 19, 2023, 3:06pm UTC](https://gov.gmx.io/t/when-will-developers-implement-200-mp-cap-boost/2434/3 "2023-11-19T15:06:31Z")

</div>

Circling back on this. This Snapshot was already voted on? We need to understand a respective timeline here.

---

<div class="post-metadata">

**Author:** ![tbudd23](https://avatars.discourse-cdn.com/v4/letter/t/45deac/32.png) [@tbudd23](https://gov.gmx.io/u/tbudd23)\
**Post date:** [November 20, 2023, 5:08pm UTC](https://gov.gmx.io/t/when-will-developers-implement-200-mp-cap-boost/2434/4 "2023-11-20T17:08:08Z")

</div>

will this topic be addressed by the core team or nah

---

<div class="post-metadata">

**Author:** ![Nuggs](https://avatars.discourse-cdn.com/v4/letter/n/8edcca/32.png) [@Nuggs](https://gov.gmx.io/u/Nuggs)\
**Post date:** [December 5, 2023, 9:43pm UTC](https://gov.gmx.io/t/when-will-developers-implement-200-mp-cap-boost/2434/5 "2023-12-05T21:43:52Z")

</div>

This really should get implemented in the near future by the team. In the future if the team doesn’t have capacity to work on an issue, it shouldn’t be moved to a vote. In this case, vote is done, result should be implemented within a reasonable amount of time - and the delay is starting to feel unreasonable.

---

<div class="post-metadata">

**Author:** ![MuzTSH](https://sea2.discourse-cdn.com/flex020/user_avatar/gov.gmx.io/muztsh/32/1097_2.png) [@MuzTSH](https://gov.gmx.io/u/MuzTSH)\
**Post date:** [December 6, 2023, 4:47am UTC](https://gov.gmx.io/t/when-will-developers-implement-200-mp-cap-boost/2434/6 "2023-12-06T04:47:32Z")

</div>

![photo_2023-12-06 05.45.51](https://us1.discourse-cdn.com/flex020/uploads/gmx/original/1X/d5463a1b797fcfb3a3f1bcdb411ae41db31fd37f.jpeg)

As far as I know this is being implemented, it’s not easy task to do and it will require some audits.

Let’s be patient
