Dude... first you tell us you're magically corrupting files when transferring them from Windows to Linux.
No, that was a flash drive I was using that was corrupting my files. It wasn't me.
At this time, this concern of yours has no measurable bearing on the functionality of my wallet.
Then I see your repository starts with the 0.16 code and that you just added the 0.15 code on top of it.
Then you tell us "its all okay except it can't keep track of your balance or import a paper wallet"
Yes, I was keeping you apprised of my progress and issues I was working out. I was keeping you guys in the loop. Should I not have done that? Version 16 has a lot more code tweaks I couldn't account for and there were measurable issues. So I changed it. Therefor I stopped using it to avoid the
measurable problems I had with it and began using v15 instead so that those issues no longer existed and I could release a functional wallet.
At this time, this concern of yours has no measurable bearing on the functionality of my wallet.
Then I see you've selected yet another network ID to further disrupt consensus.
"Yet another"? I've been talking about changing the pchmessage code for a while now. At least since October 6th, before you released your fork. You were the one who changed it the first time, without consensus. You arbitrarily changed it for your own little fork, but if we're all updating to new wallets, it won't matter anyhow. We can change it to whatever we want and with only the new wallets working with the forks to begin with, its a perfect and rather ideal time to change the pchmessage code to something not shared by litecoin.
At this time, this concern of yours has no measurable bearing on the functionality of my wallet.
Add to that not actually using Super Majority for BIP 66 and BIP 65.
So, what measurable harm is that doing? Nothing, as far as I can see.
At this time, this concern of yours has no measurable bearing on the functionality of my wallet.
Add to that not using Gitian to produce deterministic builds.
That is in the category of "bells and whistles" and has no bearing on the functionality of the wallet or the blockchain itself and therefor not cause to dump my new version. Not to mention that can be done at a later time without impacting the wallet or releasing a new version.
At this time, this concern of yours has no measurable bearing on the functionality of my wallet.
I don't want to start nitpicking, but look
here.
Then look at this output and tell me why 1537616302 is in your code.
noodlyappendagecoind getblock d28dd9b4ae980c409440dfbd2d743696a88901dfc3520d70e8d69cb0416053ba
{
"hash" : "d28dd9b4ae980c409440dfbd2d743696a88901dfc3520d70e8d69cb0416053ba",
"confirmations" : 18904,
"size" : 189,
"height" : 1300000,
"version" : 2,
"merkleroot" : "d0244b9a2aca4d81c918fc0a8064bbaa91656c79b8743f4f7fb516cb0c0e4981",
"tx" : [
"d0244b9a2aca4d81c918fc0a8064bbaa91656c79b8743f4f7fb516cb0c0e4981"
],
"time" : 1538619046,
"nonce" : 21270,
"bits" : "1e0a3b9c",
"difficulty" : 0.00038173,
"previousblockhash" : "e506e0fed6f5922ec8cedf68df41ad0ab0c11aef9c10e3e3e631ad9783f10ab1",
"nextblockhash" : "16d37abd4cbbfe12b289c82f2c0e8e3e7a72da31059141b2ea298d62a4ff4c0e"
}
I don't mind nitpicking, as long as its valid. In the realm of functionality; this is not valid nitpicking and not significant to the concerns you have expressed.
Or are you just trying to dramatize the fact that I put the wrong time stamp in for the block? I think that's because I originally had a different "most recent" checkpoint block than 1300000, and then when I changed it to 1300000 I forgot to update it. It's a trivial error that has no functional impact on the wallet or the blockchain. I have updated the code to reflect the correct timestamp. When finalizing it with a much more recent block I would have changed it anyhow, but either way, that is an objective existing error you caught and I have fixed it.
At this time, this concern of yours has no measurable bearing on the functionality of my wallet (nor did it before I fixed it).
Nothing, thus far presented, negatively impacts the wallet or the blockchain in any measurable way. Therefor, there is no measurable reason to scrap my new wallet as of yet.
And if you're testing my wallet now, go ahead; wipe the noodlyappendagecoin folder clean and start it anew and make it download the whole blockchain. Takes a while, but some errors only crop up if you make it download the whole blockchain anew. How do I know? Because I had those errors and fixed them. Because I've already spent substantial amounts of time testing my wallet. Downloaded the whole blockchain over a dozen times. Why? To find the errors before others do; to streamline the process. Because I'm not trying to half-ass this thing like the dev that so concerned you with that "other" alt-coin.