Increasing the block time doesn't help to solve orphans blocks problem.
The problem with orphan blocks is:
..there is malicious miner which has more than 50% of network hashrate.
He shows his 'private' chain to public chain/wallets with delay just when his chain better (in terms of found blocks) than public chain.
Almost in all cases when reorganization has happened, 'alternate' chain has more blocks than public chain.
This problem is solving automatically. When hashrate of public miners is more than hashrate of malicious miner (MM).
It was illustrated by coinmine.pl pool.
There was hashrate war between MM and 'youguqm'. So when youguqm has won there was no orphan block at all. After that the crew of MM has DDoS-ed the pool.
So feeleep and others have made wrong decisions..
First, feeleep has been an amazing supporter and friend to YACoin. His pool has been around for as long as I can remember, and he has ALWAYS been on top of things. He is actually losing YACs because of this orphan, 'reorganization of long chain' issue of late. YAC stakeholders can't thank feeleep enough!
Looking at the network hashrate right now... it is at 185 khash/s! The network block time at this moment is at 30 seconds! I've seen youguqm's hashrate hit over 50 khash/s. His hashrate is 33 khash/s at this moment, and the pool (which isn't paying out right now) is still having those orphan problems.
I hear your point. Let's say the 'malicious miner' goes away...(btw I think there is another, consistent 30 khash/s at least that isn't malicious out there) I feel I would have a difficult time solo-mining YACoin at 5-10% of the total network hashrate. Someone please tell me I am wrong. That is actually my biggest concern.
A 2-minute block time increase might be a solution. Perhaps, there might be something that can be done on the PoS side of things to help fix PoW? I have some inputs of 2000+ YAC that are taking 40+ days to stake. Groko has explained it could be an issue with my wallet getting 'overwhelmed' with too many inputs--even the ones that aren't staking? I feel a fix in terms of that could alleviate some of the PoW problems...
The solution may very well be let the 'market' of PoW fix itself.
@Joe_Bauers @ThirtyBird @Groko @senj @WindMaster @old_c_coder or any others... can you share any thoughts??
Hello Beave162 & everyone,
To get more people/computers involved in YAC or any crypto-currency, including BTC, one needs to go after the biggest audience. See
http://www.netmarketshare.com/ and in "Market Share Reports" near the top, choose "Operating Systems", then "Desktop Share by Version".
OK, what wins with ~92% of all desktops connected to the internet? That is what one should target! That is why I did my videos (
https://www.youtube.com/channel/UCytoaHvG3H1y9CnxZS819eQ), showing how easy it is to make a Windows version of YAC, BTC, etc. Of course the latest version of BTC, roughly versions 9.x, 10.x, 11.x and any other *coin derived from them, now obscure the
make file inside
autogen machinery, making it more difficult to tease out the minimum set of files needed to create a *coind.exe &/or *coin-qt.exe
I prefer to work with Bitcoin 0.8.6 and *coins derived from that version or older, since there was much less "confusion" about which version of gcc, which version of Qt, which version of levelDB, which version of OpenSSL (now there's a deep hole!), UPnP, QRencode,... and who knows how many more with the latest versions of Bitcoin? Boost?, gcc?, Qt?, GMP, secp256k1, etc. etc. etc.
All with no specifications given about which version works, or doesn't, with which older or newer versions? I tried making this argument on various bitcoin foums, but to no avail
I think there are just too many Linux geeks that are burned out looking at too many text mode screens! I did that in the 1970s and 1980s in CPM/ZCPM and DOS (LOL). Don't mind a good
.bat file here and there to ease building a Windows gcc daemon or Qt version
Ron
