yes someone just dumped 150ghash/sec within the last few hours, solo miners are jumping on the pools it seems :/
looks like because deepbit is down... |
|
|
|
By the way, webserver is pretty overloaded last two days and crashing more often than I want  . Initially there was few thousand pageviews per day back in December and January. Now we're on few milions pageviews (including json stats)... I'll move website to much stronger hardware tomorrow, hope it will keep up for following few hours. |
|
|
|
Warning!During last two days, three users reported that somebody attacked their pool accounts and steal their bitcoins. All users told me that they used weak passwords or even same password as login . I highly recommend to all users to change their weak passwords to something stronger to protect your funds! You can change your password using 'Forgot username/password' link on login page.
|
|
|
|
Slush's pool is not secure because he messed up his algorithm.
Can you be more specific? Looks like you found (or you think that you found) some mistake in score implementation, but currently I don't know about any. |
|
|
|
EDIT: After a while the statistic page showed that i had a reward in that block.
Yes, it take few minutes after round closing to calculate round rewards. |
|
|
|
|
kiba, bitcoin value went up drastically since December. Because nobody is working on this project yet, can I change my offer from 100 BTC to 40 BTC? It is still much higher than original offer (in USD prices). Thanks.
|
|
|
|
Unconfirmed/confirmed should not be affecting the total...
Of course not. But during block confirmations I'm 'moving' those unconfirmed funds from one 'heap' to another. This can take some time, usually few seconds. Don't forget that profile page is cached for minute, so when you hit time during this calculation, you might see this for one minute. Technical details: unconfirmed reward is calculated as database query from block reward table, filtering out already confirmed blocks. Once funds are confirmed, they are added to user's 'reward' field. |
|
|
|
|
Yes, website was down for +- 40 minutes. I'm sorry for troubles. Mining worked all the time.
|
|
|
|
I have the my account page open and I refresh it every now and then so I can see my estimated reward and the total. I keep an eye on total so I know when a round is over then I check the Statistics page to see what my exact reward was. My total was 2.64xxxx bitcoins, I hit refresh to see updated stats and it went to 2.51xxx bitcoins. Sometimes it will go back to normal after a few minutes, but I was alarmed today when the round ended and my reward as added to the lower total. So I just lost some bitcoins. I'm not sure if Slush is even aware of this. Can others please keep an eye on their My account page and see if anyone else is experiencing this?
OK, this is possible in time when blocks are just confirming (once every hour). Confirmation is taking longer time as there are more workers to calculate. But after few seconds it will 'repair' itself (as calculation is done, unconfirmed reward is moved to confirmed). No need to worry about this. |
|
|
|
No one look at their "my account" page enough to notice sometimes the total reward goes down? I've seen this multiple times a day
Payout? |
|
|
|
I see that when the internet is disconnected and then reconnects poclbm doesn't resume. Would a router giving a dedicated 192... address solve this ? Or a static IP ? I mean is there a solution that when theres an internet disconnection poclbm resumes ?
Are you using latest version? There were some issues in older releases. |
|
|
|
That's what I meant. "Owned up to" is an American idiom meaning "publicly admitted".
Oh, then excuse my ignorance |
|
|
|
No, nobody has owned up to cheating everybody else out of money.
Well, nobody *publicly* claimed that he's cheating others. But I'm sure that somebody implemented it, because free money are free money . I wanted to implement it (and openly demonstrated) because of never ending discussion with some people (who don't understant that it really works), but then lost a motivation. It's their problem that they didn't catch it (actually they later introduced some anti-hoping strategy, too; you know who . |
|
|
|
I've been getting a lot of
Listener for "Default": 26/05/2011 23:25:41, Unknown login xxxx.xxxx
Listener for "Default": 26/05/2011 23:25:42, Unknown login xxxx.xxxx
Listener for "Default": 26/05/2011 23:25:43, Unknown login xxxx.xxxx
Listener for "Default": 27/05/2011 00:23:06, Problems communicating with bitcoin RPC
for about two minutes and then it worked
Database was down for a moment, so authentication didn't work. |
|
|
|
I've been getting 404s, 502s and 504s quite often today, including a couple in the last 15 minutes or so. On the regular web interface, not on the miners.
Yes, my fault, I'm sorry. Should be finally fixed. |
|
|
|
Without longpole us little miners are dead in the water
Why? Long polling does not affect mining profit so much. Of course it improve stale rate a bit, but mostly it is performance optimization on pool side... On the other side, I don't understand why (with current difficulty) is somebody still mining with CPU |
|
|
|
With current difficulty it should give me something like 5BTC per day @ 9$/BTC...
Don't you just take 1BTC/block? I was talking about my mining rig, of course. |
|
|
|
Jesus h....it's nuts how much hashing power has been added to the network lately. It's as if everyone, their mother, father, cousin, and their dog bought a high end ATI card and started mining.
Yes, looks like difficulty 1.000.000 will be reached soon. On the other side, when I started my current rig in January, it earned 100BTC per day @ 0.3$/BTC. With current difficulty it should give me something like 5BTC per day @ 9$/BTC... |
|
|
|
|
Bitcoin difficulty changed, it is over 434000 now. With current pool speed at 500GHas/s it will take in average almost exactly one hour to find a block.
|
|
|
|
|
Show Posts
