[0 GH/s 0% fee SMPPS] ArsBitcoin mining pool!

[BurningToad]

My THIRD testnet test.... hey look, blocks!!!
http://75.101.142.241/stats.php

Testnet blocks are worth something.... right??

* BurningToad goes and mumbles in the corner

[goldcd]

My THIRD testnet test.... hey look, blocks!!!
http://75.101.142.241/stats.php

Testnet blocks are worth something.... right??

* BurningToad goes and mumbles in the corner

I was about to ask if the pool was actually working
Still I'm in this until somebody finds that f'in block. This has become personal.

[Tx2000]

This is pretty torturous right about now.

[goldcd]

This is pretty torturous right about now.

I prefer to think of it as character-building.

[Tx2000]

This is pretty torturous right about now.

I prefer to think of it as character-building.

If by character-building, you miners climbing to the top of a building and contemplating the jump, then yea   

On a serious note though, I had to disable CPU mining.  For some reason it pretty much cuts into the Mhashes coming from my GPU (and I even used the no GPU argument when setting up the Ufasoft miner).

[theowalpott]

I ran my cpu miner for a good number of hours - it didnt get a single share.. and the worker didn't seem to show up as active on the workers page either. GPU is going fine though. I switched the CPU to a different pool and it generated 8 shares within an hour or so.. very odd lol

Ah well, I'm gonna keep going with my GPU until we get the first block or 2

Like you said - its personal now!

[Andrey]

hey, it does shows  Est. Unconfirmed: now, does that mean that block is found but not confirmed? why isn't it in the blocks found with 0 confirms?
Who found that unconfirmed block?

[shamen]

Lifetime Shares: 17228
Lifetime Stale: 435
Valid This Round: 14 shares
Round Shares: 4020 shares

Huh? So we found a block 4020 shares ago?

Nothing showing up in the found blocks section though

[goldcd]

hey, it does shows  Est. Unconfirmed: now, does that mean that block is found but not confirmed? why isn't it in the blocks found with 0 confirms?
Who found that unconfirmed block?

I was just about to say exactly the same... 'Something' seems to have happened.
Not sure if it's connected, but I had 'problem communicating with server' popping up about 10 mins ago.

[shamen]

Woop!! firt block found. Lets hope the next few blocks are better luck!

congrats user74!!

133,099   2   User 74   2011-06-24 06:35:01 PM

[fpgaminer]

I think the finder should get an extra reward for cracking such a difficult block!

[shamen]

I think the finder should get an extra reward for cracking such a difficult block!

They do, they get 10BTC

[goldcd]

Putting aside my understanding of probability, I quite like the small pool thing.
Actually fun crossing fingers for a good block or cursing a bad one.

[BurningToad]

The stats update at different times, thats why it looked out of sync for a bit.  I will work on improving things now that we actually have a block to work with!!

I don't know if user 74 wants his username published (didn't set a nickname).  So I'm going to email him about it.

Also, the "Est. Unconfirmed" is exactly that, the estimated earnings you will get credited to your account after 120 confirmations (which is when I get the BTC in the pool wallet.)  Now, this EST could be slightly off, because it is based on your estimate at the time it was found (remember I said stats update at different times?)  What this means is at 120 confirmations, the 100 % precise share counts are done, and BTC is credited out.

[theowalpott]

woo! first block.. just disappointed it wasn't me

will probs stick to this pool at least for the weekend - I've still not made my first whole BTC yet

If we get lucky, then at least I'll get a decent share compared to the other pools!

[fpgaminer]

During the course of the first round, I noticed I was mining at 5-6% rejection rate. After seeing that, I started to investigate. Long story short I came to an odd conclusion. Some shares were being rejected for no obvious reason whatsoever. Here are the circumstances of those rejected shares:

1) Lots of accepted shares surrounding it.
2) No new blocks recently found.
3) Timestamp adjustment disabled.
4) Work shouldn't be much older than 13 seconds.
5) Share verified on CPU by poclbm (so the GPU isn't to blame).

BurningToad: Any idea why these shares might have been rejected?

I used my local long polling patch, which verifies #2 above. #3 means that the only thing the miner is fiddling with is the nonce, in case changing the timestamp was causing a weird bug on the pool. #4 means the share wasn't rejected because its timestamp was too old.

The only other thing I can think of is the pool giving me duplicate work. I have vague memory of other pools running into this problem; where they were seeing high rejected share rates and discovered the pool was giving out duplicate work.

EDIT: Found the thread I remember. http://forum.bitcoin.org/index.php?topic=14483.0. Bitcoins.lc was having duplicated work problems, and it turned out to be a bug. BurningToad you could check your DB and see if a lot of rejected shares are due to duplicate work.

[shamen]

he only other thing I can think of is the pool giving me duplicate work

That could explain something I was seeing. I was seeing more shares 'accepted' on my client here than I was seeing as accepted on the server. So i tested that out.

The way I tested it was thus

- Stopped mining for a period (i think it was an hour. More than enough for the stats lag to catch up anyways)
- Verify the amount of submitted shares in the pool control panel
- Started guiminer
- Ran for a time (about 1000 shares i think), then stopped and noted the 'accepted' shares listed in guiminer
- Waited for a while for pool stats to catch up (30 mins?)
- Noticed a discrepancy of about 50 shares between my client and what the server had

I thought maybe I just did something wrong, but someone else seeing possible duplicates made me post this up.

Can you check into it BF?

[BurningToad]

Shaman, your issue is caused by the way I am currently updating stats at the moment.  I update your current round shares at a slightly different time from your lifetime shares.  So they won't match sometimes.  Some shares will be reflected in the current round that are not yet added to your lifetime count.  They are only added to lifetime amount when the network itself finds a block.  When I increment the block count, i add to lifetime shares.

About the stales, I will look into it when I get some more time.  It is strange though because some people have extremely low (0.2%) stales while others have fairly high (6%).  So something in the user setup must be involved too, not just the server.

I'll be working on various issues with the pool.  Remember, this is just our first block, I'm still working things out!

[gentakin]

BurningToad, I sent you a private message. Since I know this forum sucks at showing incoming private messages, I'm just telling you here.

[shamen]

Shaman, your issue is caused by the way I am currently updating stats at the moment.  I update your current round shares at a slightly different time from your lifetime shares.  So they won't match sometimes.  Some shares will be reflected in the current round that are not yet added to your lifetime count. 

Thats good to know, but that wasnt the two counts I was comparing. I was not comparing lifetime shares vs round shares. I was comparing round shares with shares my miner here listed that the pool had 'accepted'

I'll be working on various issues with the pool.  Remember, this is just our first block, I'm still working things out!

As I can see a popup saying "bug" is appearing on the stats page now