Improving the error message when exceeding the ledger's withdrawal capacity

[leobragaz]

After delegating to more than 20 validators, I tried to withdraw the rewards from all of them and the extension showed me a "connection refused from x.forbole.com" that, if inspected, was caused by a 520 server error.

I think it should be more explicit telling users why they're receiving that error.

[kwunyeung]

Does this only happen with Ledger? If so, should we limit the selection to be Max 20 if we know the account is from Ledger?

[RiccardoM]

@kwunyeung I confirm this happens when you delegate to more than the maximum amount of validators that the Ledger allows to withdraw with a single message, which is:

• 3 validators if you are using a Ledger Nano S
• 20 validators if you are using a Ledger Nano X

After reducing the delegations to from 21 to 20 validators, it works properly.

I think that to limit the selection you would also need to know the Ledger device they are using (since the limits are different as written inside Forbole X as well).

[kwunyeung]

There is a device id on Ledger. It's being returned when the device is being connected. We should be able to identify it's an S or X from it.

https://github.com/LedgerHQ/ledgerjs/blob/90360f1b00a11af4e64a7fc9d980a153ee6f092a/packages/react-native-hid/src/index.ts#L28

[leobragaz]

@kwunyeung Yes limiting the selection is a good choice in this case

[calvinkei]

i found that the issue is not related to ledger withdraw limit, since it crashes on extension load instead of during tx signing. the issue is i am using the JSON string of tx data as query params in a web url, which exceeds the string length limit when you withdraw from > 20 validators. i will fix it by compressing the JSON string, otherwise the same will happen when you withdraw from >20 validators with recovery phrase