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

feat(core/stellar): show trusted SEP-41 token contracts as token operations.

Public commit record

What the developer wrote

Authored by Jakub Janků

100/100 · Strong
feat(core/stellar): show trusted SEP-41 token contracts as token operations.

The token UI was reachable only for a Stellar Asset Contract, whose asset the
host can point out and the device can verify by re-deriving the contract
address. A token that is only a SEP-41 contract cannot be identified that way,
so its transfers showed up as an opaque contract call.

Add a hardcoded, network-bound list of vetted contracts, starting with SolvBTC
and xSolvBTC. Symbol and precision are what the contracts report, but both are
upgradeable, so this is a trust decision rather than a proof. A Stellar Asset
Contract still takes precedence, since its hint proves the contract's identity.

Fixes: https://github.com/trezor/trezor-firmware/issues/7314

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
✓ 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 improves how the Trezor hardware wallet displays certain Stellar token transactions on its screen. Previously, some token transfers looked like confusing generic contract calls. Now, for two specific vetted tokens (SolvBTC and xSolvBTC), the device will show a friendly token transfer screen. This is a user-interface improvement based on a hardcoded trust list, not a fix for a code execution or theft vulnerability. The change does not alter what transactions the device will or won't sign.

Recommended action

Review as a normal feature enhancement. Verify that the two hardcoded contract addresses and decimals match the intended SolvBTC/xSolvBTC deployments on Stellar public network, and that the precedence logic (SAC match before PUBLIC_TOKENS fallback) is correctly implemented. No urgent security patch is indicated by the diff alone.

Security signals we found

01

Hardcoded trust list of token contracts introduced

02

Host-supplied asset hint no longer the only path to token UI; fallback table is network-bound

03

SAC cryptographic proof retained as higher precedence, preventing host hint relabeling of built-in tokens

04

Symbol and decimals are taken on trust because SEP-41 contracts can be upgraded

05

No signature validation, authorization, or parsing logic changed beyond token metadata resolution

Risk score

Why this scored 30/100

Our methodology →
Potential impact 4/30
Exploitability 3/25
Stealth signal 5/15
Affected reach 6/15
Confidence 8/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.