termination: haveno multi os app
Proposal termination December 31st, 2024
A contractor presented themselves to the CCS for the sole purpose of creating a Multi-OS Haveno App using a portion of funds from the abandoned Haveno frontend proposal. 1 (of which 378XMR remain)
There has since been a public controversy surrounding this proposal/contractor. 2 3
The CCS itself is devoid of opinion/emotion regarding 'extra curricular' activities. 4
As per the Community meeting on December 7th 5, the partial payout request was unanimously denied.
During this meeting, Woodser, the lead developer of Haveno suggested 6:
[a] deadline to release the code, in hopes of getting the code for the greater benefit of the project
Whilst the majority voted to close the proposal with immediate effect.
Community trust and sentiment plays a significant role in our Crowdfunding System. For this contractor, it has been irrevocably and permanently lost.
On December 10th the contractor was explicitly informed 7 to not expect payment outside of milestones 2.
"Work done as per your proposal is work paid":
- As per the contractors own admission8 on December 21st via another partial payout request, the work is not done.
The decision is simple and the contractor is to blame. They:
- Will not continue working on the proposal until a partial payout is made. (This will not happen again)
- Demand a decision as soon as possible.
All deadlines have passed:
-
The latest, mentioned by the contractor in their own proposal (31st December)
-
The community calling for immediate closure (December 7th)
-
One mention of allowing an extra week to complete9 (December 14th).
-
Given this, the expert witness review will now focus solely on:
- Validating the legitimacy of the previous Milestone 2 payout (75 XMR)10.
- Assessing the utility of the existing open source code for future development.
If Milestone 2's work meets the proposal requirements and the existing source code is of high quality, despite being incomplete, a new team or contractor can continue the development after a more stringent vetting process if the community wishes to continue this venture.
Should the review expose any shortcomings in the payout review process, these will be addressed moving forward.
Merge request reports
Activity
mentioned in issue #143 (closed)
There are so many things wrong with this agenda, just as there was with the refusal to payout work rendered, that my will in defending has been reduced to nothing anyway.
I’ll just work to warn any other ambitious developers looking to help this community of the wrong doings and malpractice of the core and corrupt psuedo-core teams leading the sentiment.
I’ll end on this note, in which public forum was the Reddit moderator elected by the community that drove this sentiment in the first place? (The reason I present this, is because there was no public discussion on this, if these ‘shadow’ members just ‘becoming’ of power is not enough to prove there is serious corruption then I don’t know what more I can offer in terms of proof
-
Defence in legitimacy of first payout:
As any developer knows, when extending the functionality of software, it’s prudent to accustom yourself with the previous developments so that you can follow conventions and get a good enough understanding on how to proceed, these will likely be undervalued during this expert witness evaluation I’m sure. I’d also be interested in knowing the credentials and history of any expert witness evaluation candidate selected, if I suspect there is further fraud I’ll release my true identity to the public. Which shows my credentials and should filter out and further nonsense.
Though most of these points were covered on a monero.town post (less corrupt version of the monero Reddit) they seem to fall on deaf ears. You’ll be able to find this information on a Google search.
It was also covered impartially on [redacted]
Actually milestones were being met on time until payments were being delayed, refused. So nice try there but dates and github commits don’t lie.
Edited by plowsoff -
Additionally, the community need not worry about the delivery, as I am still committed (outside of the holidays and the purview of any ties with the CCS, bounties system) to completing the project nonetheless, so the community will not be at any loss, the only loss here is between the myself and the corruption here on Monero. So I am the one at the most loss personally, this will be more and more evident as I continue to release code despite being scammed.
-
‘The community’ referenced in the post is NOT referring to the actual community. It’s referring to about 9 people at most in the top scopes of ‘the community’ of at least 500,000 people, and none of those 9 people can be proven to be distinguished individuals.
Edited by Kewbit mentioned in commit 86207294
