Skip to content
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

2021 11 cherry anchors #4

Draft
wants to merge 6 commits into
base: master
Choose a base branch
from
Draft

2021 11 cherry anchors #4

wants to merge 6 commits into from

Conversation

ksedgwic
Copy link

This is v0.0.102 with our anchor MRs cherry-picked, plus more fixes.

The plan is to get this working and then divide it into sensible upstream PR(s) ...

@ksedgwic ksedgwic force-pushed the 2021-11-cherry-anchors branch from 2df5f4d to 0e3c95c Compare November 16, 2021 15:55
@ksedgwic ksedgwic force-pushed the 2021-11-cherry-anchors branch from 5635359 to 6837b75 Compare November 16, 2021 19:41
@@ -42,8 +42,10 @@ use chain;

pub(crate) const MAX_HTLCS: u16 = 483;

pub(super) const HTLC_SUCCESS_TX_WEIGHT: u64 = 703;
pub(super) const HTLC_TIMEOUT_TX_WEIGHT: u64 = 663;
/// The fee for an HTLC-success transaction
Copy link
Collaborator

Choose a reason for hiding this comment

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

it's the weight, not the fee

@devrandom
Copy link
Collaborator

One more nit - commit descriptions are usually in the present tense.

Any ideas about the PR title for upstream? maybe "Anchor support for HTLCs"?

@devrandom
Copy link
Collaborator

Also, I think this can be submitted as a single PR.

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.

2 participants