You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Drop RevokedOutput::is_counterparty_balance_on_anchors
When we added anchors support we declined to aggregate claims
across different types of outputs for anchor channels, requiring
that we track whether a `RevokedOutput` claim came from an anchor
channel or not. This was only ever used to decide whether the claim
was aggregable or not.
In 0fe90c6 we started aggregating
by determining whether a claim is pinnable or not, rather than the
much-too-coarse aggregable flag, leaving
`is_counterparty_balance_on_anchors` unused.
Here we remove it entirely (as it would become ambiguous with
zero-commitment-fee anchor channels).
We always write `Some(())`, marking the claim as an anchor claim
and resulting in LDK prior to 0.1 refusing to aggregate the claim
(which is the more conservative stance). This breaks downgrade to
LDK 0.0.115 and earlier.
(15, channel_parameters,(option:ReadableArgs,None)),// Added in 0.2.
191
191
});
192
192
@@ -1821,16 +1821,13 @@ mod tests {
1821
1821
1822
1822
#[rustfmt::skip]
1823
1823
macro_rules! dumb_revk_output {
1824
-
($is_counterparty_balance_on_anchors: expr) => {
1824
+
() => {
1825
1825
{
1826
1826
let secp_ctx = Secp256k1::new();
1827
1827
let dumb_scalar = SecretKey::from_slice(&<Vec<u8>>::from_hex("0101010101010101010101010101010101010101010101010101010101010101").unwrap()[..]).unwrap();
1828
1828
let dumb_point = PublicKey::from_secret_key(&secp_ctx,&dumb_scalar);
1829
1829
let channel_parameters = ChannelTransactionParameters::test_dummy(0);
0 commit comments