alloy-rs/alloy

[Feature] More well-considered `Wallet` behavior

Open

#638 opened on Apr 26, 2024

View on GitHubContributor guide
 (2 comments) (0 reactions) (0 assignees)Rust (631 forks)github user discovery
c-networkenhancementhelp wanted

Repository metrics

Stars
 (1,280 stars)
PR merge metrics
 (PR metrics pending)

Description

Component

signers

Describe the feature you would like

We currently only handle individual signers, each of which has a single address. This doesn't deal well with bip32 xprivs and related signers like ledger and trezor.

EthereumSigner and the NetworkSigner trait need to be updated to allow derivation path enrollment or something else. I don't have a good design here yet but it's stewing

Additional context

No response

Contributor guide

Research direction
Investigate how to integrate hierarchical deterministic wallets (BIP32) and hardware signers (Ledger, Trezor) into the existing EthereumSigner and NetworkSigner traits.
Tech stack
rust
Domain
blockchain
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
Rust
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30