Bitcoin Forum
September 27, 2016, 06:56:16 PM *
News: Due to DDoS attacks, there may be periodic downtime.
 
   Home   Help Search Donate Login Register  
Poll
Question: What type of pool payouts do you prefer?
Bitcoins - 3151 (80.4%)
Bank transfer / USD - 407 (10.4%)
Gold/silver coins and bars - 359 (9.2%)
Total Voters: 3915

Pages: « 1 ... 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 712 713 [714] 715 716 717 718 719 720 721 722 723 724 725 726 727 728 729 730 731 732 733 734 735 736 737 738 739 740 741 742 743 744 745 746 747 748 749 750 751 752 753 754 755 756 757 758 759 760 761 762 763 764 ... 1104 »
  Print  
Author Topic: [40+ PH] SlushPool (slushpool.com); World's First Mining Pool  (Read 3855144 times)
MrTeal
Legendary
*
Offline Offline

Activity: 1232


View Profile
January 14, 2014, 02:06:11 PM
 #14261

I have recently started using slush pool and noticed that on some blocks my income is zero despite having shares and on other blocks I have shares "none" and reward "none". I have been mining without interruption or errors.

279765
279819
279837
279847
279890
279904
279918
280422
280374
280362
280337
280328

Also on my account page it says that the last submitted share was 20h ago, which is wrong since I am still mining and submitting shares.
Should I worry ?
Are you sure your credentials are current and that you're actually submitting shares to Slush?
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1475002576
Hero Member
*
Offline Offline

Posts: 1475002576

View Profile Personal Message (Offline)

Ignore
1475002576
Reply with quote  #2

1475002576
Report to moderator
unknown.usr
Member
**
Offline Offline

Activity: 106


View Profile
January 14, 2014, 02:39:28 PM
 #14262

Dammit!  My Pi goes down when I am out for 16 hours, and all sorts of blocks process.  I am back up and now it's six+ hour blocks all the way.  Arghhh!
Matumaru
Member
**
Offline Offline

Activity: 73


View Profile
January 14, 2014, 05:37:51 PM
 #14263

Hi ya all,

It is not a complain, but I have been noticing last months, that every time that pool's hashrate has a huge hop (like >20TH/s) we are experiencing problems of "stolen" blocks or long rounds (>6h). The last 48h is another example. Hope this new hardware Slush implemented is going to kill this glitches with time.

Salute all Slusher's.
bspurloc
Hero Member
*****
Offline Offline

Activity: 569


View Profile
January 14, 2014, 09:15:17 PM
 #14264

Slush having back end issues?

How are 3 blades that show running perfectly for 5 days straight doing 144 shares a minute bfg showing no issues 10gh/s 10gh/s 10gh/s showing this?
shares 31549   18319.2919   0 minutes   23290.121  23gh?!?!
while another 3 are more semi normal 28gh/s is pretty low for 3 blades, but 23 is a sign something is up
shares 38193   19111.7396   0 minutes   28194.858

Yes the 2nd group has more shares submitted but there is no reason for the first groups to be low as they are all running fine, so I assume slush back end lost shares again?
all other miners are dead on... 10gh/s missing is pretty noticeable
cenicsoft
Member
**
Offline Offline

Activity: 116


View Profile WWW
January 14, 2014, 09:21:47 PM
 #14265

Hi ya all,

It is not a complain, but I have been noticing last months, that every time that pool's hashrate has a huge hop (like >20TH/s) we are experiencing problems of "stolen" blocks or long rounds (>6h). The last 48h is another example. Hope this new hardware Slush implemented is going to kill this glitches with time.

Salute all Slusher's.

It's not a hardware issue on Slush's end.  During long rounds, many people will hop to other pools.  You'll see a drop in hashing power which means that there's less chance to find a block compounding the problem.  Also, the hash rate is fluid meaning it can vary even if no miners came or went.  Hardware errors, vardiff, etc. play a factor in determining the hash rate the pool recognizes.

BannerView.com - Energize your Business Online, powered by BannerOS, the platform that turns your website into a powerful business tool.
Want to grow your website traffic? Check out the BannerMethod.
Matumaru
Member
**
Offline Offline

Activity: 73


View Profile
January 14, 2014, 11:47:02 PM
 #14266

Hi ya all,

It is not a complain, but I have been noticing last months, that every time that pool's hashrate has a huge hop (like >20TH/s) we are experiencing problems of "stolen" blocks or long rounds (>6h). The last 48h is another example. Hope this new hardware Slush implemented is going to kill this glitches with time.

Salute all Slusher's.

It's not a hardware issue on Slush's end.  During long rounds, many people will hop to other pools.  You'll see a drop in hashing power which means that there's less chance to find a block compounding the problem.  Also, the hash rate is fluid meaning it can vary even if no miners came or went.  Hardware errors, vardiff, etc. play a factor in determining the hash rate the pool recognizes.

Well, if you were right, then the hashrate would have a decrease in those long rounds which is not. 700+ keeps on.

I don't point to hardware issue,but seems kind of overloading. If your read to this post often, you should have notice that since this was on 380GH some glitches started to appear, and coming up to this "hardware upgrade". Hope with this, pool has resilence for a long time. but there are some ISP related issues pointed last week that cannot be ignored.

What I'm talking about are those "none" rounds, stolen blocks (by ghash.io mostly), worker hashrate variance, very long rounds, variance in score results, variance between round logs from peer to peer, etc.... I'm user of SLUSH's pool (not our's, but his) pool, and I think for a 2% fee we deserve the best beyond an admin that is not present even on his forum (even when he recovered his access, beyond support questions).

Talking about 2% fee. My math perhaps might be not good, but WE are making around 1500 BTC per week which means:

1500 BTC * 2 / 100 = 30 BTC WEEKLY!!!

I mean, I am not talking about profit or something else. But for around 100.000$ monthly (rounded pondered value last months). WE deserve the best pool in the world. [SLUSH I hope you are reading this and comment about]

Matumaru
Member
**
Offline Offline

Activity: 73


View Profile
January 15, 2014, 12:14:38 AM
 #14267

Hi ya all,

It is not a complain, but I have been noticing last months, that every time that pool's hashrate has a huge hop (like >20TH/s) we are experiencing problems of "stolen" blocks or long rounds (>6h). The last 48h is another example. Hope this new hardware Slush implemented is going to kill this glitches with time.

Salute all Slusher's.

It's not a hardware issue on Slush's end.  During long rounds, many people will hop to other pools.  You'll see a drop in hashing power which means that there's less chance to find a block compounding the problem.  Also, the hash rate is fluid meaning it can vary even if no miners came or went.  Hardware errors, vardiff, etc. play a factor in determining the hash rate the pool recognizes.

Sorry, but, answering to your assumption about "factors". I am a systems engineer certified in a lot of technologies (and updated my certs) and what your are talking and assuming is "Coincidence". Which with time and experience your know that coincidence does not exist anymore talking about computering. It is like talking about "magic, or how the small men inside the server trick you", and yes sure you can "fix up a server hitting it enough times with your hand".

People, please. Think.

EDIT. And if your can explain in 500 words what VARDIFF is, without looking in wikipedia or even google earth, I will tranfer you 1 Satoshi. Fees on my own.

PD. "fluid" is not a substantive that you want to use for hashrate.| And... sorry, you were trying to answer only about "determining the hash rate the pool recognizes"HuhHuh What about the other one hundred questions?
PostMixer
Jr. Member
*
Offline Offline

Activity: 53


View Profile
January 15, 2014, 12:42:19 AM
 #14268

My understanding of VARDIFF is that the pool sends different levels of difficulty to you based on your miners capability. i.e. 125/22. This gives you better awards for working on more difficult work without the need to hog a lot of I/o bandwidth. I believe it helps keep the traffic in and out of the server to a more predictable level while still giving stronger miners more work, therefor more rewards.

Again this is just my interpretation ?

I won't ask for donations but I will ask for help. And I won't give donations but I will help if I can.
KNK
Hero Member
*****
Offline Offline

Activity: 614


View Profile
January 15, 2014, 08:37:20 AM
 #14269

working on more difficult work
There is no more (or less) difficult work - you always work on the same block (and data) as the rest of the world.

VARDIFF is the minimum result (share diff) you report back to the pool in order to send on average ~15 reports per minute.

If your hardware is capable of calculating 1000 jobs per minute (~72GH/s) and each job returns at least one 'diff 1 share' (which is exactly the case with dblSHA256) - you will need to send 1000 reports, which is too much load for the server and your bandwidth

But because 500 from those will have diff of 2 or more, 250 will have diff of 3 or more etc. ... then for you to send ~15 reports means that you need to send back only those shares that are of diff 7 or higher


BTC tips: 1KNK1akhpethhtcyhKTF2d3PWTQDUWUzHE
cenicsoft
Member
**
Offline Offline

Activity: 116


View Profile WWW
January 15, 2014, 05:13:33 PM
 #14270


EDIT. And if your can explain in 500 words what VARDIFF is, without looking in wikipedia or even google earth, I will tranfer you 1 Satoshi. Fees on my own.

PD. "fluid" is not a substantive that you want to use for hashrate.| And... sorry, you were trying to answer only about "determining the hash rate the pool recognizes"HuhHuh What about the other one hundred questions?

Don't need 500 words to explain VARDIFF.  Stands for Variable Difficulty which means that the higher your hash rate, the more work the pool sends to your miner (worker).  Once you solve the work, all shares are sent at once then counted as a difficulty of one. It reduces the amount of traffic you need to send to the server.  It's unrelated to the current difficulty of the network, only related to the difficulty the pool sets to your miner.

Fluid - as in the Internet is a fluid network with sometimes it losing packets, capacity issues, network connectivity issues.  If your miner solves 1,000 difficulty 1 equivalent shares, but then goes to send them to the pool and there's a network issue, you could lose them.  Or if a new block is found or the server sends new work, the work you did on those shares is discarded.  All of that will be reflected in how the pool determines the hash rate.  Yes, therefore the hash rate is fluid. 

Keep your Satoshi.

BannerView.com - Energize your Business Online, powered by BannerOS, the platform that turns your website into a powerful business tool.
Want to grow your website traffic? Check out the BannerMethod.
MrTeal
Legendary
*
Offline Offline

Activity: 1232


View Profile
January 15, 2014, 05:26:30 PM
 #14271


EDIT. And if your can explain in 500 words what VARDIFF is, without looking in wikipedia or even google earth, I will tranfer you 1 Satoshi. Fees on my own.

PD. "fluid" is not a substantive that you want to use for hashrate.| And... sorry, you were trying to answer only about "determining the hash rate the pool recognizes"HuhHuh What about the other one hundred questions?

Don't need 500 words to explain VARDIFF.  Stands for Variable Difficulty which means that the higher your hash rate, the more work the pool sends to your miner (worker).  Once you solve the work, all shares are sent at once then counted as a difficulty of one. It reduces the amount of traffic you need to send to the server.  It's unrelated to the current difficulty of the network, only related to the difficulty the pool sets to your miner.

Keep your Satoshi.
You wouldn't have earned the Satoshi anyway, as I assume he wanted an explanation that was at least on the same continent as correct.
Matumaru
Member
**
Offline Offline

Activity: 73


View Profile
January 15, 2014, 05:43:53 PM
 #14272

I feel such a Troll in this moment for have done that. Is always funny when they use those "big words" that briefly resumes everything.

Anyway, not a point of discussion for this thread.
KNK
Hero Member
*****
Offline Offline

Activity: 614


View Profile
January 15, 2014, 06:20:08 PM
 #14273

Is this normal to see a 5ghs difference between miner stats and pool stats? Any info would be greatly appreciated.
Yes, because your miner has the exact info for your hardware capabilities, while the pool is trying to guess it with backward calculation based on the shares submitted from you. If you miner has a luck to find more - the pool will show more and the opposite.

BTC tips: 1KNK1akhpethhtcyhKTF2d3PWTQDUWUzHE
Billbags
Sr. Member
****
Offline Offline

Activity: 280

Brainwashed this way


View Profile
January 15, 2014, 07:33:39 PM
 #14274

Thanks for the info

Listen: meat beat manifesto ~ Edge of no control (pt.1)
Read:"He who controls the past controls the future. He who controls the present controls the past." ~ George Orwell
Think: http://unenumerated.blogspot.com/2014/12/the-dawn-of-trustworthy-computing.html
PostMixer
Jr. Member
*
Offline Offline

Activity: 53


View Profile
January 15, 2014, 08:20:51 PM
 #14275

The pool automatically recognizes strength of your mining hardware and adjusts work difficulty for the miner accordingly. With Vardiff implemented, each miner is led to send results of its work to the server around 20 times per minute. That's the goal. If the miner is too fast, Vardiff increases the difficulty for its work and when too slow, the difficulty decreases.

This does not affect your score or rewards. For example: When your miner submits a proof of work with difficulty set to 5, it is counted as 5 shares by the pool. When submitted with difficulty 1 then only 1 share is counted. It takes 5x more work to find a proof of work when difficulty is set to 5 then when set to 1. So it is valued 5x more.

The algorithm re-evaluates your miner's strength continuously but it doesn't change the difficulty when your hashrate is stable.

I won't ask for donations but I will ask for help. And I won't give donations but I will help if I can.
Sir Alan
Full Member
***
Offline Offline

Activity: 221


View Profile
January 16, 2014, 04:07:09 PM
 #14276

“Mr Bond, they have a saying in Chicago: 'Once is happenstance. Twice is coincidence. The third time it's enemy action'.”
Well, GHash.IO has done it to us again with block 280616.  The timings are really weird:  the timestamp for 280616 - 12:20:06 - is more than two minutes later than the received time - 12:17:31 (which is the same as the time claimed by Slush) - and is even nearly two minutes later than the next block, 280617, which was also bagged by GHash.IO.  Something doesn't look right.

Does anybody know if they have done this to other pools?

1Eeyore17YeHrbJW5Q3pSdV8sXujkdrrFc
MrTeal
Legendary
*
Offline Offline

Activity: 1232


View Profile
January 16, 2014, 04:23:42 PM
 #14277

“Mr Bond, they have a saying in Chicago: 'Once is happenstance. Twice is coincidence. The third time it's enemy action'.”
Well, GHash.IO has done it to us again with block 280616.  The timings are really weird:  the timestamp for 280616 - 12:20:06 - is more than two minutes later than the received time - 12:17:31 (which is the same as the time claimed by Slush) - and is even nearly two minutes later than the next block, 280617, which was also bagged by GHash.IO.  Something doesn't look right.

Does anybody know if they have done this to other pools?
Yes, repeatedly. It's a common complain about gigahash.io

Though to be fair, we did solve two blocks in a row yesterday (280561 and 280562) and orphaned someone else's block (280562) when the network picked ours.
EasyQuest
Full Member
***
Offline Offline

Activity: 198


Brony Bitcoin, Litecoin Miner


View Profile
January 17, 2014, 01:00:24 AM
 #14278

Why I like mining on slush

21478   2014-01-16 23:27:08   0:00:20   2784211        1680     0.01479891       280890    25.01347342    88 confirmations left
21477   2014-01-16 23:26:48   2:15:28   1344679965   471240   0.00814433           280889   25.05321188    87 confirmations left

Nearly got a double in reward from that block.
kfactor
Member
**
Offline Offline

Activity: 109


View Profile
January 17, 2014, 01:19:32 AM
 #14279

Why I like mining on slush

21478   2014-01-16 23:27:08   0:00:20   2784211        1680     0.01479891       280890    25.01347342    88 confirmations left
21477   2014-01-16 23:26:48   2:15:28   1344679965   471240   0.00814433           280889   25.05321188    87 confirmations left

Nearly got a double in reward from that block.

If you don't mind my asking, what's your hashrate on slush, around 210GH/s?
EasyQuest
Full Member
***
Offline Offline

Activity: 198


Brony Bitcoin, Litecoin Miner


View Profile
January 17, 2014, 01:28:45 AM
 #14280

Why I like mining on slush

21478   2014-01-16 23:27:08   0:00:20   2784211        1680     0.01479891       280890    25.01347342    88 confirmations left
21477   2014-01-16 23:26:48   2:15:28   1344679965   471240   0.00814433           280889   25.05321188    87 confirmations left

Nearly got a double in reward from that block.

If you don't mind my asking, what's your hashrate on slush, around 210GH/s?

You are close but it is 240 GH/s
Pages: « 1 ... 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 712 713 [714] 715 716 717 718 719 720 721 722 723 724 725 726 727 728 729 730 731 732 733 734 735 736 737 738 739 740 741 742 743 744 745 746 747 748 749 750 751 752 753 754 755 756 757 758 759 760 761 762 763 764 ... 1104 »
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!