-
Notifications
You must be signed in to change notification settings - Fork 364
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cut 0.0.115 #2211
Cut 0.0.115 #2211
Conversation
Codecov ReportPatch coverage has no change and project coverage change:
📣 This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more Additional details and impacted files@@ Coverage Diff @@
## main #2211 +/- ##
==========================================
- Coverage 91.57% 91.54% -0.03%
==========================================
Files 104 104
Lines 51745 51745
Branches 51745 51745
==========================================
- Hits 47386 47371 -15
- Misses 4359 4374 +15 see 6 files with indirect coverage changes Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report in Codecov by Sentry. |
4f971d5
to
ccaafa0
Compare
|
||
## Security | ||
* Transaction re-broadcasting is now substantially more aggressive, including a | ||
new regular rebroadcast feature called on a timer from the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"If the rebroadcast is called directly from ChainMonitor::rebroadcast_pending_claims
, it can be invoked as a aggressive as every 30s on mobile” ?
Should we say it comes at the downside of inflating the feerate paid? Might be concerning if you’re not using Core’s fee estimator but relying on a mempool only fee estimator.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It doesnt inflate the feerate, we don't bump on rebroadcasts.
`ChannelMonitor` on 0.0.114 or before may panic (#2059). Note that this is | ||
in general unsupported, and included here only for completeness. | ||
|
||
## Bug Fixes |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think 2161 is an API change, but included both, thanks.
ccaafa0
to
035c79c
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM after squash
Want to land #2220 first. |
Let's do #2004 as well. |
1c624a2
to
33a396b
Compare
Rebased on #2004, updated release notes to include everything, added diff totals. Should be good to go! |
33a396b
to
dafa095
Compare
Rebased again, and added the one missing commit. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 🚀
Still need to come up with a release name, but here's draft release notes.