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

chore: refactor ton add add more tests

Public commit record

What the developer wrote

Authored by soralit

67/100 · Adequate
chore: refactor ton add add more tests
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Mentions testing or verification! No meaningful explanatory body
The short version

What changed, and why it matters

This commit is a routine code-quality and test-coverage update for the TON (The Open Network) wallet code in the Keystone 3 firmware. It replaces several Rust `.unwrap()` calls with proper error handling, adds many unit tests, and improves how sensitive seed data is cleared from memory after signing. There is no direct evidence in the commit that these changes fix an active exploit; they look like defensive hardening and cleanup.

Recommended action

Treat as a routine hardening/refactoring commit. Reviewers should verify that the new error paths in `structs.rs` propagate correctly to the UI, that `zeroize` is applied consistently to all copies of the seed, and that the added tests pass. No urgent security response is indicated by the diff alone.

Security signals we found

01

Replaced panicking `.unwrap()` calls in `get_jetton_amount_text` with explicit `Result` error handling

02

Added `zeroize()` of the normalized mnemonic word vector after seed derivation

03

Added `seed.zeroize()` in Rust C signing entry points after secret key derivation

04

Switched C signing code to use `GetCurrentAccountSeedLen()` and check `GetAccountSeed` return value

05

Added `memset_s` clearing of the local seed buffer in C after TON transaction and proof signing

06

Removed `#![feature(error_in_core)]` nightly Rust feature

Risk score

Why this scored 33/100

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