# An error occured at task: MakerCreateAndSignContract

**URL:** <https://bisq.community/t/an-error-occured-at-task-makercreateandsigncontract/7431>\
**Category:** Support\
**Created:** [April 19, 2019, 3:20am UTC](https://bisq.community/t/an-error-occured-at-task-makercreateandsigncontract/7431 "2019-04-19T03:20:48Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![CryptoGal](https://bisq.community/letter_avatar/cryptogal/32/5_5575768a8748004e209b776fc1b2916d.png) [@CryptoGal](https://bisq.community/u/CryptoGal)\
**Post date:** [April 19, 2019, 3:20am UTC](https://bisq.community/t/an-error-occured-at-task-makercreateandsigncontract/7431/1 "2019-04-19T03:20:48Z")

</div>

Have an offer up and I have had a message box pop up a couple of times already saying:  
An error occured when someone tried to take one of your offers:  
An error occured at task: MakerCreateAndSignContract  
Exception message: makerPaymentAccountPayload must not be null

Here is the entry from the log regarding the transaction:  
[JavaFX Application Thread] WARN bisq.network.p2p.P2PService: We don’t have the peer in our persisted peers so we don’t know his capabilities. We decide to not sent the msg. peersNodeAddress=xxxxxxx:9999  
[JavaFX Application Thread] ERROR b.core.offer.OpenOfferManager: AckMessage for OfferAvailabilityRequest failed. AckMessage=AckMessage{  
uid=‘xxxxxxx’,  
senderNodeAddress=xxxxxxxx:9999,  
sourceType=OFFER\_MESSAGE,  
sourceMsgClassName=‘OfferAvailabilityRequest’,  
sourceUid=‘xxxxxxx’,  
sourceId=‘xxxxxx’,  
success=true,  
errorMessage=‘null’  
} NetworkEnvelope{  
messageVersion=10  
}, takersNodeAddress=xxxxxx:9999, errorMessage=We did not send the EncryptedMessage because the peer does not support the capability.

I am running version 1.0.1

---

<div class="post-metadata">

**Author:** ![Homard](https://bisq.community/letter_avatar/homard/32/5_5575768a8748004e209b776fc1b2916d.png) [@Homard](https://bisq.community/u/Homard)\
**Post date:** [April 19, 2019, 7:12am UTC](https://bisq.community/t/an-error-occured-at-task-makercreateandsigncontract/7431/2 "2019-04-19T07:12:23Z")

</div>

It may be related to the scam attempts at work atm.  
See [URGENT: Certain banks banned until further notice](https://bisq.community/t/urgent-certain-banks-banned-until-further-notice/7420/8)  
Please look if the mentioned onion in your log is one of the scammer’s onion.

---

<div class="post-metadata">

**Author:** ![CryptoGal](https://bisq.community/letter_avatar/cryptogal/32/5_5575768a8748004e209b776fc1b2916d.png) [@CryptoGal](https://bisq.community/u/CryptoGal)\
**Post date:** [April 19, 2019, 7:19am UTC](https://bisq.community/t/an-error-occured-at-task-makercreateandsigncontract/7431/3 "2019-04-19T07:19:07Z")

</div>

I only had altcoin trades active at the time. None of the banned .onion’s showed up in my log either.

---

<div class="post-metadata">

**Author:** ![SeveredinTwain](https://bisq.community/letter_avatar/severedintwain/32/5_5575768a8748004e209b776fc1b2916d.png) [@SeveredinTwain](https://bisq.community/u/SeveredinTwain)\
**Post date:** [April 19, 2019, 3:36pm UTC](https://bisq.community/t/an-error-occured-at-task-makercreateandsigncontract/7431/4 "2019-04-19T15:36:04Z")

</div>

This error has occurred for me as well. I made an offer to buy BSQ and I get that same exact recurring error.

---

<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:** [April 21, 2019, 10:56am UTC](https://bisq.community/t/an-error-occured-at-task-makercreateandsigncontract/7431/5 "2019-04-21T10:56:45Z")

</div>

You might want to create an issue on [GitHub](https://github.com/bisq-network/bisq/issues), if this keeps happening.