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

Propose new decay rate #9

Closed
wants to merge 1 commit into from

Conversation

mctrivia
Copy link

DigiByte current block rewards end on block 40265288 with 90.29 DGB/block this is a huge drop to 0 and probably way to close to the current date for tx fees to take over.

I propose we change the decay rate of the rewards at block 12993200 from 0.98884 to 0.98652 this will make almost no difference to rewards over the next 5 years but will stretch the rewards phase to block 116731970 with a 0.16 DGB/block reward.

I have written a block reward simulator so you can easily double check my math available at https://github.com/mctrivia/dgb_reward_simulator

DigiByte current block rewards end on block 40265288 with 90.29 DGB/block this is a huge drop to 0 and probably way to close to the current date for tx fees to take over.

I propose we change the decay rate of the rewards at block 12993200 from 0.98884 to 0.98652 this will make almost no difference to rewards over the next 5 years but will stretch the rewards phase to block 116731970 with a 0.16 DGB/block reward.

I have written a block reward simulator so you can easily double check my math available at https://github.com/mctrivia/dgb_reward_simulator
@Sbosvk
Copy link

Sbosvk commented Mar 1, 2021

I support this proposal.

@ChillingSilence
Copy link

Having commented on this on the other places, I just want to reiterate my thanks to @mctrivia for picking this up and running with it, and thanks too for correcting my also slightly off math 😅
On a personal level I'm of two minds about pushing out the final emissions date, however this 100% needs to be addressed sooner rather than later, I'm in full agreement with you there. This can should not be kicked down the road and no matter which route it's taken it should be resolved in DigiByte version 8.

@SmartArray SmartArray mentioned this pull request Apr 2, 2021
@SmartArray
Copy link

SmartArray commented Apr 12, 2021

This PR will be closed in favor of some new PRs. Please follow #20.

The subsidy parameter will be used if I can confirm it is appropriate.

Thank you @mctrivia

@SmartArray SmartArray closed this Apr 12, 2021
@SmartArray SmartArray reopened this Apr 12, 2021
@SmartArray SmartArray closed this Apr 12, 2021
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.

4 participants