🚀 Implement Direction Filter for Transactions

[MrLutik]

Feature Description

Implement the direction (or directions) filter for the /api/transactions endpoint to filter transactions by inbound/outbound direction relative to a specified address.

This is a split from issue #41 to track this specific feature.

Requested Behavior

Similar to Etherscan's in and out transaction filters:

# Filter inbound transactions to an address
/api/transactions?address=kira1...&direction=inbound

# Filter outbound transactions from an address
/api/transactions?address=kira1...&direction=outbound

Implementation Notes

Direction filtering requires:

1. An address parameter must be provided (direction is relative to an address)
2. Check message type and address fields to determine direction:
   • Inbound: Address appears in to_address field
   • Outbound: Address appears in from_address field

Current State

• directions field is defined in QueryTxsParams struct but not implemented
• Parameter format discussed: ?direction=inbound or ?direction=outbound

Location

• manager/types/cosmos.go:182 - struct field exists
• manager/gateway/cosmos_agregated3.go - needs implementation

References

• Parent issue: 🐛 Transaction Query Filters Not Implemented or Broken #41
• Discussion: Bugfix/41 #56 (comment)

Acceptance Criteria

• Direction filter implemented (inbound/outbound)
• Requires address parameter when using direction
• Works with all message types that have address fields
• Tests added for direction filtering

[muknta]

@MrLutik it's working, we can close the issue

in:

curl http://3.123.154.245:11000/api/transactions?directions[]=inbound&address=kira177lwmjyjds3cy7trers83r4pjn3dhv8zrqk9dl

returns 8 txs

out:

curl http://3.123.154.245:11000/api/transactions?directions[]=outbound&address=kira177lwmjyjds3cy7trers83r4pjn3dhv8zrqk9dl

returns 5 txs (all identity records which is correct for this acc. It hasn't Sent to anyone)