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

spend: ensure fee above min relay value #1323

Merged
merged 1 commit into from
Sep 12, 2024

Conversation

jp1ac4
Copy link
Collaborator

@jp1ac4 jp1ac4 commented Sep 11, 2024

This is a quick change to address #1322.

It adds 10 sats to the fee for a non-replacement transaction targeted at 1 sat/vb.

This is a quick change to prevent the fee being below the
min relay fee.
@nondiremanuel nondiremanuel added this to the v7 - Liana milestone Sep 11, 2024
@darosior
Copy link
Member

utACK 74a53ba. Looking forward to a real fix.

@darosior darosior merged commit b2da2b7 into wizardsardine:master Sep 12, 2024
31 checks passed
@jp1ac4 jp1ac4 deleted the spend-prevent-fee-too-low branch November 6, 2024 15:30
edouardparis added a commit that referenced this pull request Nov 15, 2024
…tisig primary path spends

6e74a96 Revert "spend: add 10 sats to fee for 1 sat/vb txs" (Michael Mallan)
cf88aca descriptors: fix satisfaction size for Taproot (Michael Mallan)
e9c6995 qa: add threshold paramater for multisig descs (Michael Mallan)

Pull request description:

  This is a fix to #1371 and the related #1322.

  As per #1371 (comment), this adds the varint length for the script and control block elements of a Taproot primary path spend.

  I think this is what caused #1322 and so I have reverted the change from #1323.

ACKs for top commit:
  edouardparis:
    utACK 6e74a96

Tree-SHA512: 754e5c2186de853cde9006aeab7989141a4d363b9e3d8adb3f0264bcbca7e3b56a94822d434f6f7d8108e7c0e3023959fa407643e5868082f8981c5ce10b9a1e
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

3 participants