mirror of
https://github.com/bisq-network/bisq.git
synced 2025-02-28 17:15:14 +01:00
Use taker's burning man selection height
When a taker takes a trade he sends his burning man selection height to the maker. After validating the taker's burning man selection height, he has to use the taker's burning man selection height to verify the taker's delayed payout transaction because the maker's and taker's burning man selection height could be different. The current implementation uses the maker's burning man selection height. This can cause failed trades. Relates to #7393.
This commit is contained in:
parent
96355d7a3c
commit
df78cb7381
1 changed files with 1 additions and 1 deletions
|
@ -90,7 +90,7 @@ public class MakerProcessesInputsForDepositTxRequest extends TradeTask {
|
|||
checkArgument(areBurningManSelectionHeightsValid,
|
||||
"takersBurningManSelectionHeight does no match makersBurningManSelectionHeight");
|
||||
|
||||
processModel.setBurningManSelectionHeight(makersBurningManSelectionHeight);
|
||||
processModel.setBurningManSelectionHeight(takersBurningManSelectionHeight);
|
||||
|
||||
// We set the taker fee only in the processModel yet not in the trade as the tx was only created but not
|
||||
// published yet. Once it was published we move it to trade. The takerFeeTx should be sent in a later
|
||||
|
|
Loading…
Add table
Reference in a new issue