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

Use official feature bit for `option_simple_taproot` (#3144)

Public commit record

What the developer wrote

Authored by Bastien Teinturier

81/100 · Strong
Use official feature bit for `option_simple_taproot` (#3144)

Use the official feature bit and name for taproot channels and the
corresponding channel types. Activate taproot channels support by
default (without support for announcing such channels yet).

See https://github.com/lightning/bolts/pull/995
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
The short version

What changed, and why it matters

This commit updates the Eclair Lightning node software to use the official protocol feature bit and name for a new kind of Bitcoin payment channel called 'taproot channels.' It turns taproot channel support on by default, but only for private (unannounced) channels, because the public-announcement rules are not finalized. The change is mostly a rename and feature-bit swap from an earlier experimental/staging version, plus adding guards so users cannot accidentally open a public taproot channel. It is a protocol-alignment change, not a fix for an active security bug.

Recommended action

Treat this as a normal feature-alignment commit. Reviewers should verify that the new feature bit and dependency set do not accidentally enable taproot channels in contexts where they are unsupported (e.g., public/announced channels, incompatible peers), and that the new test vectors pass. Node operators upgrading to this release should be aware that taproot channels are now enabled by default for private channels and can disable them via `eclair.features.option_simple_taproot = disabled` if desired.

Security signals we found

01

Protocol feature bit migration from staging/experimental to official BOLT specification

02

Default activation of a new channel type (taproot) that affects transaction construction and key aggregation

03

Added explicit guardrails against opening publicly announced taproot channels

04

New BOLT3 reference test vectors for taproot commitment transactions included

05

No evidence of a vulnerability fix, CVE, or security advisory in the commit materials

Risk score

Why this scored 37/100

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