You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The number of shares did updated and the redelegation/unbonding have been created. This is rather an inconsistency in the message and the operation. If it only take shares, then the message should not require submitting in coin.
On the other hand, the doc in LCD show shares in the example
Thanks @kwunyeung! The concept of shares has been removed from both the messages and the outputs of unbondings/redelegations. Users provide an amount (currently Coin). So we can either:
Note: this is an UX bug, it does not affect the state machine as the tokens are converted to shares (worth of params.BondDenom) on the redelegation and unbond funcs within the staking Keeper.
Summary of Bug
Both
redelegation
andunbond
tx can be processed even if theamount
is specified with denom other thanuatom
.e.g.
Redelegation
https://cosmos.bigdipper.live/transactions/7D153586C7FC707708F954DD5F7C795745DC99AF11C7CFAE0458A87F2A5388AA
Unbonding
https://cosmos.bigdipper.live/transactions/83D4D5CFDE8AC2F5B340A5BF275FDF8C9FDAB5604C5B488D44F7E1F65A548913
The number of shares did updated and the redelegation/unbonding have been created. This is rather an inconsistency in the message and the operation. If it only take shares, then the message should not require submitting in coin.
On the other hand, the doc in LCD show
shares
in the examplehttps://cosmos.network/rpc/#/ICS21/post_staking_delegators__delegatorAddr__redelegations
and it will give error if number of shares is specified in the request. It takes coin as well.
Version
v0.34.7
Steps to Reproduce
For Admin Use
The text was updated successfully, but these errors were encountered: