AI-generated analysisPublished automatically and not human-verified. Validated context appears in community notes below.
← Watch feed
Low 25 Bitcoin

fix(legacy): allow cross-sign with ETH mainnet

Public commit record

What the developer wrote

Authored by Roman Zeyde

88/100 · Strong
fix(legacy): allow cross-sign with ETH mainnet

Backport #5622 to legacy:

- Previously only non-standard networks (not SLIP-44 60 or 1) could cross-sign
with Ethereum mainnet. Now any network that isn't Ethereum mainnet can use
Ethereum derivation paths
- This is a workaround enabling access to networks like Hyperliquid that
have conflicting chain IDs and can't claim official SLIP-44 registration.

Also, backport legacy testnets' support from #5970.
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
The short version

What changed, and why it matters

This commit loosens address-path validation for older Trezor (legacy) devices when signing Ethereum-style transactions. Previously, only non-standard networks could use Ethereum's mainnet derivation path; now any network except Ethereum mainnet itself can do so, and Ethereum mainnet additionally accepts testnet-style paths. The stated purpose is to support newer networks like Hyperliquid that cannot get an official coin-type registration. The change is a deliberate feature backport, not a covert bug fix, but it does relax a security-relevant boundary that normally prevents cross-network address reuse.

Recommended action

Treat as a deliberate product change rather than an urgent security patch. Review whether the relaxed cross-signing policy matches intended risk acceptance for legacy devices, and ensure users are informed that the same private key/address may now be used across multiple EVM-compatible networks. No immediate patching is indicated by the commit content.

Security signals we found

01

Relaxation of derivation-path validation for Ethereum signing

02

Cross-network address reuse now permitted by design

03

Backport of prior feature work (#5622, #5970) to legacy firmware

04

Changelog frames change as user-facing feature, not security fix

05

No mention of vulnerability, CVE, bug bounty, or researcher attribution

Risk score

Why this scored 25/100

Our methodology →
Potential impact 4/30
Exploitability 3/25
Stealth signal 4/15
Affected reach 5/15
Confidence 6/10
Evidence quality 3/5
Human-validated context

Community notes

Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.

No validated notes yet.

The AI analysis stands alone for now. Submit a note if you can add evidence or important context.