[ANN][YAC] YACoin ongoing development

[ksmx]

Hi, could any provide a valid seednode address or point me to how to sync the wallet?
Just download the latest wallet and it doesn't  have any connection to network. Is it alive?

Yes, it works. Use these, some of them are not working

addnode=54.160.76.44
addnode=89.90.190.248
addnode=114.82.153.68
addnode=99.108.237.173
addnode=91.206.16.214
addnode=217.241.63.39
addnode=195.22.25.132
addnode=71.59.11.80
addnode=97.70.78.42
addnode=69.119.30.86
addnode=84.255.221.212
addnode=37.201.88.79
addnode=71.59.11.80
addnode=79.118.169.82
addnode=71.59.11.80

[ksmx]

A lot of resources have been dedicated, spent to making 0.4.9 and 1.0.0 usable. If you see any specific problems, you can bring it up in github or even do a pull request for a change. You can also point out the specific problem in here.

I tried to send some coins into your address using 0.4.9 wallet. No success.

Status: 0/unconfirmed
Date: 26.02.2021 08:36
To: test YL5kf54wPPXKsXd5T18xCaNkyUsS1DgY7z
Debit: -1.00 YAC
Net amount: -1.00 YAC
Transaction ID: a05776ef909c64aedea33c275989b8571057d4eceb6a7b4668208bc633a97ab1


Status: 0/unconfirmed, broadcast through 3 node(s)
Date: 08.03.2021 08:41
To: test YL5kf54wPPXKsXd5T18xCaNkyUsS1DgY7z
Debit: -5.00 YAC
Net amount: -5.00 YAC
Transaction ID: 3ee3753a0d489a3110a69011ad09bc699581be5f94f0336d84af45e4d8fd4133

Status: 0/unconfirmed, broadcast through 3 node(s)
Date: 08.03.2021 08:42
To: test YL5kf54wPPXKsXd5T18xCaNkyUsS1DgY7z
Debit: -5.00 YAC
Transaction fee: -0.001 YAC
Net amount: -5.001 YAC
Transaction ID: f1bcfa64f24152d7b8394a683759811387379822d8a1f943f7074a842c6bc7ba


Any idea?
Best

[love diem]

A lot of resources have been dedicated, spent to making 0.4.9 and 1.0.0 usable. If you see any specific problems, you can bring it up in github or even do a pull request for a change. You can also point out the specific problem in here.

If you run 1.0.0 right now, you will be running under the old YACoin rules (0.4.9, 0.4.4, and prior). At block 1,890,000, the new rules will take into effect. Make sure you are running 1.0.0 by that point. The Windows link at the website has been updated (thank you aso!). If someone wants to create a faucet, I can link to it from the website. Otherwise, it will likely be removed soon.

Again, if you try to keep the old chain alive, you are taking a big risk by transacting on it. What's interesting is that NO ONE cared about keeping the old chain going (except for me) until I announced the hard fork. Armchair quarterbacking has nothing to do with consensus (PoW-PoS or PoW).

Now I have been changed to use wallet v1.0.0 already.
Another question , I'd like to ask you about my YAC at Yobit. At present time , I can't withdraw them from Yobit. ( due to the status of wallet is maintenance ).How to do about this matter?
I don't know that I have to withdraw them from Yobit to my desktop wallet or not.

[Beave162]

A lot of resources have been dedicated, spent to making 0.4.9 and 1.0.0 usable. If you see any specific problems, you can bring it up in github or even do a pull request for a change. You can also point out the specific problem in here.

If you run 1.0.0 right now, you will be running under the old YACoin rules (0.4.9, 0.4.4, and prior). At block 1,890,000, the new rules will take into effect. Make sure you are running 1.0.0 by that point. The Windows link at the website has been updated (thank you aso!). If someone wants to create a faucet, I can link to it from the website. Otherwise, it will likely be removed soon.

Again, if you try to keep the old chain alive, you are taking a big risk by transacting on it. What's interesting is that NO ONE cared about keeping the old chain going (except for me) until I announced the hard fork. Armchair quarterbacking has nothing to do with consensus (PoW-PoS or PoW).

Now I have been changed to use wallet v1.0.0 already.
Another question , I'd like to ask you about my YAC at Yobit. At present time , I can't withdraw them from Yobit. ( due to the status of wallet is maintenance ).How to do about this matter?
I don't know that I have to withdraw them from Yobit to my desktop wallet or not.

DO NOT USE YOBIT

It is an absolute scam exchange. They don't have any YAC because they participated in fraudulent tactics such as naked short-selling.

Unfortunately, your YAC on YoBit is worthless. You will never be able to withdraw them.

[love diem]

A lot of resources have been dedicated, spent to making 0.4.9 and 1.0.0 usable. If you see any specific problems, you can bring it up in github or even do a pull request for a change. You can also point out the specific problem in here.

If you run 1.0.0 right now, you will be running under the old YACoin rules (0.4.9, 0.4.4, and prior). At block 1,890,000, the new rules will take into effect. Make sure you are running 1.0.0 by that point. The Windows link at the website has been updated (thank you aso!). If someone wants to create a faucet, I can link to it from the website. Otherwise, it will likely be removed soon.

Again, if you try to keep the old chain alive, you are taking a big risk by transacting on it. What's interesting is that NO ONE cared about keeping the old chain going (except for me) until I announced the hard fork. Armchair quarterbacking has nothing to do with consensus (PoW-PoS or PoW).

Now I have been changed to use wallet v1.0.0 already.
Another question , I'd like to ask you about my YAC at Yobit. At present time , I can't withdraw them from Yobit. ( due to the status of wallet is maintenance ).How to do about this matter?
I don't know that I have to withdraw them from Yobit to my desktop wallet or not.

DO NOT USE YOBIT

It is an absolute scam exchange. They don't have any YAC because they participated in fraudulent tactics such as naked short-selling.

Unfortunately, your YAC on YoBit is worthless. You will never be able to withdraw them.

Thank you very much for your answer.
Another question , Where are the markets for YAC ?

[aso118b]

YACoin Resurrection Hard Fork – Heliopolis

...

-Unique algorithm. Sticking to its roots, YAC will maintain the inventive scrypt-chacha (aka scrypt-jane). NFactor will be set at 21 to be ASIC resistance but also mineable for many CPUs and GPUs.

...

I was hoping to better understand this.

Currently (pre hard-fork) the N-factor was set to be increase on a fixed schedule.  After the hard-fork I believe it will be "set" to 21. 

What are the plans to increase the N-factor over time?  As technology improves so will the mining capabilities.  Litecoin for example - was "GPU proof" and shortly after home graphic cards became powerful enough to mine.  Following that the "scrypt" algorithm became ASIC territory.  I'm sure we don't want something similar to occur to YAC down the road.  And to increase the N-factor when 'ASICs seem to be getting close' seems arbitrary.

Is there something in the protocol to handle N-factor increases?  Or can it be included?

[Beave162]

YACoin Resurrection Hard Fork – Heliopolis

...

-Unique algorithm. Sticking to its roots, YAC will maintain the inventive scrypt-chacha (aka scrypt-jane). NFactor will be set at 21 to be ASIC resistance but also mineable for many CPUs and GPUs.

...

I was hoping to better understand this.

Currently (pre hard-fork) the N-factor was set to be increase on a fixed schedule.  After the hard-fork I believe it will be "set" to 21. 

What are the plans to increase the N-factor over time?  As technology improves so will the mining capabilities.  Litecoin for example - was "GPU proof" and shortly after home graphic cards became powerful enough to mine.  Following that the "scrypt" algorithm became ASIC territory.  I'm sure we don't want something similar to occur to YAC down the road.  And to increase the N-factor when 'ASICs seem to be getting close' seems arbitrary.

Is there something in the protocol to handle N-factor increases?  Or can it be included?

The debate over ASIC resistance has been raging on for quite a few years now.

I think it's best to think of 3 categories: !) ASIC-proof 2) ASIC Resistance 3) ASIC friendly. And really, there is a spectrum in between.

Bottomline, the most important aspect is adoption. The hashing algorithm should be decided on what is the most optimal way to achieve mass adoption. Under that premise, it was decided to go with NFactor 21--not the increasing NFactor schedule up to NF30. There will be a lot of discussion on why NFactor 21 was chosen.

Meanwhile, everyone will be able to mine with their CPU running the core wallet. You can set "gen=1" in the yacoin.conf file. That was erroneously removed in previous version, but YAC 1.0.0 has it back in.

[vampirus]

I have two questions.
1 - Why someone with new v1.0 already on block 1917342 but all others nodes on old versions and block explorer http://explore.grokonet.com/ only on block 1888070.
2 - Why last hard checkpoint in new version still from 2014 year?

[Beave162]

I have two questions.
1 - Why someone with new v1.0 already on block 1917342 but all others nodes on old versions and block explorer http://explore.grokonet.com/ only on block 1888070.
2 - Why last hard checkpoint in new version still from 2014 year?

1) The node on block 1917342 is from a test. It will be orphaned eventually.

2) There hasn't been a reason for more checkpoints. After the hard fork, we will implement checkpoints. That is already ready to go.

Less than 2000 blocks to go!

[minerja]

I have two questions.
1 - Why someone with new v1.0 already on block 1917342 but all others nodes on old versions and block explorer http://explore.grokonet.com/ only on block 1888070.
2 - Why last hard checkpoint in new version still from 2014 year?

I also have some questions and observations....
Since i got notified of the v1.0.0 update, i thought i'd try and mine this coin again....

Well question
1 - Who the heck is actually managing to mine this coin.
2 - What hardware are you using
3 - What hashrate are you getting

Reason i ask, is simple
If was crap to mine at N=19, and now @ N=20 i cannot even get a hashrate on a Rzyen1800x, using every available cpuminer....
I have tried cpuminer, yacminer, rplant miner, on win 7 / 10, Ubuntu, Mint, LinuxLite, Debian, ALL the same....if i get a hashrate it's less than 0.1H/s
Last time i asked "Beave162" i believe he suggested about everyway possible to try, BUT i did as he said and left the wallet with gen=1, genproclimit=8 and 7 days later, NADA. NOTHING, ZERO, not 1 block, not 1 coin.

So i have a look today using wallet v1.0

Same issue....i don't even register as mining according to the wallet
So how come if i look at the block explorer, last 100 blocks....
First of all, how come in less than 24 hours well over 40 blocks have been mined?
In the last 100 blocks, looks like 30 have been mined (going by rewards of 100 coins) to just 2 addresses...

YFyGkZDYQiHxf35PBwRFrXi48fNuYhkSp5   22 blocks (2200 coins) giving a TOTAL Balance of 81,529 coins
Y2Jo5wT56r4EXdbMetFUsHdA72SrKrgDtV   8 blocks (800) giving a TOTAL Balance of 82,986 coins

My gawd the nethash is over 850H/s....what hardware is winning these guys these blocks?
I coudn't even mine a block when i borrowed a 3990wx (64c/128t), si i am guessing some one has a cpu farm, OR is using pro gpus (I bet a 6x3090 24GB rig  can mine this)

So please tell me what i am doing wrong?
Tell me how a normal miner is ever supposed to win 1 block (not that that makes any money)
Also where is the market, for the current nethash, someone is spending money to mine, so where are they cashing in? I see no exchange?

Please bring foward some answers cos it's starting to feel , well....


Oh, here's my N19 speed
.\minerd-x64-core2.exe -a scrypt-jane --nfmin=19 --nfmax=19 -t 8 --benchmark
[2021-03-19 17:17:06] 4 miner threads started, using 'scrypt-chacha' algorithm.
[2021-03-19 17:17:06] Scrypt-Chacha NFactor set to 19
HANGS

and my N20 speed
.\minerd-x64-core2.exe -a scrypt-jane --nfmin=20 --nfmax=20 -t 8 --benchmark
[2021-03-19 17:17:06] 4 miner threads started, using 'scrypt-chacha' algorithm.
[2021-03-19 17:17:06] Scrypt-Chacha NFactor set to 20
HANGS

How are you hoping to get any new miners, and support for this coin....

[Beave162]

YACoin Resurrection Hard Fork – Heliopolis

YACoin is getting an upgrade (finally)! At block height 1,890,000, a hardfork will occur. Here is a list of main features of the upgraded chain:


-PoW ONLY – No more Proof of Stake. Proof of Work is the innovation of Bitcoin.

-2% annualized supply inflation max. Fees are destroyed, which can cause supply deflation with increased economic activity. The block reward is calculated off of the total money supply. First PoW coin to do so.

-Unique algorithm. Sticking to its roots, YAC will maintain the inventive scrypt-chacha (aka scrypt-jane). NFactor will be set at 21 to be ASIC resistance but also mineable for many CPUs and GPUs.

-Intelligent Block Size Increase. Block size will increase over time at no more than 2%--dependent on the total money supply.

 -Set epoch lengths. At 21,000 blocks for each epoch, the ‘compounding bad luck’ problem faced by the mining ecosystem is addressed. The system incentivizes more decentralization, smaller miners/pools.

-Timelock and atomic swap/loans capabilities.

Upgrade includes many bug fixes (incl. txid malleability bug, UTC timestamp bug) as well as other features and more to come. [/color]

Download/compile the latest YACoin 1.0.0 repo build at the public github repo: https://github.com/yacoin/yacoin/

Less than 1700 blocks to go until the Heliopolis Hard Fork!!

Reminder: YACoin 1.0 is a completely open, decentralized cryptocurrency, which means anyone can support the network with their computing hardware.

It will be interesting and exciting to see how the mining landscape develops over time. It will be the most miner-friendly coin to exist.

[minerja]

"YACoin 1.0 is a completely open, decentralized cryptocurrency, which means anyone can support the network with their computing hardware."
 "It will be the most miner-friendly coin to exist."

Maybe one day, but not this day.

Finally got wallet 049 to sync, finally found a miner than seems to wrk (none of the ones suggested on this forum have worked for me)
Mining away @ 1 H/s 8 cores, then i noticed wallet was syncing again.
Let if sync, took 1 hour, started mining, out of sync again....
Don't even get me started on wallet 1.0.1 it's clearly on a fork, cos its about 15441 blocks in front....

Broken wallets. broken chain.....2 massive miners and no way for any "normal miner" to compete.

wallet 049 says
YAC-v0.4.9.02-leveldb
OpenSSL 1.0.1u  22 Sep 2016
Berkeley DB 4.8.30: (April  9, 2010)
Sep 22 2018, 13:54:31
2 (Inbound: 0 / Outbound: 2)
1888314
1888322
Sat 20. Mar 16:13:55 2021

getpeerinfo
"addr" : "73.237.45.147:7688",
"version" : 60009,
"subver" : "/Yacoin-WM Qt:1.0.0/",

"addr" : "99.108.237.173:7688",
"version" : 60008,
"subver" : "/YACoin-WM:0.7.3/",

Wallet 1.0.0.
YAC-v1.0.0.16-f5d0b4221407-leveldb
OpenSSL 1.0.1u  22 Sep 2016
Berkeley DB 4.8.30: (April  9, 2010)
2021-02-01 19:09:02 -0500
2 (Inbound: 0 / Outbound: 2)
1888265
1903763
Sat 20. Mar 07:58:51 2021


18:14:00

getpeerinfo
"addr" : "73.237.45.147:7688",
"version" : 60009,
"subver" : "/Yacoin-WM Qt:1.0.0/",

"addr" : "66.172.33.20:7688",
"version" : 60009,
"subver" : "/Yacoin-WM:0.7.5/",


Lets start again, with 1 wallet, 1 zipped working, synced bootstrap, with 1 authenticated seednode, and a handfull of trusted nodes.....
Then along with a pool, normal miners may a reason to try this coin....

As for my track record, i currently mine successfully over 130 different coins, and hold closer to 400 different coins,
BUT Since i have failed to have any success with this coin, having spent many many hours over several months, please anyone winning blocks, please give me clear instructions how to mine it with a standard desktop PC, not some insane 64c monster
I will try any OS, and wallet, and when i am mining at lease 2 blocks a day, will stop whining

[minerja]

OK,
Finally wallet 0.5.9 has synced one more time

Only working miner i have found is this one
https://github.com/JayDDee/cpuminer-opt/files/1996977/cpuminer-opt-3.8.8.1-windows.zip
(i have no affiliation with jaydee, check for virus yourself, etc, i just find his miners cool)

i am using the command below  (ryzen 1800x)
cpuminer-avx2-sha -a scryptjane:20 -o http://127.0.0.1:7687 -u user049 -p pass049 -t 8
and getting approx 1.5H/s per core, so in theory 12 H/s

The miner only reports total hash once a hash has been submitted and accepted, so will update you if that ever happens.



oh, wallet 1.0.0. is currently on same block height as 0.4.9 BUT thinks it has 30881 block to sync....DUH

[vampirus]

Current good nodes on main chain (1888324)

Code:

addnode=99.108.237.173:7688
addnode=66.172.33.20:7688
addnode=71.59.11.80:7688

[Joe_Bauers]

I'm wondering how it was decided to convert YAC to POW only.  I don't recall seeing a discussion here, in GitHub, or miners voting with their hashrate.

YACoin Resurrection Hard Fork – Heliopolis

Agree. I was mining yac since the beginning. This is pretty decent currency, why spoil it? v1.0 client is unstable, crashes all the time. I propose staying at the old one for a longer time. No hard fork is needed. Why?

Rather than talk about... in the next 2 weeks, month, etc... blah blah blah... I am going to release something.  I will take a note from Elon Musk who is way better at promotion and say...

Stay Tuned!  

I will say, I'm spending 8+ hours a day working on getting something for the "old" client released ASAP.  

This is NOT to say that I disagree in any way with the current Yacoin team's approach and changes, because I don't in any way. But yes, I agree people should be able to run the old protocol for sure if they wish.  

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...

Code:

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.

[Joe_Bauers]

God, you are an absolute, pathetic loser.

This is the PM response from the person I made the terrible mistake of leaving Yacoin to 

I call for a vote of no confidence in the "Leadership" of Beave162.

Stop wasting everyone's time Beave162, or turn Yacoin over to someone that can fix the issues, rather than try to game it so you can mine more blocks with your GPU farm 

[Beave162]

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...

Code:

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.

https://mega.nz/file/SZcVWSRK#HEP0u6GkrNBuvloZv-vijcJtCXPNgiHv1WHAzeSoxDY

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.

[Beave162]

By the way, did you know that in YACoin 1.0, the off-by-one difficulty/time-warp bug is fixed?

https://bitcoin.stackexchange.com/questions/20597/where-exactly-is-the-off-by-one-difficulty-bug#:~:text=The%20%22off%2Dby%2Done%22%20or%20Time%20Warp%20Bug,blocks%202017%20up%20to%204032.

Did you know, the UNIX timestamp bug in Bitcoin is also fixed:
https://www.reddit.com/r/Bitcoin/comments/89wuvp/bitcoin_unix_epoch_y2k_bug/

There is a lot of work done to make #Heliopolis successful, and there are more features on the roadmap. Again, it is a functioning cryptocurrency undergoing a hard fork upgrade. The future of YACoin is great, despite the many trolls that will surely pop up everywhere.

[Joe_Bauers]

Beave162 quack quack quack

[MyCousinVinny]
Every thing that guy just said is bullshit[/MyCousinVinny]

Or to put it another way, everything you mentioned is hilariously what you are trying to do. You have the worst mirror complex I've ever witnessed.

As it was already mentioned, where was the vote to convert Yacoin to PoW only made? Oh right, in your garage with your giant custom GPU Yacoin mining rig  

Why is Yacoin still being catered to GPU mining btw? It's supposed to be an ASIC unfriendly CPU coin.

Still, even though I "think" you're an idiot, I'm glad you have a few good programmers helping you.
Here's what you need them to work on, preferably BEFORE you do any hard-fork.

1) Upgrade all code. No one is going to take seriously a coin that is running Bitcoin 0.8.6 code. You mention fixing a few errors, GREAT, what about the few hundred commits that have occurred in Bitcoin since?

2) Stop allowing this nonsense.

Code:

    if (
        (0 < nPosBlockCount) 
        &&
        ( 
         (
          fTestNet 
          && 
          pprev 
         ) 
         ||
         !fUseOld044Rules         //(nTime >= YACOIN_NEW_LOGIC_SWITCH_TIME)
        )
       ) 

What the fuck is that, COBOL?

3) Fix the GetPoWHash issue I mentioned. Litecoin uses GetPoWHash TWICE, Yacoin, almost 100. No serious user or exchange wants to use your bootstrap file to try to offset the 14+ days average of syncing, Bitcoin stopped doing this a long time ago.  Or run a client that uses far more resources than any other, even as a node.

4) Remove the built in miner. You are giving people the impression that they will be able to solo mine blocks against your GPU farm. People need to be incentivized to form Yacoin pools.  

5) Once you're done with all that, turn Yacoin over to someone from the community that will keep the coin in the best interest of everyone rather than just their own. Windmaster.... WHERE ARE YOU?

In the meantime, yes I am working on YacoinCash, (which I chose to amuse myself as in this case it's better than the original) which uses a new code-base, and fixes all of the above issues with the exception of #3 which as I mentioned before, I am still working on. Of course if Yacoin wasn't being run (into the ground) by an out of touch megalomaniac, maybe we could all work together to fix these issues?

But alas, I guess I will just keep working to fix it all myself.    

[ksmx]

But alas, I guess I will just keep working to fix it all myself.    

Thank you.