@auth arguments
auth was meant to be purely optional. It is currently purely optional in bleeding edge and I think the previous version.
Topic: bitHopper: Python Pool Hopper Proxy - page 29. (Read 355768 times)
I got almost the same graph of @organofcorti two weeks ago. (from my own open-sourced simulator)
However, 100% agree with @deepceleron
When we have more proportional pools, efficiency doesn't 'seem' to be decaying because we have more chance to hop into < 43% pool all the time.
Earlier share is always more profittable, slicing reduces profit in the long time, and a share from > 43% pool is less profittable than a share from pps pool.
However, 100% agree with @deepceleron
When we have more proportional pools, efficiency doesn't 'seem' to be decaying because we have more chance to hop into < 43% pool all the time.
Earlier share is always more profittable, slicing reduces profit in the long time, and a share from > 43% pool is less profittable than a share from pps pool.
I´m with latest version 0.1.7.1-30, don´t know why but: Polmine at the instant i run bh, shows the real percentage ad share count, and when it start a round resets to 0% and hop there and mine ok... but with bclc and db nothing of that happens
I think for moment i go back to mine bclc with the old pools.cfg, I know is not the real stats but i least i take some BTC in there that way... and with DB, don´t know.. I think i can live without it until it works, no problem!
btw, bitclockers is fakin the stats too?? just when i thought it starting to mine better there, with less "reconections" (?)
I think for moment i go back to mine bclc with the old pools.cfg, I know is not the real stats but i least i take some BTC in there that way... and with DB, don´t know.. I think i can live without it until it works, no problem!
btw, bitclockers is fakin the stats too?? just when i thought it starting to mine better there, with less "reconections" (?)
I think Bitclockers is alright for the moment. For about an hour their they seemed to reset their JSON stats but they have been back to normal for a few hours now.
I´m with latest version 0.1.7.1-30, don´t know why but: Polmine at the instant i run bh, shows the real percentage ad share count, and when it start a round resets to 0% and hop there and mine ok... but with bclc and db nothing of that happens
I think for moment i go back to mine bclc with the old pools.cfg, I know is not the real stats but i least i take some BTC in there that way... and with DB, don´t know.. I think i can live without it until it works, no problem!
btw, bitclockers is fakin the stats too?? just when i thought it starting to mine better there, with less "reconections" (?)
I think for moment i go back to mine bclc with the old pools.cfg, I know is not the real stats but i least i take some BTC in there that way... and with DB, don´t know.. I think i can live without it until it works, no problem!
btw, bitclockers is fakin the stats too?? just when i thought it starting to mine better there, with less "reconections" (?)
This made me think:
I tried several schedulers now and I thought about the following (new "--HopLowestSharecount" scheduler):
- mine the 3 pools with lowest sharecount at any moment (where 3 can be changed to a custom value with "--hop_ x_pools=3" parameter)
- forget about the 0.43 threshold
- It won't need back-up pools, it will always hop between the 3 pools with lowest sharecount and with 18 pools, that should work without problems
It's a bit like the OldDefaultScheduler and SliceScheduler, without the threshold.
Good news everyone! 43% is dead!
We no longer have to hop at 0.43*difficulty!
...
Of course in any given round, after total shares=diff, your shares are worth less than one. But over time the shorter rounds make up for it. Even with only 3 Prop and backup, your efficiency will always be about 1.83, unless you hop off *too soon*. With ten other pools you get about 250% over PPS - sound familiar?
tl;dr BOLD CLAIM: As long as you always hop to the pool with the lowest shares - regardless of hashspeed - you don't need to hop to backup at 0.43.
We no longer have to hop at 0.43*difficulty!
...
Of course in any given round, after total shares=diff, your shares are worth less than one. But over time the shorter rounds make up for it. Even with only 3 Prop and backup, your efficiency will always be about 1.83, unless you hop off *too soon*. With ten other pools you get about 250% over PPS - sound familiar?
tl;dr BOLD CLAIM: As long as you always hop to the pool with the lowest shares - regardless of hashspeed - you don't need to hop to backup at 0.43.
I tried several schedulers now and I thought about the following (new "--HopLowestSharecount" scheduler):
- mine the 3 pools with lowest sharecount at any moment (where 3 can be changed to a custom value with "--hop_ x_pools=3" parameter)
- forget about the 0.43 threshold
- It won't need back-up pools, it will always hop between the 3 pools with lowest sharecount and with 18 pools, that should work without problems
It's a bit like the OldDefaultScheduler and SliceScheduler, without the threshold.
That is bold to make bold claims, and be incorrect at them. A share submitted after 43.3% of difficulty has elapsed in a proportional pool has a lower expected return than if that share was submitted to a 0 fee PPS or even-paying pool, or if a switch was made to solo mining. By mining from the start until 100% of difficulty shares, you reduce your expected return from 28% to 22%. Considering the lag in statistics and delays switching into and out of a proportional pool, you should be triggering an earlier exit than that to maximize your expected earnings. By mining more pools, you have a higher chance of one of the pools being in the sweet spot, and can also choose the highest reward pool at a particular time, but that doesn't change the ultimate temporal valuation of a submitted share.
I understand your confusion, but if you read my post you'd se the reason for the 200% efficiency at hop=1.0 is that IN THE LONG TERM (sorry but I *am* feeling a bit shouty since we've already been through this when I first posted) it doesn't matter. The simulations are for about 100000 rounds and tell us the expected efficiency.
If you set the hop to 1.0, and you have ten pools then the very few times it actually hits 1.0 before it jumps will have a minimal effect in the long term.
Quote
That is bold to make bold claims, and be incorrect at them.
I quite agree.
ooc
New namecoin pool:
Code:
[nmcbit]
name: nmcbit.com
namecoin: Yep
mine_address: nmcbit.com:8332
api_address: http://nmcbit.com/statistics
api_method: re
api_key: Valid\s+shares\s+for\s+current\s+round:([,0-9]+)
api_strip: ','
url: http://nmcbit.com/dashboard
lol looks like rfc pool is done, this is from the website.
Quote
rfcpool has been shut down because the owner is a fucking idiot - that
should sum it up in brief.
If you were a miner, your money is all accounted for, and you will be paid as
soon as the most recent block matures. If you did not have a wallet address
in your account then email [email protected] and after slinging your abuse
at me, tell me the username/email on account/wallet combination and you will
get paid.
So what happened? Well in short, running a pool and dealing with
people's money is a metric fucktonne harder than I ever imagined it would
be, and a series of fuckups relating to handling all said money has left me
about 150BTC out of pocket, so I'm pulling the plug before the situation
gets any worse.
- an early invalid cost us 30BTC
- the decision to go PPS was crazy and cost us 20BTC
- accidentally paying out double for a block reset in an attempt to turn PPS
off again cost 100BTC
Good luck to all other pool ops.
---
And a note from Rennex: we've been sustaining losses from PPS and the
invalid block along the way, but this latest mess happened at almost
the worst possible moment - Chris was just about to leave on a trip, so
there was no time to start cleaning it up.
But things aren't all FUBAR, we'll take some time to examine the damage
and correct the errors. Some people may have been paid too much because
of auto payouts, and others' accounts got credited too much. We can fix
the latter and deal with the former - and if miners feel that they want
to return excess payouts once we determine the real balances, there will
be a way to do that too.
But for now, we'll cool off and examine the situation, and see if we
want to continue in the near future. Check back in a while
You can also contact us on IRC: #rfcpool on FreeNode.
Oh and if you don't know which pool to choose for now, I hear that
Ozcoin isn't half bad
should sum it up in brief.
If you were a miner, your money is all accounted for, and you will be paid as
soon as the most recent block matures. If you did not have a wallet address
in your account then email [email protected] and after slinging your abuse
at me, tell me the username/email on account/wallet combination and you will
get paid.
So what happened? Well in short, running a pool and dealing with
people's money is a metric fucktonne harder than I ever imagined it would
be, and a series of fuckups relating to handling all said money has left me
about 150BTC out of pocket, so I'm pulling the plug before the situation
gets any worse.
- an early invalid cost us 30BTC
- the decision to go PPS was crazy and cost us 20BTC
- accidentally paying out double for a block reset in an attempt to turn PPS
off again cost 100BTC
Good luck to all other pool ops.
---
And a note from Rennex: we've been sustaining losses from PPS and the
invalid block along the way, but this latest mess happened at almost
the worst possible moment - Chris was just about to leave on a trip, so
there was no time to start cleaning it up.
But things aren't all FUBAR, we'll take some time to examine the damage
and correct the errors. Some people may have been paid too much because
of auto payouts, and others' accounts got credited too much. We can fix
the latter and deal with the former - and if miners feel that they want
to return excess payouts once we determine the real balances, there will
be a way to do that too.
But for now, we'll cool off and examine the situation, and see if we
want to continue in the near future. Check back in a while
You can also contact us on IRC: #rfcpool on FreeNode.
Oh and if you don't know which pool to choose for now, I hear that
Ozcoin isn't half bad
Bitclockers.com Webpage: 3,407,040 shares
Bitclockers.com API:
The hashrate and the currentblockstart field seem to be ok - we could run sanity checks there. OR we just scrub their web page, which might hurt them more + force them to lie to their users more openly.
Edit: can we have the statspage login data at least in the config file instead of in the command line?! Bash history and stuff...
Edit2:
About bitcoinpool.com, we might need a mine_trickle role. Basic outline:
1) Mine until 43.5% of difficulty is reached + time how long it took to reach it.
2) Deduct from this the time it takes you to find 2-3 shares (about a minute for a normal GPU) or just some plain 5 minutes (or nothing, as they expect 50% anyways)
3) After this time, mine on the mine_trickle pool again until 1 valid share has been found. Then issue a LP to your miners and continue with whatever you were doing.
If you look at their stats page, there are ~50 hoppers out of ~400 users who would benefit from this.
The impact isn't that huge anyways, as the real money comes from short rounds - but I still find it very repulsive if pool operators just arbitrarily set rules to get money from miners instead of fixing the real issue.
Bitclockers.com API:
Code:
{"hashrate":233367.6,"activeworkers":641,"roundshares":100322,"roundstales":35389,"lastroundshares":102881,"currentblock":109,"currentblockstart":"2011-08-12 06:15:02"}The hashrate and the currentblockstart field seem to be ok - we could run sanity checks there. OR we just scrub their web page, which might hurt them more + force them to lie to their users more openly.
Edit: can we have the statspage login data at least in the config file instead of in the command line?! Bash history and stuff...
Edit2:
About bitcoinpool.com, we might need a mine_trickle role. Basic outline:
1) Mine until 43.5% of difficulty is reached + time how long it took to reach it.
2) Deduct from this the time it takes you to find 2-3 shares (about a minute for a normal GPU) or just some plain 5 minutes (or nothing, as they expect 50% anyways)
3) After this time, mine on the mine_trickle pool again until 1 valid share has been found. Then issue a LP to your miners and continue with whatever you were doing.
If you look at their stats page, there are ~50 hoppers out of ~400 users who would benefit from this.
The impact isn't that huge anyways, as the real money comes from short rounds - but I still find it very repulsive if pool operators just arbitrarily set rules to get money from miners instead of fixing the real issue.
How exactly can you accidentally open bithopper page to internet ? Option for authentication is nice if you do but i doubt its necessary unless bithopper automatically opens port in firewalls and uses upnp.
it cant... however.. a large portion of us, have the port forwarded, so we can check the stats page from anywhere.
second, the newest hopper connects to IRC, and right now they can get your ip from irc.
third the stats page has some sql injection vulnerabilities.
fourth dont worry about it.. it isnt that much of a pain and helps some of our users.
Couldn't we just add up the user stats for bitcoinpool? They list them all here:
http://bitcoinpool.com/index.php?page=1&ipp=All&do=currentround
for the current round.
Edit: Bitclockers may be doing the same thing.
Stats on their webpages gives a much higher round shares, yes. http://bitcoinpool.com/index.php?page=1&ipp=All&do=currentround
for the current round.
Edit: Bitclockers may be doing the same thing.
Couldn't we just add up the user stats for bitcoinpool? They list them all here:
http://bitcoinpool.com/index.php?page=1&ipp=All&do=currentround
for the current round.
Edit: Bitclockers may be doing the same thing.
http://bitcoinpool.com/index.php?page=1&ipp=All&do=currentround
for the current round.
Edit: Bitclockers may be doing the same thing.
How exactly can you accidentally open bithopper page to internet ? Option for authentication is nice if you do but i doubt its necessary unless bithopper automatically opens port in firewalls and uses upnp.
Quote
The fallacy of reducing variation is why people are paying 7% for PPS (and 20% for credit cards), they can't see or comprehend the long-term.
the problem is you left human behavior out of the equation. How many here lost coin when bitminers union reset? how many are missing coin on rfc? a few of the small pools have also changed payouts mid block. How many pools have we dropped in a month? and then their is crossing difficulty lines which non of yall put into the equations.
it's not just variation, it is how many eggs i want in a weak basket.
Quote
Wouldn't it be better to just show the stats-page (insted of nothin), if no --auth was given?
Not but a note to reconfigure bithopper would be nice.. every single person who hops and will come here and ask what happened to the stats page.
90% of them wont understand that they make up their own user name and pass either.. when you tell them to use --auth user,pass
or has been my exp so far
@c00w
Wouldn't it be better to just show the stats-page (insted of nothin), if no --auth was given?
No, if you don't have a login you most likely are not allowed to see and should not see anything. Noone has to see your stats beside you. And you should know your login credentials.
So wait, are you guys saying that bitcoinpool didn't just solve like 5 blocks today? Because its showing up on my unconfirmed rewards . . . .
it did but it reset json round shares counter several times during current block, it should be ~15% right now according to time*speed
So wait, are you guys saying that bitcoinpool didn't just solve like 5 blocks today? Because its showing up on my unconfirmed rewards . . . .
We need to be able to mark the pool as faker and then bh to vote as fake on p2plp. Because in disabled state it just won't vote at all.
If bitcoinpool is faking stats then they are also faking my estimated reward as well.
@c00w
Wouldn't it be better to just show the stats-page (insted of nothin), if no --auth was given?
No, if you don't have a login you most likely are not allowed to see and should not see anything. Noone has to see your stats beside you. And you should know your login credentials.
are the stats from bclc correct?
it shows on HP:
Friday 12 Aug 23:48:02 CEST
round 17 hours, 6 minutes
7 249 657 shares
and in bh
27700 1,47%
*confused*
it shows on HP:
Friday 12 Aug 23:48:02 CEST
round 17 hours, 6 minutes
7 249 657 shares
and in bh
27700 1,47%
*confused*
Jump to: