ledger-signing

Secure Ethereum transaction signing with a Ledger requires guiding the device through unlock, review, and approval steps over a direct USB/HID connection. This Skill orchestrates that flow, validating inputs and rendering signing guidance for safe user review.

Clear signing displays transaction details on the Ledger device for user verification, while blind signing signs hashes without full payload visibility. This Skill orchestrates clear signing flows with a blind-signing fallback when full clarity is not possible.

Yes, EIP-712 typed data can be signed by providing the domain_separator_hex and hash_struct_message_hex inputs. The Skill accepts these hashes alongside the payload_kind and derivation_path to produce signed outputs from the connected Ledger.

Yes, a local Ledger USB/HID runtime with ledgerblue and hidapi is required to execute direct signing. These dependencies enable the local runtime to communicate with a connected Ledger device over USB.

The signing flow enforces a dry_run safety refusal to prevent unsafe automation during testing. You must explicitly set dry_run to false and use the execute flag to trigger the actual USB/HID signing runtime.

The signing guidance supports transaction, message, and typed_data payload types. It validates payload_hex inputs with strict sizes and orchestrates the appropriate signing flow for each Ethereum payload kind.