[DEAD] DeepBit.net PPS+Prop,instant payouts, we pay for INVALID BLOCKS too - page 324.

xenon481

sr. member

Activity: 406

Merit: 250

Quote from: [Tycho] on February 26, 2011, 08:56:09 PM

Quote from: NicholasBell on February 26, 2011, 08:48:12 PM

Quote from: [Tycho] on February 26, 2011, 08:27:05 PM

Now you can try some new exciting feature - optional Pay-Per-Share mode is enabled in my pool.

I'm curious, being new to pooled mining--what is the motivation for choosing one mode over the other? Is it to remove some of the luck component? I can see that maybe if the pool as a whole is really unlucky and doesn't solve a block then each share in "proportional" would be worth less than if the pool solves it faster.

Does the current pay rate you have there represent the statistical average rate we would expect in proportional mode anyway?

Depends on people. Some just like getting their cents now, some can wait. Some feel lucky and some - not.
Price is calculated as (50 / current difficulty) - 10%, exactly as other pay-per-share pools, just some nano-coins more because of higher precision

That's actually really important! That's a 10% (statistical average) fee instead of the 3% fee for "Proportional" that you mention in your first post.

I don't think the 10% is out of line, just that it is important that it be disclosed as different.

xenon481

sr. member

Activity: 406

Merit: 250

Quote from: NicholasBell on February 26, 2011, 08:48:12 PM

Quote from: [Tycho] on February 26, 2011, 08:27:05 PM

Now you can try some new exciting feature - optional Pay-Per-Share mode is enabled in my pool. You can choose payments method for any of your workers, look at your account page for workers configuration.

Current rate is 0.0012342331201539 BTC per share.

I'm curious, being new to pooled mining--what is the motivation for choosing one mode over the other? Is it to remove some of the luck component? I can see that maybe if the pool as a whole is really unlucky and doesn't solve a block then each share in "proportional" would be worth less than if the pool solves it faster.

Does the current pay rate you have there represent the statistical average rate we would expect in proportional mode anyway?

Yes, with a Pay-Per-Share model (like BitPenny), the vast majority of the variance is moved from the individual miner client to the pool operator. In this mode, the pool operator is betting (like a casino) that the statistical average number of shares to solve a block will hold true over time. As casinos prove, this is a near certainty over time unless somebody finds a way to cheat and skew the statistical average.

It also moves the risk of being harmed by cheaters from the miners to the pool operator.

[Tycho]

hero member

Activity: 742

Merit: 500

Quote from: NicholasBell on February 26, 2011, 08:48:12 PM

Quote from: [Tycho] on February 26, 2011, 08:27:05 PM

Now you can try some new exciting feature - optional Pay-Per-Share mode is enabled in my pool.

I'm curious, being new to pooled mining--what is the motivation for choosing one mode over the other? Is it to remove some of the luck component? I can see that maybe if the pool as a whole is really unlucky and doesn't solve a block then each share in "proportional" would be worth less than if the pool solves it faster.

Does the current pay rate you have there represent the statistical average rate we would expect in proportional mode anyway?

Depends on people. Some just like getting their cents now, some can wait. Some feel lucky and some - not.
Price is calculated as (50 / current difficulty) - 10%, exactly as other pay-per-share pools, just some nano-coins more because of higher precision :)

NicholasBell

newbie

Activity: 34

Merit: 0

Quote from: [Tycho] on February 26, 2011, 08:27:05 PM

Now you can try some new exciting feature - optional Pay-Per-Share mode is enabled in my pool. You can choose payments method for any of your workers, look at your account page for workers configuration.

Current rate is 0.0012342331201539 BTC per share.

I'm curious, being new to pooled mining--what is the motivation for choosing one mode over the other? Is it to remove some of the luck component? I can see that maybe if the pool as a whole is really unlucky and doesn't solve a block then each share in "proportional" would be worth less than if the pool solves it faster.

Does the current pay rate you have there represent the statistical average rate we would expect in proportional mode anyway?

[Tycho]

hero member

Activity: 742

Merit: 500

Now you can try some new exciting feature - optional Pay-Per-Share mode is enabled in my pool. You can choose payments method for any of your workers, look at your account page for workers configuration.

Current rate is 0.0012342331201539 BTC per share.

[Tycho]

hero member

Activity: 742

Merit: 500

Quote from: ?? on ??

In other words, if your own miners are on the same LAN,
(or very close-by from a latency P.O.V.) your failure rate
will be much lower than that of someone who is 300ms
away.

Actually no, i'm 144 ms away from DC :)

paulofisch

newbie

Activity: 12

Merit: 0

Quote from: prcarter on February 26, 2011, 07:37:14 PM

Quote from: paulofisch on February 26, 2011, 07:24:10 PM

*snip*
At your rate of around 100Kh/s you should see a hit every 11-12h by my count.

If the RPC failures increase, check you have the latest clients that persist connections nicely, rather than fire-hosing the server with connection attempts :-)

You are right. I was wrong again. When that is the hash rate, one can expect solutions every that often. Now I have a 1Mhash/sec rate (gcc -O3) so I should get solutions approximately every 70 minutes.

~~There wasn't one single correct thing in what I posted!~~ No, there was!

For the "fire-hosing" problem, I simply reduced the "getwork" call frequency from once every 5 seconds to once every 20 seconds.

Not wrong, just learning, and quickly :-)

The fire-hose thing was more of a problem with the official client until recently and applies less to what you're doing I think.

prcarter

newbie

Activity: 30

Merit: 0

Quote from: paulofisch on February 26, 2011, 07:24:10 PM

The benchmark/avg. is currently 1 share every 5 minutes at 14200Kh/s.
At your rate of around 100Kh/s you should see a hit every 11-12h by my count.

If the RPC failures increase, check you have the latest clients that persist connections nicely, rather than fire-hosing the server with connection attempts :-)

You are right. I was wrong again. When that is the hash rate, one can expect solutions every that often. Now I have a 1Mhash/sec rate (gcc -O3) so I should get solutions approximately every 70 minutes.

~~There wasn't one single correct thing in what I posted!~~ No, there was!

For the "fire-hosing" problem, I simply reduced the "getwork" call frequency from once every 5 seconds to once every 20 seconds.

paulofisch

newbie

Activity: 12

Merit: 0

Quote from: prcarter on February 26, 2011, 07:02:43 PM

Sorry, the number of bits is 32. My mistake. I'm new. The probability is one in 2^32. Should take around 5-6 hours on average if that hash rate is correct.

The benchmark/avg. is currently 1 share every 5 minutes at 14200Kh/s.
At your rate of around 100Kh/s you should see a hit every 11-12h by my count.

If the RPC failures increase, check you have the latest clients that persist connections nicely, rather than fire-hosing the server with connection attempts :-)

And hi and welcome etc. Cheesy

[Tycho]

hero member

Activity: 742

Merit: 500

Quote from: ?? on ??

My miner logs start to show a small rate of failed RPCs ... out of curiosity,
(and unless it's a trade secret :) ) do you load balance the incoming RPC stream
to multiple instances of the C++ bitcoin daemon ? If so, can you tell us what's
your load balancing strategy (i.e. how many RPC/s do you send to each instance)

Actually i don't need load balancing at this moment. My tests showed that one instance will be enough for much more users.
I have some plans for this, but there are no problems with it yet.

I'm mining in my pool myself and don't see any RPC failures, except for some moments when pool software was updated. Are you sure it's not a problem with your connection ? You can run a ping -t deepbit.net and look if there is packet loss at the same time with RPC failures.

prcarter

newbie

Activity: 30

Merit: 0

I've noticed one failed RPC so far (the server returned a 404 error) but that's a very minor issue.

prcarter

newbie

Activity: 30

Merit: 0

I'm sorry, I haven't understood the terms you are using. I am guessing that a "share" is when somebody finds a solution to a simpler problem than the current difficulty? Demonstrating proof-of-work that way, only less work? I hope I got it right.

I see in the replies to "getwork" that your server is sending, that the "target" field has 32 zero bits to the right, which is the same number as the zero bits in the "prev_block" field in the "data". Does that mean that I am supposed to give you only full solutions? From looking at the code, I think that my miner program (cpu-miner) will send you the data block, with the "nonce" value that was used, whenever the hash contains at least 8 zero bits at the end. The probability for that is one in 256 (unless I don't understand something), and there is a printf() call when that happens. However, that hasn't happened yet! And the program reports hash rates of around 100khash/sec!

I'm using the 4-way SSE2 code and I have no GPU. And this is strange. The official bitcoin client gave me much lower hash rates.

And I'm probably missing something again.

Sorry, the number of bits is 32. My mistake. I'm new. The probability is one in 2^32. ~~Should take around 5-6 hours on average if that hash rate is correct.~~ Also, the official client hash rate was around 1Mhash/sec which I've now reached with cpu-miner, because I didn't compile it with debugging flags this time.

All is well...

[Tycho]

hero member

Activity: 742

Merit: 500

Quote from: paulofisch on February 26, 2011, 05:48:42 PM

Thanks for setting this up Tycho. Nice, simple start is good :-)
Let me know if you need any gfx/design to pimp up the deepbit.net site at any point as that is in my line.

You are welcome :)
Thanks for your offer, i'll tell if some help will be needed.

[Tycho]

hero member

Activity: 742

Merit: 500

Quote from: CorneredS on February 26, 2011, 05:32:55 PM

This might be a noobish question, but I've been receiving shares for a while now, but my account is on 0.0000000 bitcoins still...

Your account will be credited during the first hour after finding the block (approximately every 36500 shares received by pool from all users).

Currently i'm implementing pay-per-share option, that will increase balance after each share. Will be available soon.

EDIT: Heh, two posts already appeared while i was answering :)

CorneredS

newbie

Activity: 6

Merit: 0

Quote from: paulofisch on February 26, 2011, 05:48:42 PM

Quote from: CorneredS on February 26, 2011, 05:32:55 PM

This might be a noobish question, but I've been receiving shares for a while now, but my account is on 0.0000000 bitcoins still...

Looking at http://deepbit.net/stats.php , the last payout for a successful find was around 3:19pm on the 26th Feb.

If you started submitting shares after this then there is no payout, yet :-)

-

Thanks for setting this up Tycho. Nice, simple start is good :-)

Let me know if you need any gfx/design to pimp up the deepbit.net site at any point as that is in my line.

I was afraid the answer might be that easy XD

paulofisch

newbie

Activity: 12

Merit: 0

Quote from: CorneredS on February 26, 2011, 05:32:55 PM

This might be a noobish question, but I've been receiving shares for a while now, but my account is on 0.0000000 bitcoins still...

Looking at http://deepbit.net/stats.php , the last payout for a successful find was around 3:19pm on the 26th Feb.

If you started submitting shares after this then there is no payout, yet :-)

-

Thanks for setting this up Tycho. Nice, simple start is good :-)

Let me know if you need any gfx/design to pimp up the deepbit.net site at any point as that is in my line.

CorneredS

newbie

Activity: 6

Merit: 0

This might be a noobish question, but I've been receiving shares for a while now, but my account is on 0.0000000 bitcoins still...

[Tycho]

hero member

Activity: 742

Merit: 500

Quote from: theGECK on February 26, 2011, 04:09:07 PM

Well, I can't get any miner to work with the CPU I'm trying to donate to your pool - m0mchil's won't work, and I can't get Diablo's to function. I'll have to wait a few more days before I'm back to my main miner to throw some hash/s your way for testing.

I didn't realize that the pool had to be configured to accept a particular miner - that's too bad. I was under the impression that I could use any miner, such as ufasoft's CPU miner (which is my current CPU miner), and connect to any pool that was around.

Oh, now i see what's your problem. ufasoft's CPU miner is the only one that is not supported by my pool because it's not fully compliant with the protocol (as i see it). I said this in the first post.

m0mchil's and Diablo's miners are mainly for GPU, not CPU miners.

AmpEater

full member

Activity: 232

Merit: 250

I signed up and just pointed 2x 5970s your way. Everything seems to be going OK, though I did get a "could not communicate with RPC server" error for a minute or two about an hour ago.

theGECK

sr. member

Activity: 411

Merit: 250

Well, I can't get any miner to work with the CPU I'm trying to donate to your pool - m0mchil's won't work, and I can't get Diablo's to function. I'll have to wait a few more days before I'm back to my main miner to throw some hash/s your way for testing.

I didn't realize that the pool had to be configured to accept a particular miner - that's too bad. I was under the impression that I could use any miner, such as ufasoft's CPU miner (which is my current CPU miner), and connect to any pool that was around.

Topic: [DEAD] DeepBit.net PPS+Prop,instant payouts, we pay for INVALID BLOCKS too - page 324. (Read 1601412 times)