Implement send token across application

[sridharmeganathan]

Description

• Update send native and LSK token across application component according to new
  • Native token design
  • LSK token design
• Fetch and display active supported blockchain applications
  • Display only active applications (this information is similar to application management, except here we only show the names of the applications)
• Fetch and display supported tokens for a given application
  • Filter tokens which has zero balance
• Reuse recipient address input and adopt to new design
  • All existing validation logic should be retained
• Display the transaction fee token symbol based on application configuration
• Adopt transaction summary according to new design
• Include Enter your password screen in the send flow
• Adopt transaction result screen according to new design
• Reuse the Add message input and retain the existing logic
  • Update to new design
• Display initialisation fee when recipient address selected token balance is zero
  • The initialisation fee displayed should be corresponding native token
• Display ccm fee in LSK
  • If the send account doesn’t have enough LSK, then display error message

Acceptance Criteria

• Set LSK token as default in the token dropdown
• User should be able to send LSK tokens from Mainchain to Sidechain
• User should be able to send supported Native tokens selected from the dropdown
• User should be able to sign and broadcast transaction to network (Mock)
• User should be able to see the token balance
• User should receive feedback when failed to send transaction to network (Mock)

Additional information

• The logo and token symbol can be hardcoded for now and updated once the service API is ready
• Mock RPC endpoint token_getBalances to return the following:

{ balances: { tokenID: string, availableBalance: string, lockedBalances: { moduleID: number, amount: string }[], }[], } []

Use application management Mock API to display supported applications