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

feat(core/ethereum): support EIP-7702 delegation for `Simple7702Account`

TZ255787a9 View source ↗
Public commit record

What the developer wrote

Authored by Roman Zeyde

100/100 · Strong
feat(core/ethereum): support EIP-7702 delegation for `Simple7702Account`

https://etherscan.io/address/0x4Cd241E8d1510e30b2076397afc7508Ae59C66c9#code
https://ethereum.org/roadmap/pectra/7702/#:~:text=0x4Cd241E8d1510e30b2076397afc7508Ae59C66c9

Also, update "unknown" test case.

[no changelog]
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference
The short version

What changed, and why it matters

This commit adds support for recognizing one more Ethereum smart-contract account type (Simple7702Account) when signing EIP-7702 delegation authorizations on Trezor hardware wallets. It is a small feature addition that updates a known-address lookup table and adds matching test vectors. There is no indication it fixes a security bug or introduces a vulnerability.

Recommended action

No security action required. Treat as a normal feature commit. Reviewers may verify that the added address matches the published Simple7702Account contract and that the existing EIP-7702 nonce/destination validation rules remain unchanged.

Security signals we found

01

No cryptographic, parsing, or authorization logic is changed beyond adding a recognized address mapping.

02

The change is additive: a previously unknown delegate address is now treated as a known implementation.

03

Test fixtures were updated to cover the new recognized delegate and to keep an 'unknown' error case using a non-recognized address.

04

No vendor disclosure, CVE, or researcher attribution is present in the commit.

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 15 AI analysisMessage 57 · Thin
TZ TrezorTrezor firmware BitcoinHardware wallets

chore(core): improvements to English copy

This commit is a routine text cleanup for the Trezor hardware wallet's on-screen English messages. It fixes punctuation, removes unnecessary line breaks, and makes small wording tweaks (for example, changing 'PIN will be required' to 'A PI…

1dbc2c3cby Michal Kazda+22−422 files
No security note in commit
Open full analysis →Source commit ↗
Moderate 59 AI analysisMessage 57 · Thin
TZ TrezorTrezor firmware BitcoinHardware wallets

feat(core): app root packet downgrade protection

This commit adds downgrade protection for a new 'app root packet' system in Trezor firmware. Previously, the code had a TODO note saying downgrade protection needed to be considered. The change makes the device remember the timestamps of p…

Replaces a TODO comment ('!@# TODO: Consider downgrade protection') with concrete timestamp-based anti-downgrade checksAdds per-ring timestamp state to prevent rollback of root-of-trust packetsAdds chain_timestamp field and 90-day drift bound to root packet format
4a9cf168by cepetr+335−3112 files
No security note in commit
Open full analysis →Source commit ↗
Moderate 67 AI analysisMessage 62 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

fix(core/rust): discard low-order keys in THP handshake

This commit fixes a cryptographic edge case in Trezor's THP (Trezor Host Protocol) handshake. It now rejects Curve25519 public keys that are all zeros or that produce an all-zero shared secret. A zero public key can cause the Diffie-Hellma…

Curve25519 zero/low-order public key rejection added to DHZero shared-secret output rejected after scalar multiplicationHandshake state machine now transitions to Failed on initiation-response error
429a283dby M1nd3r+45−74 files
No security note in commit
Open full analysis →Source commit ↗