The block detection is delayed for up to 2 hours. The stats it self isn't delayed, but we made it harder to pool hop with delaying detection/showing of new rounds and blocks.
Exactly the same as BTC Guild, deepbit and other prop-pools does it - to avoid huge amounts of pool hoppers.
How can you say the stats aren't delayed when your site says: Current round: 14 hours blah blah blah and then 3 minutes later it says Current round: 45 minutes blah blah Previous round 13 hours 15 minutes It does this ALL the time. You are delaying stats. At least acknowledge it and make it apparent to your users. When your JSON API is giving incorrect "round_shares" for over an hour, that is called delaying stats. Also, I asked you weeks ago if you were delaying stats and you without hesitation said you were:  Its your pool. Do whatever you want with it. I think it would be nice if you told your users on the stats page that they are possibly looking at lies put in place to try and stop pool hopping. |
|
|
|
You are doing some awesome work here Bloodred.
Indeed, today has been my single biggest income day to date (thanks primarily to BitClockers solving 4 blocks and 2 of those at < 43%). I will have to be taking a look this week at flower's poclbm mod since it provides the bithopper web UI for monitoring and bitclockers support. All this development is exciting and your cherry picker is pushing other projects forward. Now if you would just open source it  Yep. Bitclockers made me a TON today. The thing I am watching is this LP hopping they are investigating over in the bithopper thread. c00w is working on hopping deepbit, which I think may be VERY profitable. |
|
|
|
you think you do better with cherry picker just with bitclocker?.. i still make decent over there. but i dont get to mine as much as i would like.
c00ws seems to have faster development and more pools and I havent quite figured out making my own cherry pickers pool configs too well.,
anyways you know if deepbit works.. cherry wont be far behind adding it.
Well today alone I have found 4 blocks at bitclockers for a total of 0.63544748 BTC with 690Mhash/s. So yea, its awesome. With bithopper I MAY have made .3 BTC out of those 4 blocks if I was lucky. Cherrypickers has taken my estimated payout from .03BTC/round while mining to .2 BTC a round while mining. Also, for some odd reason I have NEVER seen my hash rate reported on the site below 750Mhash/s and its usually above 800Mhash/s. No idea why that is but I am not complaining. Can't wait to see how this LP hopping works out. Has a lot of potential to cut through all of the BS that pools do to stop hoppers. And to your last point, I'd rather bithopper figure out bitclockers so that I could come back here because the entire website monitoring thing is awesome c00w is a mad genius. |
|
|
|
|
You are doing some awesome work here Bloodred.
|
|
|
|
|
The suspense is killing me waiting for the first report on whether deepbit mining is working and the related efficiency rating. This is something that might make me switch back to bithopper from Cherrypicker. Deepbit vs bitclockers . . . . .
|
|
|
|
Did Bitcoin.lc just jump to ± 35% in a new round?
That would mean the're delaying stats?
Yes, they do delay stats from 0-3600 seconds randomly. Still turns out to be profitable, but far less than it would be if they didn't. |
|
|
|
Regarding the bitclocker issues: I don't think they slow down or disturb hoppers connections. Their server is just totally overloaded or in any other way can't handle things.
is this the reason too that I have <= 3% rejected and bithopper always disconnects from bitclocker? Yep, that is the reason it always disconnects from bitclockers. Right now they appear to be completely down to me. Then why does cherrypicker hop them flawlessly with .4% stales? Its obviously an issue with the way bithopper works. |
|
|
|
Ryouiki backed out his algorithm and went to vanilla least shares based hopping. I really liked his multi-threshold, time/speed, dynamic penalty approach and would probably still use it if he didn't have the issues with bitclockers like c00w. I'm hooked on picking now and c00w's seems to me to have 'slice'-ed it's own throat for the time being. I'm sure it will work itself out but for now and until ryouiki integrates slicing into his fork I'll keep picking.
Same. Hard to give up bitclockers. I am making 5x as much per round at bitclockers with CP compared to BH. |
|
|
|
So they aren't crooks, instead they got hacked. This is not really great news. How many major robberies have there been in the bitcoin world in the last two months, I've lost count ? No kidding. If anyone really things that any business is ever going to adopt bitcoins as a payment method or that regular people will start using it, they are delusional. Every couple of weeks you hear about hundreds of thousands of dollars worth of bitcoins being stolen with absolutely no recourse for the victims. Yep, that sounds like something that businesses and regular people want to get involved with. |
|
|
|
Good idea. They have a fee for PPS?
7% at MtRed last time I checked. |
|
|
|
Thats what I was thinking. I don't know if that would be the most profitable, but I have to think sticking with one pool that is slow and only getting a few shares in on faster pools isn't the most profitable. Over on the bithopper thread they are all trying to implement "slicing" which basically tells the hopper that if there is more than 1 pool under 43% to rotate between them submitting shares. Again, there are people a lot smarter than me who know what is the most profitable though.
The earlier shares are most profitable afaik. I wanted to release 0.6.4 today but I'll delay it a bit longer to add this mode that takes hashrate into account. The next version will have 2 prop pool hopping modes to choose from, picking fast pools first or this regular one. There is a thread discussing this exact thing here: http://hoppersden.info/showthread.php?25-What-s-the-better-strategyI don't know what is the best option anymore. Looks like slicing or dynamic penalties like Ryouiki's fork is the most efficient according to Ryouiki's simulation. I am sure you know more about this than I do. I am grateful for all of your hard work. Edit: Also, nofee seems to be switching their server over to google's apparently after this long block is over and I think the host address and username and passwords for everyone will be changing. No idea what the correct port is because they didn't say. |
|
|
|
Was just thinking that it would be cool to have not only a "PROP" setting but also a "SLOWPROP" setting. This would be kind of a hack so that you could mine on the slow prop pools after finishing a fast round with a pool with a much faster rate instead of getting stuck at a slow pool all day. This would work until the miner takes hashrates into account on choosing which pool to hop to.
The idea would be so that the picker chooses PROP>SLOWPROP>SCORE/SMPPS>BACKUP. Actually ideally the SCORE implementation would be like bithoppers so that you jump on for 10% and then get off, so that the picker would choose: SCORE>PROP>SLOWPROP>BACKUP.
I could make it take hash rate into account, but what method are you suggesting? Going to the fastest (prop) pool under 43%, then switching to the 2nd fastest when the 1st goes over 43%? Thats what I was thinking. I don't know if that would be the most profitable, but I have to think sticking with one pool that is slow and only getting a few shares in on faster pools isn't the most profitable. Over on the bithopper thread they are all trying to implement "slicing" which basically tells the hopper that if there is more than 1 pool under 43% to rotate between them submitting shares. Again, there are people a lot smarter than me who know what is the most profitable though. |
|
|
|
They are trying to scare you out of the market..get you to sell at $9 thinking that it will go down to $5.
But after you sell, they will buy it, it will go up..then keep going up.
The worst is behind us.
Anyone who was being responsible knew that you shouldnt have your coins on mybitcoin.com. I feel sorry for their loss, wish it wasnt so, and wish them the best. But there is no excuse for what they did, it was their own fault, and not a flaw in bitcoin. This situation was a known outcome. As a community we have all learned from it.
The market will continue with your regularly scheduled program.
Well you look like an ass now don't you. Current price: 7.31USD/BTC |
|
|
|
Well so far poclbm fork doesnt help me, new ip, new account, single miner or miner via bithopper.. Bitclockers just giving me the finger.
I think its whole batches of ip ranges the retard just completely limited to get dropped even if it sneezes at his server.
No wonder even when new block gets found the server barely increase traffic by 20gh, his server wont grow like this.
The next thing I will do is route my traffic through different geo-VPN's and see if it still screws with me.
It isn't the server. Switched over to cherrypicker and all problems dissapeared instantly. Its the hopper causing the problems. I think you may have too many gpu's requesting getworks on a single accunt at bitclockers for cherrypicker even. If you spread them out over a couple different accounts it would probably work well. |
|
|
|
|
Was just thinking that it would be cool to have not only a "PROP" setting but also a "SLOWPROP" setting. This would be kind of a hack so that you could mine on the slow prop pools after finishing a fast round with a pool with a much faster rate instead of getting stuck at a slow pool all day. This would work until the miner takes hashrates into account on choosing which pool to hop to.
The idea would be so that the picker chooses PROP>SLOWPROP>SCORE/SMPPS>BACKUP. Actually ideally the SCORE implementation would be like bithoppers so that you jump on for 10% and then get off, so that the picker would choose: SCORE>PROP>SLOWPROP>BACKUP.
|
|
|
|
Does it have to be one account per GPU? I haven't looked too much into this yet, but I have 28 GPUs, and I don't want to create a worker for each on each pool. Any way to make it per system?
I have two GPU's in two different systems both using the same workers on every pool without a problem. IDK if this will scale to 28 GPU's. I might consider at least for bitclockers using different workers, because you might run into trouble with that many gpu's requesting getworks. |
|
|
|
1:29:36] slush: 4817926
1:29:36] RPC request [getwork] submitted to DigBTC.net (DigBIT)
1:29:36] RPC request [getwork] submitted to DigBTC.net (DigBIT)
1:29:36] RPC request [getwork] submitted to DigBTC.net (DigBIT)
1:29:37] RPC request [getwork] submitted to DigBTC.net (DigBIT)
1:29:37] RPC request [getwork] submitted to DigBTC.net (DigBIT)
1:29:38] RPC request [getwork] submitted to DigBTC.net (DigBIT)
1:29:38] RPC request [getwork] submitted to DigBTC.net (DigBIT)
1:29:38] RPC request [getwork] submitted to DigBTC.net (DigBIT)
1:29:39] RPC request [getwork] submitted to DigBTC.net (DigBIT)
1:29:39] RPC request [getwork] submitted to DigBTC.net (DigBIT)
1:29:39] RPC request [getwork] submitted to DigBTC.net (DigBIT)
1:29:40] RPC request [getwork] submitted to DigBTC.net (DigBIT)
1:29:40] RPC request [getwork] submitted to DigBTC.net (DigBIT)
1:29:40] RPC request [getwork] submitted to DigBTC.net (DigBIT)
1:29:41] RPC request [getwork] submitted to DigBTC.net (DigBIT)
1:29:41] RPC request [getwork] submitted to DigBTC.net (DigBIT)
1:29:41] RPC request [getwork] submitted to DigBTC.net (DigBIT)
1:29:42] RPC request [getwork] submitted to DigBTC.net (DigBIT)
1:29:42] btcpool24: 977187
1:29:42] RPC request [getwork] submitted to DigBTC.net (DigBIT)
1:29:43] RPC request [getwork] submitted to DigBTC.net (DigBIT) is the newest version supposed to do this sooo much? I think that is the reason Bitclockers kills bithopper. Too many getworks. Switched to CherryPicker yesterday to test it out and OMFG:  Worked flawlessly. Just need to figure out what Cherrypicker is doing differently and emulate it. Also, I am getting .2% stales with Cherrypicker and never got below 4% stales with bithopper. . . . . . Edit: In fact, I am getting DRASTICALLY less stales on every pool. Like by a factor of 10. |
|
|
|
Bloodred, here's where a slicing function could come in handy  I'll probably only end up with a few shares on BitClockers once it is higher than Bithasher. Would be good to submit to both. Yea, I disabled bithasher until bitclockers finishes. Probably should have let the hopper stay on bithashers, but I guess I was too excited to see bitclockers working to see some newly added pool take away its shares.  |
|
|
|
Damn you, just made me add ANOTHER pool. Ive had like 15 tabs open just for pools for like a month now.
I used to do that. I stopped and now just have this quick shortcut list: https://i.imgur.com/WlBjL.pngThats awesome, but I'm too lazy for that. Ill stick with the 15 tabs in Chrome. I do like that I can Ctrl+Shift+R and reload all the tabs at once. Also, bitclockers working flawlessly, LOVE IT. Edit: Just saw you have bitp.it on there. Have the config for CP for that? I tried to make it myself but got stuck trying to figure out the hashrate.Edit: NVM, saw the new configs. |
|
|
|
|
Show Posts
