chore(deps): bump @ledgerhq/hw-app-eth from 6.5.0 to 6.22.3

[dependabot]

Bumps @ledgerhq/hw-app-eth from 6.5.0 to 6.22.3.

Release notes

Sourced from @​ledgerhq/hw-app-eth's releases.

6.22.x

Rework hw-app-eth to split out "ledger services" from the app logic LedgerHQ/ledgerjs#747

eth.signTransaction(path, txHex)

becomes deprecated in favor of

eth.signTransaction(path, txHex, resolution)

where resolution is an object with following shape:

{
  erc20Tokens: Array<string>;
  nfts: Array<string>;
  externalPlugin: Array<{ payload: string; signature: string }>;
  plugin: Array<string>;
}

This object contains all the hex serialized data the device may need to clear sign information on device screen.

Hopefully we also provide a default "service" to resolve this data, example:

import ledgerService from "@ledgerhq/hw-app-eth/lib/services/ledger"
async function main() {
  ...
  const resolution = await ledgerService.resolveTransaction(txHex, loadConfig, resolutionConfig)
    .catch(() => null); // <-- up to you if you want a fallback to blind sign. (which was previous behavior)
   const result = eth.signTransaction("44'/60'/0'/0/0", txHex, resolution);
}

This allows us to decouple the transaction resolution from the device signature logic itself in order for you to have better control and for more usecases

• an alternative service (rather than Ledger's) could be used.
• we plan to make even more things dynamic, typically the way we load and resolve ERC20 and plugins are too monolithic. This rework pave the path to allow this even more easily.
• you may want to load the resolve data way ahead in your "validation process" and typically inform the user if an error occurs before it reach the device phase.
• you may want a finer control weither you allow blind sign or not. Typically, you may or may not use .catch(() => null) in the snippet above

loadConfig

loadConfig is a configuration file that allows to configure what endpoints are used for the resolution mecanism.

NFT resolution is not yet active in this current version but will be soon. That said, you need to explicitly request it in resolutionConfig.

... (truncated)

Commits

• 753cf3f v6.22.3
• bf35c3a fix: cryptoassets exchange erc20 & coins import names (#752)
• b300cfc have hw-app-eth specific error and add one for NFT clear signing (#756)
• b7c891f v6.22.2
• 520944e LL-8906 implement better resilience of hw-app-eth on resolution service (#755)
• d74633a Fixes blind signing fallback on erc20 tx if NFT mode used (#753)
• 6a77967 v6.22.1
• d677eba Fix broken link for Cosmos
• d5ef6b6 Fix broken link for Cosmos
• df473b6 v6.22.0
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Superseded by #29.