search

kuutamolabs / kld

A Lightning Service Provider router by kuutamo
Apache License 2.0
26 stars 3 forks source link

build(deps): bump lightning-net-tokio from 0.0.121 to 0.0.123 #1063

Closed dependabot[bot] closed 4 months ago

dependabot[bot] commented 4 months ago

Bumps lightning-net-tokio from 0.0.121 to 0.0.123.

Release notes

Sourced from lightning-net-tokio's releases.

v0.0.123 - May 08, 2024 - "BOLT12 Dust Sweeping"

API Updates

  • To reduce risk of force-closures and improve HTLC reliability the default dust exposure limit has been increased to MaxDustHTLCExposure::FeeRateMultiplier(10_000). Users with existing channels might want to consider using ChannelManager::update_channel_config to apply the new default (#3045).
  • ChainMonitor::archive_fully_resolved_channel_monitors is now provided to remove from memory ChannelMonitors that have been fully resolved on-chain and are now not needed. It uses the new Persist::archive_persisted_channel to inform the storage layer that such a monitor should be archived (#2964).
  • An OutputSweeper is now provided which will automatically sweep SpendableOutputDescriptors, retrying until the sweep confirms (#2825).
  • After initiating an outbound channel, a peer disconnection no longer results in immediate channel closure. Rather, if the peer is reconnected before the channel times out LDK will automatically retry opening it (#2725).
  • PaymentPurpose now has separate variants for BOLT12 payments, which include fields from the invoice_request as well as the OfferId (#2970).
  • ChannelDetails now includes a list of in-flight HTLCs (#2442).
  • Event::PaymentForwarded now includes skimmed_fee_msat (#2858).
  • The hashbrown dependency has been upgraded and the use of ahash as the no-std hash table hash function has been removed. As a consequence, LDK's Hash{Map,Set}s no longer feature several constructors when LDK is built with no-std; see the util::hash_tables module instead. On platforms that getrandom supports, setting the possiblyrandom/getrandom feature flag will ensure hash tables are resistant to HashDoS attacks, though the possiblyrandom crate should detect most common platforms (#2810, #2891).
  • ChannelMonitor-originated requests to the ChannelSigner can now fail and be retried using ChannelMonitor::signer_unblocked (#2816).
  • SpendableOutputDescriptor::to_psbt_input now includes the witness_script where available as well as new proprietary data which can be used to re-derive some spending keys from the base key (#2761, #3004).
  • OutPoint::to_channel_id has been removed in favor of ChannelId::v1_from_funding_outpoint in preparation for v2 channels with a different ChannelId derivation scheme (#2797).
  • PeerManager::get_peer_node_ids has been replaced with list_peers and peer_by_node_id, which provide more details (#2905).
  • Bolt11Invoice::get_payee_pub_key is now provided (#2909).
  • Default[Message]Router now take an entropy_source argument (#2847).
  • ClosureReason::HTLCsTimedOut has been separated out from ClosureReason::HolderForceClosed as it is the most common case (#2887).
  • ClosureReason::CooperativeClosure is now split into {Counterparty,Locally}Initiated variants (#2863).
  • Event::ChannelPending::channel_type is now provided (#2872).
  • PaymentForwarded::{prev,next}_user_channel_id are now provided (#2924).
  • Channel init messages have been refactored towards V2 channels (#2871).
  • BumpTransactionEvent now contains the channel and counterparty (#2873).

... (truncated)

Changelog

Sourced from lightning-net-tokio's changelog.

0.0.123 - May 08, 2024 - "BOLT12 Dust Sweeping"

API Updates

  • To reduce risk of force-closures and improve HTLC reliability the default dust exposure limit has been increased to MaxDustHTLCExposure::FeeRateMultiplier(10_000). Users with existing channels might want to consider using ChannelManager::update_channel_config to apply the new default (#3045).
  • ChainMonitor::archive_fully_resolved_channel_monitors is now provided to remove from memory ChannelMonitors that have been fully resolved on-chain and are now not needed. It uses the new Persist::archive_persisted_channel to inform the storage layer that such a monitor should be archived (#2964).
  • An OutputSweeper is now provided which will automatically sweep SpendableOutputDescriptors, retrying until the sweep confirms (#2825).
  • After initiating an outbound channel, a peer disconnection no longer results in immediate channel closure. Rather, if the peer is reconnected before the channel times out LDK will automatically retry opening it (#2725).
  • PaymentPurpose now has separate variants for BOLT12 payments, which include fields from the invoice_request as well as the OfferId (#2970).
  • ChannelDetails now includes a list of in-flight HTLCs (#2442).
  • Event::PaymentForwarded now includes skimmed_fee_msat (#2858).
  • The hashbrown dependency has been upgraded and the use of ahash as the no-std hash table hash function has been removed. As a consequence, LDK's Hash{Map,Set}s no longer feature several constructors when LDK is built with no-std; see the util::hash_tables module instead. On platforms that getrandom supports, setting the possiblyrandom/getrandom feature flag will ensure hash tables are resistant to HashDoS attacks, though the possiblyrandom crate should detect most common platforms (#2810, #2891).
  • ChannelMonitor-originated requests to the ChannelSigner can now fail and be retried using ChannelMonitor::signer_unblocked (#2816).
  • SpendableOutputDescriptor::to_psbt_input now includes the witness_script where available as well as new proprietary data which can be used to re-derive some spending keys from the base key (#2761, #3004).
  • OutPoint::to_channel_id has been removed in favor of ChannelId::v1_from_funding_outpoint in preparation for v2 channels with a different ChannelId derivation scheme (#2797).
  • PeerManager::get_peer_node_ids has been replaced with list_peers and peer_by_node_id, which provide more details (#2905).
  • Bolt11Invoice::get_payee_pub_key is now provided (#2909).
  • Default[Message]Router now take an entropy_source argument (#2847).
  • ClosureReason::HTLCsTimedOut has been separated out from ClosureReason::HolderForceClosed as it is the most common case (#2887).
  • ClosureReason::CooperativeClosure is now split into {Counterparty,Locally}Initiated variants (#2863).
  • Event::ChannelPending::channel_type is now provided (#2872).
  • PaymentForwarded::{prev,next}_user_channel_id are now provided (#2924).
  • Channel init messages have been refactored towards V2 channels (#2871).
  • BumpTransactionEvent now contains the channel and counterparty (#2873).
  • util::scid_utils is now public, with some trivial utilities to examine

... (truncated)

Commits
  • 475f736 Merge pull request #3055 from TheBlueMatt/2024-05-123-backports-2
  • a366d53 Bump to release versions, dropping -rc1
  • fba4eef Bump possiblyrandom to 0.2
  • 37122dd Add changelog entries for 0.0.123
  • 61e9038 Keep newlines between releases in CHANGELOG consistent
  • f385c1f Add release note for 0.0.122 with just three PRs.
  • 30a208e Use consistent byte/char offsets when parsing invoice HRPs
  • 0924850 Fix the full_stack_target breakage test and doc feerate requests
  • 95acb42 Merge pull request #3048 from TheBlueMatt/2024-05-123-backports
  • 1f018dc Bump crate versions to rc1
  • Additional commits viewable in compare view


Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
yanganto commented 4 months ago

This version will be updated later and following lightning-related crates.

dependabot[bot] commented 4 months ago

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.