Split from https://github.com/cosmos/voyager/issues/1364#issuecomment-425074861.

Just to be sure: should we fetch the transactions related to unbounding or it's enough to show the data coming from /stake/delegators/{addr}/unbonding_delegations
[
{
"balance": {
"amount": "3",
"denom": "steak"
},
"creation_height": "1379",
"delegator_addr": "cosmos1ccwqds0dd6cxp44a7rpc6kscm7zj6jdcykaeut",
"initial_balance": {
"amount": "3",
"denom": "steak"
},
"min_time": "2018-12-14T15:02:05.203889Z",
"validator_addr": "cosmosvaloper1ccwqds0dd6cxp44a7rpc6kscm7zj6jdcpzfvsc"
}
]
Maybe also add redelegations as undelegations?
As for now it seems we can't have more than an unbounding transaction per validator: "existing unbonding delegation found"
@cwgoes if I understood you are on this right?
If I understood you are on this right?
Yes. Working on some changes to fee distribution first but hopefully multiple unbonding delegations per validator should come long in a week or two - tracking issue here: https://github.com/cosmos/cosmos-sdk/issues/1402
The concept of the My Delegations is wrong here since we're showing the validators instead of the actual delegations/unbonds/redelegations.
Imo we should change here My Delegations for My Validators. The actual contents for the My
Delegation should be the discussed on another issue based on the new unbonding and redelegation index implementation
Most helpful comment
The concept of the
My Delegationsis wrong here since we're showing the validators instead of the actual delegations/unbonds/redelegations.Imo we should change here
My DelegationsforMy Validators. The actual contents for theMy Delegationshould be the discussed on another issue based on the new unbonding and redelegation index implementation