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
Interoperable chains may have multiple tokens. The transactions of such chains may use different tokens for
Amount
Fee
Message fee
Therefore the lists should read the tokes from the transaction object, rather than assuming it based on the token of the current chain.
Lisk Desktop should be able to display such transactions in a list.
Acceptance Criteria
Lisk Desktop must be able to display transactions that may use more than one token for different values.
All relevant components and utility functions must reside under the transaction domain.
The Redux store reducer, actions, and middleware must reside under the transaction domain.
The Token domain is responsible for storing the token (list and selected) and providing it through out the app.
Update unit tests.
Update and enable relevant e2e tests.
Additional Information
We need the transaction object schema from Lisk Service to understand how to read the data from the transaction object.
The text was updated successfully, but these errors were encountered:
Description
Interoperable chains may have multiple tokens. The transactions of such chains may use different tokens for
Therefore the lists should read the tokes from the transaction object, rather than assuming it based on the token of the current chain.
Lisk Desktop should be able to display such transactions in a list.
Acceptance Criteria
transaction
domain.transaction
domain.Additional Information
We need the transaction object schema from Lisk Service to understand how to read the data from the transaction object.
The text was updated successfully, but these errors were encountered: