Feed for tag: c-lightning
Notable Commits For Thu, Nov 15
Notable issues and merges on Bitcoin Core, LND, c-lightning and libsecp256k1 Originally published by BitcoinOptech on newsletter #21 Bitcoin Core #14410 adds an ischange field to the getaddressinfo RPC indicating whether the wallet used the address in a change output. Bitcoin Core #14060 makes configurable the maximum number of messages the ZeroMQ (ZMQ) interface will queue for a client. The default High-Water Mark (HWM) allows up to 1,000 messages to be queued before some messages are dropped.
Commit Activity For Thu, Nov 08
Notable issues and merges on Bitcoin Core, LND, c-lightning and libsecp256k1 Originally published by BitcoinOptech on newsletter #20 Bitcoin Core #14454 Adds support to the importmulti RPC for segwit addresses and scripts (P2WPKH, P2WSH, and P2SH-wrapped segwit). A new witnessscript parameter fulfills the same role for segwit as the redeemscript parameter for P2SH. Also a solvable parameter is added to the getaddressinfo RPC to let the user know whether the wallet knows the redeemScript or witnessScript for a P2SH or P2WSH address, i.
Commit Activity For Thu, Nov 01
Notable issues and merges on Bitcoin Core, LND, c-lightning and libsecp256k1 Originally published by BitcoinOptech on newsletter #19 Bitcoin Core #14451 Allows optionally building Bitcoin-Qt without support for the BIP70 payment protocol and adds a deprecation warning indicating the default support may be removed in a future release. The CEO of BitPay, which is the largest user of BIP70 (but which wants to use a different version of the protocol), indicated that they supported Bitcoin Core removing BIP70.
Commit Activity For Thu, Oct 25
Notable issues and merges on Bitcoin Core, LND, c-lightning and libsecp256k1 Originally published by BitcoinOptech on newsletter #18 Bitcoin Core #14291: For use with Bitcoin Core’s multiwallet mode, a new listwalletdir RPC can list all available wallets in the wallet directory. Bitcoin Core #14424: Fixes a likely regression in 0.17.0 for watch-only wallets that require users to import their public keys for multisig scripts (rather than just importing the script) in order for Bitcoin Core to attempt spending the script using RPCs such as fundrawtransaction with theincludeWatching flag.
Commit Activity For Thu, Oct 18
Notable issues and merges on Bitcoin Core, LND and c-lightning. Originally published by BitcoinOptech on newsletter #17 LND #1970: The AbandonChannel RPC method (only available in the developer debug mode) now provides additional information when users tell their node to abandon a payment channel (a method that can cause monetary loss if used carelessly). The additional information is enough to allow either restarting an open payment channel later or to prove that the program had enough information to make additional commitments to a now-closed payment channel.
Commit Activity For Thu, Oct 4
Notable issues and merges on Bitcoin Core, LND and c-lightning. Originally published by BitcoinOptech LND #1987: The NewWitnessAddress RPC has been removed and the NewAddress RPC now only supports generating addresses for P2SH-wrapped P2WKH and native P2WPKH. C-Lightning #1982: The invoice RPC now implements RouteBoost by including a BOLT11 r parameter in the invoice that provides routing information to the payer for an already-open channel that has the capacity to support paying the invoice.
Commit Activity For Thursday, Sep 27

Notable issues and merges on Bitcoin Core, LND and c-lightning.

Originall published by BitcoinOptech

Bitcoin Core #14305

After the discovery of a few cases where Python-based tests were passing incorrectly as a result of using misnamed variables, a variable name whitelist was implemented using Python 3’s __slots__ feature for classes.

Bitcoin Core #13152

When connected to the peer-to-peer network, nodes share the IP addresses of other nodes they’ve heard about and these addresses are stored in a database that Bitcoin Core queries when it wants to open a new connection. This PR adds a new RPC command,getnodeaddresses, that returns one or more of these addresses. This can be useful in conjunction with tools like bitcoin-submittx.

LND #1738

the logic for validating channel updates has been moved to the routing package so that it’s available both in routing (to handle failed payment sessions) and the gossiper (where it was handled before). This fixes issue #1707 (and implements a test case for it) that may have allowed a node to trick one of its peers into believing a different peer had a routing failure, thus possibly redirecting traffic to the malicious node.

C-Lightning

  • C-Lightning now provides a gossipwith tool that allows you to receive gossip from a node independently of lightningd or even to send the remote node a message. This tool is used for additional testing of lightningd’s gossip component. C-Lightning now provides a gossipwith tool that allows you to receive gossip from a node independently of lightningd or even to send the remote node a message. This tool is used for additional testing of lightningd’s gossip component.

  • C-Lightning now complies with updates to BOLT7 by splitting the previous flags field for the listchannels RPC into two new fields: message_flags and channel_flags. Also code comments and references to BOLT2 and BOLT11 have been updated.

  • C-Lightning has significantly expanded the in-code documentation of its secrets module. The documentation is remarkably good (and, at times, quite humorous). See hsmd.c. The code comments even document other code comments:

/*~ You'll find FIXMEs like this scattered through the code.
* Sometimes they suggest simple improvements which someone like
* yourself should go ahead an implement. Sometimes they're deceptive
* quagmires which will cause you nothing but grief. You decide!

*/ /* FIXME: We should cache these.*/
get_channel_seed(&c->id, c->dbid, &channel_seed);
derive_funding_key(&channel_seed, &funding_pubkey, &funding_privkey);