-
Notifications
You must be signed in to change notification settings - Fork 155
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
Have SubtensorModule::TotalIssuance track extrinsic fees #816
Labels
bug
Something isn't working
Comments
Merged
It does handle transaction fees: Lines 394 to 409 in 0b2f65c
This rounding issue is tiny (~20 rao) due to floating point arithmetic issues. |
does this hook on account kill sweeps? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
The
pallet_subtensor::migrations::migrate_init_total_issuance::initialise_total_issuance
migration is seemingly running every time there is a runtime upgrade. Also running every upgrade is atry_state
check for the total issuance trackers, to make sure they are summing to the right values.However, because the migration runs first, we can never reach a state where the
try_state
check fails.Removing the migration run appears to create a fail-state for the
try_state
check, meaning some difference in the balances palletTotalIssuance
is differing from what we are tracking with the Subtensor palletTotalIssuance
.My first assumption is the extrinsic fees and/or the balances pallet's account kill, where it burns the remainder of the balance below the existential deposit.
To Reproduce
pallet_subtensor::migrations::migrate_init_total_issuance::initialise_total_issuance
ERROR runtime::frame-support] ❌ "SubtensorModule" try_state checks failed: Other("TotalIssuance accounting discrepancy")
Expected behavior
I would expect the total issuance to not differ between the storage values, as the try_state expects.
Screenshots
No response
Environment
Subtensor 201
Additional context
No response
The text was updated successfully, but these errors were encountered: