Skip to content
This repository has been archived by the owner on Nov 15, 2023. It is now read-only.

Wrong value in Staking.Bonded event after Staking.Rebond extrinsic #9840

Closed
TheGoldenEye opened this issue Sep 19, 2021 · 4 comments · Fixed by #9866
Closed

Wrong value in Staking.Bonded event after Staking.Rebond extrinsic #9840

TheGoldenEye opened this issue Sep 19, 2021 · 4 comments · Fixed by #9866
Labels
I3-bug The node fails to follow expected behavior.

Comments

@TheGoldenEye
Copy link

If Staking.Rebond extrinsic was executed with a value greater than the current / available balance, the resulting Staking.Bonded event should contain only the actual bonded value (currently it does not).
I see 2 solutions:

  • the transaction fails due to insufficient balance
  • the value ist interpreted as max_additional like in Staking.BondExtra extrinsic (here the Staking.Bonded event provides the actual bonded value)

Example 1 (Westend):
Stash 5D9x7E3f7VT2RqdpA54V8MJSh5xBr7pUV6bCDmGbpjZ9mi75 with balance of 178 WND
Staking.Rebond with 200 WND: https://westend.subscan.io/extrinsic/7435449-2

Example 2 (Kusama):
Stash DcAgRyM7BCEToY43W3WesEtPKWDBJ5RDDc5FEE38pbP25AD with balance of 2768 KSM
Staking.Rebond with 27 million! KSM: https://kusama.subscan.io/extrinsic/9008712-3

@TheGoldenEye TheGoldenEye changed the title Possible wrong value in Staking.Bonded event after Staking.Rebond extrinsic Wrong value in Staking.Bonded event after Staking.Rebond extrinsic Sep 19, 2021
@rphmeier rphmeier transferred this issue from paritytech/polkadot Sep 22, 2021
@github-actions github-actions bot added the J2-unconfirmed Issue might be valid, but it’s not yet known. label Sep 22, 2021
@bkchr
Copy link
Member

bkchr commented Sep 25, 2021

CC @kianenigma

@shawntabrizi shawntabrizi added the I3-bug The node fails to follow expected behavior. label Sep 25, 2021
@shawntabrizi shawntabrizi removed the J2-unconfirmed Issue might be valid, but it’s not yet known. label Sep 25, 2021
@TheGoldenEye
Copy link
Author

In which runtime it will be active?

@kianenigma
Copy link
Contributor

Should be in 9.11, but unfortunately it won't be in the chanegelog since the PR did not have the correct label.

@TheGoldenEye
Copy link
Author

hmm, seams not
tested in westend with runtime 9111, old behavior

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
I3-bug The node fails to follow expected behavior.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants