Just a quick update, and a clarification.
First, to clarify as it seems there was a
lot of confusion by the Yacoin team and perhaps some others, and assumptions here and there seem to overtake the simple act of asking a question
I AM NOT WORKING ON A REPLACEMENT FOR YACOIN I am working on a fork of the original Yacoin protocol, similar to Bitcoin Cash or SPV.
Your Yacoin wallet and coins will be valid until the fork on this chain, and then it will become it's own thing. I encourage anyone that was looking forward to Heliopolis to continue to look forward to it, download, install, what have you. I have changed the network port on the coin I'm working on, so you'll be able to run both on the same machine if you wish.
As far as the update goes, I am likely NOT going to be finished before the Yacoin fork at 1900000. In fact, I may never release it unless I can fix the
terrible design flaw that has plagued Yacoin since day one. That is, using the PoW hash for EVERYTHING. This, as you know makes the client use more and more resources to run and gets worse for every Nf change. It shouldn't take a coin 15 days to sync and a non mining client shouldn't run at a high CPU and Memory rate. That's the main reason Yacoin is not on any exchanges.
There are 2 options I see to fix this.
1) My solution, which I'm not entirely sure is even feasible is to REHASH the Yacoin blockchain. In theory I believe it will work as the underlying data is not changing, just switching the hash field in LevelDB from the ever increasing (in resources) Nf hash with the normal 256 hash. The proof of work will still work, just the hash will be sha256. The client will then be able to sync, from 0 in a few hours. It's interesting to me that Pakapaka used the correct hashing for testnet...
static const uint256 hashGenesisBlockTestNet("0xfe20c2c2fc02b36d2473e1f51dba1fb455d41ff42966e2a4edabb98fdd7107e6");
if only they would have switched that around!
2) Figure out the best way to transfer all coins to a new block-chain that starts out using the correct 256(256,block) hashing for all but PoW which would still of course use Nfactor.
This, in my opinion, is the ONLY thing the Yacoin team should be working on. There is one of me and many of you, I'm sure you could devise a solution quicker than I can, but either way (in my opinion) it needs to be done.
I am also happy to have any help from programmers that are extremely familiar with databases, especially LevelDB.
Not really worthy of a comment/response, but here it goes...
This proposal from this user is not some kind of replacement, but it is a 'fake YACoin'. I guess it will continue the PoW-PoS mechanism... for now. The goal is to undermine the current efforts and earn a quick buck? A lot of people are like that, unfortunately. We know people have tried to essentially steal the value from the Bitcoin brand with fake knockoffs. YACoin Cash maybe? By the way, there will certainly be other in the future.
Again, it is a functioning cryptocurrency. There is a lot of freedom for people to create their own forks. YACoin 1.0 is a hard fork upgrade. The risk in trying to continue the original chain is significant IF it actually worked. ANYONE can do it.
Yes, we don't need the NFactor hash for everything. It is Yet Another flaw to address, although it is overblown. A solution to that is already in the works. It's not like other cryptocurrencies haven't address this. In the meantime, for downloading and syncing the chain, you can use this link.
Please point out any more issues if you can't sync to the current chain with reliable peers. Thank you to those who have been helpful to others with questions.