[4+ EH] Slush Pool (slushpool.com); Overt AsicBoost; World First Mining Pool

[bobR]

What's with the invalids AFTER they are started as confirned

they should not start with vaild confirms and not give credit later as invalid blocks

WTF

[1715090267]

1715090267

[1715090267]

1715090267

[1715090267]

1715090267

[1715090267]

1715090267

[slush]

What's with the invalids AFTER they are started as confirned

That happen? Pool added you a reward and then removed it?

[Miner-TE]

What's with the invalids AFTER they are started as confirned

they should not start with vaild confirms and not give credit later as invalid blocks

WTF

It is network convergence, where we solved the block and submitted it to the network and someone else solved the block and submitted it to the network except they are on separate sides of the P2P network.  Being P2P, Nodes near us accepted our block and nodes near the other accepted their block.  Eventually, the network converges and the solved block with the earlier time stamp wins.  Our block lost.

This is why it takes 120 (now 100?) blocks before payout.  

[bobR]

What's with the invalids AFTER they are started as confirned

they should not start with vaild confirms and not give credit later as invalid blocks

WTF

It is network convergence, where we solved the block and submitted it to the network and someone else solved the block and submitted it to the network except they are on separate sides of the P2P network.  Being P2P, Nodes near us accepted our block and nodes near the other accepted their block.  Eventually, the network converges and the solved block with the earlier time stamp wins.  Our block lost.

This is why it takes 120 (now 100?) blocks before payout. 

More BS
Either its a good block or NOT
now it takes  .. 120 0r 100 confirms before it is really a confirmed block

ok you can back out on the confirms ... after they start
something else new

[Miner-TE]

I believe it is not 100 blocks before Slush pays out.

BobR,  Are you referring to round #2694 2011-04-01 14:59:48?

and are you saying that it went invalid after Slush's site said it was confirmed or during the 100 blocks before validity?

[TenthReality]

I believe it is not 100 blocks before Slush pays out.

BobR,  Are you referring to round #2694 2011-04-01 14:59:48?

and are you saying that it went invalid after Slush's site said it was confirmed or during the 100 blocks before validity?

It was during the validation station, there were still a good 60 odd validations left before it went invalid.  Nothing new, fairly standard.

[demonofelru]

There seems to be quite a lot of invalids is it just terrible luck slush?

[OVerLoRDI]

Slush,

You list reward as being calculated by this forumla:
(50 BTC - 1 BTC fee) * (shares found by user's workers) / (total shares in current round)

What about transaction fees that get added on to the 50 BTC reward?  It isn't hugely relevant at this point, but transactions fees will become more significant as time goes on, so I'm wondering how your pool handles them.

Thanks

[xenon481]

Slush,

You list reward as being calculated by this forumla:
(50 BTC - 1 BTC fee) * (shares found by user's workers) / (total shares in current round)

What about transaction fees that get added on to the 50 BTC reward?  It isn't hugely relevant at this point, but transactions fees will become more significant as time goes on, so I'm wondering how your pool handles them.

Thanks

The pool doesn't use SharesFound/TotalPoolShares anymore, it uses a scoring algorithm.

But that doesn't change the answer to your question. There are currently no pools which distribute the transaction fees associated with a block.  The transaction fees all currently go to the pool operators.

This may change in the future as transaction fees become more significant.

[Tomaster]

well.

[slush]

xenon, thanks for the answer . Text on homepage need some update, as it describes share based system and not score based .But it will makes things harder to explain and the description of share based system still +/- fits.

[Fiyasko]

Im really hating the score system, anytime i turn my miner off i my "vaild" shares go invalid and i loose out

[slush]

Im really hating the score system, anytime i turn my miner off i my "vaild" shares go invalid and i loose out

You mean that estimated reward is going down? I have simple advice - don't turn off your mining machine

To be serious - it's of course expected, as fast the estimated reward is going down when you disconnect, as fast it is climbing up when you connnect, so no difference here. Of course you can be unlucky and disconnect few minutes before block is found; but - come on - there is a block every half of hour, you don't lose such big money .

[dansthunder]

How long till confirmed payouts on the stats page actually show up on "My Account" page as a confirmed reward?

I've got two so far that have made it past the 120 confirms, yet the BTC amount hasn't made it to my reward.

Edit... took about 1/2 hour or so.

[Psychoactive]

Slush, I think it could be nice if we could specify one wallet address per worker instead of per account. That would allow to 'monitor' payout per worker. I don't know how difficult that would be.

Straightforward, obviously.

[slush]

How long till confirmed payouts on the stats page actually show up on "My Account" page as a confirmed reward?

Monitoring on stats page is realtime (calculated from block number and current block height), but rewards are calculated once per hour, so there is some latency.

[slush]

Slush, I think it could be nice if we could specify one wallet address per worker instead of per account. That would allow to 'monitor' payout per worker. I don't know how difficult that would be.

It requires much complicated gui also for people not interested in monitoring each workers separately. I also though about this but rejected the idea of 'subaccounts'. But you can register multiple accounts with same email, so feel free to create more separate registrations for each worker...

[Psychoactive]

Slush, I think it could be nice if we could specify one wallet address per worker instead of per account. That would allow to 'monitor' payout per worker. I don't know how difficult that would be.

It requires much complicated gui also for people not interested in monitoring each workers separately. I also though about this but rejected the idea of 'subaccounts'. But you can register multiple accounts with same email, so feel free to create more separate registrations for each worker...

But then I can't monitor them together. I understand your 'strategy' of not complicating the gui though. What about generating the additional worker's estimated reward column in the webpage and leave it commented, ready to be uncommented for users that want it with a 'pimping' script like dacoinminster's script ?

[mrjones]

I'm new here, so perhaps this has been answered earlier.  However, I wasn't able to find an answer by searching.  (If the answer is found in another post, if someone could please link to it it would be much appreciated.)

What's the situation with blocks such as #2861 in the "Block History" section of the BPM stats page where it shows "Block #" as 0 with an invalid blockexplorer.com link and lists the validity as "Confirmed" immediately?

Code:

#	Block found		Duration	Total shares 	Your reward 	Block #		Validity
2861 	2011-04-05 15:33:16 	0:07:49 	17885	 	0.20570832 	0 		confirmed 

Is that a real block, or a bug, or something else?  Is the reward for such blocks valid?

EDIT: Several minutes after my post (and about 20 minutes after the block first appeared in the list, saying "confirmed" etc.), the validity changed to "invalid."

[cdhowie]

But then I can't monitor them together. I understand your 'strategy' of not complicating the gui though. What about generating the additional worker's estimated reward column in the webpage and leave it commented, ready to be uncommented for users that want it with a 'pimping' script like dacoinminster's script ?

If you want to script, you already have the information needed to determine the estimated reward from each miner account.  Take the sum of the scores for all your miners.  Then, for each miner, the estimated reward is (estimated_reward * (miner_score / total_score)).