No Payout #1227
Comments
|
Can you post or DM your latest logs related to processing the DisputeClosedMessage? That will give us a better idea of what it's doing. |
|
I'm sorry, I'm not sure where to find logs.
Sent from Proton Mail Android
…-------- Original Message --------
On 8/19/24 5:51 PM, woodser wrote:
Can you post or DM your latest logs related to processing the DisputeClosedMessage? That will give us a better idea of what it's doing.
—
Reply to this email directly, [view it on GitHub](#1227 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/BIWUOL6LMSY6T6RTNCCMY7LZSJSFBAVCNFSM6AAAAABMYJYHBKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOJXGUYTSNZVG4).
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
|
You can find your logs in haveno.log within your application folder:
|
|
Aug-20 09:40:08.105 [dpkWHQrO-20ae8688-d6e7-4910-9b3d-e7f599296f2e-108] WARN h.c.s.d.a.ArbitrationManager: Error processing dispute closed message: Failed to sign and publish dispute payout tx from arbitrator for BuyerAsTakerTrade dpkWHQrO-20ae8688-d6e7-4910-9b3d-e7f599296f2e-108: Not enough signers signed this transaction.
Sent with [Proton Mail](https://proton.me/) secure email.
…On Tuesday, August 20th, 2024 at 9:38 AM, woodser ***@***.***> wrote:
You can find your logs in haveno.log within your application folder:
- Linux: ~/.local/share/Haveno/
- macOS: ~/Library/Application Support/Haveno/
- Windows: ~\AppData\Roaming\Haveno\
—
Reply to this email directly, [view it on GitHub](#1227 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/BIWUOLZF2DD77E2HNZSABTLZSNBF5AVCNFSM6AAAAABMYJYHBKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOJYHA4DMOBXGE).
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
|
Is there an error stack trace, or multiple of them? Is it repeating the same error over and over again in your logs? |
woodser
added a commit
to woodser/haveno
that referenced
this issue
Aug 21, 2024
|
You can try applying this patch, which will correctly reject the arbitrator's last dispute decision when your error happens, so that you can open a new dispute and try again: #1228 Here's the patch as a downloadable file: |
woodser
added a commit
to woodser/haveno
that referenced
this issue
Aug 21, 2024
|
I hate to be a pain in the ass, but this is all new to me. I haven't a clue how to apply a patch. I'm beginning research on the process, but it seems there is quite a bit I need to learn, I'm just starting with the terminology. I really need to know this stuff anyway, but if you have any advice or recommendations on sources for info, I would appreciate it. A shortcut or a simple explanation how to approach this particular operation would be awesome, as I could really use payout. Thanks again I really do appreciate how helpful and responsive you have been.
Sent from Proton Mail Android
…-------- Original Message --------
On 8/21/24 9:48 AM, woodser wrote:
You can try applying this patch, which will correctly reject the arbitrator's last dispute decision when your error happens, so that you can open a new dispute and try again: [#1228](#1228)
Here's the patch as a downloadable file:
[pr_1228.patch](https://github.com/user-attachments/files/16692503/pr_1228.patch)
—
Reply to this email directly, [view it on GitHub](#1227 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/BIWUOLYSYOXVPCGE35Y4DY3ZSSLBVAVCNFSM6AAAAABMYJYHBKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMBSGEYDKMBYGQ).
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
|
Sure no problem. Perhaps it's easiest to DM on matrix or email? Then we can walk through it step by step to test the fix, and we'll release the fix as part of the next release. First build Haveno by following these instructions, but after installing the dependencies, replace the official GitHub URL in the instructions with the URL of the third party network you're using. After building successfully, you can apply the fix by: Then launch Haveno with: Then the fix will be applied, so that it will reject the previous payout, and you can re-open the dispute to get the final payout. Again, please feel free to DM for more direct communication. |
woodser
added a commit
that referenced
this issue
Sep 4, 2024
|
So I need to build Haveno? What about what I already installed? It has my account and the trade that I need the payout on.
Sent from Proton Mail Android
…-------- Original Message --------
On 8/28/24 1:35 PM, woodser wrote:
Sure no problem. Perhaps it's easiest to DM on matrix or email? Then we can walk through it step by step to test the fix, and we'll release the fix as part of the next release.
First build Haveno by following these [instructions](https://github.com/haveno-dex/haveno/blob/master/docs/installing.md), but after installing the dependencies, replace the official GitHub URL in the instructions with the URL of the third party network you're using.
After building successfully, you can apply the fix by:
git remote add upstream https://github.com/haveno-dex/haveno.git
git fetch upstream
git pull --rebase upstream pull/1228/head
make skip-tests
Then launch Haveno with: make haveno-desktop-mainnet
Then the fix will be applied, so that it will reject the previous payout, and you can re-open the dispute to get the final payout.
Again, please feel free to DM for more direct communication.
—
Reply to this email directly, [view it on GitHub](#1227 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/BIWUOL6UAQS6Z6VUEAHIZZDZTYC6VAVCNFSM6AAAAABMYJYHBKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMJVHEYTGNRZG4).
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
|
The fix was incorporated in the last release, v1.0.11. Please update to the latest version. If your payout is still not complete, then you should be able to re-open the dispute. |
|
I updated and initially trade was still open. Now trade is no longer open, no payout and xmr in reserve is gone.
Sent from Proton Mail Android
…-------- Original Message --------
On 9/10/24 9:17 AM, woodser wrote:
The fix was incorporated in the last release, v1.0.11. Please update to the latest version. If your payout is still not complete, then you should be able to re-open the dispute.
—
Reply to this email directly, [view it on GitHub](#1227 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/BIWUOL53MJ77MUWU7P5G4ELZV3WNVAVCNFSM6AAAAABMYJYHBKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNBQG42DOMJTHA).
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
|
That would make sense if the payout was made. Can you confirm the payout state by going to Portfolio > History > select the trade > Info. Is there a Payout transaction ID? If you go to Detail Data, does it say |
|
Okay so I found trade in failed. Moved back to open, reserved is back but still no payout.
Sent from Proton Mail Android
…-------- Original Message --------
On 9/10/24 9:53 AM, waltsgarden wrote:
I updated and initially trade was still open. Now trade is no longer open, no payout and xmr in reserve is gone.
Sent from Proton Mail Android
-------- Original Message --------
On 9/10/24 9:17 AM, woodser wrote:
> The fix was incorporated in the last release, v1.0.11. Please update to the latest version. If your payout is still not complete, then you should be able to re-open the dispute.
>
> —
> Reply to this email directly, [view it on GitHub](#1227 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/BIWUOL53MJ77MUWU7P5G4ELZV3WNVAVCNFSM6AAAAABMYJYHBKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNBQG42DOMJTHA).
> You are receiving this because you authored the thread.Message ID: ***@***.***>
|
|
Ok, you should be able re-open the dispute to resolve the trade then. |
|
There is now an orange link with an exclamation point that says trade is in an invalid state.
Sent from Proton Mail Android
…-------- Original Message --------
On 9/10/24 9:53 AM, waltsgarden wrote:
I updated and initially trade was still open. Now trade is no longer open, no payout and xmr in reserve is gone.
Sent from Proton Mail Android
-------- Original Message --------
On 9/10/24 9:17 AM, woodser wrote:
> The fix was incorporated in the last release, v1.0.11. Please update to the latest version. If your payout is still not complete, then you should be able to re-open the dispute.
>
> —
> Reply to this email directly, [view it on GitHub](#1227 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/BIWUOL53MJ77MUWU7P5G4ELZV3WNVAVCNFSM6AAAAABMYJYHBKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNBQG42DOMJTHA).
> You are receiving this because you authored the thread.Message ID: ***@***.***>
|
|
Yeah that's just because an error was associated with the trade. Feel free to copy and paste the error here (from within the trade's Info screen), but it should be fine to ignore. |
|
Ok I reopened dispute, and messaged arbitrator letting them know that I updated to latest version.
Sent from Proton Mail Android
-------- Original Message --------
On 9/10/24 10:07 AM, woodser wrote:
Yeah that's just because an error was associated with the trade. Feel free to copy and paste the error here (from within the trade's Info screen), but it should be fine to ignore.
—
Reply to this email directly, [view it on GitHub](#1227 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/BIWUOL3OAA737GQ4XBBVZILZV34IZAVCNFSM6AAAAABMYJYHBKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNBQHEZDKNZUGU).
You are receiving this because you authored the thread.Message ID: ***@***.***>
@github.com>
|
|
Great. You should receive the payout when they resolve your dispute this time. |
|
I still did not receive payout, and trade is still open with same error message.
Sent from Proton Mail Android
…-------- Original Message --------
On 9/10/24 10:27 AM, woodser wrote:
Great. You should receive the payout when they resolve your dispute this time.
—
Reply to this email directly, [view it on GitHub](#1227 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/BIWUOL4Y5QYHH6DX65KI2ELZV36ULAVCNFSM6AAAAABMYJYHBKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNBQHE4TGOJXGU).
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
|
It seems the wallet was corrupted somehow. This is the first case I've seen with this error, "Not enough signers". The error would suggest either the multisig wallet wasn't initialized correctly, or one of your apps is not signing the dispute payout transaction correctly for some unknown reason. In a worst case, you and the arbitrator may need to manually restore the multisig wallet by using monero-wallet-cli to import the wallet files, exchange updated info, and create the payout transaction. In addition, I've added checks when the multisig is created to assert the expected state: #1272 |
|
Okay, I'm now on simplex chat, and talking with tintedbrief, the arbitrator for dispute. Thanks again I really appreciate you guys and what you do!
Sent from Proton Mail Android
…-------- Original Message --------
On 9/12/24 10:42 AM, woodser wrote:
It seems the wallet was corrupted somehow. This is the first case I've seen with this error, "Not enough signers".
The error would suggest either the multisig wallet wasn't initialized correctly, or one of your apps is not signing the dispute payout transaction correctly for some unknown reason.
In a worst case, you and the arbitrator may need to manually restore the multisig wallet by using monero-wallet-cli to import the wallet files, exchange updated info, and create the payout transaction.
In addition, I've added additional checks when the multisig is created to assert the expected state: [#1272](#1272)
—
Reply to this email directly, [view it on GitHub](#1227 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/BIWUOL4QR7EHVUXORSFESN3ZWGR67AVCNFSM6AAAAABMYJYHBKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNBWGQ4TSMJUHE).
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
|
I was finally able to reproduce and fix a bug which could have originally caused this, fixed in: #1287 |
|
What do I need to do?
Sent from Proton Mail Android
…-------- Original Message --------
On 9/25/24 9:47 AM, woodser wrote:
I was finally able to reproduce and fix a bug which could have originally caused this, fixed in: [#1287](#1287)
—
Reply to this email directly, [view it on GitHub](#1227 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/BIWUOL6HOMFAYGTPBER7VGLZYK5HZAVCNFSM6AAAAABMYJYHBKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNZUGE2DENJUHE).
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
|
I'm not sure if it will fix your app with the state it's in, but you can test it when the next version of Haveno is released, or by applying the PR yourself. |
|
I think there's a good chance it will fix your situation, if you want to apply it manually before the next release. Otherwise will have to wait a week or two until the next version is released. |
|
I don't know how to apply it myself. Arbitrator tried to help me do something with signing but I got lost and never succeeded.
Sent from Proton Mail Android
…-------- Original Message --------
On 9/25/24 9:58 AM, woodser wrote:
I'm not sure if it will fix your app with the state it's in, but you can test it when the next version of Haveno is released, or by applying the PR yourself.
—
Reply to this email directly, [view it on GitHub](#1227 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/BIWUOL6ANR3A3VPGLEQ5BY3ZYK6P7AVCNFSM6AAAAABMYJYHBKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNZUGE3TCNZZGE).
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
|
Yes it would great if I could apply it manually, I could really use funds at the moment. But I really have no idea how to do it.
Sent from Proton Mail Android
…-------- Original Message --------
On 9/25/24 10:02 AM, woodser wrote:
I think there's a good chance it will fix your situation, if you want to apply it manually before the next release. Otherwise will have to wait a week or two until the next version is released.
—
Reply to this email directly, [view it on GitHub](#1227 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/BIWUOL5RJQ26JHHOKYSBS3LZYK7AFAVCNFSM6AAAAABMYJYHBKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNZUGE4DGNZXGM).
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
|
Can you PM me? We can work through it. I'm on matrix, woodser:monero.social, or protonmail by the same name. |
|
Is there any way I can get the deposit back in the meantime?
Sent from Proton Mail Android
…-------- Original Message --------
On 9/25/24 10:02 AM, woodser wrote:
I think there's a good chance it will fix your situation, if you want to apply it manually before the next release. Otherwise will have to wait a week or two until the next version is released.
—
Reply to this email directly, [view it on GitHub](#1227 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/BIWUOL5RJQ26JHHOKYSBS3LZYK7AFAVCNFSM6AAAAABMYJYHBKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNZUGE4DGNZXGM).
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
|
There's a decent chance you'll get the deposit + payout (if applicable) by applying the change. Otherwise they're both locked in the multisig. |
|
Sorry didn't read this before I sent that last message. I'm going to go where I have better Wi-Fi and then I will get back to you. Thanks
Sent from Proton Mail Android
…-------- Original Message --------
On 9/25/24 11:14 AM, woodser wrote:
Can you PM me? We can work through it. I'm on matrix, ***@***.***(https://github.com/woodser):monero.social, or protonmail by the same name.
—
Reply to this email directly, [view it on GitHub](#1227 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/BIWUOL7TQ3UPWHHOIXEFT2LZYLHONAVCNFSM6AAAAABMYJYHBKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNZUGM4DGOJZHA).
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
|
I've installed matrix username damyth518
Sent from Proton Mail Android
…-------- Original Message --------
On 9/25/24 11:16 AM, woodser wrote:
There's a decent chance you'll get the deposit + payout (if applicable) by applying the change. Otherwise they're both locked in the multisig.
—
Reply to this email directly, [view it on GitHub](#1227 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/BIWUOL53B354PUHGRKSAO33ZYLHVZAVCNFSM6AAAAABMYJYHBKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNZUGM4DSMJXHE).
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
|
Hello I sent you an invite from damyth518.
Sent from Proton Mail Android
…-------- Original Message --------
On 9/25/24 11:16 AM, woodser wrote:
There's a decent chance you'll get the deposit + payout (if applicable) by applying the change. Otherwise they're both locked in the multisig.
—
Reply to this email directly, [view it on GitHub](#1227 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/BIWUOL53B354PUHGRKSAO33ZYLHVZAVCNFSM6AAAAABMYJYHBKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNZUGM4DSMJXHE).
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
|
Yes I'm available now. You haven't replied to my DM. |
|
Sorry where did you do me?
Sent from Proton Mail Android
…-------- Original Message --------
On 9/26/24 10:00 AM, woodser wrote:
Yes I'm available now. You haven't replied to my DM.
—
Reply to this email directly, [view it on GitHub](#1227 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/BIWUOLYISJMAYBYDS6L3QYTZYQHRBAVCNFSM6AAAAABMYJYHBKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNZXGA3DGMJSHA).
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
|
I'm in the damyth518 room you created. I also just sent you a DM. |
|
Any luck? |
|
If I backed up Haveno-Reto onto a thumbdrive from the device i was accessing it on can i install it on another device and access the same account? I no longer have access to that device but i backed it up before installing the version you sent me with the fix. |
|
You could install from the installer onto another Windows machine, but you'll need to restore your application directory to access your old account data. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
#1187 (comment).
Pertaining to this issue, I updated to lastest version, reopened dispute, and messaged arbitrator. The said they would try to release payout again. But dispute was closed and trade is still open and I haven't received payout.
The text was updated successfully, but these errors were encountered: