CoalesceUpgrading from Pre-0.1.6
A breaking change to dfund and coopclose you need to handle manually.
Breaking change
As of v0.1.6, dfund records a settlement destination for each member. A cluster funded
with an older version has no destination on file, and coopclose will refuse to run rather
than guess.
What you need to do
Before closing a cluster that was funded on a pre-0.1.6 binary, add a settlement_pkscript
(hex-encoded scriptPubKey) to each peer entry in every member's config file. Every member needs
this fix applied to their own config; there's no way for coopclose to infer it after the
fact, by design. Guessing a payout destination for real funds isn't a decision the software
should make for you.
Why this exists
dfund now lets each member choose their own close payout destination at funding time
(dfund <sats> [fee] <address>, defaulting to their funding wallet). Requiring that destination
to exist on file, rather than falling back to a default at close time, means coopclose never
sends anyone's payout somewhere they didn't explicitly agree to.