# PUP-21 Setting parameter values for the PIP-22 new parameter set

**URL:** <https://forum.pokt.network/t/pup-21-setting-parameter-values-for-the-pip-22-new-parameter-set/3200>\
**Category:** Parameters\
**Tags:** approved\
**Created:** [June 30, 2022, 7:26pm UTC](https://forum.pokt.network/t/pup-21-setting-parameter-values-for-the-pip-22-new-parameter-set/3200 "2022-06-30T19:26:59Z")\
**Posts on this page:** 1\
**Showing post:** 37

<div class="post-metadata">

**Author:** ![iaa12](https://forum.pokt.network/letter_avatar_proxy/v4/letter/i/848f3c/32.png) [@iaa12](https://forum.pokt.network/u/iaa12)\
**Post date:** [July 26, 2022, 1:17am UTC](https://forum.pokt.network/t/pup-21-setting-parameter-values-for-the-pip-22-new-parameter-set/3200/37 "2022-07-26T01:17:25Z")

</div>

> [@msa6867](#):
>
> I believe the community sentiment in passing PIP-22 was implicit approval to utilize the knobs to offer some consolidation ability.

I’d have to disagree with that based on some of the comments in that thread. I think PIP-22 was green light to develop the feature in case it was needed, with no implicit approval to turn any knobs. At least not right now.

> [@PIP-22: Stake-weighted Servicer Rewards](https://forum.pokt.network/t/pip-22-stake-weighted-servicer-rewards/3101/80):
>
> To me it seems that the ones voting against PIP-22 have lost sight that by itself the proposal adds the parameters and the few lines of code that provide the knobs needed to enable varying degrees of weighed rewards while deferring to an accompanying PUP the actual setting of the parameters ( **i.e., whether or not to turn on the weighted staking and if so by how much** ).

> [@PIP-22: Stake-weighted Servicer Rewards](https://forum.pokt.network/t/pip-22-stake-weighted-servicer-rewards/3101/79):
>
> From my understanding, the set parameter at 1 will not incentize any node consolidation or affect rewards distribution. BUT what it does do is effectively gives the Core Team/@andy the green light for development. Essentially, if the DAO ever needs to trigger this mechanism then we can, and we should at least support giving the engineers the “go” to finish the development work

> [@PIP-22: Stake-weighted Servicer Rewards](https://forum.pokt.network/t/pip-22-stake-weighted-servicer-rewards/3101/79):
>
> I **suggest that the DAO does not change/vote on a new set of parameters for consolidating until development is fully completed and the network is upgraded with this consensus change.** This will also give more time for this proposal to marinate in people’s mind (perhaps some more dissenting opinions/implications may show up for this proposal) & to observe the effects of the economy, other PUP’s and PIP’s, and LeanPOKT

---

_[View the full topic](https://forum.pokt.network/t/pup-21-setting-parameter-values-for-the-pip-22-new-parameter-set/3200)._