highperfocused/lnd
1
0
Fork 0
mirror of https://github.com/lightningnetwork/lnd.git synced 2025-03-29 11:11:53 +01:00
Code Issues Packages Projects Releases Wiki Activity
lnd/docs/release-notes/release-notes-0.15.1.md
Olaoluwa Osuntokun 492f8b6999
chainreg: shutdown if backend node doesn't support taproot 
In this commit, we add a check during normal node construction to see if
the backend node supports Taproot. If it doesn't, then we want to
shutdown and force the user to take note.

To check if the node supports Taproot, we'll first try the normal
getblockchaininfo call. If this works, cool, then we can rely on the
value. If it doesn't, then we'll fall back to the getdeploymentinfo call
which was added in a recent version of bitcoind [1]. Newer versions of
bitcoind might also have this call, and the getblockchaininfo call, but
not actually populate the softforks field [2]. In this case, we'll fall
back, and we also account for the case when the getblockchaininfo RPC is
removed all together.

[1]: https://github.com/bitcoin/bitcoin/pull/23508
[2]: https://github.com/bitcoin/bitcoin/pull/25114

Fixes #6773
2022-08-05 17:23:31 -07:00

6.0 KiB
Raw Blame History

Release Notes

Protocol Extensions

Zero-Conf Channel Opens

Build system

Taproot

lnd will now refuse to start if it detects the full node backned does not support Tapoot.

lncli

Database

  • Delete failed payment attempts once payments are settled, unless specified with keep-failed-payment-attempts flag.

  • A new db configuration flag db.prune-revocation is introduced to take the advantage enabled by a recent space optimization. Users can set this flag to true to run an optional db migration during lnd's startup. This flag will prune the old revocation logs and save them using the new format that can save large amount of disk space. For a busy channel with millions of updates, this migration can take quite some time. The benchmark shows it takes roughly 70 seconds to finish a migration with 1 million logs. Of course the actual time taken can vary from machine to machine. Users can run the following benchmark test to get an accurate time it'll take for a channel with 1 millions updates to plan ahead,

    cd ./channeldb/migration30
go test -bench=. -run=TestMigrateRevocationLogMemCap -benchtime=1000000x -timeout=10m -benchmem

Documentation

RPC Server

Bug Fixes

Code Health

Code cleanup, refactor, typo fixes

Tooling and documentation

  • An .editorconfig file was added to autoconfigure most text editors to respect the 80 character line length and to use 8 spaces as the tab size. Rules for Visual Studio Code were also added. And finally, the code formatting rules were extracted into their own document.

Contributors (Alphabetical Order)

  • Carsten Otto
  • Elle Mouton
  • ErikEk
  • Eugene Siegel
  • Matt Morehouse
  • Slyghtning
  • Oliver Gugger
  • Olaoluwa Osuntokun
  • Priyansh Rastogi
  • Tommy Volk
  • Yong Yu