CommitWatch RSS
AI-generated analysisPublished automatically and not human-verified. Validated context appears in community notes below.
← Watch feed
Informational 20 Bitcoin

chore(ethereum): upgrading from Holesky to Hoodi

TZ58c0e94b View source ↗
Public commit record

What the developer wrote

Authored by Jiří Čermák

80/100 · Strong
chore(ethereum): upgrading from Holesky to Hoodi

- Ethereum testnet upgrade. Updated literal references, and fixtures with the new name and chain ID.
- SLIP44 base indices updated from 1 to 60.
- Small change in eth/keychain required to work with older 1 index based
testnet addresses.
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context
The short version

What changed, and why it matters

This commit replaces the deprecated Ethereum Holesky testnet with the new Hoodi testnet across Trezor firmware. It updates network names, chain IDs, SLIP44 derivation indices, staking contract address labels, and test fixtures. There is no indication of a security vulnerability being fixed; it is a routine network-maintenance change.

Recommended action

No security action required. Treat as normal maintenance; verify Hoodi network parameters and ensure downstream apps/wallets are updated to use the new chain_id 560048 and slip44 60 derivation paths.

Security signals we found

01

Routine testnet deprecation/replacement

02

SLIP44 index change from 1 to 60 for testnets

03

Legacy path compatibility added for old testnet derivation indices

04

Staking contract addresses relabeled but byte values unchanged

Risk score

Why this scored 20/100

Our methodology →
Potential impact 2/30
Exploitability 1/25
Stealth signal 1/15
Affected reach 3/15
Confidence 9/10
Evidence quality 4/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.

More from Trezor firmware

Related watches

Informational 18 AI analysisMessage 57 · Thin
TZ TrezorTrezor firmware BitcoinHardware wallets

chore(core): remove sha1 from regular FW

This commit removes the SHA-1 hashing function from the regular Trezor firmware. SHA-1 is an old, weak hash algorithm that is no longer considered secure for sensitive uses. The change deletes the code that exposes SHA-1 to apps running on…

Removal of a deprecated cryptographic primitive (SHA-1) from the firmware API surfaceReduction of attack surface and prevention of future misuse of a collision-vulnerable hashNo direct vulnerability patch or memory-safety bug is present in the diff
16d15774by M1nd3r+0−2006 files
No security note in commit
Open full analysis →Source commit ↗
Low 27 AI analysisMessage 62 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

refactor(crypto): pass static public key to `noise_xxpsk3_*_init()`

This commit changes how a cryptographic library sets up secure connections. Previously, the code automatically calculated the public key from the private key. Now, the caller must provide the public key directly. This is a code-quality ref…

Cryptographic key handling changed: public key is now supplied rather than derivedPotential reduction of key-mismatch risk if caller provides correct public keyNew null-pointer check added for static_public_key
1b3128a4by Ondřej Vejpustek+20−92 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 57 · Thin
TZ TrezorTrezor firmware BitcoinHardware wallets

refactor(crypto): change order of parameters

This commit simply reorders the arguments of an internal function called dh() and updates every place that calls it. The actual math and security behavior are unchanged; it is a code cleanup with no security effect.

33a119eeby Ondřej Vejpustek+15−151 file
No security note in commit
Open full analysis →Source commit ↗