KlimaDAO Forum

I see this with being inline with the intent and purpose of KIP-3, so yes.

hotstovesports This truly is only aiming at achieving the targeted APY approved in KIP-3 while factoring in the shorter rebase periods. Instead of the APY being in the mid 30k% range as displayed over the past weeks, it's actually been closer to 70k%

I don't see an issue with the reduction, as it maintains what we set out to do with KIP-3 and takes into consideration the faster than anticipated block times on Polygon. Should also help with maintaining a strong $BCT backing.

Hindsight is 20/20, but this should have been considered in positioning and proposing Kip-3

I think this is overkill tbh since we already voted and passed the original proposal. This is simply modifying the policy to Polygon's block time differences to align with the intent of the prior proposal.

[unknown] so your telling me that somehow this wasn't discovered until just now and that noone thiught to data mine until right now? I don't buy it. As they can see the fors are barely a majority, so I hope everyone is ready for the incoming price crash if this passes.

[unknown] yes the website APY will display correctly tomorrow (Nov 30).

[unknown] fix is ready already to account for this so we will deploy when the APY is adjusted again

While the timing of this is a bit unfortunate (following KIP-3), and so people might misinterpret this KIP as being a further reduction, I think it makes a 100% sense to implement this right away. We really do need to stress that this is just a correction due to block timings because I have the feeling that some people might not fully understand why this is happening right now. But full support from my side in favour of this proposal.

Sustainable project is what we need, reduce it!!!

A healthy reduction is needed to avoid dilution long term, I would much rather see price stability too and this is all a step in the right direction long term.

Agreed with [unknown]. This seems more of a bug fix rather than a new proposition to be voted for. Thanks for the hard work.

Let's build up our treasury! LFG

Klima is just a seed of what it can be and this is a great step to solidify long term. slowly getting myself into defi and the amazing world of what the future can be.

Using a fixed number of blocks per epoch based on the prior 3-month average isn't flexible. If the number of blocks per epoch subsequently decreases over a period of time, you would need to raise the APY since
each epoch now takes longer. This constant re-adjustment could be painful, and it's always retrospective. An alternative approach might be to factor the average blocks per epoch into the APY calculation so that
the APY automatically adjusts as the number of blocks increases or decreases. This would operate similar to a moving average, where the average is calculated based on the block time of the previous 'n' days. https://polygonscan.com/chart/blocktime