Skip to content

Conversation

@t-bast
Copy link
Member

@t-bast t-bast commented Oct 24, 2025

When addres type or change type is not specified, bitcoind will now start with addresstype=bech32m and changetype=bech32m.

We take this opportunity to fix feerate tests that failed because of the following reasons:

  • first of all, we had a bug where we didn't take into account the anchor amount in our fee calculation, so we ended up always adding 330 sats to the on-chain fees we paid, which was hidden by our tolerance interval, but started appearing with smaller p2tr inputs
  • then we fix the remaining tests that need manual tweaking of the utxos available in the test wallet, because they end up creating transactions where we don't have a change output (and overpay fees slightly, but not enough to make it worth adding a change output), these tests simply needed to be tweaked to accomodate p2tr weights

Co-authored by @sstone

Replaces #3191

When addres type or change type is not specified, bitcoind will
now start with addresstype=bech32m and changetype=bech32m.

We take this opportunity to fix feerate tests that failed because
of the following reasons:

- first of all, we had a bug where we didn't take into account the
  anchor amount in our fee calculation, so we ended up always adding
  `330 sats` to the on-chain fees we paid, which was hidden by our
  tolerance interval, but started appearing with smaller p2tr inputs
- then we fix the remaining tests that need manual tweaking of the
  utxos available in the test wallet, because they end up creating
  transactions where we don't have a change output (and overpay fees
  slightly, but not enough to make it worth adding a change output),
  these tests simply needed to be tweaked to accomodate p2tr weights

Co-authored by @sstone
pm47
pm47 previously approved these changes Oct 24, 2025
Instead of specifically 29.1 or 29.2.
@t-bast t-bast merged commit 9771b2d into master Oct 24, 2025
1 of 3 checks passed
@t-bast t-bast deleted the bitcoind-use-bech32m-bast branch October 24, 2025 12:12
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.

4 participants