lol WHAT?
so their servers are raspberry pi's?
that might be just some of the dumbest shit I have read today
Topic: [HYP] HyperStake | Generous Reward Staking | Advanced Staking Controls & Wallet - page 128. (Read 679332 times)
June 24, 2015, 10:56:39 PM
June 24, 2015, 10:40:17 PM
Also cryptopia rubbed me the wrong way. Apparently the hate PoS in general. I would encourage not trading there. https://i.imgur.com/HSNZih1.jpg
June 24, 2015, 09:42:02 PM
I have made an attempt to reduce the number of orphans some are experience. I have reduced the amount of hashing into the future that the wallet does from a default of 60 to a default of 45. The hope is that this will make for less stakes that are submitted with a timestamp that is too close to the timedrift cutoff. Please feel free to test this wallet if you are seeing too many orphans. I dont get a lot of orphans myself, but I am staking with linux daemon.
This version also has the ability to alter you hashdrift parameter by entering rpc command "hashdrift" you should not go over 60 seconds, as that will produce orphans. Entering only "hashdrift" will return your current hashdrift parameter.
https://www.dropbox.com/s/2c3sdb0995knlh1/HyperStake-qt-hashdrift-beta.zip
This version also has the ability to alter you hashdrift parameter by entering rpc command "hashdrift
https://www.dropbox.com/s/2c3sdb0995knlh1/HyperStake-qt-hashdrift-beta.zip
June 24, 2015, 04:47:41 PM
Could you add BTC sum and checkboxes to select different markets? Should be quite advanced market tool.
Both of those items is on my "I want to have this list". Just depends on when I will get around to it
June 24, 2015, 02:12:50 PM
Could you add BTC sum and checkboxes to select different markets? Should be quite advanced market tool.
June 24, 2015, 08:35:17 AM
My first attempt at a 'master' depth chart is up @ presstab.pw/phpexplorer/HYP/markets.php
It's the best Block Explorer around, just keeps getting better and better. I haven't used any other since presstab built it, a true work of art.
Agreed. You are a very gifted individual @presstab.
June 24, 2015, 04:05:03 AM
My first attempt at a 'master' depth chart is up @ presstab.pw/phpexplorer/HYP/markets.php
It's the best Block Explorer around, just keeps getting better and better. I haven't used any other since presstab built it, a true work of art.
June 24, 2015, 01:46:12 AM
My first attempt at a 'master' depth chart is up @ http://www.presstab.pw/phpexplorer/HYP/markets.php
June 23, 2015, 03:06:53 AM
Problems with very high orphan rate is usually due to your computer's timekeeping not agreeing with the rest of the network, and the network rejecting your blocks.
Check your time against NTP. Computers sometimes drift a lot and need to be kept synced regularly to compensate.
Check your time against NTP. Computers sometimes drift a lot and need to be kept synced regularly to compensate.
Time is (and has been) perfect.
I'm running the latest version of the wallet without any issues (on Ubuntu). Ping your network connection. Check CPU load. You can also use this RPC command to be sure: 'strictprotocol true'.
June 22, 2015, 01:18:03 PM
Okay. I will try that. Thanks for the tip!
June 22, 2015, 01:16:45 PM
Problems with very high orphan rate is usually due to your computer's timekeeping not agreeing with the rest of the network, and the network rejecting your blocks.
Check your time against NTP. Computers sometimes drift a lot and need to be kept synced regularly to compensate.
Check your time against NTP. Computers sometimes drift a lot and need to be kept synced regularly to compensate.
Time is (and has been) perfect.
try repairwallet if you haven't already. Sometimes having the orphans in your database causes problems. Or at least it appeared that way to me when I was having a similar problem. I actually ended up resynching on my episode, and that fixed it in combination with repairwallet. I'm far from an expert, but that's what I did
June 22, 2015, 01:08:17 PM
Problems with very high orphan rate is usually due to your computer's timekeeping not agreeing with the rest of the network, and the network rejecting your blocks.
Check your time against NTP. Computers sometimes drift a lot and need to be kept synced regularly to compensate.
Check your time against NTP. Computers sometimes drift a lot and need to be kept synced regularly to compensate.
Time is (and has been) perfect.
June 22, 2015, 01:02:28 PM
Problems with very high orphan rate is usually due to your computer's timekeeping not agreeing with the rest of the network, and the network rejecting your blocks.
Check your time against NTP. Computers sometimes drift a lot and need to be kept synced regularly to compensate.
Check your time against NTP. Computers sometimes drift a lot and need to be kept synced regularly to compensate.
June 22, 2015, 10:44:06 AM
Hey all,
I am running the newest wallet 24/7.
I have all block sizes optimized, and in more than two weeks, I have a 61.5% orphan block rate.
The problem is equally bad with the new wallet. Someone suggested I might be on an old wallet, and I was at first, but for the last five days, I have had the newest wallet running. In sheer percentages, my orphaned block rate is actually worse with the new wallet, but to be fair, my coins have been mature longer with the newer wallet running.
I have also occasionally restarted the wallet to make sure that isn't causing any issues.
All I am seeing is an unacceptably high 61.5% orphan rate.
Why is this happening?
I am running the newest wallet 24/7.
I have all block sizes optimized, and in more than two weeks, I have a 61.5% orphan block rate.
The problem is equally bad with the new wallet. Someone suggested I might be on an old wallet, and I was at first, but for the last five days, I have had the newest wallet running. In sheer percentages, my orphaned block rate is actually worse with the new wallet, but to be fair, my coins have been mature longer with the newer wallet running.
I have also occasionally restarted the wallet to make sure that isn't causing any issues.
All I am seeing is an unacceptably high 61.5% orphan rate.
Why is this happening?
June 22, 2015, 10:43:12 AM
The problem with a large block is that although it has more weight and is thus more likely to stake, it also only creates one has per second, which you can basically say is one attempt to stake per second. If you split that between a few blocks, you would have more attempts per second, and the more attempts, the more likely it will line up with statistics.
So there is no point in creating blocks greater than, let's say, 20k?
It could make some sense if you were creating multiple large ones. But personally I am going below 10k each.
June 22, 2015, 10:26:37 AM
The problem with a large block is that although it has more weight and is thus more likely to stake, it also only creates one has per second, which you can basically say is one attempt to stake per second. If you split that between a few blocks, you would have more attempts per second, and the more attempts, the more likely it will line up with statistics.
So there is no point in creating blocks greater than, let's say, 20k?
June 22, 2015, 10:24:06 AM
The problem with a large block is that although it has more weight and is thus more likely to stake, it also only creates one has per second, which you can basically say is one attempt to stake per second. If you split that between a few blocks, you would have more attempts per second, and the more attempts, the more likely it will line up with statistics.
June 22, 2015, 10:16:28 AM
getstakesplitthreshold
Saw that already, not listed but it works.
Thanks!
June 22, 2015, 10:15:13 AM
Did you ever save the settings back to the wallet? I believe
Code:
setstakesplitthreshold 20000
tells the client to not allow blocks greater than 20k. Or is it the other way around?Really? I was convinced it was the other way around... meaning
Code:
setstakesplitthreshold 20000
would prevent my blocks from becoming smaller than 20k 
What do you mean by "saving the settings back to wallet"?
How can I check my current status and/or remove this setting altogether?
getstakesplitthreshold
edit: I think this one was a little different then what I assumed it would be. I think the threshold is the size of the split blocks. So don't split until the result will be greater the 20000. Someone that actually knows can weigh in....
June 22, 2015, 09:54:27 AM
Did you ever save the settings back to the wallet? I believe
Code:
setstakesplitthreshold 20000
tells the client to not allow blocks greater than 20k. Or is it the other way around?Really? I was convinced it was the other way around... meaning
Code:
setstakesplitthreshold 20000
would prevent my blocks from becoming smaller than 20k What do you mean by "saving the settings back to wallet"?
How can I check my current status and/or remove this setting altogether?
Jump to: