Tried an escaped ; as the separator, also tried a different address, still the same output from the pool side monitors..
Any other ideas? I was under the impression that if it wasn't registering the correct address, it wouldn't accept my hashes?
Topic: Continuum Mining Pool: No fees; Client uptime monitoring via twitter and email - page 11. (Read 50243 times)
June 01, 2011, 01:00:28 AM
June 01, 2011, 12:20:10 AM
Btw, I am curious as to how useful publishing the share and score logs would be. Particularly whether that ensures pool integrity given that the worker solution is included. I would not be willing to publish the IP addresses of workers but could make previous round sharelog data available less IP address. So, would that be useful to anyone? Does anyone object IE are their privacy concerns here of which I am not aware?
May 31, 2011, 11:57:56 PM
Also, does "overall hash rate" include PPS miners? It would be more useful to know the hashrate of the score-based so we can know its variance.
Overall hashrate is currently only score-based miners as pps doesn't really factor into normal pool performance.If PPS is abused, it will go away but will not affect the score-based payouts.
Quote
I don't know if that's the problem, but I noticed that when I copy-paste my address I often get a stray space which causes it to be unrecognized.
Note to martok - trim spaces from the input.
Indeed, will do. Note to martok - trim spaces from the input.
May 31, 2011, 11:36:38 PM
For those wanting PPS payment, it is now live. Simply use yourpaymentaddress;pps or yourpaymentaddress0pps as the username. PPS miners will not affect regular miners and PPS carries a 5% expected fee. Regular mining is of course still at no fee. However, PPS was requested so there it is.
edit: PPS payout rate:
http://www.continuumpool.com/ppsrate.php
or preferably through the ppsrate RPC call.
edit: You can now pass a boolean pps (null by default) argument to hashrate.
pps => null = overall hashrate
pps => false regular miners only
pps => true only pps miners
I hope you have carefully evaluated the risks of PPS due to sabotage as well as normal variance. Tycho takes 10% for a reason.edit: PPS payout rate:
http://www.continuumpool.com/ppsrate.php
or preferably through the ppsrate RPC call.
edit: You can now pass a boolean pps (null by default) argument to hashrate.
pps => null = overall hashrate
pps => false regular miners only
pps => true only pps miners
Also, does "overall hash rate" include PPS miners? It would be more useful to know the hashrate of the score-based so we can know its variance.
However on the continuumpool page I am getting 0 for my hash rate and ?> for confirmed payouts at 12DbPbfp2twBTfjSBW9QhVQ5PrGb2puisV
Any idea what's going on here?
I don't know if that's the problem, but I noticed that when I copy-paste my address I often get a stray space which causes it to be unrecognized.Any idea what's going on here?
Note to martok - trim spaces from the input.
May 31, 2011, 11:36:32 PM
I've been mining for a while now with this poclbm invocation;
./poclbm.py -v -w 128 -d 0 --user 12DbPbfp2twBTfjSBW9QhVQ5PrGb2puisV0pps --pass any --host continuumpool.com --port 8332
The hashes are going through;
01/06/2011 14:30:01, 7869656a, accepted
01/06/2011 14:30:36, long poll: new block 00000648a0f3b516
01/06/2011 14:31:49, b7c004ce, accepted
01/06/2011 14:31:53, e9698573, accepted
01/06/2011 14:32:09, bc9158e3, accepted
01/06/2011 14:32:20, 3988c4da, accepted
01/06/2011 14:32:40, e4c0a789, accepted
01/06/2011 14:32:49, 77ff441b, accepted
01/06/2011 14:33:19, bf329670, accepted
01/06/2011 14:34:56, b450a6a0, accepted
01/06/2011 14:35:07, 73f1a043, accepted
However on the continuumpool page I am getting 0 for my hash rate and ?> for confirmed payouts at 12DbPbfp2twBTfjSBW9QhVQ5PrGb2puisV
Any idea what's going on here?
./poclbm.py -v -w 128 -d 0 --user 12DbPbfp2twBTfjSBW9QhVQ5PrGb2puisV0pps --pass any --host continuumpool.com --port 8332
The hashes are going through;
01/06/2011 14:30:01, 7869656a, accepted
01/06/2011 14:30:36, long poll: new block 00000648a0f3b516
01/06/2011 14:31:49, b7c004ce, accepted
01/06/2011 14:31:53, e9698573, accepted
01/06/2011 14:32:09, bc9158e3, accepted
01/06/2011 14:32:20, 3988c4da, accepted
01/06/2011 14:32:40, e4c0a789, accepted
01/06/2011 14:32:49, 77ff441b, accepted
01/06/2011 14:33:19, bf329670, accepted
01/06/2011 14:34:56, b450a6a0, accepted
01/06/2011 14:35:07, 73f1a043, accepted
However on the continuumpool page I am getting 0 for my hash rate and ?> for confirmed payouts at 12DbPbfp2twBTfjSBW9QhVQ5PrGb2puisV
Any idea what's going on here?
May 31, 2011, 04:29:34 PM
I can confirm that these functions are now operational, thanks.
May 31, 2011, 04:12:06 PM
I have been able to login using "worker;payto" now for some reason.. Although I had tried quotes before and it was not working. My problem now is how do I get an accurate hashrate for the workers combined, as well as unconfirmed balance? If you do an rpc-call to the payment address, it does not properly display either clienthashrate(paytoaddr) or currentbalance(paytoaddr)
Should be fixed. You can now pass either a worker or payment address to balancecurrent or hashrate. For the confirmed balance though, you can only query the address that is to actually be paid (payto in your instance). If specific worker balances are needed, I can add a call for that at some point.
May 31, 2011, 04:01:59 PM
I have been able to login using "worker;payto" now for some reason.. Although I had tried quotes before and it was not working. My problem now is how do I get an accurate hashrate for the workers combined, as well as unconfirmed balance? If you do an rpc-call to the payment address, it does not properly display either clienthashrate(paytoaddr) or currentbalance(paytoaddr)
May 31, 2011, 02:41:14 PM
monitordrop({id => monitorid, worker => 'workeraddr'}) Cancels a monitor. Get the ID from the generated email.
How can I get the monitor ID if I'm using twitter but not email?
May 31, 2011, 02:33:58 PM
monitordrop({id => monitorid, worker => 'workeraddr'}) Cancels a monitor. Get the ID from the generated email.
How can I get the monitor ID if I'm using twitter but not email?
May 30, 2011, 07:48:48 PM
For those wanting PPS payment, it is now live. Simply use yourpaymentaddress;pps or yourpaymentaddress0pps as the username. PPS miners will not affect regular miners and PPS carries a 5% expected fee. Regular mining is of course still at no fee. However, PPS was requested so there it is.
edit: PPS payout rate:
http://www.continuumpool.com/ppsrate.php
or preferably through the ppsrate RPC call.
edit: You can now pass a boolean pps (null by default) argument to hashrate.
pps => null = overall hashrate
pps => false regular miners only
pps => true only pps miners
edit: PPS payout rate:
http://www.continuumpool.com/ppsrate.php
or preferably through the ppsrate RPC call.
edit: You can now pass a boolean pps (null by default) argument to hashrate.
pps => null = overall hashrate
pps => false regular miners only
pps => true only pps miners
May 30, 2011, 12:34:53 PM
Do you aggregate payouts from the same IP? I have 6 poclbm instances running on two machines, each with a different address, and it seems I got to one of the addresses the rewards for all.
No. The IP is not used in any payout calculations so that is strange indeed. I am using the sendmany RPC call to batch send transactions into a single TX but your bitcoind should still show you receiving payments on different addresses. May 30, 2011, 05:59:16 AM
Do you aggregate payouts from the same IP? I have 6 poclbm instances running on two machines, each with a different address, and it seems I got to one of the addresses the rewards for all.
May 30, 2011, 02:25:46 AM
Three questions:
1) I seem to be getting a TON of invalid/stale exceptions now - did something drastic change?
Or have I messed something up with my settings? invalid/stales are current around 30% of what I am generating.
I broke LP. Fixed now but I'll watch the logs for stales for the next hour and see if that fixes it.1) I seem to be getting a TON of invalid/stale exceptions now - did something drastic change?
Or have I messed something up with my settings? invalid/stales are current around 30% of what I am generating.
Quote
2) I have been unable to login to the pool with poclbm using "-u wokeraddr;paymentaddr" where workeraddr and paymentaddr, could you perhaps give an example?
Try -u "worker;payto"or to avoid the quotes
-u worker0payto
0 also works as a seperator because 0 cannot appear in a bitcoin address.
So:
poclbm -u "16d1jmkPHy26aCTA9TzCD5LbByMVHb4Wu1;1AkUQgtqHbiN4hpYX7VbJVR5hhhb3SAck9"
works for me. Feel free to post your command line though and I'll give it a test over here.
Quote
3) I am using multiple computers over a lan, is there someway I can set this up to connect to your server from only one of my computers?
You could use the mining proxy discussed on the forum elsewhere. That proxy can switch over to another pool if the primary is down also. You would have all your lan computers connect to the proxy and have the proxy connect to the pool.
(edit) added 0 seperator.
May 30, 2011, 12:36:19 AM
Three questions:
1) I seem to be getting a TON of invalid/stale exceptions now - did something drastic change?
Or have I messed something up with my settings? invalid/stales are current around 30% of what I am generating.
2) I have been unable to login to the pool with poclbm using "-u wokeraddr;paymentaddr" where workeraddr and paymentaddr, could you perhaps give an example?
3) I am using multiple computers over a lan, is there someway I can set this up to connect to your server from only one of my computers?
Thanks.
1) I seem to be getting a TON of invalid/stale exceptions now - did something drastic change?
Or have I messed something up with my settings? invalid/stales are current around 30% of what I am generating.
2) I have been unable to login to the pool with poclbm using "-u wokeraddr;paymentaddr" where workeraddr and paymentaddr, could you perhaps give an example?
3) I am using multiple computers over a lan, is there someway I can set this up to connect to your server from only one of my computers?
Thanks.
May 29, 2011, 02:57:20 PM
I have applied an async RPC patch to bitcoind. Hopefully it will drastically reduce RPC errors and idle miners. I had no idea bitcoind blocked the entire process for a getwork request.
http://forum.bitcoin.org/index.php?topic=7757.0
Let me know if you're still getting RPC idle messages.
http://forum.bitcoin.org/index.php?topic=7757.0
Let me know if you're still getting RPC idle messages.
May 28, 2011, 10:07:37 PM
Sure, but the combination of payment address and worker name is almost guaranteed to be unique, even if it's not a bitcoin address. If I am bringing a new miner here, I don't need the association with old mined BTC, and it'd be more meaningful for me to just name them something reasonable.
Of course, I could just write fake bitcoin addresses that contain the name I want, but that seems inefficient.
Of course, I could just write fake bitcoin addresses that contain the name I want, but that seems inefficient.
I see what you're saying. But if we did that, we break the whole monitor API as that takes a worker address. Though you can associate a meaningful name in a monitor for things like Twitter and email alerts. If the pool switched to potentially non-unique worker names, we would need to redo monitors, of which there are currently quite a few. Feel free to put in dummy BTC addresses though.
May 28, 2011, 09:47:33 PM
Does workeraddr have to be a valid Bitcoin address when I do this, or can I generate my own arbitrary worker name and follow it with an actual address?
If not, is there any reason you can't make it this way? It would really make my life easy
If not, is there any reason you can't make it this way? It would really make my life easy
It needs to be a valid address. The reason for this is because monitors need a unique value per worker and creating your own name would have no guarantee of uniqueness. The other reason is a problem of previous shares. Let's say I switch my worker to the a payto address mid-round. My worker address has a balance between 0 and 1 but now will never reach 1 because new shares are being credited to the new payto address. Having the same valid worker address still present will allow the pool to pay out the previous worker address once the payto address + worker hits 1 BTC. Er hope that makes some sense.
Sure, but the combination of payment address and worker name is almost guaranteed to be unique, even if it's not a bitcoin address. If I am bringing a new miner here, I don't need the association with old mined BTC, and it'd be more meaningful for me to just name them something reasonable.
Of course, I could just write fake bitcoin addresses that contain the name I want, but that seems inefficient.
May 28, 2011, 02:31:56 PM
Does workeraddr have to be a valid Bitcoin address when I do this, or can I generate my own arbitrary worker name and follow it with an actual address?
If not, is there any reason you can't make it this way? It would really make my life easy
If not, is there any reason you can't make it this way? It would really make my life easy
It needs to be a valid address. The reason for this is because monitors need a unique value per worker and creating your own name would have no guarantee of uniqueness. The other reason is a problem of previous shares. Let's say I switch my worker to the a payto address mid-round. My worker address has a balance between 0 and 1 but now will never reach 1 because new shares are being credited to the new payto address. Having the same valid worker address still present will allow the pool to pay out the previous worker address once the payto address + worker hits 1 BTC. Er hope that makes some sense.
May 28, 2011, 12:24:18 PM
You can now aggregate your worker payments by logging in with
workeraddr;paymentaddr
as your username. workeraddr is still the primary address to which notification monitors are tied etc, paymentaddr is the address to which payments can be sent. So for example, if you have multiple workers, you can set the same paymentaddr for all of them to get to the 1 BTC payment threshold faster.
workeraddr;paymentaddr
as your username. workeraddr is still the primary address to which notification monitors are tied etc, paymentaddr is the address to which payments can be sent. So for example, if you have multiple workers, you can set the same paymentaddr for all of them to get to the 1 BTC payment threshold faster.
Does workeraddr have to be a valid Bitcoin address when I do this, or can I generate my own arbitrary worker name and follow it with an actual address?
If not, is there any reason you can't make it this way? It would really make my life easy
Jump to: