[1050 TH] BitMinter.com [1% PPLNS,Pays TxFees +MergedMining,Stratum,GBT,vardiff]

[Hunyadi]

Same here...

[1656752559]

1656752559

[1656752559]

1656752559

[1656752559]

1656752559

[Gibson]

It's down, grrrrrr!

[DrHaribo]

There is very high packet loss right now (network issue). I'm looking into it.

[BitAddict]

2013.06.06 [19:30]  Communication error, HTTP status code 50

Time to reset the computer 

[Gibson]

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.

[Xian01]

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.

[Gibson]

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.

I do agree that the graphs and stats... at Slush is a bit better and they are missed here.

[ddalex]

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. ...

Not only the POOL, the BITMINTER Client is also the best, written in the best language today - SCALA
You can trust me - I started 40 years ago with CS

[DrHaribo]

The high packetloss is caused by backbone connectivity issues at Hetzner: http://www.hetzner-status.de/en.html

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.

[Xian01]

The high packetloss is caused by backbone connectivity issues at Hetzner: http://www.hetzner-status.de/en.html

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.

 Issues appear to be resolved.

 Cheers !

[btceic]

The high packetloss is caused by backbone connectivity issues at Hetzner: http://www.hetzner-status.de/en.html

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.

 Issues appear to be resolved.

 Cheers !

confirmed, thx!

[badalien]

do you know that hetzer was hacked the last days.

[DrHaribo]

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.

[GuiltySpark343]

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 ...

[redtwitz]

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.

[kano]

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.

... and you'd have to discount all the ASICs, rewrite the firmware for the FPGA's, write a new OpenCL for the GPUs and of course a new miner.

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.

[badalien]

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.

[Jayjay04]

Only 3 blocks in the last 15h...

[DrHaribo]

Edit: Whe i see the transaction history i understand why my earnings is so slow, but i dont understand why.

When your proofs of work are accepted by the server they are registered in the current (not yet finished) shift. Each time a block is found the last 10 completed shifts are paid.

After the shift is completed the work is now eligible for pay from any blocks we find. From then on, every time we find a block those proofs of work are paid from the income in that block, until 10 more shifts are completed. This causes a delay from the moment you do the work until it is fully paid and stops receiving payments.

Currently shifts take almost 1 hour. So it takes anything from a split second to 1 hour from the time you do some work until its shift is finished. And then it takes 10 shifts (10 hours) until it is fully paid. So the delay from you did some work until it is fully paid is 10 to 11 hours with the current pool hashrate and Bitcoin difficulty.

In addition, if you don't have the prepay perk activated then the payments are only set up when a block is found but not executed until the block is confirmed. This causes an additional delay of about 20 hours from the block is found until the coins hit your BitMinter account.

That's a total payment delay from 10 up to 31 hours.

And then there is luck... daily earnings fluctuate as we play the Bitcoin lottery called mining.

[badalien]

Thanks for the good explanation, i understand this now, its no Problem in my little mining environment and in the last day i do some things, check route, Ping , check router, antivir check from all sides, test new version of cgminer, check logs etc ..Puhhh, i need a little bit of oxygen :-)