I am still at the old version without the slice things..This seems pretty stable..
What is the status of the new version? Is it stable and should I update or just wait a bit more?
What is the idea of the slice things and is there any benefit?
better stay with that atm , having issues with the new one the benefit would be getting a "slice" of the pie on every available pool, do some numbers  |
|
|
|
Ed, the scheduler option for RoundTimeDynamicPenaltyScheduler , does that actually work? I get the following error when I try to use that: [03:08:31] Selecting scheduler: RoundTimeDynamicPenaltyScheduler
[03:08:31] FATAL Error, scheduler did not return any pool!
c00w said it's just a placeholder |
|
|
|
Let me just make sure I'm reading this right. I should basically be enabling ALL the backup pools and setting them all to backup_latehop?
not all, only the backup pools you use Ok, even the PPS ones? As far as the slicing goes, I've disabled BTCPool24 and it's now just been stuck on MtRed for 15 mins or so. I don't think it's working PPS pool should be used as backup always, you're stuck on mt.red if is the only prop pool available, seems to be working allright |
|
|
|
Is polmine.pl down for anyone else?
yep, down here too, ozco is back, mt.red got a lucky one, and btcpool24 posibly faking stats (collecting info) EXTRA edit: btcpool24 changed their payout system with an unknown one and their json stats seem to have a life of their own  |
|
|
|
Let me just make sure I'm reading this right. I should basically be enabling ALL the backup pools and setting them all to backup_latehop?
not all, only the backup pools you use |
|
|
|
So for some reason it likes to get stuck on BTCPool24.
yep, something is not right, 40593 seconds from beginning of the round (11 hours) at 30Gh on average (have seen 50Gh+), has only 288422 shares... So disable it for now you reckon? I did  just trying to find out if they're scr...g with us |
|
|
|
So for some reason it likes to get stuck on BTCPool24.
yep, something is not right, 40593 seconds from beginning of the round (11 hours) at 30Gh on average (have seen 50Gh+), has only 288422 shares... |
|
|
|
mine stuck with polmine and putting it on info or disable doesn't seem to matter edit: where is macboy80 ? I'm gonna give him a chat, he f.. up a little bit the stats page, the colors look nice but has lost functionality, grr edit2: I retry that, sorry macboy, it's the scheduler, without it enabled changing roles in stats page works like charm, this time I freaked out  |
|
|
|
Testing for 10 minutes now, but it didn't hop yet...
It stays on bitcoins.lc (36%) while polmine (29%) and bloodys (27%) are available...
it should slice not hop, I think, look in the console at the getwork's c00w will break the myth  Hmm, isn't slicing the same word for "hopping between <43% (or something) pools"? Getwork is only at bitcoin.lc since I started it. correct what I've said, time slicing (what we have) is submitting to same pool from available ones any predet. number of minutes, and share based would be balancing between available pools (round-robin) what c00w said it was a little more difficult to implement edit: we're testing time slicing now and seems it doesn't work like it should |
|
|
|
Testing for 10 minutes now, but it didn't hop yet...
It stays on bitcoins.lc (36%) while polmine (29%) and bloodys (27%) are available...
it should slice not hop, I think, look in the console at the getwork's c00w will break the myth |
|
|
|
c00w updated something!
Dammit I just spent the last half hour working on the slice scheduler myself and I was about to post my fix... you sound like the avatar (no pun intended) make you pull request anyways if you want to share, it might have something needed |
|
|
|
hey, seems like ozco covered their windows so we cannot see in, they have 110 hours from last block so the probabilities are high. I suppose they want to make sure were not counted in the next round  It's working for me? Can you not get to the api? yep it's definitely working but not updating for couple of hours |
|
|
|
hey, seems like ozco covered their windows so we cannot see in, they have 110 hours from last block so the probabilities are high. I suppose they want to make sure were not counted in the next round edit: I would be more than happy to donate 1% if pool ops. quit doing tricks with stats |
|
|
|
Yeah, except you don't know if when you jump in, that's the start of a long round. The graph is what has already happened. eeehh, If you know some method to find out if it will be a long or short round share it please, it would be a great help to all of us I have a quarter. Shall we flip it? tails - short heads - long give it a try... edit : the short story of finding a block |
|
|
|
yep just like a normal page, if you open a port in your router I could see it too |
|
|
|
can it be worth to force mine at slush when we see someting like this: [url]  there have been some very short rounds... Yeah, except you don't know if when you jump in, that's the start of a long round. The graph is what has already happened. eeehh, If you know some method to find out if it will be a long or short round share it please, it would be a great help to all of us |
|
|
|
can it be worth to force mine at slush when we see someting like this: [url] there have been some very short rounds... mine_slush already does that, hope it didn't broke with the new scheduler, so you're getting a share of that don't worry |
|
|
|
Ahh, good to know I'm not the only one. I'll see if I can fix it up, not sure how c00w intended to trigger a switch, let me try a quick hack.
now it was very long from BtcPool24 ------------------------ [17:02:02] Error in pool api for btcpool24 [17:02:02] Error in pool api for btcpool24 [17:02:02] Error in pool api for btcpool24 [17:02:02] Error in pool api for btcpool24 ------------------------ and then BtcPool24 and polmine changed to api_disable I have it manually changed back to mine - if I have not done this, does this stay at api_disable or sometimes changing back? can someone update pools.cfg in git [btcworld]
name: BTC World
mine_address: btcworld.de:8332
api_address: http://www.btcpool24.com/json_stats.php
api_method: json
api_key: shares_this_round
Works fine now yep with pleasure but you're getting share count from "btcpool24" and put it in "btcworld" pool , 2 distinct pools |
|
|
|
I believe it always stays api_disabled right now. When it actually says api_disabled.
BTCworld.. didnt we give up on them for faking stats? I have them disabled.. pretty sure it was due to screwing with us.
hehe lots of btc[any] pools here, |
|
|
|
|
Show Posts
(
