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

btc: use constant-time ECDH for silent payments

Public commit record

What the developer wrote

Authored by benma's agent

68/100 · Adequate
btc: use constant-time ECDH for silent payments

Use libsecp256k1's constant-time ECDH to multiply the scan public key
by the sum of the input private keys. Reuse this DLEQ point to derive
the same BIP352 shared point by multiplying it by the input hash. The
host receives the DLEQ point with the proof and can compute the hash,
so both operands of the remaining variable-time tweak are public to it.
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
The short version

What changed, and why it matters

This commit hardens the BitBox02 hardware wallet's silent-payments feature against a side-channel attack. Previously, the device multiplied a secret key with a public key using a routine whose execution time could leak information about the secret. The change uses libsecp256k1's constant-time ECDH for the secret multiplication, and only performs a variable-time multiplication on a value that is already public to the connected computer. This reduces the risk that a local attacker or malware could recover private key material by timing how long the device takes.

Recommended action

No immediate user action required; this is a defensive hardening patch. Users should ensure firmware containing this commit is installed if they use silent payments. Developers should verify that `shared_secret_point` is indeed constant-time in the linked libsecp256k1 version and that no other secret-key multiplications remain on variable-time paths.

Security signals we found

01

Constant-time cryptographic operation introduced to replace variable-time secret-key multiplication

02

Variable-time scalar multiplication retained only on public operands

03

Silent payments private input key material (a_sum) no longer used in variable-time path

04

libsecp256k1 ECDH module enabled in build configuration

Risk score

Why this scored 59/100

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