-
Notifications
You must be signed in to change notification settings - Fork 610
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
[v10] Thirdening Testing #1597
Comments
Epoch 364:
Epoch 365:
Epoch 366:
Epoch 367:
Epoch provisions are now 2/3rds what it was, as expected. The thirdening will happen on epoch 367. This translates to the epoch that occurs on Monday, June 20th on mainnet. |
I wanted to query to community pool and note the differences, but for some reason I think the state export broke this connection since the account I know to be the community pool does not increase at all (both pre and post thirdening). I could also be querying the wrong address Edit: Community pool address is osmo1jv65s3grqf6v6jl3dp4t6c9t9rk99cd80yhvld |
My numbers weren't adding up for community pool, so this is my attempt at getting them to work for a dev reward wallet. Should be less varying factors. Doing it on this address osmo14kjcwdwcqsujkdt8n5qwpd8x8ty2rys5rjrdjj with 0.288700000000000000 weight Epoch 364:
Epoch 365:
Epoch 366:
Epoch 367:
|
Spun up another testnet to check total supply Epoch 364:
Epoch 365:
Epoch 366:
Epoch 367:
|
Are we happy with the above tests? If so, I will close this issue |
Yeah,thanks! We can just keep an eye on the total supply query on mainnet as a final sanity check |
Background
While there is no reason to be suspicious of the code in place to reduce token emissions by 1/3rd every year (the thirdening), since this is a fairly significant event, it should get extensively tested prior to it happening.
Suggested Design
Prior to June 18th
Acceptance Criteria
Actions related to thirdening are reviewed for any odd behaviors. If odd behavior is noted, a plan is put into action to address prior to June 18th
The text was updated successfully, but these errors were encountered: