Do note:
The second phase (Limit) allows a maximum vote of 1024 HVC for the first 59,876 blocks, but 8 HVC for the last ~3,600 blocks so it can transition into to the last phase (Sustain).
I personally would rather see POS for phase 3 as I agree if hash drops significantly there could be potential malicious attacks.
Keccak any comment on the network security during phase 3?
Yep, for 51 days you can vote anything you want up to 1024 but during the last 5 days your vote has to be 8 or under. I'm sure that's going to work well.
Hopefully we can get an update before then for CGMiner and CCMiner that will fix this automatically. Maybe we could get a --sustainvote switch thrown in early that will allow both votes to be set now. The program would use the --vote setting up until the last 5 days and will switch to the -sustainvote switch at the correct block so all blocks are counted. Otherwise we could see another drop in hash rate during these last 5 days as invalid votes (higher then
are used and they are thrown out.
What do you mean by during last 5 days? Last 5 days of what?
Show Posts
