Topic: [ANN][YAC] YACoin ongoing development - page 36. (Read 379983 times)

I have solo minig whith 7khs

we need ate least 100 khs combined

61 kH/s is not enough too.


Does somebody know how deep can be reorganization (in terms of block numbers)?

based on the logs of my wallet
i would say we need more 50% hashrate to overcome the 51% attack in place

REORGANIZE: Disconnect 5 blocks; 000000aef98d90f4a52c..000002d1572251c175f4
REORGANIZE: Connect 5 blocks; 000000aef98d90f4a52c..df58d0c58ecd8d85236b
REORGANIZE: done
REORGANIZE
REORGANIZE: Disconnect 7 blocks; 000000aef98d90f4a52c..0000027c06d4848df73d
REORGANIZE: Connect 9 blocks; 000000aef98d90f4a52c..0000016fda17bbe9990b
REORGANIZE: done
REORGANIZE
REORGANIZE: Disconnect 5 blocks; 0000016fda17bbe9990b..684878caaaa9b1fa9188
REORGANIZE: Connect 6 blocks; 0000016fda17bbe9990b..000000da3869125102cc
REORGANIZE: done
REORGANIZE
REORGANIZE: Disconnect 6 blocks; 0000016fda17bbe9990b..000000da3869125102cc
REORGANIZE: Connect 6 blocks; 0000016fda17bbe9990b..000000f85c8e82e2027d
REORGANIZE: done
REORGANIZE
REORGANIZE: Disconnect 6 blocks; 0000016fda17bbe9990b..000000f85c8e82e2027d
REORGANIZE: Connect 8 blocks; 0000016fda17bbe9990b..0000011c22cf7c199286
REORGANIZE: done
REORGANIZE
REORGANIZE: Disconnect 2 blocks; 0000005459eb9871c485..000001873fb9b261a339
REORGANIZE: Connect 3 blocks; 0000005459eb9871c485..000002de81c2d3bef76b
REORGANIZE: done
REORGANIZE
REORGANIZE: Disconnect 3 blocks; 0000005459eb9871c485..000002de81c2d3bef76b
REORGANIZE: Connect 4 blocks; 0000005459eb9871c485..000002a84f23b6b7b82e
REORGANIZE: done
REORGANIZE
REORGANIZE: Disconnect 7 blocks; 0000005459eb9871c485..00000174b90e3f1f5806
REORGANIZE: Connect 8 blocks; 0000005459eb9871c485..000002bd1d0ba8c36154
REORGANIZE: done
REORGANIZE
REORGANIZE: Disconnect 1 blocks; 0000020c5bf715e99cb5..000001a045ebf0a94f66
REORGANIZE: Connect 1 blocks; 0000020c5bf715e99cb5..3c96515763c79e6a98fd
REORGANIZE: done
REORGANIZE
REORGANIZE: Disconnect 42 blocks; 000001f9b7180174f150..00000088af6c29abc046
REORGANIZE: Connect 52 blocks; 000001f9b7180174f150..0000021be0aa50f45fa3
REORGANIZE: done
REORGANIZE
REORGANIZE: Disconnect 1 blocks; 000002545517485c91b7..0000016473c0867dc284
REORGANIZE: Connect 2 blocks; 000002545517485c91b7..00000155038d300bc382



that's crazy

lets increase it...

Actually 100%


youguqm's 48kH/s is not enough to win

I'm moving some miners from other coins to yac to increse my hashrate

but still 80% of orphans...

This is The War. Total War !!!

As I can see, feeleep allowed youguqm  to hash a bit more ))
To feeleep: You'd better prepare for DDoS in near time

this is insane


100% orphan blocks

lololololoolo

I don't blame feeleep for not supporting yac.
I glad feeleep reads this thread actually..

I'll try to explain what has happened on 19 June 2015
So knowing the history we can make the right decision what to do!

On 19 June there was the hashrate war between youguqm and MM. Both of them was constantly increasing their own hashrate up to 200kH/s. At 12:20 (pool time) (block #1106872) youguqm has won! His hashrate was more than 240kH/s while network hashrate was about 400k. After that during 2 hours there was no orphaned blocks at all. The pool had worked very stable.
When MM couldn't find more hashrate, you all know what has happened..

I think that no increasing block time nor the changing diff algo does not help.
All we need is more pools and more hashrate.
More pools is for DDoS protection.
More hashrate is for no orphan blocks.

I'm soloming whith 5 khs


32 blocks found  last 24 hours

29 orphans  !!!!

the last good block was 13 hours ago !!!


But i'm not giving up

i wil try to increse my hashrate to se if it helps

Hi,

@up - indeed my pool was the first one I believe

anyway - I allowed our botnet guy to hash a bit to check if this change anything... unfortunately no. I may suspect that we would need to change diff algo, because this would limit a chance for MM to be far ahead of the pool. Right now he has a lot of time to mine more blocks than we do. Also block time would help I think. Just my 2 cents...

feeleep

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

That would mean hard forking yacoin. Would people support it?

Why not be part of the Yacoin dev effort instead?

Increasing the block time doesn't help to solve orphans blocks problem.

The problem with orphan blocks is:


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

Can we get some opinions on the 2-minute block time please? Or some other fix?

That would make it harder to put together currency supply projections.
Perhaps something like this could serve as a template.

It is not infinite. At some point all the possible hash power will be mining and then the reward will no longer increase. And then you would be buying something very secure. There has to be value in that.

It's just a different kind of distribution, it doesn't reward mining there first.


Then again why would you mine if it's more cost effective to buy?
And then if nobody mines, then it's an insecure coin. Why buy at all?

It's more of a chicken and the egg kind of problem here.
And you did provide the answer yourself, you would buy if you need more coin than you can mine within a specific time frame. Why would you need yac? For some P&D, not much interest there, I agree.
Why would you need a secure coin? Because it's better than bitcoin.

I'll definitely make an increasing reward YAC clone. Why not? I was just looking for some support, I guess.
All coins seem to fail. Perhaps this is the reason.
And perhaps that's the solution.

I guess nobody would really buy now, but what if bitcoin fails, because of this? A coin that fixes it would be most interesting at that point.