You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
How to search/list the transactions/files efficiently? When listing files we only care for the top-level root aggregate transaction (especially the inner transfers with the meta), individual data aggregate transactions are not useful. The current solution is to have 2 recipients, the root transaction transfer uses the “owner” as the recipient, the data transfers use “sink/burn/garush” address as the recipient. Then we can search by “recipient=owner” and just get the root transaction. From there, the Storage Service picks the files.
Atm the 2 recipients work ok but we may need to add more fields to further trim down the search, especially when they are regular user transfer in the mix.
One option is adding transaction searches by "message" (=, or maybe like) to Rest. We could search for transfer where the message includes "ype: garush or type: garush and"parser: png. Note the type: garush is required to filter out other transfers that aren't root transfers (like data transfers or unrelated transfers)
The text was updated successfully, but these errors were encountered:
How to search/list the transactions/files efficiently? When listing files we only care for the top-level root aggregate transaction (especially the inner transfers with the meta), individual data aggregate transactions are not useful. The current solution is to have 2 recipients, the root transaction transfer uses the “owner” as the recipient, the data transfers use “sink/burn/garush” address as the recipient. Then we can search by “recipient=owner” and just get the root transaction. From there, the Storage Service picks the files.
Atm the 2 recipients work ok but we may need to add more fields to further trim down the search, especially when they are regular user transfer in the mix.
One option is adding transaction searches by "message" (=, or maybe like) to Rest. We could search for transfer where the message includes
"ype: garush
ortype: garush and"parser: png
. Note thetype: garush
is required to filter out other transfers that aren't root transfers (like data transfers or unrelated transfers)The text was updated successfully, but these errors were encountered: