Topic: Continuum Mining Pool: No fees; Client uptime monitoring via twitter and email - page 15. (Read 50243 times)

Cool, a Canadian based pool ! I definitely shall give your pool a try.

Do you pay out from generated blocks or directly like Luke's (Eligius) pool?

Seems like a clone of Luke's (Eligius) pool, but it doesn't really matter. The more pools the better.

Now for some quick questions. Are you running this off of a dedicated connection (data center) or a shaw cable connection ? Do you have a backup server or some sort of high availability setup?

Also where do you guys get the pool software from? I too would like to setup a similar type of pool for me and a bunch of friends. Any chance of sharing the software?

To the user submitting shares with a username which is not a valid bitcoin address: you can no longer use a username which is not a bitcoin address so are no longer able to submit shares. That being said, we found two quick blocks today so you are owed some BTC assuming they mature. If you can PM me with the username your client was using and a BTC address, I will have them credited to you.

Twitter monitoring support is in. You simply use twitter:username instead of mailto:username in the contact field shown above. When your miner goes down, you'll get a DM which you can have Twitter send to your phone etc.

Note: you must be following ContinuumPool on Twitter for this to work.

If there is interest, I can add the ability to query balances, set up monitors etc via Twitter. Might be handy for those who don't want to code RPC clients.

For those interested, here is a little bit of perl that sets up a monitor for a worker. Replace the obvious bits.

#!/usr/bin/perl
use JSON::RPC::Client;
my $client = new JSON::RPC::Client;
my $uri = 'http://rpc.continuumpool.com:8330/rpc';
$client->prepare($uri, ['hashrate','roundstart','monitoradd','dropmonitor', 'balance','balancecurrent']);
$worker = '1NNdsxTuF1p9J9hmFKoxdM3ki4GgMBajN7';
$res = $client->monitoradd({
'worker' => $worker, 'contact' => 'mailto:[email protected]',
'sharetime' => '10 minutes', 'name' => 'My 5970'}));
print "Success" if ($res == 1);

Using the framework above, you can get the pool hashrate with:
print $client->hashrate(undef);
or the worker hashrate with:
print $client->hashrate("workeraddr");

balance and balancecurrent work the same way.

Thank you, sounds great!

I am using the scoring algorithm described here:
https://bitcointalksearch.org/topic/geometric-method-new-cheat-proof-mining-pool-scoring-method-4787
It was designed to prevent pool-hopping attacks.

Payout is automatic when the worker hits 1 BTC.

Share or Score based?

When are confirmed balances paid? At x time, threshold, etc?

Hello,

I would like to announce the availability of the Continuum mining pool. It is new and could use some testing. The pool runs with no fees and is aimed at more serious miners, though all are certainly welcome. The pool supports long-polling and should provide good connectivity to north-american miners. It also supports monitoring of miners; if your miner hasn't submitted a share within a defined period, you will get an email or Twitter to that effect.

Usage:
Simply connect your miner to continuumpool.com port 8332. Use the bitcoin address to which you would like to be paid as the username and use any password. I recommend that you use a different Bitcoin address for each worker so that balances and uptime monitoring can be set per-worker.

The pool provides an RPC interface. It does not provide a web interface, though anyone is welcome to write one. To use the RPC service, connect to http://rpc.continuumpool.com:8330/rpc and use the following methods.

balance(workeraddr) Returns confirmed unpaid balance
balancecurrent(addr) Current round balance
roundstart() Returns the time of the start of the round.
monitoradd({worker => 'workeraddr', 'contact' => 'mailto:[email protected]', 'sharetime' => '5 minutes', 'name' => 'some descriptive name'}) Adds an email monitor. If the worker hasn't submitted a share in set time, an email is generated
monitordrop({id => monitorid, worker => 'workeraddr'}) Cancels a monitor. Get the ID from the generated email.

Once again, testing and feedback would be greatly appreciated.