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

[[Tycho]]

I keep seeing this hash in the "prev_block" field in the data of the work that I get from deepbit.net :

b84401536a5ec2fca283157d1ba9b80c0259a63954659d20000113dd00000000

Have you tried to look at other pool's work or your local bitcoin's one ?

3 blocks already found and they are surely not from testnet :)

[1714771889]

1714771889

[1714771889]

1714771889

[1714771889]

1714771889

[1714771889]

1714771889

[1714771889]

1714771889

[1714771889]

1714771889

[prcarter]

Have you tried to look at other pool's work or your local bitcoin's one ?

3 blocks already found and they are surely not from testnet

I'm just quoting what the server at deepbit.net is returning in response to my "getwork" JSON requests.

I feel happy right now, as I just found my first "share", but I still don't understand why there are so few zeros in prev_block, since we are supposedly trying to generate real blocks.

EDIT: Maybe that part (first 64-byte chunk) of the "data" field is not filled correctly? I think it's not used by the SHA256 algorithm on the client, being already hashed by the server, with the result placed in "midstate", so that the client needs to perform only two rounds of SHA256.

EDIT: Still, it would be nice if the right data was placed there, so I'd at least know which real block I am contributing to!

[paulofisch]

After using the Pay-Per-Share for a few hours it seems to be working just pukka, apart from a slightly odd behaviour in the Account Balance (http://deepbit.net/acc.php)

It appears to track each new share perfectly in the balance sometimes, then will 'rewind' to an earlier value. Possibly in conjunction with an hourly balance update?

[telestrial]

Are CPU miners not supported? It's okay if not. I just don't want to continue messing with this trying to make it work.

[[Tycho]]

Are CPU miners not supported? It's okay if not. I just don't want to continue messing with this trying to make it work.

Just tested jgarzik's CPU miner and it worked fine for me.
Try to use -P key and see, what it's trying to parse. Then copy it and send to me by private message, i'll try to resolve.

BTW it's deepbit.net, not www.deepbit.net. But works anyway.

[Ricochet]

Are CPU miners not supported? It's okay if not. I just don't want to continue messing with this trying to make it work.

In the first post, the only one claimed not to work is the SSE2 miner.  I got it to work with Puddinpop's RPC CPU miner, for instance

[[Tycho]]

EDIT: Still, it would be nice if the right data was placed there, so I'd at least know which real block I am contributing to!

Do you clearly understand what a "share" is and why you are working with difficulty-1 task ?
Just wanted to be sure.

[[Tycho]]

After using the Pay-Per-Share for a few hours it seems to be working just pukka, apart from a slightly odd behaviour in the Account Balance (http://deepbit.net/acc.php)

It appears to track each new share perfectly in the balance sometimes, then will 'rewind' to an earlier value. Possibly in conjunction with an hourly balance update?

Thanks for your bug report. Just fixed that for displaying pay-per-share rewards.

[prcarter]

EDIT: Still, it would be nice if the right data was placed there, so I'd at least know which real block I am contributing to!

Do you clearly understand what a "share" is and why you are working with difficulty-1 task ?
Just wanted to be sure.

I think so. Or maybe I haven't understood something correctly again.

[ronaldmaustin]

Same speeds as on Slush's server, but am getting no stale's or invalids so far.  So I'll be switching over for the time being as the stales/invalids were costing me as much as 5-10 percent.  I think it may be the load on Slush's server, so hopefully yours will not have the same problem as it gets popular.  I'll leave 2 5970's on your server and the other 2 on Slush's and compare after awhile.  But, so far, excellent.  I'd like to see even more competition to ease up the load on the various pools.  I see this is in Beta.  Hopefully you will not have much downtime.  If you're down for an hour in a day, for example, that would cost well over the commission.

[[Tycho]]

Same speeds as on Slush's server, but am getting no stale's or invalids so far.  So I'll be switching over for the time being as the stales/invalids were costing me as much as 5-10 percent.  I think it may be the load on Slush's server, so hopefully yours will not have the same problem as it gets popular.  I'll leave 2 5970's on your server and the other 2 on Slush's and compare after awhile.  But, so far, excellent.  I'd like to see even more competition to ease up the load on the various pools.  I see this is in Beta.  Hopefully you will not have much downtime.  If you're down for an hour in a day, for example, that would cost well over the commission.

I'm not expecting load problems yet, it's really easy to avoid.

Beta actually means that i'm gradually adding features and looking carefully if everything works fine.
Downtime was about 5-10 seconds in last two days, due to software updating.

[whyjustin]

First of all thanks for setting up a second pool for everybody; I recently got into the BTC hype but was having trouble going at it alone. I've been running for about 8 hours with little to no problems, although I don't have much to compare to seeing this is the first pooled experience I have. The only issue I've seen so far is occasionally DiabloMiner will give the following feedback:

85413/90697 khash/secException in thread "DiabloMiner Executor (GeForce GTX 295
(#1)/2)" java.lang.NullPointerException
        at com.diablominer.DiabloMiner.DiabloMiner$DeviceState$ExecutionState$Ge
tWorkParser.parse(DiabloMiner.java:731)
        at com.diablominer.DiabloMiner.DiabloMiner$DeviceState$ExecutionState$Ge
tWorkParser.getWork(DiabloMiner.java:636)
        at com.diablominer.DiabloMiner.DiabloMiner$DeviceState$ExecutionState$Ge
tWorkParser.update(DiabloMiner.java:630)
        at com.diablominer.DiabloMiner.DiabloMiner$DeviceState$ExecutionState.ru
n(DiabloMiner.java:534)
        at java.lang.Thread.run(Unknown Source)

It would seem that the work returned is null and cannot be parsed. It corrects itself after a while, probably by asking for more work until something comes back. Forgive my noobidity if that's an incorrect assumption.

[[Tycho]]

First of all thanks for setting up a second pool for everybody; I recently got into the BTC hype but was having trouble going at it alone. I've been running for about 8 hours with little to no problems, although I don't have much to compare to seeing this is the first pooled experience I have. The only issue I've seen so far is occasionally DiabloMiner will give the following feedback:

85413/90697 khash/secException in thread "DiabloMiner Executor (GeForce GTX 295
(#1)/2)" java.lang.NullPointerException
        at com.diablominer.DiabloMiner.DiabloMiner$DeviceState$ExecutionState$Ge
tWorkParser.parse(DiabloMiner.java:731)

I thought that I fixed this issue yesterday... Ok, will check again, thanks for your report :)

[JoeGTN1]

First of all thanks for setting up a second pool for everybody; I recently got into the BTC hype but was having trouble going at it alone. I've been running for about 8 hours with little to no problems, although I don't have much to compare to seeing this is the first pooled experience I have. The only issue I've seen so far is occasionally DiabloMiner will give the following feedback:

85413/90697 khash/secException in thread "DiabloMiner Executor (GeForce GTX 295
(#1)/2)" java.lang.NullPointerException
        at com.diablominer.DiabloMiner.DiabloMiner$DeviceState$ExecutionState$Ge
tWorkParser.parse(DiabloMiner.java:731)

I thought that I fixed this issue yesterday... Ok, will check again, thanks for your report

I'll second this, I've gotten it about 5 times in the past 5 hours w/ Diablo on a GTX460, I also have cpuminer-0.7 going and got a few "not enough semaphores" or some such.  Most of the time Diablo recovers and keeps going, once it went like 20min without doing any work before I killed it.

Should I have a separate account/worker set-up for the cpuminer?  I currently have them both logged in to the same user.

Also, I think everything is fine, but should I be expecting more than ~8Mh/s out of an i7 860 and 44Mh/s out of a GTX 460?

[whyjustin]

Sounds about right, I'm getting ~8 out of an i7 and it looks like the GTX460 does ~68. https://en.bitcoin.it/wiki/Mining_hardware_comparison. If you're doing graphic related stuff on your computer (games/streaming video) then it'll drop below the numbers on that site.

EDIT: I wrote 64, [Tycho] FTFM

[[Tycho]]

I'll second this, I've gotten it about 5 times in the past 5 hours w/ Diablo on a GTX460, I also have cpuminer-0.7 going and got a few "not enough semaphores" or some such.  Most of the time Diablo recovers and keeps going, once it went like 20min without doing any work before I killed it.

Should I have a separate account/worker set-up for the cpuminer?  I currently have them both logged in to the same user.

Also, I think everything is fine, but should I be expecting more than ~8Mh/s out of an i7 860 and 44Mh/s out of a GTX 460?

You can run many miners on same account, it's ok.
Today i'll add the option to create new workers.

This table says that you should get ~68 MH/s on GTX460 @ 1350 MHz. Looks like you should try another miner.
https://en.bitcoin.it/wiki/Mining_hardware_comparison

I'll try to find out the cause of that bug with DiabloMiner today too.

[dishwara]

I joined ur pool.
Even i mined some shares at 220MH.
But so far even after 7-10 hours no share is showed in my account.
It says 0000000 balance only & i have not received any btc. even micros.
also ur stats page says reward none.
No one so far paid?
Or i am the only one having problem?

[paulofisch]

But so far even after 7-10 hours no share is showed in my account.
It says 0000000 balance only & i have not received any btc. even micros.
*snip*
Or i am the only one having problem?

The last block that paid out (the pool hit a +50BTC) was 17 hours ago.

Yours shares for the last 7-10 hours will only pay out when the pool hits a new +50BTC.

Simples. :-)

[Ricochet]

Hehe, I was about to ask the exact same question.  Did one share at PayPerShare before switching to Proportional for a few hours.  Would be nice to see an "expected reward" field like with slush's pool to avoid confusion here, but it's not too big a deal.

[paulofisch]

Hehe, I was about to ask the exact same question.  Did one share at PayPerShare before switching to Proportional for a few hours.  Would be nice to see an "expected reward" field like with slush's pool to avoid confusion here, but it's not too big a deal.

I'm sure Tycho has it on the TODO list along with the pretty graphs and everything :-)

Clean up this thread and it will be the help/FAQ page as well more or less. Eventually anyway.