Inconsistency between LCD client and CLI client - slashing/signing-info

[joe-bowman]

Summary of Bug

gaiacli stake signing-info takes the validator public key, from which it derives the validator address.

<rest_api_endpoint>/slashing/signing_info/<validator> expects the validator address (which incidentaly I haven't been able to find? is this actually displayed/used anywhere?)

Should the REST api be updated to use the bech32valpubkey and compute the validator address from that, as per the CLI?

Steps to Reproduce

Attempt to hit REST signing-info endpoint with the same address used for identical CLI query and receive the following error: invalid bech32 prefix. Expected cosmosvaladdr, Got cosmosvalpub

---

For Admin Use

• Not duplicate issue
• Appropriate labels applied
• Appropriate contributors tagged
• Contributor assigned/self-assigned

[alexanderbez]

Agreed it should be consistent.

[cwgoes]

I think we're getting rid of pubkeys in ABCI in favor of just passing validator addresses - so agreed on consistency but it may need to be based on address.

[joe-bowman]

Sorry. Fat fingers!

[alexanderbez]

Whoops. Closed via #1889