Skip to content

Conversation

@ValuedMammal
Copy link
Collaborator

@ValuedMammal ValuedMammal commented Aug 12, 2025

Description

Use the new bdk_tx transaction building library to create PSBTs in BDK Wallet. Primary benefits include the use of bdk_coin_select as well as miniscript::plan module under the hood.

close #164

Notes to the reviewers

Remaining TODOs are listed in the table below #297 (comment).

Changelog notice

Added

- new type `PsbtParams`
- new type `ReplaceParams`
- methods `Wallet::create_psbt{_with_aux_rand}`
- methods `Wallet::replace_by_fee{_with_aux_rand}`
- convenience method `Wallet::replace_by_fee_and_recipients`
- `examples/psbt.rs`
- `examples/rbf.rs`

Checklists

All Submissions:

New Features:

  • I've added tests for the new feature
  • I've added docs for the new feature

Bugfixes:

  • This pull request breaks the existing API
  • I'm linking the issue being fixed by this PR

@ValuedMammal ValuedMammal moved this to In Progress in BDK Wallet Aug 12, 2025
@ValuedMammal ValuedMammal added this to the Wallet 3.0.0 milestone Aug 12, 2025
@ValuedMammal ValuedMammal self-assigned this Aug 12, 2025
@coveralls
Copy link

coveralls commented Aug 26, 2025

Pull Request Test Coverage Report for Build 18791891690

Details

  • 517 of 644 (80.28%) changed or added relevant lines in 5 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage decreased (-0.2%) to 84.587%

Changes Missing Coverage Covered Lines Changed/Added Lines %
src/wallet/tx_builder.rs 7 12 58.33%
src/wallet/error.rs 0 19 0.0%
src/wallet/mod.rs 320 357 89.64%
src/psbt/params.rs 173 239 72.38%
Totals Coverage Status
Change from base Build 18318022693: -0.2%
Covered Lines: 7431
Relevant Lines: 8785

💛 - Coveralls

@thunderbiscuit
Copy link
Member

I like the create_psbt name for the function. The Params struct I need to do a quick search but off the top of my head it feels like we have a few of those scattered across the crates named exactly that, so it gets confusing. In my exploration PR I used TransactionParams, but that's a bit long and verbose.

What do you envision the API for replace-by-fee transactions look like in this new bdk-tx world? I'm picturing something like Wallet::create_replacement_psbt which takes a WalletTx and another Params struct.

@ValuedMammal ValuedMammal moved this from In Progress to Needs Review in BDK Wallet Sep 11, 2025
@ValuedMammal ValuedMammal marked this pull request as ready for review September 11, 2025 15:39
@ValuedMammal ValuedMammal changed the title [WIP] Implement create_psbt for Wallet Implement create_psbt for Wallet Sep 11, 2025
Copy link
Member

@thunderbiscuit thunderbiscuit left a comment

Choose a reason for hiding this comment

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

So this is more of a conceptual review/question set, as I'm getting acquainted with the PR, and it also requires knowledge and understanding of the bdk-tx crate/workflow.

One general question I have is do you think is missing in functionality between this and the current TxBuilder? Can we make a todo list that compares functionality with the current TxBuilder to better visualize how close of a replacement this is, or if it only provides part of the functionality for now (and if so which parts)?

I haven't had time to look/test the examples and my day is over, but I'll come back to this on Monday.

///
/// Return `None` if `outpoint` doesn't correspond to an indexed txout, or
/// if the assets are not sufficient to create a plan.
fn try_plan(&self, outpoint: OutPoint, assets: &Assets) -> Option<Plan> {
Copy link
Member

Choose a reason for hiding this comment

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

Do you have a favourite resource for learning about this plan thing? I'm looking at the docs here and I get a rough idea of how it must work but I'm wondering if there is this "standard expected reading" on it or something similar that I've just missed.

Copy link
Collaborator Author

@ValuedMammal ValuedMammal Sep 16, 2025

Choose a reason for hiding this comment

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

https://hackmd.io/@valuedmammal/B1lxzomj0 It could use an update though.

Copy link
Member

Choose a reason for hiding this comment

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

Perfect thank you! Quick and easy read. Cements my high-level understanding of it.

/// Coin select strategy.
#[derive(Debug, Clone, Copy, Default)]
#[non_exhaustive]
pub enum SelectionStrategy {
Copy link
Member

Choose a reason for hiding this comment

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

I like the coin selection strategy as a simple enum rather than the CoinSelectionAlgorithm trait. Easier to use and reason about, and most people will only ever need the standard ones (which I assume can eventually get added to this enum) or pick the individual UTXOs themselves.

///
/// A single outpoint may appear at most once in the list of UTXOs to spend. The caller is
/// responsible for ensuring that elements of `outpoints` correspond to outputs of previous
/// transactions and are currently unspent.
Copy link
Member

Choose a reason for hiding this comment

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

Where is the error thrown if this requirement is not met? It's a good place to let people know and I would add it to the docs here.

Copy link
Collaborator Author

@ValuedMammal ValuedMammal Sep 16, 2025

Choose a reason for hiding this comment

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

Wallet::create_psbt will throw a CreatePsbtError::UnknownUtxo if the outpoint doesn't match a previously indexed outpoint (i.e. a wallet-owned tx output). I agree it should be documented somewhere.

}

/// Set the definite descriptor used for generating the change output.
pub fn change_descriptor(&mut self, desc: DefiniteDescriptor) -> &mut Self {
Copy link
Member

Choose a reason for hiding this comment

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

Is it correct to think that if not defined here, the change just goes to:

  1. The next index on Keychain::Internal if available
  2. If no internal keychain is available, the next index on the KeychainKind::External

Copy link
Member

@thunderbiscuit thunderbiscuit Sep 16, 2025

Choose a reason for hiding this comment

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

Ok awesome thanks for confirming. In this case, I'd just mention this in the docs (that this method is basically "if you want to send change elsewhere than your default change location").

/// `ReplaceParams` provides a thin wrapper around [`PsbtParams`] and is intended for
/// crafting Replace-By-Fee transactions (RBF).
#[derive(Debug, Default)]
pub struct ReplaceParams {
Copy link
Member

Choose a reason for hiding this comment

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

Can you tell me more about why we want this new ReplaceParams type? Naively I would have thought you'd just call PsbtParams::replace and you'd get a sort of pre-populated PsbtParams ready for replacing your tx, but I assume this doesn't quite work?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Naively I would have thought you'd just call PsbtParams::replace and you'd get a sort of pre-populated PsbtParams ready for replacing your tx

That works too.

Copy link
Member

Choose a reason for hiding this comment

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

If that works that's my preferred approach, unless there is something I'm not seeing.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Sorry I didn't elaborate before. We want to provide some separation to make it difficult to misuse the API. Once you've committed to replacing a tx, you can't go back and fiddle with the params, instead you're limited to doing only what is permitted by the ReplaceParams, at least that's the general idea. This prevents a situation where some params override others and the implementation becomes unwieldy.

Right now the key difference is that you're not allowed to add more utxos (outpoints) in addition the ones being replaced, because it may lead to creating an invalid tx. Still open to suggestions for improvement.

/// # Ok::<_, anyhow::Error>(())
/// ```
#[cfg(feature = "std")]
pub fn create_psbt(&self, params: PsbtParams) -> Result<(Psbt, Finalizer), CreatePsbtError> {
Copy link
Member

Choose a reason for hiding this comment

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

Why do we return this Finalizer? I'd like to see that expanded upon in the docs. When looking into it I see that the Finalizer is

pub struct Finalizer {
    pub(crate) plans: HashMap<OutPoint, Plan>,
}

so probably something that helps the signers figure out what to sign and how to sign once you give them a psbt, but I'm not sure. The docs on Finalizer are also a bit... brief 😂😂

Copy link
Contributor

Choose a reason for hiding this comment

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

I still need to take a deeper look into bdk-tx, but I think the name could be misleading with Input Finalizer from the PSBT BIP-174 (if it's not following the same proposed idea).

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

It is meant to handle the role of a PSBT input finalizer as described in BIP174.

Copy link
Contributor

@oleonardolima oleonardolima left a comment

Choose a reason for hiding this comment

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

I did an initial review, with simple comments/questions. Still need to take a deeper look into bdk-tx and do a more thorough review here.

bip39 = { version = "2.0", optional = true }
bdk_file_store = { version = "0.21.1", optional = true }
anyhow = { version = "1.0.98", optional = true }
tempfile = { version = "3.20.0", optional = true }
Copy link
Contributor

Choose a reason for hiding this comment

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

I guess this can be removed, as it's not being used.

Comment on lines +264 to +267
/// No Bnb solution.
Bnb(bdk_coin_select::NoBnbSolution),
/// Non-sufficient funds
InsufficientFunds(bdk_coin_select::InsufficientFunds),
Copy link
Contributor

Choose a reason for hiding this comment

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

Can't we have a generic CS error instead ?

/// # Ok::<_, anyhow::Error>(())
/// ```
#[cfg(feature = "std")]
pub fn create_psbt(&self, params: PsbtParams) -> Result<(Psbt, Finalizer), CreatePsbtError> {
Copy link
Contributor

Choose a reason for hiding this comment

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

I still need to take a deeper look into bdk-tx, but I think the name could be misleading with Input Finalizer from the PSBT BIP-174 (if it's not following the same proposed idea).

@ValuedMammal
Copy link
Collaborator Author

Thank you for the quick review @thunderbiscuit @oleonardolima.

@ValuedMammal
Copy link
Collaborator Author

ValuedMammal commented Sep 20, 2025

TxBuilder vs PsbtParams feature comparison

subject to change

Feature TxBuilder PsbtParams Status
internal_policy_path NA
external_policy_path NA
manually_selected_only Done
include_output_redeem_witness_script NA
current_height Done
fee_rate Done
fee_absolute TODO
sighash (type) TODO
ordering Done
add_global_xpubs Done
allow_dust Done
unspendable NA
recipients Done
utxos Done
drain_wallet Done
drain_to/change_script Done
locktime Done
version Done
fallback_sequence Done
bumping_fee Done
only_witness_utxo Done
change_policy NA
add_foreign_utxo / planned_input Done
utxo_filter Done

N/A:
- *_policy_path: deprecated, ref: add_assets
- include_output_redeem_witness_script: deprecated, not used
- unspendable: NA, ref: utxo_filter
- change_policy: NA, ref: utxo_filter

@ValuedMammal
Copy link
Collaborator Author

ValuedMammal commented Oct 1, 2025

  • We need a way to implement fee_absolute or find out if this is possible using bdk_coin_select.
  • Note that UtxoFilter can accomplish a number of things from the old interface, such as "change policy" and "unspendable".
  • To prevent multiple parameters from trying to dictate the current height, the current_height option can be achieved via the assets.absolute_timelock.
  • current_height renamed to maturity_height, as it's only used as a parameter to is_mature.

Add module psbt/params.rs and introduce PsbtParams.

test: Add `test_create_psbt`

Introduce `ReplaceParams`

Add `Wallet::replace_by_fee_and_recipients`

Add `Wallet::replace_by_fee_with_aux_rand`

test: `test_sanitize_rbf_set`

test: Add `test_replace_by_fee`

test: Add `test_spend_non_canonical_txout`
`UtxoFilter` is a user-defined Fn closure which takes a
`&FullTxOut` and decides whether to exclude it from coin selection.
This can be used, for example, to mark an output unspendable
or apply custom UTXO filtering logic.
..by exposing the generic from `TxSort` function. We use
bitcoin `TxIn` and `TxOut` as the default type parameter for
backward compatibility.

Add `sort_with_aux_rand` for `TxOrdering<In, Out>` for sorting
two generic mutable slices.
`add_global_xpubs` is a boolean which decides whether
to fill in the PSBT global xpubs. If true, we proceed
to gather extended keys of the wallet's descriptors
and add them to the map of global xpubs with their
origin.
@ValuedMammal
Copy link
Collaborator Author

We need a way to implement fee_absolute or find out if this is possible using bdk_coin_select.

I think a straightforward approach is to set a target feerate of 0 and add the fee amount to the output value_sum. The effect is to raise the cost of meeting the target by the amount of the target fee.

I can see it being relevant to CPFP, since there we're less concerned about the feerate of an individual tx and more so with the fee needed to bump a package to a target feerate.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

summit To review at rust bitcoin summit.

Projects

Status: In Progress

Development

Successfully merging this pull request may close these issues.

Redesign TxBuilder

5 participants