Improve staking endpoints

[faboweb]

Improvement ideas:

• The new staking endpoints for querying unbonding and redelegation are not really speaking. Can we change them to speaking names?
• There are now 3 endpoints to query for every candidate. Can we abstract the backend logic to make this more convenient to app developers and provide one endpoint, i.e. GET /stake/{candidate}/delegators/{delegator} that returns an accessible state like { shares: x, unbondingShares: y, redelegatingShares: z }

[faboweb]

Another huge improvement would be transmitting actual token amounts instead for rationals. Each app desired to show a staked amount would need to implement calculating the tokens.

Pulling in @rigelrozanski

[rigelrozanski]

what do you mean by "speaking names" like better names?

There are now 3 endpoints to query for every candidate. Can we abstract the backend logic to make this more convenient to app developers and provide one endpoint, i.e. GET /stake/{candidate}/delegators/{delegator} that returns an accessible state like { shares: x, unbondingShares: y, redelegatingShares: z }

Nice, yeah really into this

Another huge improvement would be transmitting actual token amounts instead for rationals. Each app desired to show a staked amount would need to implement calculating the tokens.

Yeah we could transmit a decimal amount, that's probably the most easily readable/accurate output, additionally and integer is transmittable (which would be the withdrawal amount) however much of the staking logic requires higher degrees of accuracy so we use rationals, probably want to depict those higher levels of accuracy

[fedekunze]

Check #1010 in Voyager for the proposed refactor