Olaoluwa Osuntokun ebfe7feae8 multi: rename "taproot" channel type to mean production variant ... In this commit, we shuffle the CLI and RPC names so the bare "taproot" identifier refers to the production taproot channel type (final scripts, feature bits 80/81), i.e. the variant new integrations should actually be using. Before this commit, "taproot" on the CLI mapped to the staging bits, and anyone who wanted a real production taproot channel had to spell out "taproot-final" on `lncli openchannel` or `SIMPLE_TAPROOT_FINAL` over RPC. The recommended choice was hidden behind the longer name. On the CLI (`lncli openchannel --channel_type=...`): - "taproot" now selects the production variant (it used to mean staging). - "taproot-staging" is added for the legacy development bits, for peers that haven't moved over yet. - "taproot-final" stays as a deprecated alias for "taproot" so existing scripts don't break. On the RPC (`CommitmentType`): - `TAPROOT = 7` is added as the canonical name for the production type. `SIMPLE_TAPROOT_FINAL = 7` is kept as a deprecated alias via `option allow_alias = true`, so existing clients keep compiling against the same Go constant and the wire value doesn't change. - `SIMPLE_TAPROOT = 5` (staging) is unchanged. - `SIMPLE_TAPROOT_OVERLAY = 6` is unchanged. The taproot-assets daemon hard-codes this distinct enum value, so it's unaffected. Wire compat is preserved end-to-end: only the comments, enum entry order, and the CLI string-to-enum mapping change. The numeric values and the existing generated Go identifiers stay stable. (cherry picked from commit 0aa1d8bdd6)		2026-05-21 19:12:35 +08:00
..
commands	multi: rename "taproot" channel type to mean production variant	2026-05-21 19:12:35 +08:00
lncli	cmd/lncli: move commands and export	2024-08-23 10:57:59 +02:00
lnd	multi: extract wallet initialization	2021-10-08 12:13:15 +02:00