release(7.15.0): RC19 audited firmware candidate - #452
Open
BitHighlander wants to merge 12 commits into
Open
Conversation
Add registry-backed clear signing, EIP-712 and EIP-7702 handling, ERC-20 policy checks, and regression coverage. Review lineage: keepkey#444.
Add the protocol flows, confirmations, serialization, and tests required for the 7.15 chain expansion. Review lineage: keepkey#445.
Add deterministic entropy export, BIP-39 recovery validation, fault-injection resistance, and focused tests. Review lineage: keepkey#446.
Add policy and display handling for TRON, Solana v0, TON, MayaChain, THORChain, and Tendermint-family requests. Review lineage: keepkey#447.
Introduce the 7.15 build matrix, seed-lock behavior, and version wiring. Review lineage: keepkey#448.
Integrate the full 7.15 feature set across firmware, emulator, protocol pins, storage migrations, and test infrastructure. Review lineage: #311.
Bind THORChain router policy per chain and apply the corresponding protocol, parsing, and test corrections. Review lineage: #313.
Report paced device progress during long Orchard signing operations and cover the display behavior. Review lineage: #314.
Apply the RC security review across display binding, parsers, persistent signer identities, signing policy, RNG handling, and regression tests. Review lineage: #317.
Make release-candidate tags first-class, keep artifacts draft-only, and fetch only the submodules required by each build. Review lineage: #318.
Finalize constant-time RedPallas signing, ARM and host leakage gates, emulator CSPRNG handling, immutable build inputs, signing progress, canonical crypto pinning, and the RC19 validation matrix. This tree is identical to v7.15.0-rc19.
13 tasks
BitHighlander
changed the title
BitHighlander
force-pushed
the
release/7.15.0-rc19-upstream
branch
from
July 30, 2026 20:43
40fa3b1 to
27e036d
Compare
BitHighlander
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This is the consolidated KeepKey firmware 7.15.0 candidate represented by the signed annotated tag v7.15.0-rc19.
Review shape
This single PR supersedes the closed #444–#448 stack and incorporates the later fork review, including BitHighlander#319 and #320. The history has been rebuilt as 12 ordered review units; snapshot commits and the temporary add/remove vendoring churn are gone.
The final source tree is identical to the RC19 reference tree f06cd8e87c71d96ad0c50f990e8cb5c7669f0772. The diff is 168 files, +21,569/−1,888; 7,273 added lines are test code. trezor-crypto is not vendored into this repository—it is pinned to the reviewed merge from keepkey/trezor-firmware#4 (62230ee620fa9ea2bdd2c8067be7fde3f9362248).
Validation
Merge gates