Files
giza-kmp/composeApp/src
Kgothatso NgakoandClaude Opus 5.5 b481c14cf9 feat(lightning): every co-signer checks a liquidity purchase before the group signs it (liquidity, Phase 5)
A co-signer keeps a ledger per funding output now (schema 35: IcebergChannelLedger keyed by output,
with its index, the parent it spent and the purchase that let it). A commitment on an output it has
no ledger for is the first commitment on a splice's new one: it must follow the newest output by one
index, rebuild from its context, and open from the parent's ledger at the same number with the same
HTLCs, the group's balance lower by no more than an open buy-liquidity authorisation's fee cap
(CoSignerPolicy.openSplice). The shared input is then held to that authorisation: it spends the pinned
output, makes one new output of the group's key with the LSP's under the cap, buys the amount the
group named, is paid from the channel balance alone, costs what the first commitment took to the
msat and no more than the cap, and the LSP puts in what it is paid for. An authorisation is bound to
the parent of the first splice it let, so however many attempts there are, one confirms.

While two outputs are live a payment settles on both at one commitment number; each ledger records
what its last commitment consumed, and a sibling spends only the difference. Before this the second
commitment was refused as under its floor.

GroupLightningSpliceCoSigningJvmTest, seven four-device tests on regtest and mainnet: a purchase the
group signs and the script interpreter accepts, payments over both live outputs, and each refusal.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-01 12:30:10 +02:00
..