Josh Jeffryes

For what it's worth, I get the same result trying to open these orders on the seller side from the transactions screen. They show up normal in the sales call....

After seeing this error, I am also getting a 400 bad request error when trying to make a BCH purchase.

``` 2019-12-19 17:21:06.343 [ERROR] [core/SendOrder] failed to send order request: dial attempt failed: --> dial attempt failed: dial tcp4 108.18.249.29:4101: connect: connection refused 2019-12-19 17:21:06.343 [WARNING] [core/processOfflineModeratedOrder] Vendor QmaWkAWZ5ZS1dGmYkkJRBMVGMmAbjpRCPCNeGsxgYLCcx9 is...

I'm still seeing this on master, I can confirm if the node resyncs their wallet the dispute is updated as finalized and they don't see this error because they don't...

This bug is still present in 2.3.5 RC2. I reproduced it as follows: 1. The seller node was turned off. 2. The buyer made an order and disputed it.The order...

When this happens, the seller's node has the order stuck in DECIDED, and can't accept the payout.

This is still 100% reproducible using current master for the seller and moderator, and current develop for Haven.

I get this error on 2 different listings (same seller) if I try to make a moderated purchase, but making a direct purchase works normally with both.

Here's the log from the buyer's server when a purchase is made with an invalid payment: ``` 2020-02-24 15:40:40.884 [DEBUG] [recordAgingNotifier/PerformTask] notifications created/records updated: dispute: 0/0, sales: 0/0, purchaseTimeout: 0/0,...

``` { "listing": { "slug": "jj-test-usd-to-eth-conversion", "vendorID": { "peerID": "QmdE1iJkTvbvRVf9pj6t7vCiv46VepP53t8AZsnkobC5Zw", "handle": "", "pubkeys": { "identity": "CAESIKWy9WR9N9wxhM1/5mqnx83NsUV5YeIsDc6Cc831AhUw", "bitcoin": "AkCez6qEcbOoY4ejKd6aw//uzb6riZ/HIZ+hpU9B9Mfh" }, "bitcoinSig": "MEUCIQDtjbdwjDOQvgXzwMgNj6OfZ3x+l4JCfGx0y7QHf+3CjgIgG8LVdK7YAzxrfFbtWwhTs3wJkmNlvy5vu5WKE8Ug8XI=" }, "metadata": { "version": 5, "contractType": "PHYSICAL_GOOD", "format": "FIXED_PRICE",...