[500 GH/s]HHTT -Selected Diff/Stratum/PPLNS/Paid Stales/High Availability/Tor

[silverserpent]

i just pointed some firepower over there last night...just changed Diff to 512. rates seem more reasonable than say BTC Gld but we'll see how it actually performs

[1714034777]

1714034777

[1714034777]

1714034777

[1714034777]

1714034777

[1714034777]

1714034777

[1714034777]

1714034777

[1714034777]

1714034777

[spiccioli]

i just pointed some firepower over there last night...just changed Diff to 512. rates seem more reasonable than say BTC Gld but we'll see how it actually performs

silverserpent,

being a PPLNS pool, it takes at least a  day before you see your real payout when a block is found.

Look at your "Last Day MH/s" column value and wait till it reaches your real hashrate.

spiccioli

[silverserpent]

i just pointed some firepower over there last night...just changed Diff to 512. rates seem more reasonable than say BTC Gld but we'll see how it actually performs

silverserpent,

being a PPLNS pool, it takes at least a  day before you see your real payout when a block is found.

Look at your "Last Day MH/s" column value and wait till it reaches your real hashrate.

spiccioli

ok, thanks.
previous change (Diff to 512) made system unstable, reverted to standard/default 32; any tips?
*I did change to 300 Freq and have been averaging bout 72GH/s. Utility@ 30.64? is that good?
appreciate any feedback

[spiccioli]

i just pointed some firepower over there last night...just changed Diff to 512. rates seem more reasonable than say BTC Gld but we'll see how it actually performs

silverserpent,

being a PPLNS pool, it takes at least a  day before you see your real payout when a block is found.

Look at your "Last Day MH/s" column value and wait till it reaches your real hashrate.

spiccioli

ok, thanks.
previous change (Diff to 512) made system unstable, reverted to standard/default 32; any tips?
*I did change to 300 Freq and have been averaging bout 72GH/s. Utility@ 30.64? is that good?
appreciate any feedback

Try using 129 as difficulty, 32 is too low for an Avalon.

spiccioli

[spiccioli]

One point three TH/s !!!

fireduck please update thread title, this pool is growing

[BenTuras]

I am trying to understand the payout of this pool.

Mining Rewards

This pool does Pay-Per-Last-N-Shares (PPLNS) at:

BLOCK_REWARD * (1.0 - FEE) * (1 / difficulty)
The fee is calculated as 0.0025 + (0.0475/pow(share_difficulty,0.6))

The look back for the PPLNS is 2 * network_difficulty

If I chose 128 difficulty, FEE is 0.51%

Code:

BLOCK_REWARD	25	
FEE	        0.51%	
difficulty	12153412	
PPS	        0.0000020466 ฿ x 128 = 0.00026196 ฿

This is 2x what is shown for a share, so it must be the last sentence that specifies the needed divide by 2 to get the right answer. Can someone explain this look back to me ?

Then the monies on the miner page:
The earned and paid stays the same value, no matter how many shares are found. They only change after a payout. I would expect earned to increase for every new share. Is this intentional or not completely implemented yet ?

Then the pool funds:
Looks like the pool is 800BTC in the negative, is this correct ?

Has someone managed to get hhtt-payout or hhtt-block working via Amazon Services ?
Edit: I will answer the last question myself: It seems that there are no messages send from HHTT to Amazon(NumberOfMessagesPublished=0 on Amazon SNS), hence Amazon can't send out messages...

[spiccioli]

I am trying to understand the payout of this pool.

Mining Rewards

This pool does Pay-Per-Last-N-Shares (PPLNS) at:

BLOCK_REWARD * (1.0 - FEE) * (1 / difficulty)
The fee is calculated as 0.0025 + (0.0475/pow(share_difficulty,0.6))

The look back for the PPLNS is 2 * network_difficulty

If I chose 128 difficulty, FEE is 0.51%

Code:

BLOCK_REWARD	25	
FEE	        0.51%	
difficulty	12153412	
PPS	        0.0000020466 ฿ x 128 = 0.00026196 ฿

This is 2x what is shown for a share, so it must be the last sentence that specifies the needed divide by 2 to get the right answer. Can someone explain this look back to me ?

Then the monies on the miner page:
The earned and paid stays the same value, no matter how many shares are found. They only change after a payout. I would expect earned to increase for every new share. Is this intentional or not completely implemented yet ?

Then the pool funds:
Looks like the pool is 800BTC in the negative, is this correct ?

Has someone managed to get hhtt-payout or hhtt-block working via Amazon Services ?
Edit: I will answer the last question myself: It seems that there are no messages send from HHTT to Amazon(NumberOfMessagesPublished=0 on Amazon SNS), hence Amazon can't send out messages...

BenTuras,

this pool went from PPS to PPLNS shortly after the first batch of Avalons went out since PPS was causing it to go bankrupt, in fact the pool, or better, fireduck is in red by 800 BTCs he paid to users (suckers) when this pool was PPS.

I think part of the payout description was never changed.

In the monies table:

Earned: what you earned given found blocks
Paid:   how much of your Earned income has already been paid
Owed: how much the pool still owes you
PPLNS Share: your share (how much you're going to earn) of the next block the pool will find.

spiccioli

[BenTuras]

Thanks for your answer spiccioli,
So how this pool calculates what we earn is not written out on the webpage...
I have looked at a few miner pages, on all pages earned equals paid.
This sounds wrong to me, after finding a share, earned should increase.
Too bad fireduck is 800 BTC in the negative. And of course no PPS 'sucker' felt the need to partly refund.

Too bad two big miners decided to leave today, hashing power of 5 Avalons. Or they had a problem, looks like they're back.

I will stay on this pool for a few more days.
I would like to get some more info though.

[spiccioli]

Thanks for your answer spiccioli,
So how this pool calculates what we earn is not written out on the webpage...
I have looked at a few miner pages, on all pages earned equals paid.
This sounds wrong to me, after finding a share, earned should increase.
Too bad fireduck is 800 BTC in the negative. And of course no PPS 'sucker' felt the need to partly refund.

Too bad two big miners decided to leave today, hashing power of 5 Avalons. Or they had a problem, looks like they're back.

I will stay on this pool for a few more days.
I would like to get some more info though.

BenTuras,

please read here https://bitcointalk.org/index.php?topic=95378.msg1812740#msg1812740  and some previous/next messages to see the switch to PPLNS and fireduck own words.

I think that miner pages show a share value as it was with PPS, but now with PPLNS the only value that matters is the one inside "PPLNS Share"'s column and this value reflects the miner's share of a block and depends on miner's hashing power.

spiccioli.

ps. if fireduck could confirm/clarify and/or show where I'm wrong it would be a good thing

[spiccioli]

1 TH/s lost in half a day...

spiccioli

[spiccioli]

Well, we have lost someone with 8 to 10 Avalons, but given that 2nd batch is made up of 600 units... we should reach around 36 TH/s in the coming weeks

spiccioli

[spiccioli]

Pool stabilized (as if I did something... ) and two blocks found as of now for today.

spiccioli

ps. so, stop wondering and point your hashing machines here!

[BenTuras]

Pool stabilized (as if I did something... ) and two blocks found as of now for today.

spiccioli

ps. so, stop wondering and point your hashing machines here!

Sorry spiccioli, but that's too simple.
I want to know how a pool handles its shares and payout and for this pool it's not clear to me, the information on the website is outdated and fireduck is missing in action.

[Hippie Tech]

I'd like to know why the PPLNS credit on these asic miners last so long.

My credits were gone in less than a day, yet the top miner still has more than 60% of theirs after the same amount of idle time.

[silverserpent]

I'd like to know why the PPLNS credit on these asic miners last so long.

My credits were gone in less than a day, yet the top miner still has more than 60% of theirs after the same amount of idle time.

yeah, its pretty bad...lost internet access for 4 hrs was knocked down to .96, from 1.84; as a result lost more than half of what I should have rec'd

[roy7]

I can only speculate, but if your shares in the look back window dropped in half in 4 hours and you mine constantly, then I'm guessing it'd only take 8 hours for your score to go to zero. Meaning the full N shares only take 8 hours for the pool to mine. It's only your shares within the last N shares that count for payment.

[silverserpent]

I can only speculate, but if your shares in the look back window dropped in half in 4 hours and you mine constantly, then I'm guessing it'd only take 8 hours for your score to go to zero. Meaning the full N shares only take 8 hours for the pool to mine. It's only your shares within the last N shares that count for payment.

actually, the PPLNS value dwindled down over time but the outage itself was about 4 hrs. Perhaps the fact that the history is so limited had a significant impact (only started on HHTT about 5-31)

[Hippie Tech]

I'd like to know why the PPLNS credit on these asic miners last so long.

My credits were gone in less than a day, yet the top miner still has more than 60% of theirs after the same amount of idle time.

yeah, its pretty bad...lost internet access for 4 hrs was knocked down to .96, from 1.84; as a result lost more than half of what I should have rec'd

I'm sure this guy isn't complaining.
http://hhtt.1209k.com/user-details.php?user=19ihxgbVYHv5P9uAWhPJYcPEqJfqkrGy9n

[roy7]

I can only speculate, but if your shares in the look back window dropped in half in 4 hours and you mine constantly, then I'm guessing it'd only take 8 hours for your score to go to zero. Meaning the full N shares only take 8 hours for the pool to mine. It's only your shares within the last N shares that count for payment.

actually, the PPLNS value dwindled down over time but the outage itself was about 4 hrs. Perhaps the fact that the history is so limited had a significant impact (only started on HHTT about 5-31)

Right, I just mean if you add shares at a steady rate and after 4 hours half are gone, then the window probably moved N/2 shares in 4 hours. At that rate you'd be at zero in 8 hours.

When you stop mining your score would slowly go down each time one of your shares was pushed out of the N share window by someone else's newer share.

[roy7]

I'm sure this guy isn't complaining.
http://hhtt.1209k.com/user-details.php?user=19ihxgbVYHv5P9uAWhPJYcPEqJfqkrGy9n

Is the hash rate graph not scaled for the difficulty of the submitted shares? The hash rate on graph doesn't seem at all accurate.