a couple selected release notes:
* transactions with 65+ bytes in non-witness data are now acceptable by
mempool and relay policies.
* improvements to parallel compact block downloads
* avoid serving stale fee estimates
new features which nakamochi might find useful in the future:
* a new shutdownnotify option, a command to exec synchronously before
bitcoind initiates its shutdown sequence
* a new /rest/deploymentinfo endpoint which reports consensus changes
all details:
- https://bitcoincore.org/en/releases/25.0/
- https://bitcoincore.org/en/releases/25.1/
ndg release v0.6.0 introduced a mechanism in which LND TLS cert is
regenerated if ndg's HTTP client refuses to initialize TLS certs bundle
in https://git.qcode.ch/nakamochi/ndg/commit/b57ebacd
in most cases, it is due to outdated cert's notAfter.
however, because raspberry pi cannot preserve current system time,
it starts from year 1969 and the TLS client init fails.
the latter leads to ndg forcing LND to regenerate the certs to no avail
because the system time isn't syncronized yet.
simple solution: wait to start LND service until the system clock is in
sync.
the release adds UI for switch sysupdates channel.
there are two channels at the moment: edge (dev branch)
and stable (master branch).
see all release details at
https://git.qcode.ch/nakamochi/ndg/releases/tag/v0.5.0
this "splits" the output into sections so it's easier to attribute what
is curretly run. useful for debugging failures. in the end, the script
reports total CPU time it took to run the update.
a bugfix release. one notable change is the default CLTV delay increase
from 40 to 80 blocks, or equivalently from ~7 hours to ~13 hours.
this is a more conservative default time lock which can help to avoid
unnecessary force closures due to persistent mempool backlog or node downtime.
more details at:
https://github.com/lightningnetwork/lnd/blob/master/docs/release-notes/release-notes-0.16.1.md
no breaking changes. release highlights:
- prioritize sending out local gossip updates to all connected peers
- potentially missed channel updates bugfix
- rebroadcast unconfirmed transactions with each passing block the transaction
hasn't been confirmed
- channel updates without the maxHTLC message flag set are recognized as
invalid and are not relayed
- new pathfinding algorithms; leaving nakamochi with the default for now
- watchtower improvements; we don't run a watchtower at the moment
- cli now recognizes base_fee_msat and fee_rate_ppm flags for openchannel command
read more at https://lightning.engineering/posts/2023-03-29-lnd-0.16-launch/
and https://github.com/lightningnetwork/lnd/blob/master/docs/release-notes/release-notes-0.16.0.md
the tor service provides hidden services for bitcoin and lightning.
in the latter case, both P2P and RPC/REST.
the commit also starts a new directory files. the idea is to mirror
config files layout in the target system.
the apply.sh script should assume current directory is arbitrary after
executing each step: base, bitcoin, lnd and so on.
this commit simply changes current dir to the repo root before executing
every step.
the first run of update.sh sets up a cron job to run itself
periodically. the update script takes one position argument, the git
branch to pull changes from, which is also known as "sysupdates channel"
- master for stable, dev for testing.
the sysupdates channel was lost in the cron job setup, always defaulting
to master (stable). this commit preserves the original arg value given
to update.sh during the initial run.
when testing upcoming changes on a live node, it is desirable to turn
off automatic updates simply by removing the x file permissions bit.
this commit makes sure the x bit is set only for newly created file.
extract from upstream release notes:
- bug has been fixed where the responder of a zero-conf channel could forget
about the channel after a hard-coded 2016 blocks
- bug where LND wouldn't send a ChannelUpdate during a channel open has been fixed
- bug has been fixed that caused fee estimation to be incorrect for taproot
inputs when using the SendOutputs call
- bug has been fixed that could cause lnd to underpay for co-op close transaction
when or both of the outputs used a P2TR address
all details are here:
https://github.com/lightningnetwork/lnd/releases/tag/v0.15.3-beta
