Walkthrough

This pull request updates the ledger integration by changing the ledger derivation assignment in the keyring options and restructuring the package organization. New account management functionalities are added, including Ethereum account structures, HD wallet derivation, URL parsing, and dedicated error types with tests. Package names and import paths have been revised (from keyring to ledger), and comprehensive USB wallet support is introduced with drivers, hub, and wallet implementations to manage Ledger/Trezor hardware wallets.

Changes

Sequence Diagram(s)

sequenceDiagram
    participant Hub as USB Wallet Hub
    participant Driver as Ledger Driver
    participant Device as USB Device
    participant App as Wallet App

    Hub->>Device: Scan for connected hardware wallets
    Device-->>Hub: Return device list
    Hub->>Driver: Initialize connection with device
    Driver->>Device: Open connection
    Device-->>Driver: Connection established
    Driver->>Driver: Retrieve status & version
    Driver-->>Hub: Return wallet info
    Hub->>App: Notify wallet event subscription update

sequenceDiagram
    participant App as Wallet App
    participant Wallet as USB Wallet
    participant Driver as Ledger Driver
    participant Device as USB Device

    App->>Wallet: Request to sign transaction
    Wallet->>Driver: Call SignTx with derivation path and tx
    Driver->>Device: Send APDU command for transaction signing
    Device-->>Driver: Return signature
    Driver->>Wallet: Return signed transaction
    Wallet-->>App: Deliver signed transaction

Possibly related PRs

• feat: ethereum ledger integration #365: Adjusts the ledger derivation assignment and introduces the new LedgerDerivationFn, directly affecting ledger operations.

Suggested reviewers

• sh-cha

Poem

Hoppin’ through the code, I twirl and spin,
Ledger paths and error hops, a joyous din.
USB buds and hardware thrills so keen,
Accounts and keys in every scene.
With carrot beats and ASCII gleams,
A rabbit’s code celebrates bright new dreams! 🐰🥕

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

• 📝 Generate Docstrings

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

• ❄ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.