I agree with Bobr. As someone who regularly keeps friendly relations between several parties who “know” they are “in the right” I can tell you that it’s unlikely the complete story is being told once emotions take over. When that happens truth takes a back seat to “being right”. From reading the logs, emotions were inflamed far too early with kewbit threatening to stop right at the beginning. You can’t lead a horse to water. At that point, the CSS should have dispassionally lay down the law without insult or consession and either negotiate an end to the CSS or negotiate new timelines and expectations.
My reading of that likely happened is this. Kewbit appears to have classic engineer delusions. Engineers naturally overestimate their abilities and underestimate the difficulties. Experienced engineers or well managed engineers know about this tendency and add buffers and contingencies “just in case”. Kewbit likely thought he could do more than he was able to in the time period, but “knows he is just needs to get over a minor difficulty to make up the time”. When he missed his deadlines, he became defensive and the emotions on both sides started there and escalated.
Could the drama been avoided? From the CSS side, yes. Calling Kewbit an exit scammer automatically ends any hope that can be resolved and brings needless drama. When the deadline was missed and attempts at negotiation (which are not likely show in the published logs) failed, the CSS should have been withdraw and a settlement should be made. At most, it should have been announced, “Due to on project completion disagreements, the CSS has been withdrawn. Anyone else that wishes to take over the CSS may apply with a plan.”


Thanks Kewbit. I hope this is a misunderstanding that can be resolved. That being said, it’s unlikely many people will beta test a binary without source code, especially if the main reason to use Haveno is to avoid KYC. IMO, it’s probably best to address the drama and move on. Since you’re likely gun shy about speaking out, it’s perhaps best to contact a diplomatic friend that can help express your side and why you don’t feel comfortable releasing the code and what would it take to do it.
IMO, there would only be two reasons why you’ve sent out a follow up post here: (1) You were sincere but made some bad judgements (e.g. timelines, amount of work, how much XMR you needed, “life got in the way”, overreactions that cascaded, the code is uglier than you thought and wanted to clean it up, etc) and you hope there’s some way forward, (2) You’re hoping to make more money either through binary back doors or selling data or convincing people to fund the rest of the project outside of CSS so you can scam them.
I haven’t decided which conclusion to make. At the beginning of the last crypto crash most people were angry at the original Haveno team for halting work when the price of XMR crashed with many calling that team scammers. They made a poor judgement on pricing and could have avoided the drama if they priced their work in USD (paid with XMR). Of course, if XMR continued to go up they’d miss out on the USD gains, but fair is fair. Either you want security or risk. Choosing one and then complaining about not choosing the other isn’t fair. When they continued their work once the XMR price appreciated and released, all past accusations were forgotten (I know I did until tried to remember an example) and they were and still are appreciated for their hard work.
If you are sincerely #1 and are able to express yourself reasonably, there is a way back. If not, #2 will be the conclusion most people will make and releasing the binaries without source code will reinforce this conclusion.