Skip to content

EVM send max error on HD #3357

@smk762

Description

@smk762

To Reproduce

  1. Login to HD
  2. Create additional addresses for a token and parent
  3. Fund one of the new token addresses without funding the parent (e.g. $1 USDC, 0 MATIC)
  4. Try to withdraw the token using the newly funded address as source
  5. See error

Screenshots
Image

Expected behavior
The numbers in the error are confusing, and do not match the input.
This is most likely an "insufficient gas" error (see additional context).

  • The error message should be humanised, and actionable. e.g. "no gas to pay for transaction, please add some to to continue."

In the withdraw form, source address list contains only funded coins, but for tokens, though they may be funded, the parent might not be. Given the app is tracking balances for each address of each coin, we should be able to detect when a token address has an impoverished parent. When this happens, it should be indicated in the withdraw form, so user has awareness earlier in the flow.

  • If a source token address in the withdraw form has zero balance on its parent address, show a warning and disable the list row. i.e. show address with disabled theming, and warning icon with tooltip on mouseover.

This way the user knows not to select these addresses as source, and armed with this knowledge they can rectify before attempting a doomed transaction, destined to return an error.

Found in
0.9.3 RC eb2b0b8

Additional context
Send max attempt was from third address (2nd empty)

Image

The error persisted when inputting 2 and 1 as the amount manually.
Switching to the first address was successful.

Third MATIC address was empty - which suggests the transaction error was due to insufficient gas.

Metadata

Metadata

Assignees

No one assigned

    Labels

    P1Major issue needs to be fixedUXCosmetic or flow efficiency enhancements for improved User ExperiencebugSomething isn't workingraw-error-messagesWhere raw error is displayed rather than in human words with optional json detail.

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions