Open theborakompanioni opened 5 months ago
Probably related: https://github.com/JoinMarket-Org/joinmarket-clientserver/issues/1581
I wonder if this here will cause problems when cj can not take place because the same maker gets chosen several times:
After stopping the maker service, and initiating a collaborative transaction, it seems it took it's own offer and tried to create a transaction. This happened on
regtest
after stopping the maker (via rpc) and trying to initiate a collaborative transaction (with 1 counterparty) shortly after.While this is an edge case and extremely unlikely to happen on
mainnet
, I think it provides valuable information about the seemingly unclean shutdown of the maker deamon. Maybe this happens only via RPC (as this occurred while using the Jam development environment), but it is nontheless a problem in production, as there were also reports about "old" offers being taking when a new one with other fee settings was actually active. So, my humble guess is, there is something wrong with the shutdown procedure of the subservices.Below are the logs. Notice the input
3089559b2605cb8d57d553a53c1e963f9c8f9415c3afd22f8de95563e41256e4:0
is included twice. Which hints at that somehow the service was selecting itself as the counterparty.