The Lightning wallet now opens on the node's own network, mainnet,
where the group's onchain wallet already is, so the separate testnet3
onchain wallet and its row on the group's screen are gone.
GroupLightningRollout.allows takes mainnet and regtest, nothing else.
This lifts the plan's mainnet gate by decision, ahead of its condition:
an outside review of the Iceberg scheme and the DKG, and a month on
testnet3. The LSP's signing deadline was never measured either.
Meanwhile:
- Every co-signer refuses to sign for a mainnet channel over
MAINNET_CHANNEL_CAP, 1,000,000 sats, so a bigger one never opens; none
grows, since splices are refused.
- The opening screen says the scheme is unreviewed and names the cap.
Running the co-signing suite on mainnet (now a second test class) found a
bug that would have stopped everything there: every key manager was built
with a testnet swap-in tpub, which lightning-kmp rejects on mainnet. That
covers every co-signer and the operator's node. Mainnet now takes the
mainnet LSP's published xpub; nothing derives from it.
The full JVM suite (1,578 tests) and the regtest run pass.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>