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

feat(core): support dev-signed definitions on non-production builds

Public commit record

What the developer wrote

Authored by Roman Zeyde

85/100 · Strong
feat(core): support dev-signed definitions on non-production builds

Similar to how dev-signed translations are supported via the `dev_keys` feature.

Definitions public keys are moved to `core/embed/rust/src/definitions/constants.rs`.

[no changelog]
✓ Specific, 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 moves the public keys used to verify coin/token definitions from Python code into a new Rust module. It also makes development-signed definitions accepted on non-production builds, similar to an existing feature for translations. The change is a build/configuration refactor rather than a fix for an active security flaw. Production firmware still requires production signatures; dev keys are only accepted when the `dev_keys` feature is enabled, which is intended for development builds.

Recommended action

No immediate action required. Treat as a normal feature/refactor commit. Reviewers should confirm that production release builds do not enable the `dev_keys` feature, and that the new Rust `verify()` function preserves the original threshold and public-key semantics. Continue routine monitoring for any follow-up commits that adjust gating or key material.

Security signals we found

01

Moved signature verification of external token/coin definitions from Python to Rust

02

Added development-key fallback gated by `#[cfg(feature = "dev_keys")]`

03

Removed `__debug__`-gated dev-key acceptance from Python; replaced with feature-gated Rust fallback

04

Production public keys remain unchanged and are still required on production builds

Risk score

Why this scored 19/100

Our methodology →
Potential impact 2/30
Exploitability 2/25
Stealth signal 1/15
Affected reach 2/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.