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

Use confirmed inputs for anchor transactions #3020

Merged
merged 4 commits into from
Mar 6, 2025

Conversation

t-bast
Copy link
Member

@t-bast t-bast commented Feb 27, 2025

In order to use opportunistic package relay (with 1-parent-1-child) we must use confirmed inputs when funding our anchor transactions. This will also be a requirement when using v3 transactions. We leverage the newly added minconf parameter to fundrawtransaction.

We also take this opportunity to honor the require_confirmed_inputs parameter set by our peer during interactive-tx.

In order to use opportunistic package relay (with 1-parent-1-child)
we must use confirmed inputs when funding our anchor transactions.
This will also be a requirement when using v3 transactions.

We also take this opportunity to honor the `require_confirmed_inputs`
parameter set by our peer during `interactive-tx`.
@t-bast t-bast force-pushed the package-relay-confirmed-inputs branch from e35ccd5 to 39afd22 Compare February 28, 2025 10:04
@t-bast t-bast marked this pull request as ready for review February 28, 2025 10:04
@t-bast t-bast requested a review from pm47 February 28, 2025 10:04
Copy link
Member

@pm47 pm47 left a comment

Choose a reason for hiding this comment

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

We also take this opportunity to honor the require_confirmed_inputs parameter set by our peer during interactive-tx.

We previously filtered unconfirmed inputs at the filterInputs step. Why don't we take the opportunity to simplify getInputDetails/canUseInput? It saves a RPC call.

t-bast added 2 commits March 5, 2025 17:36
Now that we delegate this to `bitcoind`, we don't need to check for
confirmations of our inputs ourselves.
@t-bast
Copy link
Member Author

t-bast commented Mar 5, 2025

We previously filtered unconfirmed inputs at the filterInputs step. Why don't we take the opportunity to simplify getInputDetails/canUseInput? It saves a RPC call.

Good point, I missed that, this is definitely worth removing! Done in 6a8c6e4

@t-bast t-bast requested a review from pm47 March 6, 2025 15:55
@t-bast t-bast merged commit 7ef55a6 into master Mar 6, 2025
1 check passed
@t-bast t-bast deleted the package-relay-confirmed-inputs branch March 6, 2025 18:44
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