server: don't mention aux stuff in error [skip ci]
What changed, and why it matters
This commit only changes the wording of an error message. It does not alter any logic, permissions, or security behavior. The new message more accurately tells standalone lnd users that taproot overlay channels are not supported in their build, rather than sounding like a forgotten configuration option.
No security action needed. This is a cosmetic/documentation-style wording change.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff modifies a single error string in server.go. The guard condition remains identical: if ProtocolOptions.TaprootOverlayChans is enabled and no AuxFundingController is provided, newServer still returns an error. Only the fmt.Errorf text is updated from ‘taproot overlay flag set, but not aux controllers’ to ‘taproot overlay flag set, but overlay channels are not supported in a standalone lnd build’. No code paths, validation, or security controls changed.
Changed components
server.go error message textInspect captured patch +3 / −2
diff --git a/server.go b/server.go
index d79cc35..f0a618a 100644
--- a/server.go
+++ b/server.go
@@ -634,8 +634,9 @@ func newServer(ctx context.Context, cfg *Config, listenAddrs []net.Addr,
if cfg.ProtocolOptions.TaprootOverlayChans &&
implCfg.AuxFundingController.IsNone() {
- return nil, fmt.Errorf("taproot overlay flag set, but not " +
- "aux controllers")
+ return nil, fmt.Errorf("taproot overlay flag set, but " +
+ "overlay channels are not supported " +
+ "in a standalone lnd build")
}
//nolint:ll
Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.