So, I guess I should chime in here. I thought we were working on creating a wallet of version .18.5 which would offer mooncoin users security and new features like MLikes and Moonword. I just wanted to take a minute to summarize where we are currently.
https://github.com/mooncoincore/wallet/releases/tag/0.13.9-segwit-b257fcd --> This version is insecure
chain v.18
https://github.com/MooncoinCommunity/wallet --> This version is insecure but has features like MLikes and Moonword that user mooncoin_foundation has paid for and wants to be included in a wallet
chain v.17
https://github.com/mooncoincore/wallet/tree/v0.17.1.0 --> this version validates the full blockchain and purges the network of invalid blocks
As agreed we began work on creating a .18.5 wallet. While checking the compatibility of .17 and .18 wallets we discovered the Michi's wallet was marked as a bad transaction and that this could be affecting any number of other users including paper wallets. This caused another fork between the .17 and .18 chains. Michi has been attempting to explain why 'locked transactions' is not a good idea. The user mooncoin_foundation has been refusing to acknowledge this and it is delaying forward progress. Michi has suggested a Miner Activated Soft Fork or User Activated Soft Fork which burns the coins on the chain. If the user mooncoin_foundation would agree to a MASF or UASF we could resolve this chain split by moving the mining pools to the .17 wallet and abandoning the .18 chain. And we could then secure the .18.5 wallet and include the MLikes, Moonword, and a MASF or UASF to do the burn and exclude the 'locking'. Are you user moncoin_foundation simply refusing to move forward without 'locking' and refusing to agree to a burn? I'm honestly just trying to understand why we are currently in a delay at this point. Is there no way that you will accept or agree to a .18.5 wallet that does a MASF or UASF burn instead of a 'lock'?
Here are some corrections and clarifications it seems there are some users that think just because this thread has a history repeating a lie makes it true.Firstly, I thought our team was inclusive of all of us, Taranis67, agswinner, and the user mooncoin_foundation (By assuming Taranis67 communication was received through agswinner as neither Taranis67 nor user mooncoin_foundation would speak directly to the other. As the user mooncoin_foundation has a history of sending inflammatory private and or public messages to others (including me) and Taranis67 had his limit of them). The user mooncoin_foundation even promised a code review before releasing .18 (which never happened, the code was released publicly and I was given a link to that public code). That is until the user mooncoin_foundation released a wallet and convinced all the mining pools to use the .18 wallet without any review or agreement from anyone.
No, you ignored my several questions. For example,
is mebagger2 part of your team or not?
Did you plan to burn 62 B coins and how exactly?
Everyone knows Mebagger is part of our team. For clarity, it's not MY team, I am part of Mebagger's team, of Michi's team, of the other members' team just as they are part of my team. We in this together, nothing is done by an individual, we use real consensus to go forward.
And yes, we do/did have plans to burn the 62B, everyone is aware of that, specifically stated to Agswinner on numerous occasions.
The how was to be sorted AFTER we finished the work on the wallet as part of long ranging plans. We did discuss the way it could be done, again Agswinner was made fully aware.
You know this is not true. At best it's a stretch. As I recall you had a wallet from James which I think is also barry and in this wallet was something no-one heard of, ballon hash. Something happen between you two and barry (AKA James) left the project. You didn't know what to do and hired Vas (who didn't make that wallet but to this day is blamed) to compile and release this wallet. I did some research into this ballon hash and found where he got this source code. In the creators release notes were numerous warnings about being an alpha release and the creator of that hash advised people to not use this code as it is likely insecure. So I guess I was at lease in part the reason we are still using scrypt and not ballon hash. But I never claimed to have vetted all the code in that wallet. I didn't build that wallet. I didn't release that wallet. I did help Vas debug some issues he was working on by providing debug logs. I assumed that Vas was vetting the code, but I'm now willing to bet that the user mooncoin_foundation paid him and instructed him to simply compile the code and release it.
However, if coins of innocent members were locked in 0.13.9, this wallet was during 2 years in your hands, it is at MooncoinCore Github. This wallet was built with help of mebagger2, by Vassilis.
This is a stretch as well. I had in the past PM'ed the user mooncoin_foundation to let him know some of the delays were due to attempts to get code signing certificates because all the code signers I could find and knew about required a company or corporate structure that could be verified to issue certificates. I was not familiar with that Russian site which issues some sort of user-level code signing certificate, but I am now.
We were investigating PoS but had no intention of just wildly building and releasing it. It was at the investigation stage that is what I said.
Mebagger also told me in PM that you wanted to start a company behind Mooncoin and also move Mooncoin to Proof-of-Stake model. When do you plan to do it exactly?
I thought we were moving forward not playing the blame game. I'm not blaming you for the 3 years in which you the user mooncoin_foundation were paying to have wallets released with these vulnerabilities (these issues are not specific to .13). The user mooncoin_foundation had six years to fix these issues and when our team was ready to fix these issues. The user mooncoin_foundation took action to delay our release so that he could release a wallet with the appearance of security while not actually having any. This is concerning but we are still attempting to move forward with you.
I explained everything, but still have no explanation why the vulnerability was not discovered and/or fixed during 2 years. It is a red flag, with all respect to MooncoinCore team.
I think you are missing the point here. "locked transaction" is not a proper solution. Michi has suggested a Miner Activated Soft Fork or User Activated Soft Fork which burns the coins on the chain. This is how coin burns work they are sent to a wallet that cannot be spent as no one has the keys to it.
First, we should see a normal research about locked transactions.
Um, as the coins have never been locked because the wallet is not secure the .17 wallet didn't unlock a single thing. Are you concerned Vas is going to spend or move the coins for some reason? Because I got the impression from Agswinner that no one wanted the burn to happen until some legal issue is complete sometime this summer, I mean everything has been unlocked for two years and you all have had physical access to the wallet and nothing moved.
No, untrue. There was and is consensus to block these coins.
Research history of this forum.
There was no consensus to unlock them, like it was done in 0.17.
What if coins would be dumped before you would find a solution to burn them (I doubt it is possible technically without a private key, several experts were asked a question about it). Who would be responsible? Devs of 0.17, or you personally?
Edit: okay, if you don't trust this forum, ask at your Telegram channel, whether people want to see these coins locked or unlocked. If they vote to unlock them, they can be unlocked in a new update, but then don't accuse us if they are dumped, also we can remove SmartLikes from the release (Michi said something against it), but then don't ask me where Smart Likes are. What was promised was done, now I am calm and you can go without Smart Likes, if consensus does not accept them.
This is an outright lie. Nuff said.
Also the addresses & code got sent to Mebagger, he reviewed it before the code was published & didnt have any comments on the blocked tx'es/addresses.
As I recall when this locking was done initially there were a bunch of people complaining about losing coins but maybe that was some general complaint about an exchange or something.
During several years no one reported that his or her address was blocked due to protection. It is very strange.