02:37:33 <rsch> hi
02:38:39 <rsch> I need to ask someone. Since weeks we face issues because of a multi sig error using retoswap. they blame the qubic attack and the monero protocol to be responsible. does anyone know how to fix and when to fix it? my funds are locked because an arbitor cannot release them with his signature. 
02:38:58 <m-relay> <o​frnxmr:xmr.mx> #haveno
02:40:34 <rsch> why haveno? I would like to ask if the problem is related to monero directly
02:41:09 <m-relay> <o​frnxmr:xmr.mx> Partially
02:41:13 <rsch> I have already contacted haveno and they dont know further. They try to build a patch but I am wondering if the issue is because of a software bug or because monero has rolled back transactions
02:41:38 <m-relay> <o​frnxmr:xmr.mx> you contacted reto
02:41:44 <rsch> yes
02:41:55 <rsch> reto is the client haveno is the protocol
02:41:56 <m-relay> <o​frnxmr:xmr.mx> Haveno has a fix coming today-or-so
02:42:29 <rsch> thats amazing. can I ask you what the issue is about? is it because the qubic attack? 
02:42:59 <m-relay> <o​frnxmr:xmr.mx> https://github.com/monero-project/monero/pull/10077
02:45:30 <rsch> can you tell me what happened related to reorg? have you rolledback transactions?
02:45:58 <m-relay> <o​frnxmr:xmr.mx> The description of the or explains the issue
02:57:26 <rsch> but it seems that the pr is not ready yet. the multi sig error is a very annoying situation. im not sure what the solution can be. i guess reto do only rpc calls so when monero daemon tells them error can they fix anything?
02:58:58 <m-relay> <o​frnxmr:xmr.mx> reto cant fix anything, a new version of haveno will
02:59:52 <rsch> sorry I mean haveno can they fix anything if the problem is rooted in monero itself?
03:00:04 <m-relay> <o​frnxmr:xmr.mx> That linked pr should help to prevent the issue, or at least to make it resolve itself after a refresh
03:00:34 <m-relay> <o​frnxmr:xmr.mx> Yes, haveno has this fixed in soon-to-be-released version