[350 GH/s] "Eligius" (experimental) pool: almost feeless PPS, hoppers welcome - page 32.

Luke-Jr

legendary

Activity: 2576

Merit: 1186

Quote from: Xer on May 08, 2011, 05:07:55 AM

Listener for "EL 5850": 08/05/2011 09:52:45, Problems communicating with bitcoin RPC
Listener for "EL 5850": 08/05/2011 10:05:41, warning: job finished, miner is idle

Are you now also under ddos luke-jr?

Hope not. I saw the "miner is idle" a lot when I had very congested (busy) bandwidth. Then I configured my router to prioritize port 8337. No problems since then...

Pieter Wuille

legendary

Activity: 1072

Merit: 1181

No problems here, during the past 10 hours, I had only 0.77% stale/invalid shares.

Xer

member

Activity: 99

Merit: 10

Listener for "EL 5850": 08/05/2011 09:52:45, Problems communicating with bitcoin RPC
Listener for "EL 6950": 08/05/2011 09:52:52, long poll: new block 000038296ef22dd6
Listener for "EL 5850": 08/05/2011 09:52:52, long poll: new block 000038296ef22dd6
Listener for "EL 6950": 08/05/2011 09:55:21, long poll: new block 00002cbbed3655b0
Listener for "EL 5850": 08/05/2011 09:55:24, long poll: new block 00002cbbed3655b0
Listener for "EL 6950": 08/05/2011 09:59:37, long poll: new block 0000665c47d2c95a
Listener for "EL 5850": 08/05/2011 09:59:37, long poll: new block 0000665c47d2c95a
Listener for "EL 6950": 08/05/2011 10:03:40, Problems communicating with bitcoin RPC
Listener for "EL 6950": 08/05/2011 10:03:41, long poll: new block 0000851c59975ed5
Listener for "EL 5850": 08/05/2011 10:03:41, long poll: new block 0000851c59975ed5
Listener for "EL 5850": 08/05/2011 10:05:41, warning: job finished, miner is idle
Listener for "EL 5850": 08/05/2011 10:05:43, Problems communicating with bitcoin RPC
Listener for "EL 5850": 08/05/2011 10:06:44, warning: job finished, miner is idle
Listener for "EL 5850": 08/05/2011 10:08:46, warning: job finished, miner is idle
Listener for "EL 5850": 08/05/2011 10:08:46, Problems communicating with bitcoin RPC
Listener for "EL 5850": 08/05/2011 10:09:46, warning: job finished, miner is idle
Listener for "EL 5850": 08/05/2011 10:09:47, Problems communicating with bitcoin RPC
Listener for "EL 6950": 08/05/2011 10:09:47, Problems communicating with bitcoin RPC
Listener for "EL 5850": 08/05/2011 10:10:38, long poll: new block 00003dee6feac479
Listener for "EL 6950": 08/05/2011 10:10:41, long poll: new block 00003dee6feac479
Listener for "EL 6950": 08/05/2011 10:17:14, warning: job finished, miner is idle
Listener for "EL 5850": 08/05/2011 10:17:17, long poll: new block 000005cdf4cce15c
Listener for "EL 6950": 08/05/2011 10:17:17, long poll: new block 000005cdf4cce15c
Listener for "EL 5850": 08/05/2011 10:18:31, warning: job finished, miner is idle
Listener for "EL 5850": 08/05/2011 10:23:34, long poll: new block 000009c7a8c83b56
Listener for "EL 6950": 08/05/2011 10:23:34, long poll: new block 000009c7a8c83b56
Listener for "EL 6950": 08/05/2011 10:24:30, warning: job finished, miner is idle
Listener for "EL 5850": 08/05/2011 10:26:06, warning: job finished, miner is idle
Listener for "EL 6950": 08/05/2011 10:29:25, long poll: new block 000077f3ac07a6cd
Listener for "EL 5850": 08/05/2011 10:29:25, long poll: new block 000077f3ac07a6cd
Listener for "EL 6950": 08/05/2011 10:31:23, warning: job finished, miner is idle
Listener for "EL 6950": 08/05/2011 10:31:24, Problems communicating with bitcoin RPC
Listener for "EL 5850": 08/05/2011 10:32:24, warning: job finished, miner is idle
Listener for "EL 6950": 08/05/2011 10:38:29, warning: job finished, miner is idle
Listener for "EL 5850": 08/05/2011 10:41:38, warning: job finished, miner is idle
Listener for "EL 6950": 08/05/2011 10:45:38, warning: job finished, miner is idle
Listener for "EL 5850": 08/05/2011 10:47:02, warning: job finished, miner is idle
Listener for "EL 5850": 08/05/2011 10:47:03, Problems communicating with bitcoin RPC
Listener for "EL 5850": 08/05/2011 10:49:31, warning: job finished, miner is idle
Listener for "EL 6950": 08/05/2011 10:55:27, long poll: new block 00000b9a443e4b31
Listener for "EL 5850": 08/05/2011 10:55:27, long poll: new block 00000b9a443e4b31
Listener for "EL 5850": 08/05/2011 11:00:08, long poll: new block 0000472862cdf745
Listener for "EL 6950": 08/05/2011 11:00:08, long poll: new block 0000472862cdf745
Listener for "EL 6950": 08/05/2011 11:03:46, warning: job finished, miner is idle
Listener for "EL 6950": 08/05/2011 11:03:47, Problems communicating with bitcoin RPC
Listener for "EL 6950": 08/05/2011 11:03:52, long poll: new block 00008d7940f92c49
Listener for "EL 5850": 08/05/2011 11:03:52, long poll: new block 00008d7940f92c49
Listener for "EL 5850": 08/05/2011 11:04:50, warning: job finished, miner is idle
Listener for "EL 5850": 08/05/2011 11:07:52, warning: job finished, miner is idle
Listener for "EL 5850": 08/05/2011 11:09:24, warning: job finished, miner is idle
Listener for "EL 5850": 08/05/2011 11:09:24, Problems communicating with bitcoin RPC
Listener for "EL 6950": 08/05/2011 11:09:27, long poll: new block 000023e70f6bf0a4
Listener for "EL 5850": 08/05/2011 11:09:27, long poll: new block 000023e70f6bf0a4
Listener for "EL 5850": 08/05/2011 11:14:34, warning: job finished, miner is idle
Listener for "EL 5850": 08/05/2011 11:14:35, Problems communicating with bitcoin RPC
Listener for "EL 6950": 08/05/2011 11:14:35, warning: job finished, miner is idle
Listener for "EL 5850": 08/05/2011 11:17:39, warning: job finished, miner is idle
Listener for "EL 6950": 08/05/2011 11:19:53, Problems communicating with bitcoin RPC
Listener for "EL 6950": 08/05/2011 11:19:54, warning: job finished, miner is idle
Listener for "EL 6950": 08/05/2011 11:20:01, long poll: new block 000022e98973e76f
Listener for "EL 5850": 08/05/2011 11:20:01, long poll: new block 000022e98973e76f
Listener for "EL 6950": 08/05/2011 11:21:21, Problems communicating with bitcoin RPC
Listener for "EL 6950": 08/05/2011 11:24:24, Problems communicating with bitcoin RPC
Listener for "EL 5850": 08/05/2011 11:26:25, warning: job finished, miner is idle
Listener for "EL 6950": 08/05/2011 11:26:25, Problems communicating with bitcoin RPC
Listener for "EL 5850": 08/05/2011 11:26:25, Problems communicating with bitcoin RPC
Listener for "EL 6950": 08/05/2011 11:26:26, warning: job finished, miner is idle
Listener for "EL 5850": 08/05/2011 11:30:13, warning: job finished, miner is idle
Listener for "EL 5850": 08/05/2011 11:30:13, Problems communicating with bitcoin RPC
Listener for "EL 6950": 08/05/2011 11:30:15, warning: job finished, miner is idle
Listener for "EL 6950": 08/05/2011 11:30:16, Problems communicating with bitcoin RPC
Listener for "EL 5850": 08/05/2011 11:30:18, Problems communicating with bitcoin RPC
Listener for "EL 6950": 08/05/2011 11:30:19, long poll: new block 00005712c78801e8
Listener for "EL 5850": 08/05/2011 11:30:22, long poll: new block 00005712c78801e8
Listener for "EL 5850": 08/05/2011 11:31:19, Problems communicating with bitcoin RPC
Listener for "EL 5850": 08/05/2011 11:33:52, Problems communicating with bitcoin RPC
Listener for "EL 5850": 08/05/2011 11:33:53, warning: job finished, miner is idle
Listener for "EL 5850": 08/05/2011 11:34:52, warning: job finished, miner is idle
Listener for "EL 5850": 08/05/2011 11:34:53, Problems communicating with bitcoin RPC
Listener for "EL 6950": 08/05/2011 11:34:53, Problems communicating with bitcoin RPC
Listener for "EL 5850": 08/05/2011 11:38:30, warning: job finished, miner is idle
Listener for "EL 5850": 08/05/2011 11:38:32, Problems communicating with bitcoin RPC
Listener for "EL 6950": 08/05/2011 11:41:04, warning: job finished, miner is idle
Listener for "EL 6950": 08/05/2011 11:41:05, Problems communicating with bitcoin RPC
Listener for "EL 5850": 08/05/2011 11:43:06, warning: job finished, miner is idle
Listener for "EL 6950": 08/05/2011 11:50:42, warning: job finished, miner is idle
Listener for "EL 6950": 08/05/2011 11:55:14, long poll: new block 00000086c33efc03
Listener for "EL 5850": 08/05/2011 11:55:14, long poll: new block 00000086c33efc03
Listener for "EL 6950": 08/05/2011 11:57:12, warning: job finished, miner is idle
Listener for "EL 6950": 08/05/2011 12:00:20, Problems communicating with bitcoin RPC
Listener for "EL 6950": 08/05/2011 12:00:20, warning: job finished, miner is idle

Are you now also under ddos luke-jr?

wumpus

hero member

Activity: 812

Merit: 1022

No Maps for These Territories

Just switched here from Slush's miner

Veldy

member

Activity: 98

Merit: 10

Quote from: cosurgi on May 02, 2011, 04:55:42 AM

I just wanted to let you know guys that this pool works very good for me. I am getting exactly the expected amounts.

None are still confirmed. but it's OK. I would like to know how invalid blocks get handled.

Also, I think that if all of us, who have external IP, connect our clients to his pool to receive newly found blocks we will a bit decrease the chance of invalid blocks - because solved blocks will spread faster in p2p network.

luke, is it enough to "-addnode pool.bitcoin.dashjr.org" upon our bitcoind start? or "-addnode 173.242.112.53" ?

You don't need an external IP if you are connected to broadband behind a router (your router already has the external IP). The latest bitcoin client (and thus bitcoind) supports uPNP, so if your router supports it, turn it on. My client currently has 64 connections. Otherwise, you have to forward port 8333 to the machine your client (or bitcoind daemon) is running on to get more than 8 connections [and to be actively part of the P2P network].

aahzmundus

hero member

Activity: 644

Merit: 500

Invest & Earn: https://cloudthink.io

Thx netxshare, I appreciate you adding this feature as looking up this info was a little bit of a hassle for me before!

netxshare

full member

Activity: 120

Merit: 100

I thought I would just let everyone know I added support for luke's pool to my windows sidebar gadget you can check out the forum post if you want to use it.

https://bitcointalksearch.org/topic/windows-sidebar-gadget-supports-deepbitslusheligiusbtcminebtcguild-7071

Grinder

legendary

Activity: 1284

Merit: 1001

Quote from: foxmulder on May 06, 2011, 04:47:19 PM

any clues why it pointed the wrong time and cannot retrieve my details ?, i have installed json-perl and libio-all-lwp-perl.

The parameter can't be read with
my $acc = $1;
it needs to be
my $acc = shift;
or
my $acc = $ARGV[0];

foxmulder

newbie

Activity: 37

Merit: 0

Quote from: ?? on ??

Slightly more informative ...

Code:

#!/usr/bin/perl

use JSON;
use LWP::Simple;
use Data::Dumper;

my $acc = $1;
my $data = decode_json(get('http://luke.dashjr.org/programs/bitcoin/pool/balances.json'))->{$acc};
my $speed = decode_json(get('http://luke.dashjr.org/programs/bitcoin/pool/hashrate.php?addr='.$acc));

printf "oldest: %4d-%02d-%02d %02d:%02d:%02d\n",
sub { $_[5]+1900, $_[4]+1, @_[3,2,1] }->(localtime($data->{oldest}));
printf "newest: %4d-%02d-%02d %02d:%02d:%02d\n",
sub { $_[5]+1900, $_[4]+1, @_[3,2,1] }->(localtime($data->{newest}));

printf "User shares: %d\n", $speed->{'shares'};
printf("Balance: %.12f\n", ( ($data->{balance})*1e-8 ));
printf "User speed: %8.4f GHash/sec (%.6f MHash/sec)\n", $speed->{'hashrate'} * 1e-9, $speed->{'hashrate'} * 1e-6;

my($total) = get('http://luke.dashjr.org/programs/bitcoin/pool/hashrate.txt');
$total =~ s/\n//g;
printf "Pool speed: %8.4f GHash/sec\n", $total * 1e-9;

I've got this :

Quote

#./luke.pl my_addr
oldest: 1970-01-01 07:00:00
newest: 1970-01-01 07:00:00
User shares: 1254
Balance: 0.000000000000
User speed: 17.9530 GHash/sec (17952.963297 MHash/sec)
Pool speed: 17.9243 GHash/sec

any clues why it pointed the wrong time and cannot retrieve my details ?, i have installed json-perl and libio-all-lwp-perl.

[Edit]

Editing $acc var to reflect my address is working fine.

cosurgi

sr. member

Activity: 298

Merit: 250

OK, I hope that your pool is going to be stable, and I joined again.

Also I hope that you eliminated all possible ways of cheating on other pool users:
- disconnecting after 50% (or such) shares, till block, were contributed
- submitting the same share multiple times

and perhaps others, that I forgot about.

gmaxwell

staff

Activity: 4284

Merit: 8808

Quote from: Luke-Jr on April 30, 2011, 08:45:52 AM

Quote from: LightRider on April 30, 2011, 02:32:47 AM

Another idea I had, was to put it back to paying out tiny coins again, but also accepting transactions using those coins at no fee. The two problems with this plan would be: 1) the clients will still think they need to pay a fee unless you hack them, and 2) it leaves less space in our blocks for normal with-fee transactions. Currently undecided. It also wouldn't be very easy to write.

How about…

Keep a queue of pool miners that need to be paid (say, balance >0.01 at the end of this block) ordered by how much they're owed.

First add miners who are owed more than 2 BTC to the block you're working on. Then add transactions ordered by profit. Then add miners owed less than 2 BTC until there is no room left. Alternatively, treat the payments as transactions having a transaction fee equal to 1/100th of what they are owed and just rank them with the normal transactions. I guess you'll need to to do a little fancy footwork for computing the size of the generated transaction.

In this way people will get paid out as fast as possible when the volume of paying transactions is low, and slower when it is high. This would reduce the number of paying transactions the pool must forgo in order to pay mining wages, though I suppose there aren't any currently

.

You could make this more attractive by changing the payouts to include the fees, since then any slowness in the payout would be directly related to increased income for the miners— and just increase your average pool payment per second a bit to compensate.

Luke-Jr

legendary

Activity: 2576

Merit: 1186

Quote from: jarly on May 05, 2011, 09:44:37 PM

Also, are you planning on implementing the threshold signed message thingy?

When there's a final standard for it (eg, merged to mainline git), probably. That way you can set your minimum payout by signing a command with your payout address.

In case anyone else noticed and is confused by it, we had an orphan block today. Sad

jarly

newbie

Activity: 29

Merit: 0

We need more people to join :-/

Also, are you planning on implementing the threshold signed message thingy?

zoro

full member

Activity: 226

Merit: 100

i think it is 1 or 2 blocks per day! that is my impression

RustyShackleford

newbie

Activity: 43

Merit: 0

Quote from: Luke-Jr on May 05, 2011, 10:04:18 AM

Quote from: RustyShackleford on May 05, 2011, 09:50:06 AM

Can you check on 1CWw7iNrhz7uHoTDTqAE2RZS9pwsD9Rfr3 for me then? Seems to have been paid more than once in a few blocks but not showing up in any blocks http://blockexplorer.com/address/1CWw7iNrhz7uHoTDTqAE2RZS9pwsD9Rfr3

It has only earned 0.60927445 BTC total, so far. Payout is once it reaches a minimum 1 BTC.

My bad, I read the line backwards Tongue

The "paid" was for a different address

Luke-Jr

legendary

Activity: 2576

Merit: 1186

Quote from: RustyShackleford on May 05, 2011, 09:50:06 AM

Can you check on 1CWw7iNrhz7uHoTDTqAE2RZS9pwsD9Rfr3 for me then? Seems to have been paid more than once in a few blocks but not showing up in any blocks http://blockexplorer.com/address/1CWw7iNrhz7uHoTDTqAE2RZS9pwsD9Rfr3

It has only earned 0.60927445 BTC total, so far. Payout is once it reaches a minimum 1 BTC.

Also, Ufasoft should work now. Fixed a bug in pushpool related to standard compliance. "The response MUST include a WWW-Authenticate header field (section 14.47) containing a challenge applicable to the requested resource."

RustyShackleford

newbie

Activity: 43

Merit: 0

Quote from: Luke-Jr on May 04, 2011, 09:27:10 PM

Quote from: RustyShackleford on May 04, 2011, 08:40:46 PM

When an address is "paid" should we expect to see it show in blockexplorer or does it then go in a queue to be paid with the next or possibly subsequent block found by the pool?

It should be part of the generation in blockexplorer.

Can you check on 1CWw7iNrhz7uHoTDTqAE2RZS9pwsD9Rfr3 for me then? Seems to have been paid more than once in a few blocks but not showing up in any blocks http://blockexplorer.com/address/1CWw7iNrhz7uHoTDTqAE2RZS9pwsD9Rfr3

Thanks

Luke-Jr

legendary

Activity: 2576

Merit: 1186

Quote from: luffy on May 05, 2011, 04:37:06 AM

what is the current block finding rate for this pool? i see the pool hash rate between 10 and 20 Gh.

[09:50:49] ;;bc,calc [bc,eligius]
[09:50:50] The average time to generate a block at 16721739.3391 Khps, given current difficulty of 109670.13329248 , is 7 hours, 49 minutes, and 28 seconds

We had a nice peak of 31 GH before the debugging and MySQL switch. Spread the word so we can reach 100 Wink

luffy

hero member

Activity: 607

Merit: 500

what is the current block finding rate for this pool? i see the pool hash rate between 10 and 20 Gh.

Luke-Jr

legendary

Activity: 2576

Merit: 1186

The bugged block has been distributed here: http://blockexplorer.com/tx/f32022e1da8a8046a4c7e76a8ad6e8322aa14e15555b8dc6159936df5850a6a3

Topic: [350 GH/s] "Eligius" (experimental) pool: almost feeless PPS, hoppers welcome - page 32. (Read 116992 times)