Bitcoin Forum
June 17, 2024, 04:04:03 AM *
News: Voting for pizza day contest
 
   Home   Help Search Login Register More  
Pages: « 1 ... 611 612 613 614 615 616 617 618 619 620 621 622 623 624 625 626 627 628 629 630 631 632 633 634 635 636 637 638 639 640 641 642 643 644 645 646 647 648 649 650 651 652 653 654 655 656 657 658 659 660 [661] 662 663 664 665 666 667 668 669 670 671 672 673 674 675 676 677 678 679 680 681 682 683 684 685 686 687 688 689 690 691 692 693 694 695 696 697 698 699 700 701 702 703 704 705 706 707 708 709 710 711 ... 1154 »
  Print  
Author Topic: [4+ EH] Slush Pool (slushpool.com); Overt AsicBoost; World First Mining Pool  (Read 4381921 times)
kabopar
Hero Member
*****
Offline Offline

Activity: 616
Merit: 500


View Profile
November 24, 2013, 07:17:50 AM
 #13201

Reward payouts not happening again.... now more than 2 hours above the threshold.... Slush, pleaaaaase Cry
jmevz
Sr. Member
****
Offline Offline

Activity: 251
Merit: 250


View Profile
November 24, 2013, 07:22:06 AM
 #13202

Reward payouts not happening again.... now more than 2 hours above the threshold.... Slush, pleaaaaase Cry

What's your threshold set at? I've upped mine a little, not too worried, I know payouts will happen. I'm more worried about the exchange rate though. How long do we think it will keep this up?

jmevz
Sr. Member
****
Offline Offline

Activity: 251
Merit: 250


View Profile
November 24, 2013, 08:26:56 AM
 #13203

If only we could somewhat control our luck?

paulus51
Sr. Member
****
Offline Offline

Activity: 616
Merit: 321



View Profile
November 24, 2013, 10:03:31 AM
 #13204

issent it time for the slush pool to join this ? :

Today, BTC Guild has reduced the minimum MANUAL withdrawal level from 0.01 BTC to 0.001 BTC.
However, any payouts under 0.01 BTC will have the transaction fee (0.0005 BTC) deducted from their payout.
 
This is in response to the steady rise of BTC:USD exchange rates,
which have now made amounts as small as 0.002-0.003 useful as they are worth more than $1.

its a win win situation , i mean "low level"  miners wil have some coins earlyer / recular and de pool get some !  Smiley
bspurloc
Hero Member
*****
Offline Offline

Activity: 569
Merit: 500


View Profile
November 24, 2013, 04:26:18 PM
 #13205

it definitely is "a lot to grasp" but all the info you are looking for has already been published. google it

its like being in the Unix channel asking a question and the grumps telling u to use MAN. all the answers are in MAN! why ask anything
bspurloc
Hero Member
*****
Offline Offline

Activity: 569
Merit: 500


View Profile
November 24, 2013, 04:27:21 PM
 #13206

Today is making up for the last few. Loving it!

or.....
maybe something is wrong!
gourmet
Sr. Member
****
Offline Offline

Activity: 311
Merit: 250


View Profile
November 24, 2013, 11:09:40 PM
 #13207

it definitely is "a lot to grasp" but all the info you are looking for has already been published. google it

its like being in the Unix channel asking a question and the grumps telling u to use MAN. all the answers are in MAN! why ask anything

Why ask simple questions that are fully covered in the man there?
joef
Member
**
Offline Offline

Activity: 93
Merit: 10


View Profile
November 25, 2013, 12:19:35 PM
 #13208

Hi,
may someone explain to me please, how userdiff/vardiff is working in detail? I know how to calculate the nounces and how they are compared with the actual difficulty for validation before the miner release the nounces to the mining software.

What I don't understand:
- if a miner calculates with a higher difficulty than the actual difficulty, then the golden nounce may be skipped.
- If a miner calculates with a lower difficulty than the actual difficulty, then invalid nounces will be counted as valid.

Maybe someone can explain to me, how to modify the difficulty per miner.

Thank you

trasla
Hero Member
*****
Offline Offline

Activity: 707
Merit: 500



View Profile
November 25, 2013, 01:18:24 PM
 #13209

There is nothing like "the golden nounce" which could accidentally get skipped.
Theres a bunch of nounces who satisfy given network diff for the actual block with given transactions to be included in the block.
Which nounce solves the block changes all the time, as new transactions get included in the data we are hashing.

As for slush, you can no longer set the diff manually, the server sets your workers diff based on the workers speed.
Workers are not working with/on/for a special diff value, because the diff is per design something which can only be known _after_ the hash is calculated - thats the trick, after all, you cant decide which diff your result should fulfill, you have to try until you find one fitting your needs.

Your worker-specific diff value just does two things:
Tell your mining software, which shares to send to the server (all with diff equal or higher to your userdiff) and which to drop (all with lower diff).
Tell the server, how high your score for each share should be, the higher your diff, the higher the score.

That way, with higher diff you send less shares to the server but get higher score for each, and with lower diff you send more shares but get lower score. Over some time, this equals out. Higher diff is a little more variance, but a little less traffic to the server, so what the pool does by setting your diff is forcing you to accept a marginal higher variance in your earnings, which will still equal out quite fast, but reducing the server load at the same time, cause the pool will no longer get flooded with low diff shares by miner which hash too fast.
joef
Member
**
Offline Offline

Activity: 93
Merit: 10


View Profile
November 25, 2013, 01:58:27 PM
 #13210

There is nothing like "the golden nounce" which could accidentally get skipped.
Theres a bunch of nounces who satisfy given network diff for the actual block with given transactions to be included in the block.
Which nounce solves the block changes all the time, as new transactions get included in the data we are hashing.

As for slush, you can no longer set the diff manually, the server sets your workers diff based on the workers speed.
Workers are not working with/on/for a special diff value, because the diff is per design something which can only be known _after_ the hash is calculated - thats the trick, after all, you cant decide which diff your result should fulfill, you have to try until you find one fitting your needs.

Your worker-specific diff value just does two things:
Tell your mining software, which shares to send to the server (all with diff equal or higher to your userdiff) and which to drop (all with lower diff).
Tell the server, how high your score for each share should be, the higher your diff, the higher the score.

That way, with higher diff you send less shares to the server but get higher score for each, and with lower diff you send more shares but get lower score. Over some time, this equals out. Higher diff is a little more variance, but a little less traffic to the server, so what the pool does by setting your diff is forcing you to accept a marginal higher variance in your earnings, which will still equal out quite fast, but reducing the server load at the same time, cause the pool will no longer get flooded with low diff shares by miner which hash too fast.

Thank you for your explanation. I understand, that the mining will be calculated with a higher difficulty than the actual difficulty.
Nonces will be dropped, if the hash result fullfill the actual difficulty, but not the increased vardiff.
But one of these dropped nounces may solve the block. Since they are not transmitted, it will not be checked.
Yes, there is a bunch of valid nounces, so the block will still be solved, but later.

trasla
Hero Member
*****
Offline Offline

Activity: 707
Merit: 500



View Profile
November 25, 2013, 03:03:36 PM
 #13211

Thank you for your explanation. I understand, that the mining will be calculated with a higher difficulty than the actual difficulty.
Nonces will be dropped, if the hash result fullfill the actual difficulty, but not the increased vardiff.
But one of these dropped nounces may solve the block. Since they are not transmitted, it will not be checked.
Yes, there is a bunch of valid nounces, so the block will still be solved, but later.


Ah, i guess i see where you misunderstood something.
But the terms to address several difficulties are a bit confusing.

We have minimum diff, thats 1.
We have the current network diff, thats the diff a hash has to fulfill to solve a block, currently some 600 million.
And there's your workers vardiff set by the pool, 16 for example.

The nounces getting dropped can never ever solve a block, cause their diff is somewhere between 1 and 16.
Those nounces submitted to the pool as share have any diff higher than 16.
Eventually, one of those billions and billions of shares will have a diff not only higher than 16, but also higher than 600 million.
That one solves the block, and we move to the next pool round.

joef
Member
**
Offline Offline

Activity: 93
Merit: 10


View Profile
November 25, 2013, 03:41:22 PM
 #13212

Yes, I don't understand these. Thank you for your help, hope I will get it soon  Wink

As Example, there are 2 miners, one is slow and gets vardiff 1 and the other is faster with vardiff 16.
The difficulty is 609482679

Both get the same input (hash, data and midstate) but a different target due to the different vardiff.

Now the slower miner will transmit nounces, which would be dropped by the faster miner.
Will the vardiff just be added to the difficulty? So the faster miner would get 609482679 + 15?



trasla
Hero Member
*****
Offline Offline

Activity: 707
Merit: 500



View Profile
November 25, 2013, 03:57:03 PM
 #13213

Now the slower miner will transmit nounces, which would be dropped by the faster miner.

Thats correct.
If the slow miner calculates a hash with diff 10, this will be submitted.
If the fast miner does, it will be dropped, and only hashes with diff >= 16 will be submitted.

Will the vardiff just be added to the difficulty? So the faster miner would get 609482679 + 15?

No.
A miner does not "get" a difficulty.
The hashes a miner calculates are exactly the same no matter what diff.
The only difference is, that _after_ the calculations, the mining software compares the _result_ of the calculation to the diff, and decides whether to send it or not. For the slow miner in the example, the software will send all hashes with diff at least one. For the fast miner, it will send all hashes with diff at least 16.

The 609482679 does not concern your miners at all. If they find a share with diff higher or equal to that, it will be send to the server, since its higher than 16 or 1. The server will see its high enough to satisfy current network diff, and publish it as new block found. You can enjoy a warm feeling, cause it was your miner who found the share. Thats all.

If you were to mine solo, not using a pool, its a little different. Your mining software would not drop all shares below 16, but all below 609482679. Those above would not be send to the pool server, but get published directly to the network, and your warm feeling for finding the hash would be worth 25 BTC plus block fees. But in this case, you would get _nothing_ for all the other shares, whereas you get still paid for all the actually useless shares below 609482679 when mining with a pool, since they proof you tried to find the winning one for the pool.
joef
Member
**
Offline Offline

Activity: 93
Merit: 10


View Profile
November 25, 2013, 04:20:13 PM
 #13214

Great, now I understand. Cheesy

Thanks a lot.
gourmet
Sr. Member
****
Offline Offline

Activity: 311
Merit: 250


View Profile
November 26, 2013, 04:51:02 AM
 #13215

The hashes a miner calculates are exactly the same no matter what diff.
The only difference is, that _after_ the calculations, the mining software compares the _result_ of the calculation to the diff, and decides whether to send it or not. For the slow miner in the example, the software will send all hashes with diff at least one. For the fast miner, it will send all hashes with diff at least 16.

The 609482679 does not concern your miners at all. If they find a share with diff higher or equal to that, it will be send to the server, since its higher than 16 or 1. The server will see its high enough to satisfy current network diff, and publish it as new block found. You can enjoy a warm feeling, cause it was your miner who found the share. Thats all.

Maybe one should add that there's only 1 to 232 probability that the hash just calculated is of difficulty one (or higher).
Trance104
Full Member
***
Offline Offline

Activity: 206
Merit: 100


View Profile
November 26, 2013, 07:53:27 PM
 #13216

Did Slush stop NMC support?
eleuthria
Legendary
*
Offline Offline

Activity: 1750
Merit: 1007



View Profile
November 26, 2013, 08:06:40 PM
 #13217

Did Slush stop NMC support?

Yes, Slush never added NMC to his stratum implementation.  For a while getwork still mined NMC blocks, but since getwork shutdown Slush has not done any NMC merged mining.

RIP BTC Guild, April 2011 - June 2015
Trance104
Full Member
***
Offline Offline

Activity: 206
Merit: 100


View Profile
November 26, 2013, 08:10:26 PM
 #13218

Thank you!
Dino50
Newbie
*
Offline Offline

Activity: 42
Merit: 0


View Profile
November 26, 2013, 08:19:49 PM
 #13219

How long till the end of maintanance?
memeticae
Newbie
*
Offline Offline

Activity: 7
Merit: 0


View Profile
November 26, 2013, 09:22:56 PM
 #13220

Did the pool's performance just increase 10-fold?
My last two rewards (20956, 20957) just decreased by a factor 10 ...

 Huh
Pages: « 1 ... 611 612 613 614 615 616 617 618 619 620 621 622 623 624 625 626 627 628 629 630 631 632 633 634 635 636 637 638 639 640 641 642 643 644 645 646 647 648 649 650 651 652 653 654 655 656 657 658 659 660 [661] 662 663 664 665 666 667 668 669 670 671 672 673 674 675 676 677 678 679 680 681 682 683 684 685 686 687 688 689 690 691 692 693 694 695 696 697 698 699 700 701 702 703 704 705 706 707 708 709 710 711 ... 1154 »
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!