Skip to content

Conversation

@harding
Copy link
Collaborator

@harding harding commented Feb 27, 2025

My apologies for opening the PR late. We recently moved; it's just a few miles away from our old place but right now my life is in disarray.

process. Users must set the `no_wait` parameter to enable this behavior;
otherwise, an error message will prompt them to specify it. This PR also
ensures that the `max_fee_rate` setting is enforced for both parties when a
cooperative channel closure is initiated; previously it was only applied to
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
cooperative channel closure is initiated; previously it was only applied to
cooperative channel closure is initiated; previously, it was only applied to

@harding
Copy link
Collaborator Author

harding commented Feb 28, 2025

Made an edit for @LarryRuane feedback (thanks!), added lede, releases, and topic links, reviewed @bitschmidty section (nice As this month!), and reviewed @Gustavojfe section (great job digging up old refs!). Thanks everyone!

@bitschmidty bitschmidty force-pushed the 2025-02-28-newsletter branch from 1fe4fd4 to a6c9eb9 Compare February 28, 2025 12:00
Copy link
Contributor

@bitschmidty bitschmidty left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ACK lede, topic entries
Squashed

Good luck with the physical rebase @harding !

@bitschmidty bitschmidty merged commit e9fcf36 into bitcoinops:master Feb 28, 2025
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants