Allow Usage of Client Provided Account Number/Sequence in Context Query

[alexanderbez]

Summary

The current refactor of #1741 contains utils.SendTx which does a lookup of an account number and sequence if the respective provided CLI arguments are 0. Majority of all CLI command implementations use utils.SendTx.

Problem Definition

A client should be able to specify 0 as an account number and/or sequence without utils.SendTx automatically doing a lookup.

Proposal

Implement some notion of determining when a user actually specified these values via the command line and allowing them through. This will most likely involve moving this logic out of utils and some some viper work somewhere else.

---

For Admin Use

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

[cwgoes]

Might be post-launch, as I think Viper just doesn't do this correctly - spf13/viper#276.

Ref #1206.

[ValarDragon]

I think we can just make the default value -1. Negative values meaning automatic isn't super uncommon. (though perhaps a bit of an anti-pattern)

[alexanderbez]

True, that is an option. Although, the UX would be a bit...weird...with the -1 default value in the CLI description.

[jackzampolin]

Closing as this has been addressed.