Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SIMD-0199: Inflation #199

Closed
wants to merge 1 commit into from
Closed

Conversation

anselsol
Copy link

@anselsol anselsol commented Nov 21, 2024

[🔥] Taken to conversation for now: #200

@anselsol anselsol changed the title SIMD-0198: Inflation SIMD-0199: Inflation Nov 21, 2024
@levicook
Copy link

First pass, quick thoughts:

The 50% threshold could cause back-and-forth inflation adjustments. Any thoughts on how to attenuate the oscillations? A general case stabilizer is probably worthwhile to make it easier to predict emission.

15% per epoch seems aggressive / volatile too.

Starting at 4.5% is a significant change from current rates too.

@anselsol
Copy link
Author

@levicook that's a very good question. Cosmos has this kind of super complex formula to stabilize oscillations depending on the multiple threshold (not just 50%) - we need to learn more about the implications to be able to reply to this (source : https://forum.cosmos.network/t/proposal-48-accepted-inflation-rate-change-correction/4834)

Right now the curve (you can find it here) goes to 1.5% in 6 years. The idea was to go there much quicker to stabilize the total supply.

From what we could gather a big part of the staking APY do come from fees right now (and the 50% fees burn will soon be removed).

The current inflation is around 4.8%. I think the staking APY (maybe you're talking about this) takes into account auto compounding + base tx fees + priority fees (+ jito tips if running Jito).

Let's take this to the the discussion tab 😅 I'll copy this in the first comment

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants