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

Use BIP-340 synthetic nonces for Schnorr signatures

Public commit record

What the developer wrote

Authored by Salvatore Ingala

78/100 · Adequate
Use BIP-340 synthetic nonces for Schnorr signatures

Instead of only relying on the TRNG, pass the randomness from the TRNG
as aux_rand and use mode CX_RND_PROVIDED, which computes the synthetic
nonce as per BIP-340 recommendations.
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Names security-relevant behavior explicitly
The short version

What changed, and why it matters

This commit changes how the Ledger Bitcoin app creates Schnorr (BIP-340) signatures. Previously it relied entirely on the device's hardware random number generator (TRNG) for the signing nonce. Now it feeds TRNG output as auxiliary randomness into BIP-340's synthetic nonce derivation. This is a defensive hardening measure: even if the TRNG were to fail or produce weak values, the nonce still depends uniquely on the private key and message, reducing the risk that two signatures leak the secret key.

Recommended action

No immediate action required. This is a security-hardening change. Users should ensure their device firmware/app is updated to a version containing this commit. Developers should verify that CX_RND_PROVIDED behavior matches BIP-340 specification on the target SDK/OS version and that cx_get_random_bytes failures are handled correctly (the added error check appears to do this).

Security signals we found

01

Change from TRNG-only nonce generation to BIP-340 synthetic nonce derivation

02

Use of CX_RND_PROVIDED with aux_rand supplied by cx_get_random_bytes

03

Defensive hardening against RNG failure or nonce reuse in Schnorr signatures

04

Nonce now deterministically bound to private key and message via BIP-340 hashing

Risk score

Why this scored 63/100

Our methodology →
Potential impact 18/30
Exploitability 12/25
Stealth signal 10/15
Affected reach 12/15
Confidence 7/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.