Uh oh!
There was an error while loading. Please reload this page.
wallet: RBF batch payments manager - #9298
Conversation
b71b11f to
45c7543Comparea48e7ca to
5c7a247Compare3bdbf87 to
3ad4406Compare9691a83 to
7a40399Compare4826f7e to
5fd2ec7Comparef321x
commented
Feb 19, 2025
I get this exception and electrum crashes when batching is enabled and trying to fully spend an unconfirmed utxo from the "Coins" tab with right click -> fully spend -> send to address in clipboard. |
9daa851 to
3f8bc37Compareecdsa
commented
Feb 21, 2025
This does not correspond to the code in the |
f321x
commented
Feb 21, 2025
Can confirm it doesn't happen on this branch, only on master. |
1b9218c to
be6f9bbCompareUh oh!
There was an error while loading. Please reload this page.
9f589b0 to
ccb0cc3Compareecdsa
commented
Feb 24, 2025
Note: This PR does not work well with fee settings. When we change the fee settings in |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
The class TxBatcher handles the creation, broadcast and replacement of replaceable transactions. Callers (LNWatcher, SwapManager) use methods add_payment_output and add_sweep_info. Transactions created by TxBatcher may combine sweeps and outgoing payments. Transactions created by TxBatcher will have their fee bumped automatically (this was only the case for sweeps before). TxBatcher manages several TxBatches. TxBatches are created dynamically when needed. The GUI does not touch txbatcher transactions: - wallet.get_candidates_for_batching excludes txbatcher transactions - RBF dialogs do not work with txbatcher transactions wallet: - instead of reading config variables, make_unsigned_transaction takes new parameters: base_tx, send_change_to_lighting tests: - unit tests in test_txbatcher.py (replaces test_sswaps.py) - force all regtests to use MPP, so that we sweep transactions with several HTLCs. This forces the payment manager to aggregate first-stage HTLC tx inputs. second-stage are not batched for now.
note: this is not "reorg safe", meaning that there is no guarantee that all payments will end up in in the blockchain.
However, I believe this is "double send safe", meaning that we will never send a payment twice.