# Can't make sell BTC-\>USD offer -- txn mempool conflict error

**URL:** <https://bisq.community/t/cant-make-sell-btc-usd-offer-txn-mempool-conflict-error/3677>\
**Category:** Support\
**Created:** [December 7, 2017, 10:47pm UTC](https://bisq.community/t/cant-make-sell-btc-usd-offer-txn-mempool-conflict-error/3677 "2017-12-07T22:47:22Z")\
**Posts on this page:** 14\
**Page:** 1

<div class="post-metadata">

**Author:** ![jmeemiller](https://bisq.community/letter_avatar/jmeemiller/32/6_22734026db12803ebb3e059622ac3534.png) [@jmeemiller](https://bisq.community/u/jmeemiller)\
**Post date:** [December 7, 2017, 10:47pm UTC](https://bisq.community/t/cant-make-sell-btc-usd-offer-txn-mempool-conflict-error/3677/1 "2017-12-07T22:47:22Z")

</div>

I am unable to submit a SELL BTC for USD offer using Bisq client 0.6.1. I am able to create and fund the offer but after reviewing and submitting the offer, it times out and generates an error message. The log file entries below indicate a transaction mempool conflict. This is a repeatable problem even after a complete shutdown and restart the client.

Can the conflict be cleared? Is there a workaround?

Note (for some background), this problem appeared after I received an earlier InsufficientFunds exception when someone tried to accept my offer. While I had sufficient funds, I noticed that they were no longer reserve.

```
**Java Log**
Dec-07 23:50:20.026 [BlockingClient network thread for 3r44ddzjitznyahw.onion:8333] ERROR o.b.core.Peer: [3r44ddzjitznyahw.onion]:8333 /Satoshi:0.15.1/: Received Reject: tx 7ec7febd4cb9675fc0f7459765d46355ef903bbd267cda1c99f2bc482bbf97e1 for reason 'txn-mempool-conflict' (18) 
Dec-07 23:50:20.205 [BlockingClient network thread for /62.75.210.81:8333] ERROR o.b.core.Peer: [62.75.210.81]:8333 /Satoshi:0.15.1/: Received Reject: tx 7ec7febd4cb9675fc0f7459765d46355ef903bbd267cda1c99f2bc482bbf97e1 for reason 'txn-mempool-conflict' (18) 
Dec-07 23:50:20.434 [BlockingClient network thread for /163.172.171.119:8333] WARN o.b.c.TransactionBroadcast: Threshold for considering broadcast rejected has been reached (3/2) 
Dec-07 23:50:20.435 [BlockingClient network thread for /163.172.171.119:8333] ERROR i.b.c.t.Task: An error occurred at task: CreateMakerFeeTx
Exception message: Reject: tx 7ec7febd4cb9675fc0f7459765d46355ef903bbd267cda1c99f2bc482bbf97e1 for reason 'txn-mempool-conflict' (18) 
Dec-07 23:50:20.435 [BlockingClient network thread for /163.172.171.119:8333] ERROR i.b.c.t.TaskRunner: Task failed: CreateMakerFeeTx / errorMessage: An error occurred at task: CreateMakerFeeTx
Exception message: Reject: tx 7ec7febd4cb9675fc0f7459765d46355ef903bbd267cda1c99f2bc482bbf97e1 for reason 'txn-mempool-conflict' (18) 
Dec-07 23:50:20.435 [BlockingClient network thread for /163.172.171.119:8333] ERROR i.b.c.o.p.PlaceOfferProtocol: An error occurred at task: CreateMakerFeeTx
Exception message: Reject: tx 7ec7febd4cb9675fc0f7459765d46355ef903bbd267cda1c99f2bc482bbf97e1 for reason 'txn-mempool-conflict' (18) 
Dec-07 23:50:20.435 [BlockingClient network thread for /163.172.171.119:8333] ERROR i.b.g.m.o.c.CreateOfferDataModel: An error occurred at task: CreateMakerFeeTx
Exception message: Reject: tx 7ec7febd4cb9675fc0f7459765d46355ef903bbd267cda1c99f2bc482bbf97e1 for reason 'txn-mempool-conflict' (18) 
Dec-07 23:50:20.436 [BlockingClient network thread for /163.172.171.119:8333] ERROR o.b.core.Peer: [163.172.171.119]:8333 /Satoshi:0.15.1/: Received Reject: tx 7ec7febd4cb9675fc0f7459765d46355ef903bbd267cda1c99f2bc482bbf97e1 for reason 'txn-mempool-conflict' (18) 
Dec-07 23:50:26.075 [BlockingClient network thread for poyvpdt762gllauu.onion:8333] ERROR o.b.core.Peer: [poyvpdt762gllauu.onion]:8333 /Satoshi:0.15.1(UASF-SegWit-BIP148)/: Received Reject: tx 7ec7febd4cb9675fc0f7459765d46355ef903bbd267cda1c99f2bc482bbf97e1 for reason 'txn-mempool-conflict' (18)
```

---

<div class="post-metadata">

**Author:** ![ManfredKarrer](https://bisq.community/user_avatar/bisq.community/manfredkarrer/32/26_2.png) [@ManfredKarrer](https://bisq.community/u/ManfredKarrer)\
**Post date:** [December 8, 2017, 12:49am UTC](https://bisq.community/t/cant-make-sell-btc-usd-offer-txn-mempool-conflict-error/3677/2 "2017-12-08T00:49:11Z")

</div>

Can you try to resync the spv chain file? In the settings/network there is a button to do that. You have to restart 2 times after that. it can take a while if the wallet has many txs so have patience.

---

<div class="post-metadata">

**Author:** ![jmeemiller](https://bisq.community/letter_avatar/jmeemiller/32/6_22734026db12803ebb3e059622ac3534.png) [@jmeemiller](https://bisq.community/u/jmeemiller)\
**Post date:** [December 8, 2017, 9:39pm UTC](https://bisq.community/t/cant-make-sell-btc-usd-offer-txn-mempool-conflict-error/3677/3 "2017-12-08T21:39:25Z")

</div>

Thanks for the quick response. I tried this and I get the following message:

![image](https://bisq.community/uploads/default/original/2X/c/cee162ffb104498ae61280ad812231f3a11d3afa.png)

There is nothing in the logs other this warning:

```
Dec-08 23:31:15.236 [JavaFX Application Thread] WARN i.b.c.t.TradeManager: We found an outdated addressEntry for trade ufwyq2-d41d670e-e0fd-4284-a381-e38683b87f5b-061 

```

I tried also running as administrator to see if it was a permission problem but it made no difference.

I found the file at ${AppData}\Roaming\Bisq\btc\_mainnet\wallet\bisq.spvchain. If I delete this manually, will it be recreated on restart?

---

<div class="post-metadata">

**Author:** ![alexej996](https://bisq.community/user_avatar/bisq.community/alexej996/32/491_2.png) [@alexej996](https://bisq.community/u/alexej996)\
**Post date:** [December 8, 2017, 10:16pm UTC](https://bisq.community/t/cant-make-sell-btc-usd-offer-txn-mempool-conflict-error/3677/4 "2017-12-08T22:16:09Z")

</div>

Yes. I think deleting it manually should be fine. Close Bisq first, just in case.

---

<div class="post-metadata">

**Author:** ![ManfredKarrer](https://bisq.community/user_avatar/bisq.community/manfredkarrer/32/26_2.png) [@ManfredKarrer](https://bisq.community/u/ManfredKarrer)\
**Post date:** [December 8, 2017, 10:37pm UTC](https://bisq.community/t/cant-make-sell-btc-usd-offer-txn-mempool-conflict-error/3677/5 "2017-12-08T22:37:43Z")

</div>

Yes delete manually. The msg in the log is not critical. Yes the spv file will be recreated that the same like when u do it in the app. it requires 2 times a restart after its synced!

---

<div class="post-metadata">

**Author:** ![jmeemiller](https://bisq.community/letter_avatar/jmeemiller/32/6_22734026db12803ebb3e059622ac3534.png) [@jmeemiller](https://bisq.community/u/jmeemiller)\
**Post date:** [December 9, 2017, 10:30am UTC](https://bisq.community/t/cant-make-sell-btc-usd-offer-txn-mempool-conflict-error/3677/6 "2017-12-09T10:30:52Z")

</div>

This has not helped. I deleted the file manually and it did recreate on startup. After restarting it a 2nd and 3rd time, I still have the same problem.

```
Dec-09 12:27:05.681 [BlockingClient network thread for /62.75.210.81:8333] WARN o.b.c.TransactionBroadcast: Threshold for considering broadcast rejected has been reached (2/1) 
Dec-09 12:27:05.681 [BlockingClient network thread for /138.68.117.247:8333] ERROR o.b.core.Peer: [138.68.117.247]:8333 /Satoshi:0.15.0.1/: Received Reject: tx 023dbcd0dacda9fce180b15fd5ecce474da05483e750ead819bdfea661859a1c for reason 'txn-mempool-conflict' (18) 
Dec-09 12:27:05.682 [BlockingClient network thread for /62.75.210.81:8333] ERROR i.b.c.t.Task: An error occurred at task: CreateMakerFeeTx
Exception message: Reject: tx 023dbcd0dacda9fce180b15fd5ecce474da05483e750ead819bdfea661859a1c for reason 'txn-mempool-conflict' (18) 
Dec-09 12:27:05.682 [BlockingClient network thread for /62.75.210.81:8333] ERROR i.b.c.t.TaskRunner: Task failed: CreateMakerFeeTx / errorMessage: An error occurred at task: CreateMakerFeeTx
Exception message: Reject: tx 023dbcd0dacda9fce180b15fd5ecce474da05483e750ead819bdfea661859a1c for reason 'txn-mempool-conflict' (18) 
Dec-09 12:27:05.682 [BlockingClient network thread for /62.75.210.81:8333] ERROR i.b.c.o.p.PlaceOfferProtocol: An error occurred at task: CreateMakerFeeTx
Exception message: Reject: tx 023dbcd0dacda9fce180b15fd5ecce474da05483e750ead819bdfea661859a1c for reason 'txn-mempool-conflict' (18) 
Dec-09 12:27:05.682 [BlockingClient network thread for /62.75.210.81:8333] ERROR i.b.g.m.o.c.CreateOfferDataModel: An error occurred at task: CreateMakerFeeTx
Exception message: Reject: tx 023dbcd0dacda9fce180b15fd5ecce474da05483e750ead819bdfea661859a1c for reason 'txn-mempool-conflict' (18) 
Dec-09 12:27:05.683 [BlockingClient network thread for /62.75.210.81:8333] ERROR o.b.core.Peer: [62.75.210.81]:8333 /Satoshi:0.15.1/: Received Reject: tx 023dbcd0dacda9fce180b15fd5ecce474da05483e750ead819bdfea661859a1c for reason 'txn-mempool-conflict' (18) 
Dec-09 12:27:05.773 [BlockingClient network thread for i3a5xtzfm4xwtybd.onion:8333] INFO o.b.core.Peer: Announcing to i3a5xtzfm4xwtybd.onion:8333 as: /bitcoinj:0.14.4/ 
Dec-09 12:27:05.862 [BlockingClient network thread for mxdtrjhe2yfsx3pg.onion:8333] ERROR o.b.core.Peer: [mxdtrjhe2yfsx3pg.onion]:8333 /Satoshi:0.15.0.1/: Received Reject: tx 023dbcd0dacda9fce180b15fd5ecce474da05483e750ead819bdfea661859a1c for reason 'txn-mempool-conflict' (18) 
Dec-09 12:27:06.117 [BlockingClient network thread for 3r44ddzjitznyahw.onion:8333] ERROR o.b.core.Peer: [3r44ddzjitznyahw.onion]:8333 /Satoshi:0.15.1/: Received Reject: tx 023dbcd0dacda9fce180b15fd5ecce474da05483e750ead819bdfea661859a1c for reason 'txn-mempool-conflict' (18) 
Dec-09 12:27:06.211 [BlockingClient network thread for i3a5xtzfm4xwtybd.onion:8333] INFO o.b.core.Peer: [i3a5xtzfm4xwtybd.onion]:8333: Got version=70015, subVer='/Satoshi:0.15.1/', services=0x13, time=2017-12-09 12:27:07, blocks=498380 
Dec-09 12:27:06.212 [BlockingClient network thread for i3a5xtzfm4xwtybd.onion:8333] INFO o.b.c.PeerGroup: [i3a5xtzfm4xwtybd.onion]:8333: New peer (10 connected, 0 pending, 10 max) 
Dec-09 12:27:06.228 [BlockingClient network thread for i3a5xtzfm4xwtybd.onion:8333] INFO o.b.core.Peer: Received alert from peer [i3a5xtzfm4xwtybd.onion]:8333: URGENT: Alert key compromised, upgrade required 
Dec-09 12:27:06.423 [BlockingClient network thread for i3a5xtzfm4xwtybd.onion:8333] INFO o.b.c.PeerGroup: [i3a5xtzfm4xwtybd.onion]:8333: Peer died (9 connected, 0 pending, 10 max) 
Dec-09 12:27:06.423 [PeerGroup Thread] INFO o.b.c.PeerGroup: Peer discovery took 2.763 ?s and returned 0 items 
Dec-09 12:27:06.423 [PeerGroup Thread] INFO o.b.c.PeerGroup: Waiting 1500 msec before next connect attempt to [i3a5xtzfm4xwtybd.onion]:8333 
Dec-09 12:27:06.466 [BlockingClient network thread for /78.47.61.83:8333] ERROR o.b.core.Peer: [78.47.61.83]:8333 /Satoshi:0.15.1/: Received Reject: tx 023dbcd0dacda9fce180b15fd5ecce474da05483e750ead819bdfea661859a1c for reason 'txn-mempool-conflict' (18) 
Dec-09 12:27:07.924 [PeerGroup Thread] INFO o.b.c.PeerGroup: Attempting connection to [i3a5xtzfm4xwtybd.onion]:8333 (9 connected, 1 pending, 10 max)
```

---

<div class="post-metadata">

**Author:** ![ManfredKarrer](https://bisq.community/user_avatar/bisq.community/manfredkarrer/32/26_2.png) [@ManfredKarrer](https://bisq.community/u/ManfredKarrer)\
**Post date:** [December 9, 2017, 2:37pm UTC](https://bisq.community/t/cant-make-sell-btc-usd-offer-txn-mempool-conflict-error/3677/7 "2017-12-09T14:37:36Z")

</div>

Can you do a backup and then restore the wallet from seed words?

---

<div class="post-metadata">

**Author:** ![jmeemiller](https://bisq.community/letter_avatar/jmeemiller/32/6_22734026db12803ebb3e059622ac3534.png) [@jmeemiller](https://bisq.community/u/jmeemiller)\
**Post date:** [December 9, 2017, 4:40pm UTC](https://bisq.community/t/cant-make-sell-btc-usd-offer-txn-mempool-conflict-error/3677/9 "2017-12-09T16:40:07Z")

</div>

After a worrying change in balance after the restore of the wallet, I restarted and everything returned to normal. I tried making the same offer but I get the same result.

```
Dec-09 18:35:14.190 [BlockingClient network thread for /37.221.198.57:8333] ERROR o.b.core.Peer: [37.221.198.57]:8333 /Satoshi:0.15.1(reddit user)/: Received Reject: tx 72edf74de83fb85c31c11f128cd116a930d21b3a9b928d4c87d02f1d63bb0a4b for reason 'txn-mempool-conflict' (18) 
Dec-09 18:35:14.295 [BlockingClient network thread for /163.172.171.119:8333] ERROR o.b.core.Peer: [163.172.171.119]:8333 /Satoshi:0.15.1/: Received Reject: tx 72edf74de83fb85c31c11f128cd116a930d21b3a9b928d4c87d02f1d63bb0a4b for reason 'txn-mempool-conflict' (18) 
Dec-09 18:35:14.939 [BlockingClient network thread for 3r44ddzjitznyahw.onion:8333] WARN o.b.c.TransactionBroadcast: Threshold for considering broadcast rejected has been reached (3/2) 
Dec-09 18:35:14.940 [BlockingClient network thread for 3r44ddzjitznyahw.onion:8333] ERROR i.b.c.t.Task: An error occurred at task: CreateMakerFeeTx
Exception message: Reject: tx 72edf74de83fb85c31c11f128cd116a930d21b3a9b928d4c87d02f1d63bb0a4b for reason 'txn-mempool-conflict' (18) 
Dec-09 18:35:14.941 [BlockingClient network thread for 3r44ddzjitznyahw.onion:8333] ERROR i.b.c.t.TaskRunner: Task failed: CreateMakerFeeTx / errorMessage: An error occurred at task: CreateMakerFeeTx
Exception message: Reject: tx 72edf74de83fb85c31c11f128cd116a930d21b3a9b928d4c87d02f1d63bb0a4b for reason 'txn-mempool-conflict' (18) 
Dec-09 18:35:14.941 [BlockingClient network thread for 3r44ddzjitznyahw.onion:8333] ERROR i.b.c.o.p.PlaceOfferProtocol: An error occurred at task: CreateMakerFeeTx
Exception message: Reject: tx 72edf74de83fb85c31c11f128cd116a930d21b3a9b928d4c87d02f1d63bb0a4b for reason 'txn-mempool-conflict' (18) 
Dec-09 18:35:14.941 [BlockingClient network thread for 3r44ddzjitznyahw.onion:8333] ERROR i.b.g.m.o.c.CreateOfferDataModel: An error occurred at task: CreateMakerFeeTx
Exception message: Reject: tx 72edf74de83fb85c31c11f128cd116a930d21b3a9b928d4c87d02f1d63bb0a4b for reason 'txn-mempool-conflict' (18) 
Dec-09 18:35:14.941 [BlockingClient network thread for 3r44ddzjitznyahw.onion:8333] ERROR o.b.core.Peer: [3r44ddzjitznyahw.onion]:8333 /Satoshi:0.15.1/: Received Reject: tx 72edf74de83fb85c31c11f128cd116a930d21b3a9b928d4c87d02f1d63bb0a4b for reason 'txn-mempool-conflict' (18) 
Dec-09 18:35:15.060 [BlockingClient network thread for mxdtrjhe2yfsx3pg.onion:8333] ERROR o.b.core.Peer: [mxdtrjhe2yfsx3pg.onion]:8333 /Satoshi:0.15.0.1/: Received Reject: tx 72edf74de83fb85c31c11f128cd116a930d21b3a9b928d4c87d02f1d63bb0a4b for reason 'txn-mempool-conflict' (18) 
Dec-09 18:35:15.973 [BlockingClient network thread for poyvpdt762gllauu.onion:8333] ERROR o.b.core.Peer: [poyvpdt762gllauu.onion]:8333 /Satoshi:0.15.1(UASF-SegWit-BIP148)/: Received Reject: tx 72edf74de83fb85c31c11f128cd116a930d21b3a9b928d4c87d02f1d63bb0a4b for reason 'txn-mempool-conflict' (18)
```

---

<div class="post-metadata">

**Author:** ![ManfredKarrer](https://bisq.community/user_avatar/bisq.community/manfredkarrer/32/26_2.png) [@ManfredKarrer](https://bisq.community/u/ManfredKarrer)\
**Post date:** [December 9, 2017, 5:42pm UTC](https://bisq.community/t/cant-make-sell-btc-usd-offer-txn-mempool-conflict-error/3677/10 "2017-12-09T17:42:26Z")

</div>

Hm… no idea what causes that.  
If you dont have open offers/trades/disputes I would recommend you to start over new with a new data directory and wallet. Backup all send out all funds with cmd+e to another wallet, export the payment methods to re-import it later.

---

<div class="post-metadata">

**Author:** ![jmeemiller](https://bisq.community/letter_avatar/jmeemiller/32/6_22734026db12803ebb3e059622ac3534.png) [@jmeemiller](https://bisq.community/u/jmeemiller)\
**Post date:** [December 10, 2017, 10:59am UTC](https://bisq.community/t/cant-make-sell-btc-usd-offer-txn-mempool-conflict-error/3677/11 "2017-12-10T10:59:42Z")

</div>

I discovered after sending out all the funds to another wallet that there was an unconfirmed transaction from a dispute payout. It might have been that it was expecting this as an input. I have sent my balance to another wallet but it says it is seen by zero peers and has zero confirmations. [blockchain.info](http://blockchain.info) cannot find the transaction ID either. How can I push this transaction through?

---

<div class="post-metadata">

**Author:** ![jmeemiller](https://bisq.community/letter_avatar/jmeemiller/32/6_22734026db12803ebb3e059622ac3534.png) [@jmeemiller](https://bisq.community/u/jmeemiller)\
**Post date:** [December 10, 2017, 6:09pm UTC](https://bisq.community/t/cant-make-sell-btc-usd-offer-txn-mempool-conflict-error/3677/12 "2017-12-10T18:09:28Z")

</div>

After a lot of fiddling around, I think I know what has happened. As I mentioned in my original post, this happened after someone accepted my open BTC-\>USD offer but the UI crashed with an InsufficientMoney exception (I am not sure how this is possible since the funds were reserved) – log below.

```
Dec-07 15:25:01.934 [JavaFX Application Thread] INFO i.b.c.t.TaskRunner: Run task: MakerProcessPayDepositRequest 
Dec-07 15:25:01.935 [JavaFX Application Thread] INFO i.b.c.t.TaskRunner: Run task: CheckIfPeerIsBanned 
Dec-07 15:25:01.936 [JavaFX Application Thread] INFO i.b.c.t.TaskRunner: Run task: MakerVerifyArbitratorSelection 
Dec-07 15:25:01.937 [JavaFX Application Thread] INFO i.b.c.t.TaskRunner: Run task: MakerVerifyMediatorSelection 
Dec-07 15:25:01.938 [JavaFX Application Thread] INFO i.b.c.t.TaskRunner: Run task: MakerVerifyTakerAccount 
Dec-07 15:25:01.938 [JavaFX Application Thread] INFO i.b.c.t.TaskRunner: Run task: VerifyPeersAccountAgeWitness 
Dec-07 15:25:01.940 [JavaFX Application Thread] INFO i.b.c.p.AccountAgeWitnessService: accountAgeCategory=LESS_ONE_MONTH, accountAge=0 days, limit=0.25 BTC, factor=1.0, accountAgeWitnessHash=7cc546fa9491854a4237a92b5bdcf3108139a949 
Dec-07 15:25:01.941 [JavaFX Application Thread] INFO i.b.c.t.TaskRunner: Run task: MakerVerifyTakerFeePayment 
Dec-07 15:25:01.942 [JavaFX Application Thread] INFO i.b.c.t.TaskRunner: Run task: MakerCreateAndSignContract 
Dec-07 15:25:01.944 [JavaFX Application Thread] INFO o.b.w.WalletFiles: Saving wallet; last seen block is height 498081, date 2017-12-07T13:09:59Z, hash 0000000000000000007632b66321aa7a5bef21186d1e5071352dc9a7dbef0548 
Dec-07 15:25:01.951 [JavaFX Application Thread] INFO o.b.w.WalletFiles: Save completed in 6.729 ms 
Dec-07 15:25:01.952 [JavaFX Application Thread] INFO o.b.w.WalletFiles: Saving wallet; last seen block is height 498081, date 2017-12-07T13:09:59Z, hash 0000000000000000007632b66321aa7a5bef21186d1e5071352dc9a7dbef0548 
Dec-07 15:25:01.958 [JavaFX Application Thread] INFO o.b.w.WalletFiles: Save completed in 5.447 ms 
Dec-07 15:25:01.964 [JavaFX Application Thread] INFO i.b.c.t.TaskRunner: Run task: SellerAsMakerCreatesAndSignsDepositTx 
Dec-07 15:25:01.968 [JavaFX Application Thread] INFO i.b.c.b.w.TradeWalletService: print tx before wallet.completeTx: 6a4592c4ee818edf5fc2a7679793a581f9edc9355a4ac1072f3c3143522fa613
  INCOMPLETE: No inputs!
 
Dec-07 15:25:01.968 [JavaFX Application Thread] INFO o.b.w.Wallet: Completing send tx with 1 outputs totalling 0.0468 BTC and a fee of 0.00 BTC/kB 
Dec-07 15:25:01.969 [JavaFX Application Thread] WARN o.b.w.Wallet: Insufficient value in wallet for send: needed 0.0468 BTC more 
Dec-07 15:25:01.975 [JavaFX Application Thread] ERROR i.b.c.t.Task: An error occurred at task: SellerAsMakerCreatesAndSignsDepositTx
Exception message: org.bitcoinj.core.InsufficientMoneyException: Insufficient money, missing 0.0468 BTC 
Dec-07 15:25:01.975 [JavaFX Application Thread] ERROR i.b.c.t.TaskRunner: Task failed: SellerAsMakerCreatesAndSignsDepositTx / errorMessage: An error occurred at task: SellerAsMakerCreatesAndSignsDepositTx
Exception message: org.bitcoinj.core.InsufficientMoneyException: Insufficient money, missing 0.0468 BTC 
Dec-07 15:25:01.997 [JavaFX Application Thread] ERROR i.b.c.t.p.TradeProtocol: An error occurred at task: SellerAsMakerCreatesAndSignsDepositTx
Exception message: org.bitcoinj.core.InsufficientMoneyException: Insufficient money, missing 0.0468 BTC 
Dec-07 15:25:01.997 [JavaFX Application Thread] WARN i.b.c.t.p.TradeProtocol: cleanupTradableOnFault tradeState=PREPARATION 
Dec-07 15:25:02.005 [JavaFX Application Thread] WARN i.b.c.t.TradeManager: We found an outdated addressEntry for trade ufwyq2-d41d670e-e0fd-4284-a381-e38683b87f5b-061 
Dec-07 15:25:02.006 [JavaFX Application Thread] INFO i.b.c.b.w.BtcWalletService: swap addressEntry with address 19ZFQpZ27pH3g8kAXpmndntHcrBXxYq4sh and offerId ufwyq2-d41d670e-e0fd-4284-a381-e38683b87f5b-061 from context MULTI_SIG to available 
Dec-07 15:25:02.006 [JavaFX Application Thread] WARN i.b.c.t.TradeManager: We found an outdated addressEntry for trade ufwyq2-d41d670e-e0fd-4284-a381-e38683b87f5b-061 

```

Today, the maker and tx fee for this transaction were finally confirmed. I did not know about this transaction because it did not appear in my “Funds” tab. So I think the reason for the mempool conflict error was because I was trying to spend my balance but in fact it was sitting in the mempool awaiting confirmation on the blockchain.

So the question is: how do I get refunded for the “maker and tx fee” for the offer that failed to be processed because of the above exception?

TX ID: 6db6f2b2ac01925da3f1aa5cbfc9b4ccb5fe1bebe61eda0198d1c77a361e0a4e

---

<div class="post-metadata">

**Author:** ![jmeemiller](https://bisq.community/letter_avatar/jmeemiller/32/6_22734026db12803ebb3e059622ac3534.png) [@jmeemiller](https://bisq.community/u/jmeemiller)\
**Post date:** [December 11, 2017, 8:13am UTC](https://bisq.community/t/cant-make-sell-btc-usd-offer-txn-mempool-conflict-error/3677/13 "2017-12-11T08:13:24Z")

</div>

The txn mempool conflict error was almost certainly due to the low fee assigned to the maker fee and disputed payout transactions. Both of these have now been confirmed so I am now able to make offers and send funds out of my wallet. 🙂

The only issue I have is being charged a “maker and tx fee” for an offer that failed due to an “InsufficientMoneyException” as described in the previous post. What is the process for reclaiming this fee?

---

<div class="post-metadata">

**Author:** ![alexej996](https://bisq.community/user_avatar/bisq.community/alexej996/32/491_2.png) [@alexej996](https://bisq.community/u/alexej996)\
**Post date:** [December 13, 2017, 9:31pm UTC](https://bisq.community/t/cant-make-sell-btc-usd-offer-txn-mempool-conflict-error/3677/14 "2017-12-13T21:31:27Z")

</div>

You can follow the more recent thread where another user had an error as well and was charged the trading fee. I already gave some info there so I it would be best just to redirect you to it

> [@Error on transaction. Fee is lost?](https://bisq.community/t/error-on-transaction-fee-is-lost/3812):
>
> Hello, I started a transaction to buy 0.03BTC but the seller disconnected causing a timeout error. I recovered my diposit, but, what happened with the transaction Fee? I lost the 0.001188 transaction fee? There are the transaction details: Thanks in advance for your replies.

---

<div class="post-metadata">

**Author:** ![jmeemiller](https://bisq.community/letter_avatar/jmeemiller/32/6_22734026db12803ebb3e059622ac3534.png) [@jmeemiller](https://bisq.community/u/jmeemiller)\
**Post date:** [December 14, 2017, 4:29pm UTC](https://bisq.community/t/cant-make-sell-btc-usd-offer-txn-mempool-conflict-error/3677/15 "2017-12-14T16:29:19Z")

</div>

Thanks, I had not seen this so your comment was very helpful.