mirror of
https://github.com/lightningnetwork/lnd.git
synced 2026-08-18 13:07:58 +02:00
The feature-bits-to-lnrpc-enum switch in sendAcceptRequests covered every commitment type the RPC acceptor can be asked about, except the production taproot variant introduced alongside the prod-taproot-chans work. For a channel open using SimpleTaprootChannelsRequiredFinal (with any combination of the scid-alias / zero-conf modifiers), the switch fell through to the default branch, which logs a warning and leaves commitmentType at its zero value -- lnrpc.CommitmentType_UNKNOWN_COMMITMENT_TYPE. External acceptor clients then see UNKNOWN rather than the actual commitment type and either reject or misclassify the channel. Add the four missing cases so the new commitment type is reported to acceptor clients correctly. |
||
|---|---|---|
| .. | ||
| acceptor_test.go | ||
| chainedacceptor.go | ||
| errors.go | ||
| interface.go | ||
| log.go | ||
| merge.go | ||
| merge_test.go | ||
| rpcacceptor.go | ||
| rpcacceptor_test.go | ||
| zeroconfacceptor.go | ||
| zeroconfacceptor_test.go | ||