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
{{ message }}
This repository has been archived by the owner on May 10, 2024. It is now read-only.
Since core is going to be upgraded to 1.52.x, we will have the ability to fetch all transactions from all networks. Currently, we are only fetching all transactions that belong to that account from the current selected(default) network of that account's coin type.
For example, if a user has an Eth account with address 0xA and it has Tx A on Eth Mainnet, and Tx B on Polygon, and the default network for Eth coin type is Eth Mainnet
Currently we display transactions under 0xA is:
Tx A on Eth Mainnet
Expected the transactions under 0xA is:
Tx A on Eth Mainnet
Tx B on Polygon
This requirement is very similar to #7233 except this issue is for Account Activity Screen
This requirement should also apply to AccountTransactionListView. Can be integrated in the same issue but feel free to create a separated issue if necessary.
The text was updated successfully, but these errors were encountered:
Since core is going to be upgraded to 1.52.x, we will have the ability to fetch all transactions from all networks. Currently, we are only fetching all transactions that belong to that account from the current selected(default) network of that account's coin type.
For example, if a user has an Eth account with address 0xA and it has Tx A on Eth Mainnet, and Tx B on Polygon, and the default network for Eth coin type is Eth Mainnet
Currently we display transactions under 0xA is:
Tx A on Eth Mainnet
Expected the transactions under 0xA is:
Tx A on Eth Mainnet
Tx B on Polygon
This requirement is very similar to #7233 except this issue is for Account Activity Screen
This requirement should also apply to
AccountTransactionListView
. Can be integrated in the same issue but feel free to create a separated issue if necessary.The text was updated successfully, but these errors were encountered: