Bugfix/41

[kobs30]

Date
/api/transactions?start_date=2025-11-17T16:45:35.710911842Z (ISO format)

Sort
/api/transactions?sort=asc (date is default field) OR /api/transactions?sort=field_name:asc

Type
/api/transactions?types[]=/cosmos.bank.v1beta1.MsgSend (transaction type as cosmos value)
We can add aliases (send, multisend and etc), but we should do it every time for a new transaction type added to the sekai. It's better to use proto naming.

[MrLutik]

@muknta
Date
/api/transactions?start_date=2025-11-17T16:45:35.710911842Z (ISO format)

What format is used on frontend side? ISO or epoch

[MrLutik]

@kobs30 @muknta
We should solve the "direction" parameter.
Direction is similar to etherscan.io in and out txs. We have to check message type and address to determine whether it's inbound or outbound tx.
Ref.: issue #41 comment

[muknta]

@MrLutik regarding the date format - we use currently the epoch.

I'll alter the implementation to ISO if needed

[muknta]

@kobs30 proto naming with transaction types is fine

[MrLutik]

Summary

Issue	Status	Tested
Date	✅	❎
Sort	✅	❎
Msg type	✅	❎
Address	❎	❎
Direction	❎	❎

[kobs30]

@MrLutik regarding the date format - we use currently the epoch.

I'll alter the implementation to ISO if needed

I can implement conversion on the BE side. As you want. Or double format support: ISO and UNIX

[MrLutik]

@MrLutik regarding the date format - we use currently the epoch.

I'll alter the implementation to ISO if needed

@kobs30: no changes needed