Fixes for compatibility with latest Kusama runtime #12
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes for compatibility with latest Kusama runtime
Description
I discovered that the
list
command was returning incorrect values for rewards on Kusama and Westend, but not on Polkadot. Going down the rabbit hole investigating that, I made "some" changes on the code and I include them all in here.Changes
.gitignore
for Python projects.substrate-interface
dependency to13.3
list
HistoryDepth
call, as it's not used (the depth is obtained from the config)ActiveEra
instead ofCurrentEra
to avoid claiming rewards for an unfinished era.--unclaimed
flag asargs.only_unclaimed
for readability.substrate.token_decimals
for balancespaymemt
->payment
.pay
HistoryDepth
call, as it's not used (the depth is obtained from the config)84
(previously82
)ActiveEra
instead ofCurrentEra
to avoid claiming rewards for an unfinished eranetwork
toss58_format
for correct keypair generation.Suggestion to bump version
I think these changes don't affect the usage of the tool from the user's perspective, but I would suggest to bump the version of the tool to
1.1.0
.Let me know what you think about this and the changes above, I hope you find them useful 😁
I just saw that @arjanz has made a PR. I think his changes are also included in this PR so far, but please, take a look at both :)