i think a have stupid problem, my miner works for 12 hours with ~ 7,3 Ghs for 0.030896BTC, i see no error on my miner, go over stratum to bitminter. The bitminter page shows the correct hasrate of my two little miner but the earning is a little bit to slow so i find this. This is the third day that i have fucking slow earning. When i go to another pool i can see the same hashrate and much more earnings. But i will not mine on another pool, so i hope you can give me a hint to solve the problem. The miner use http://mint.bitminter.com:3333 for the works. What can i do to find the problem.
Edit: Whe i see the transaction history i understand why my earnings is so slow, but i dont understand why.
Topic: [1050 TH] BitMinter.com [1% PPLNS,Pays TxFees +MergedMining,Stratum,GBT,vardiff] - page 208. (Read 837101 times)
June 07, 2013, 09:17:14 AM
June 07, 2013, 08:00:18 AM
Nice to know that there is a 120 TH/s network out there just for doing SHA256 hashing! Wonder how long it would take to crack that database ...
120 TH/s for Bitcoin mining translates to roughly 180 TH/s for SHA256-cracking. Since you need on average 2²⁵⁵ tries to brute-force a 256-bit hash, it will take on average 2²⁵⁵÷(180×10¹²)=3.22×10⁶² seconds or 3.22×10⁶²÷(60×60×24×365)=1.02×10⁵⁵ years to crack each password.
Bitcoin is an optimised double hash (though it is 3 times through the 64 stages) with optimisations to remove the first time through and some of the steps in the 2nd and 3rd.
i.e. you couldn't use it.
June 07, 2013, 07:22:08 AM
Nice to know that there is a 120 TH/s network out there just for doing SHA256 hashing! Wonder how long it would take to crack that database ...
120 TH/s for Bitcoin mining translates to roughly 180 TH/s for SHA256-cracking. Since you need on average 2²⁵⁵ tries to brute-force a 256-bit hash, it will take on average 2²⁵⁵÷(180×10¹²)=3.22×10⁶² seconds or 3.22×10⁶²÷(60×60×24×365)=1.02×10⁵⁵ years to crack each password.
June 07, 2013, 05:52:11 AM
From: http://forum.uinvest.com.ua/showthread.php?40387-German-webhoster-Hetzner-%28hoster-of-uinvest%29-got-hacked
"The access passwords for your Robot client account are stored in our database as Hash (SHA256) with salt. As a precaution, we recommend that you change your client passwords in the Robot."
Nice to know that there is a 120 TH/s network out there just for doing SHA256 hashing! Wonder how long it would take to crack that database ...
"The access passwords for your Robot client account are stored in our database as Hash (SHA256) with salt. As a precaution, we recommend that you change your client passwords in the Robot."
Nice to know that there is a 120 TH/s network out there just for doing SHA256 hashing! Wonder how long it would take to crack that database ...
June 07, 2013, 02:50:14 AM
do you know that hetzer was hacked the last days.
Yeah, sounded like some pretty fancy malware the hacker installed too. I don't know whether that has something to do with the network issues or not.
June 07, 2013, 02:16:26 AM
do you know that hetzer was hacked the last days.
June 06, 2013, 01:06:16 PM
The high packetloss is caused by backbone connectivity issues at Hetzner: http://www.hetzner-status.de/en.html
Quote
Type: Fault report
Categories: Network
Start: June 6, 2013 6:50:00 PM CEST
End: June 6, 2013 7:30:00 PM CEST
Description: We are currently experiencing a fault in the backbone connection. This may lead to brief connectivity issues. Please bear with us. As soon as more information is available, we shall inform you via this website.
We apologize for any inconvenience caused.
Thank you for your understanding.
Categories: Network
Start: June 6, 2013 6:50:00 PM CEST
End: June 6, 2013 7:30:00 PM CEST
Description: We are currently experiencing a fault in the backbone connection. This may lead to brief connectivity issues. Please bear with us. As soon as more information is available, we shall inform you via this website.
We apologize for any inconvenience caused.
Thank you for your understanding.
Issues appear to be resolved.
Cheers !
confirmed, thx!
June 06, 2013, 01:04:44 PM
The high packetloss is caused by backbone connectivity issues at Hetzner: http://www.hetzner-status.de/en.html
Quote
Type: Fault report
Categories: Network
Start: June 6, 2013 6:50:00 PM CEST
End: June 6, 2013 7:30:00 PM CEST
Description: We are currently experiencing a fault in the backbone connection. This may lead to brief connectivity issues. Please bear with us. As soon as more information is available, we shall inform you via this website.
We apologize for any inconvenience caused.
Thank you for your understanding.
Categories: Network
Start: June 6, 2013 6:50:00 PM CEST
End: June 6, 2013 7:30:00 PM CEST
Description: We are currently experiencing a fault in the backbone connection. This may lead to brief connectivity issues. Please bear with us. As soon as more information is available, we shall inform you via this website.
We apologize for any inconvenience caused.
Thank you for your understanding.
Issues appear to be resolved.
Cheers !
June 06, 2013, 01:01:46 PM
The high packetloss is caused by backbone connectivity issues at Hetzner: http://www.hetzner-status.de/en.html
Quote
Type: Fault report
Categories: Network
Start: June 6, 2013 6:50:00 PM CEST
End: June 6, 2013 7:30:00 PM CEST
Description: We are currently experiencing a fault in the backbone connection. This may lead to brief connectivity issues. Please bear with us. As soon as more information is available, we shall inform you via this website.
We apologize for any inconvenience caused.
Thank you for your understanding.
Categories: Network
Start: June 6, 2013 6:50:00 PM CEST
End: June 6, 2013 7:30:00 PM CEST
Description: We are currently experiencing a fault in the backbone connection. This may lead to brief connectivity issues. Please bear with us. As soon as more information is available, we shall inform you via this website.
We apologize for any inconvenience caused.
Thank you for your understanding.
June 06, 2013, 12:41:02 PM
There is very high packet loss right now (network issue). I'm looking into it.
One of the things I like about this pool, is the owner (the Doc) showing up right away, telling us what is wrong and that he's on it. 
...
You can trust me - I started 40 years ago with CS
June 06, 2013, 12:40:23 PM
There is very high packet loss right now (network issue). I'm looking into it.
One of the things I like about this pool, is the owner (the Doc) showing up right away, telling us what is wrong and that he's on it. This is something I really missed at Slush's.
Speaking of Slush, I really miss that dude's graphs and stats... But I will agree, DrHaribo is really on-the-ball with the way he is managing his pool and communicating with us.
Kudos, Doctor.
June 06, 2013, 12:35:43 PM
There is very high packet loss right now (network issue). I'm looking into it.
One of the things I like about this pool, is the owner (the Doc) showing up right away, telling us what is wrong and that he's on it. This is something I really missed at Slush's.
Speaking of Slush, I really miss that dude's graphs and stats... But I will agree, DrHaribo is really on-the-ball with the way he is managing his pool and communicating with us.
Kudos, Doctor.
June 06, 2013, 12:33:38 PM
There is very high packet loss right now (network issue). I'm looking into it.
One of the things I like about this pool, is the owner (the Doc) showing up right away, telling us what is wrong and that he's on it. This is something I really missed at Slush's.
Thanks Doc.
June 06, 2013, 12:29:42 PM
Quote
2013.06.06 [19:30] Communication error, HTTP status code 50
Time to reset the computer
June 06, 2013, 12:27:56 PM
There is very high packet loss right now (network issue). I'm looking into it.
June 06, 2013, 12:21:26 PM
It's down, grrrrrr!
June 06, 2013, 12:21:14 PM
Same here...
June 06, 2013, 12:20:44 PM
problems are back on bitminter, no connection to stratum.
Yep. I'm dead in the water as well on Bitminter
June 06, 2013, 12:20:02 PM
problems are back on bitminter, no connection to stratum.
Yep. I'm dead in the water as well on Bitminter
June 06, 2013, 12:19:10 PM
problems are back on bitminter, no connection to stratum.
Jump to: