- Lets Talk Bitcoin: Let's Talk Bitcoin! #428 Decentralization Philosophy '" Does Crypto Still Need Catalysts? (February 23, 2020)
- Bitcoin Optech: Bitcoin Optech Newsletter #85 (February 19, 2020)
- Lets Talk Bitcoin: Let's Talk Bitcoin! #427 Mainstream Moments and the CompuServe of Crypto (February 16, 2020)
- Bitcoin Optech: Bitcoin Optech Newsletter #84 (February 12, 2020)
We're pleased to announce 0.8.1, named by @vasild (who last release was a new committer!)
Despite the holiday break and Rusty's month off, commit numbers are only down 20%!
Highlights for Users
Highlights for the Network
More details can be found in https://github.com/ElementsProject/lightning/blob/v0.8.1/CHANGELOG.md
Thanks to everyone for their contributions and bug reports; please keep them coming!
Since 0.8.0 we've had 257 commits from 17 different authors, with 5 first-time contributors!
Cheers, Rusty, Lisa, Christian, and ZmnSCPxj.
This marks the first minor release in the
Verifying the Release
In order to verify the release, you'll need to have
Once you have the required PGP keys, you can verify the release (assuming
You should see the following if the verification was successful:
That will verify the signature of the manifest file, which ensures integrity and authenticity of the archive you've downloaded locally containing the binaries. Next, depending on your operating system, you should then re-compute the
Verifying the Release Binaries
Our release binaries are fully reproducible. Third parties are able to verify that the release binaries were produced properly without having to trust the release manager(s). See our reproducible builds guide for how this can be achieved. The release binaries are compiled with
Finally, you can also verify the tag itself with the following command:
Building the Contained Release
Users are able to rebuild the target release themselves without having to fetch any of the dependencies. In order to do so, assuming that
Additionally, it's now possible to use the enclosed
⚡️⚡️⚡️ OK, now to the rest of the release notes! ⚡️⚡️⚡️
A new flag (
We've updated a config on our end to ensure all default values are ALWAYS emitted when using the REST interface. As an example, if the field
Peer to Peer Gossip
We'll now send blank response if a peer sends us a request for channels on a different chain than we advertise.
Batch invoice expiry has been optimized for larger nodes. Before this change, very large nodes (10s of thousands of invoices) may have witnessed very slow start up if they just upgraded to this new version, or had a large number of invoices expire while they were offline.
A bug has been fixed in the wallet where rescans would include more addresses that actually necessary. This would result in slower times to readiness for larger nodes, and also trigger an increased amount of false positives for neutrinos nodes.
Channel State Machine
A number of accounting related fixes have been made to the channel state machine. With these fixes, we'll now more accurately estimate the types of HTLCs that the commitment transaction can carry, properly factoring in things like the added cost of an HTLC, the reserve, and asymmetric dust values across commitments. User affected by this bug might've seen weird retry loops when path finding due to not properly recoding the "available balance" in one's commitment transaction. This bug fixes also preps us for payment splitting, as balance will run lower as we're able to utilize multiple channels to make a single payment.
On-Chain Contract Handling
A new config option has been added to allow mobile clients to give their connected parties a chance to settle/fail an HTLC before we go to chain. This new config option takes the form of
The full list of changes since
Contributors (Alphabetical Order)
Andras Banki-Horvath Eugene Seigel Johan T. Halseth Joost Jager Olaoluwa Osuntokun Oliver Gugger Roei Erez Wilmer Paulino /firstname.lastname@example.org