Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't Send Message in Dispute Window #1409

Open
SirCreatus opened this issue Nov 12, 2024 · 23 comments
Open

Can't Send Message in Dispute Window #1409

SirCreatus opened this issue Nov 12, 2024 · 23 comments

Comments

@SirCreatus
Copy link

SirCreatus commented Nov 12, 2024

After completing a zelle trade I encountered a bug where I lost connection to my seller and I also couldn't open a dispute. This issue was posted here (see prior). In the recent update I can now open a support ticket for the trade! However I have now run into another issue where I cannot message in the dispute chat.
cantmsg
Where to from next? Thanks again for all the support,

@SirCreatus
Copy link
Author

also times out attempting to send log files

@woodser
Copy link
Contributor

woodser commented Nov 13, 2024

From the screenshot, the dispute was only requested, and not acknowledged by the arbitrator in order to be formally opened.

The arbitrator should have a warning in their logs related to processing the DisputeOpenedMessage for trade with ID 24290. It would be very helpful to see their logs related to this.

@woodser
Copy link
Contributor

woodser commented Nov 13, 2024

Can you send your log files from when you tried to open the dispute?

@SirCreatus
Copy link
Author

I cannot send log files it times out just the same

@woodser
Copy link
Contributor

woodser commented Nov 14, 2024

The logs from #1393 indicate that the seller confirmed the payment was received, so the payout should have been made and the deposit returned to your main wallet already.

Please let me know the current state of your trade 24290, if it shows that the payout was published or not, by following these steps:

  1. If you haven't already, please first update to the latest version, v1.0.13.
  2. Restart your application.
  3. Find your trade 24290 under Portfolio > Open trades or History > click the (i) to open the trade details > Detail data > copy and paste the first 3 lines here to confirm the current state of the trade.

I hope / expect it will show that the payout is unlocked, so the trade is fully closed.

If the final payout was already published, you won't be able to open a new dispute or communicate with the arbitrator or trader, because the trade is completed, so that would explain the behavior you're seeing in this issue due to the previously corrupted state. In that case, all that remains to be done is automatically close your requested dispute (from your screenshot), because the trade is closed.

If however it shows that the payout was not published, then it would be helpful to manually share your logs, named haveno.log within your application directory.

So please let me know the current state of your trade 24290, if it shows that the payout was made or not.

@SirCreatus
Copy link
Author

SirCreatus commented Nov 14, 2024

No funds were released to me. The trade is still said to be open. So it isn't in History.

Trade ID 24290-275cbd57-675d-4d1d-b914-bbefe0abb4df-1011
Trade Date Oct 26, 2024 12:14:06 AM
Security Deposit Buyer: 0.434865 XMR / Seller: 0.434865 XMR
Arbitrator / Mediator l2cyrswpqya7bxkz5u7hbupq2impjeqagjuhtk6vgxmj4ngnpfbcklid.onion:9999

Hope those are the details you meant. The trade did not close. Payout / funds have never been released. That's the issue.
opentrade2
I have the proof to show an arbitrator the seller received their cash.

@SirCreatus
Copy link
Author

SirCreatus commented Nov 14, 2024

In the dispute window itself there's a total disconnect. I'm unable to send any info or logs due to timing out
arbitrationtimeout2
Below is the details from the arbitration window.
disputedetails3
The contract in JSON format I'll attach in a .txt below as well
contract for trade with ID 24290.txt

@woodser
Copy link
Contributor

woodser commented Nov 15, 2024

Under Portfolio > Open trades > click the (i) > Detail data > can you copy/paste the first three lines?

And logs from haveno.log within your application directory would be helpful too, located at:

  • Linux: ~/.local/share/Haveno/
  • macOS: ~/Library/Application Support/Haveno/
  • Windows: ~\AppData\Roaming\Haveno\

@SirCreatus
Copy link
Author

SirCreatus commented Nov 15, 2024

I understand now. That was my mistake not knowing what three lines you're looking for

Trade state: SELLER_RECEIVED_PAYMENT_SENT_MSG
Trade payout state: PAYOUT_UNPUBLISHED
Trade dispute state: DISPUTE_REQUESTED

Oddly they don't show up as .log files on my computer but txt instead. But I believe this is the haveno.log:
haveno.log

@woodser
Copy link
Contributor

woodser commented Nov 17, 2024

Can you please update to v1.0.14 and retry opening the dispute?

You can manually re-open the dispute by clicking on your trade and then typing ctrl + o.

@SirCreatus
Copy link
Author

I have updated to 1.0.14. I can re-open the dispute with ctrl + o but the issues persist with timing out, unable to send messages or log files.

@woodser
Copy link
Contributor

woodser commented Nov 18, 2024

Thanks, can you please send your latest logs after re-opening the dispute (haveno.log file from your app directory)?

@woodser
Copy link
Contributor

woodser commented Nov 18, 2024

It would also be helpful if you could find out the arbitrator's state of the trade 24290. Without being able to message them in the app, you'd need to contact them externally. Any logs they can provide related to the trade would also be helpful.

@woodser
Copy link
Contributor

woodser commented Nov 18, 2024

Especially I'd like to know if the arbitrator has this line in their logs:

Dispute trade 24290-275cbd57-675d-4d1d-b914-bbefe0abb4df-1011 payout already published

@boldsuck
Copy link
Contributor

I asked the Arb: l2cyrswpqya7bxkz5u7hbupq2impjeqagjuhtk6vgxmj4ngnpfbcklid.onion:9999

Trade state: seller_sent_payment_received_msg
trade payout state: payout unlocked
trade dispute state no_dispute

@woodser
Copy link
Contributor

woodser commented Nov 19, 2024

Ok that's what I suspected, the payout was made, despite a broken trade instance on the client. Regardless, the funds would have been received to the main wallet.

@SirCreatus
Copy link
Author

I did not receive payout for trade 24290-275cbd57-675d-4d1d-b914-bbefe0abb4df-1011 that is why this process began. I can see in my funds where the trade shows up; One place; Where I made my security deposit. There was no payout.

Contract for trade with ID: 24290
`Trade state: SELLER_RECEIVED_PAYMENT_SENT_MSG
Trade payout state: PAYOUT_UNPUBLISHED
Trade dispute state: DISPUTE_REQUESTED

Contract as json:
{
"offerPayload": {
"id": "24290-275cbd57-675d-4d1d-b914-bbefe0abb4df-1011",
"date": 1729869468012,
"ownerNodeAddress": {
"hostName": "vbonaht55bcahvax3xy5a4kxjivlnp6xuctm37fv6bvakd6g7upru5yd.onion",
"port": 9999
},
"direction": "SELL",
"price": 0,
"marketPriceMargin": 0.07,
"useMarketBasedPrice": true,
"amount": 2899100000000,
"minAmount": 550000000000,
"makerFeePct": 0.005,
"takerFeePct": 0.001,
"penaltyFeePct": 0.02,
"buyerSecurityDepositPct": 0.15,
"sellerSecurityDepositPct": 0.15,
"baseCurrencyCode": "XMR",
"counterCurrencyCode": "USD",
"paymentMethodId": "ZELLE",
"makerPaymentAccountId": "9970590b-1eea-472a-b4a2-10f5af569ee5",
"versionNr": "1.0.11",
"blockHeightAtOfferCreation": 3266878,
"maxTradeLimit": 12000000000000,
"maxTradePeriod": 345600000,
"useAutoClose": false,
"useReOpenAfterAutoClose": false,
"lowerClosePrice": 0,
"upperClosePrice": 0,
"isPrivateOffer": false,
"extraDataMap": {
"capabilities": "0, 1, 2, 5, 6, 7, 10, 11, 12, 13, 14, 15, 16",
"accountAgeWitnessHash": "725453ce6a6f2aefb0b36251df70f8e784be312a"
},
"protocolVersion": 1,
"arbitratorSigner": {
"hostName": "53xjwdhry2aoqmysvqetzttgusriix3v2akgrzd4k5tvoqqvsfzxb6yd.onion",
"port": 9999
},
"arbitratorSignature": [
48,
60,
2,
28,
123,
-110,
-81,
-73,
65,
127,
47,
32,
89,
118,
-60,
-23,
90,
67,
-109,
13,
62,
122,
-37,
3,
-88,
76,
42,
-3,
14,
-44,
-111,
87,
2,
28,
30,
35,
40,
16,
-23,
50,
-111,
89,
119,
-26,
-25,
-123,
43,
91,
-31,
33,
122,
-41,
58,
49,
-41,
66,
-23,
-21,
12,
-62,
-47,
-15
]
},
"tradeAmount": 1948500000000,
"tradePrice": 16950405000,
"buyerNodeAddress": {
"hostName": "3pnidyhgryxwzbs73g6suaalowh6ct6srwlwbhgo7uuy5zzpgidi2wyd.onion",
"port": 9999
},
"sellerNodeAddress": {
"hostName": "vbonaht55bcahvax3xy5a4kxjivlnp6xuctm37fv6bvakd6g7upru5yd.onion",
"port": 9999
},
"arbitratorNodeAddress": {
"hostName": "l2cyrswpqya7bxkz5u7hbupq2impjeqagjuhtk6vgxmj4ngnpfbcklid.onion",
"port": 9999
},
"isBuyerMakerAndSellerTaker": false,
"makerAccountId": "270350353",
"takerAccountId": "329462319",
"makerPaymentMethodId": "ZELLE",
"takerPaymentMethodId": "ZELLE",
"makerPaymentAccountPayloadHash": [
-72,
32,
47,
45,
18,
65,
76,
-94,
15,
-50,
-38,
22,
121,
-21,
24,
-12,
104,
-54,
-88,
-91
],
"takerPaymentAccountPayloadHash": [
-42,
22,
-123,
108,
-54,
29,
101,
-127,
-117,
25,
13,
-87,
-47,
-116,
84,
29,
-8,
-48,
2,
-59
],
"makerPayoutAddressString": "84JgAdFFnxwKAbDKW85M29HWQQJfHBLoSQAUySAnqrruXM4E3vCzshPgso1S6xYSj3et8BYKwJ2Cx9G1mg8aKeDLCf3RSH7",
"takerPayoutAddressString": "86kve61iF23gokkuQ7cTGcNaw4NARxkbAVPmwAjtm2YffVNWSYwRrBe3Xfr5jnc5pPMTwmNshhRXx6iK6MW3oCg78h6M61C",
"makerDepositTxHash": "4625869adde30f86dbaa997a46e7bea1750289ac12a73cface7a7f693d4c9a7a",
"takerDepositTxHash": "cddf2b7e481413a17a18feca674b3ed98990c0ec09adec5d5acaafdf04dae933"
}

Other detail data:

Buyers witness hash,pub key ring hash: null,308203423082023506072a8648ce3804013082022802820101008f7935d9b9aae9bfabed887acf4951b6f32ec59e3baf3718e8eac4961f3efd3606e74351a9c4183339b809e7c2ae1c539ba7475b85d011adb8b47987754984695cac0e8f14b3360828a22ffa27110a3d62a993453409a0fe696c4658f84bdd20819c3709a01057b195adcd00233dba5484b6291f9d648ef883448677979cec04b434a6ac2e75e9985de23db0292fc1118c9ffa9d8181e7338db792b730d7b9e349592f68099872153915ea3d6b8b4653c633458f803b32a4c2e0f27290256e4e3f8a3b0838a1c450e4e18c1a29a37ddf5ea143de4b66ff04903ed5cf1623e158d487c608e97f211cd81dca23cb6e380765f822e342be484c05763939601cd667021d00baf696a68578f7dfdee7fa67c977c785ef32b233bae580c0bcd5695d0282010016a65c58204850704e7502a39757040d34da3a3478c154d4e4a5c02d242ee04f96e61e4bd0904abdac8f37eeb1e09f3182d23c9043cb642f88004160edf9ca09b32076a79c32a627f2473e91879ba2c4e744bd2081544cb55b802c368d1fa83ed489e94e0fa0688e32428a5c78c478c68d0527b71c9a3abb0b0be12c44689639e7d3ce74db101a65aa2b87f64c6826db3ec72f4b5599834bb4edb02f7c90e9a496d3a55d535bebfc45d4f619f63f3dedbb873925c2f224e07731296da887ec1e4748f87efb5fdeb75484316b2232dee553ddaf02112b0d1f02da30973224fe27aeda8b9d4b2922d9ba8be39ed9e103a63c52810bc688b7e2ed4316e1ef17dbde0382010500028201000f3446886e775774268a0fe2af1fdbf11ec5e657b50f8d65347da304020b69bb537055dfb732ad43dfe41b5485e4615ea9d524069c6a5ac6597f1b0892b85c6b32dc0ce3c51c82770622decfb50bb6ba6447d12e5cd1a63fb53f2c64555bed01a9c08016c6dc28a6c8cb62d99237efa0b1d4753c6e50c510b374a17db36dd0bf73fec30593dffbfeedce3265dfa94193017d4e5c0ce8ce42499f84e4cf94b83b88e49e1b70b1aac8e4f0998247bf1dc924f1176425b2f650486d7cb359f2539508d51acebc58eec43bb2c89013c87e223010db00a1f41b039eb12bdf03c4cbc4b49e589ec9604d6ceea07981c62806c199da39dcfe28e6f91dde9ced022d7f55
Buyers account age: Time since signing: 44 days
Sellers witness hash,pub key ring hash: 725453ce6a6f2aefb0b36251df70f8e784be312a,308203423082023506072a8648ce3804013082022802820101008f7935d9b9aae9bfabed887acf4951b6f32ec59e3baf3718e8eac4961f3efd3606e74351a9c4183339b809e7c2ae1c539ba7475b85d011adb8b47987754984695cac0e8f14b3360828a22ffa27110a3d62a993453409a0fe696c4658f84bdd20819c3709a01057b195adcd00233dba5484b6291f9d648ef883448677979cec04b434a6ac2e75e9985de23db0292fc1118c9ffa9d8181e7338db792b730d7b9e349592f68099872153915ea3d6b8b4653c633458f803b32a4c2e0f27290256e4e3f8a3b0838a1c450e4e18c1a29a37ddf5ea143de4b66ff04903ed5cf1623e158d487c608e97f211cd81dca23cb6e380765f822e342be484c05763939601cd667021d00baf696a68578f7dfdee7fa67c977c785ef32b233bae580c0bcd5695d0282010016a65c58204850704e7502a39757040d34da3a3478c154d4e4a5c02d242ee04f96e61e4bd0904abdac8f37eeb1e09f3182d23c9043cb642f88004160edf9ca09b32076a79c32a627f2473e91879ba2c4e744bd2081544cb55b802c368d1fa83ed489e94e0fa0688e32428a5c78c478c68d0527b71c9a3abb0b0be12c44689639e7d3ce74db101a65aa2b87f64c6826db3ec72f4b5599834bb4edb02f7c90e9a496d3a55d535bebfc45d4f619f63f3dedbb873925c2f224e07731296da887ec1e4748f87efb5fdeb75484316b2232dee553ddaf02112b0d1f02da30973224fe27aeda8b9d4b2922d9ba8be39ed9e103a63c52810bc688b7e2ed4316e1ef17dbde03820105000282010063bd60bae4b56b870d612d593775792bed477f5d3b1db8595bfda30831306bfea8c193cf875be588f36ce93c56a0ee60be4ba8855c3e951a74640ebf1c0350f6f8b56f2595c0bf78ecd560560b5d3e4064fa9d6e01814d3a6df29d628e0e4d62240cc358e7c6ab97b0d3e1c3c6990917a94a563731c57effe2fde73b4a5e117cdb6c6c10fd80c89fb0185090fc94022f057239b5116a0c1abf65e924ff741e535a8c380ea2415cdc5529cee9fd62fec91ff9b75fcfa5d356abdda9840a08fa37174167138c20bd7c60ef76acac11c3a683fa656fbed88e1a1ea3c8fc35d3ac6794281e57bc81bf2af5b3e98599d0cfd8a88b7495828a7807352ee1d5b0db62d9
Sellers account age: Payment account created 95 days ago., Not signed yet

Selected arbitrator: l2cyrswpqya7bxkz5u7hbupq2impjeqagjuhtk6vgxmj4ngnpfbcklid.onion:9999`

@SirCreatus
Copy link
Author

here is haveno.log from my app directory
haveno.log

@SirCreatus
Copy link
Author

SirCreatus commented Nov 19, 2024

It would also be helpful if you could find out the arbitrator's state of the trade 24290. Without being able to message them in the app, you'd need to contact them externally. Any logs they can provide related to the trade would also be helpful.

How do I do this? I also already emailed the seller but he's either ghosted me or cannot respond / receive my messages since the trade corrupted. (Since I emailed him I'd consider that more being ghosted.... he should get my email and know exactly who I am since it was a zelle trade)

@SirCreatus
Copy link
Author

I asked the Arb: l2cyrswpqya7bxkz5u7hbupq2impjeqagjuhtk6vgxmj4ngnpfbcklid.onion:9999

Trade state: seller_sent_payment_received_msg trade payout state: payout unlocked trade dispute state no_dispute

Did you tell him what the actual issue is? It's taken two github threads to even open a support ticket and then the support thread has only bugged / timed out since opening

tradestillopen
supportimedout

@woodser
Copy link
Contributor

woodser commented Nov 19, 2024

@SirCreatus

You should see an incoming transaction to your main wallet address 86kve61iF23gokkuQ7cTGcNaw4NARxkbAVPmwAjtm2YffVNWSYwRrBe3Xfr5jnc5pPMTwmNshhRXx6iK6MW3oCg78h6M61C on 10/27 in the amount of ~2.24 XMR.

Can you please confirm if you have that transaction within your Funds > Transactions tab?

This is the payout for trade 24290, including the amount bought and your security deposit.

When the seller confirmed the payment was received, their client published the payout transaction, or the arbitrator would have published the payout transaction as a fallback.

The arbitrator's logs indicate the payout was made, which is what I expected after analyzing the logs.

Assuming you received that payout, the only issue is that your client's trade is in a broken state, so we'll have to fix that separately.

Fortunately the bug which led to your trade's broken state has been fixed and won't be an issue in the future.

@SirCreatus
Copy link
Author

SirCreatus commented Nov 19, 2024

@Wooder you're right! the transaction is there. It isn't labeled but mysteriously showed. It was hard for me to see / notice this payout ever happened because i made trades of the same amount on that same day; I could only see those labeled with their trade #s and this one didn't name anything. Since haveno told me the trade did not complete and couldn't find any evidence that it had I assumed it had not.

@boldsuck
Copy link
Contributor

How do I do this?

Preferably in the reto Simplex chat. @TintedBrief, @m
But I already did that for you and linked this issue to them ;-)

I also already emailed the seller but he's either ghosted me or cannot respond / receive my messages since the trade corrupted. (Since I emailed him I'd consider that more being ghosted.... he should get my email and know exactly who I am since it was a zelle trade)

Unfortunately that is bad behavior. It should be in the interest of every trader to help each other.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants