unify sender tags for ease of querying

[fedekunze]

Summary of Bug

Governance txs don't follow tags standard

Steps to Reproduce

While most of the transactions from a delegator can be queried using the delegator=<address> tag. Governance txs don't follow this standard and thus clients have to additionally query each single tx independently. For eg:

For all txs from a delegator but governance:

GET /txs?delegator=<address>

For gov txs:

GET /txs?action=submit_proposal&proposer=<address>
GET /txs?action=deposit&depositor=<address>
GET /txs?action=vote&voter=<address>

---

For Admin Use

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

[alexanderbez]

I don't quite follow the proposal @fedekunze. Where is the bug here?

[fedekunze]

removed label as it's technically not a bug per se

[jackzampolin]

We should one tag that can be queried to return the list of transactions involving an address. Maybe this is something we could add as a flag to gaiacli q account

[fedekunze]

Or have a --from flag on gaiacli q txs

[jackzampolin]

Like this call

[alexanderbez]

I'm not sure if we should have --from as that may be confusing. Why not just query txs with sender=foo?

[fedekunze]

We already have that tag, but it’s not standard across all the modules

[fedekunze]

Also I’d like to get not only the ones I send but also the ones I receive, so maybe address=foo could be a better approach

[fedekunze]

@faboweb said we should use sender on all transactions, it can be either a validator or delegator address. I like that idea

[jackzampolin]

There should be an easy way to query all txns involving one address.