Bitcoin Forum
December 06, 2024, 02:35:42 AM *
News: Latest Bitcoin Core release: 28.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 ... 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 [156] 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 ... 1154 »
  Print  
Author Topic: [4+ EH] Slush Pool (slushpool.com); Overt AsicBoost; World First Mining Pool  (Read 4382698 times)
sharky112065
Sr. Member
****
Offline Offline

Activity: 383
Merit: 250



View Profile
June 25, 2011, 11:36:41 AM
 #3101

The confirmed blocks are almost caught up to the last block completed. We have been extremely unlucky.  Sad

Donations welcome: 12KaKtrK52iQjPdtsJq7fJ7smC32tXWbWr
de_bert
Newbie
*
Offline Offline

Activity: 42
Merit: 0


View Profile
June 25, 2011, 04:24:39 PM
 #3102

Slush, a question concerning transaction fees:

Is the payout
(50 BTC - 1 BTC fee) * (score) / (total score)
or
(TransFees + 50 BTC - 1 BTC fee) * (score) / (total score)?

Some recent blocks had relatively large fees in it, and distributing them along with the 50BTC of the block would of course be highly appreciated :-)

Btw, the explanation on your site does not reflect the current scoring system.
slush (OP)
Legendary
*
Offline Offline

Activity: 1386
Merit: 1097



View Profile WWW
June 25, 2011, 04:44:33 PM
 #3103

(50 BTC - 1 BTC fee) * (score) / (total score)

This.

Quote
Btw, the explanation on your site does not reflect the current scoring system.

I know that, unfortunately it's pretty complex stuff to explain (exponential functio, reason for making older shares less valuable, renormalization) and I failed with some easy description for 'common users'. But because expected payout is +- the same as for share based calculation (without pool hoping), I feel like shares/total shares * 49 is correct enough for average user.

cosurgi
Sr. Member
****
Offline Offline

Activity: 298
Merit: 250


View Profile
June 25, 2011, 09:35:52 PM
Last edit: June 25, 2011, 09:47:27 PM by cosurgi
 #3104

I feel like shares/total shares * 49 is correct enough for average user.
actually I tried to explain this on https://en.bitcoin.it/wiki/Comparison_of_mining_pools

and also it's here: http://forum.bitcoin.org/?topic=1976.msg50002#msg50002

slush (OP)
Legendary
*
Offline Offline

Activity: 1386
Merit: 1097



View Profile WWW
June 25, 2011, 11:00:21 PM
 #3105


That's why I'm talking that I failed in description for *average* user :-).

Justsomeforumuser
Member
**
Offline Offline

Activity: 84
Merit: 10


View Profile
June 26, 2011, 12:08:44 AM
 #3106

I'm still getting

Listener for "Default": 25/06/2011 22:00:27, Error while loading credentials from database for xxx.xxx

errors as posted previously.

Should I take any meaning out of that?

Ho-Hum.
slush (OP)
Legendary
*
Offline Offline

Activity: 1386
Merit: 1097



View Profile WWW
June 26, 2011, 09:01:37 AM
 #3107

Should I take any meaning out of that?

It basically means there was problem in database lookup for your username/password. Do you have correct username/password? I'll search logs, it is weird as I don't see that on other workers...

slush (OP)
Legendary
*
Offline Offline

Activity: 1386
Merit: 1097



View Profile WWW
June 26, 2011, 09:08:02 AM
 #3108

For users of Diablo Miner:

If you're using latest DiabloMiner version and see enormous stale ratio, please downgrade or use another miner. Diablo introduced "ntime rolling" feature in his miner, but those shares will be rejected by all properly coded pools using stock bitcoind as backend. There are some good reasons to *not* use ntime rolling by default. For example, poclbm uses this feature only when pool provide special http header for allowing this. Accepting shares with rolled ntime may lead to accepting duplicate work in some cases, as I found back in January.

Justsomeforumuser
Member
**
Offline Offline

Activity: 84
Merit: 10


View Profile
June 26, 2011, 09:54:40 AM
 #3109

Should I take any meaning out of that?

It basically means there was problem in database lookup for your username/password. Do you have correct username/password? I'll search logs, it is weird as I don't see that on other workers...
It only occurs rarely and mining overall seems to work. Have not changed it since signup and kept my GUIMiner settings identical except for flags and hostname for slush.

It seems similiar to an overload error as in it only pops up sometimes and mining just goes on.

Ho-Hum.
Rodyland
Hero Member
*****
Offline Offline

Activity: 499
Merit: 500


View Profile
June 26, 2011, 09:55:38 AM
 #3110

I tried to log on I got:

Forbidden (403)

CSRF verification failed. Request aborted.

More information is available with DEBUG=True.


I tried to reset my password I get:
Forbidden (403)

CSRF verification failed. Request aborted.

More information is available with DEBUG=True.

Anyone know why?

Anyone?

Beware the weak hands!
1NcL6Mjm4qeiYYi2rpoCtQopPrH4PyKfUC
GPG ID: E3AA41E3
slush (OP)
Legendary
*
Offline Offline

Activity: 1386
Merit: 1097



View Profile WWW
June 26, 2011, 11:23:31 AM
 #3111

Anyone?

I asked you what browser do you use? It happen every time or only time to time?

Basically CSRF is protection to malicious javascripts, but there's no reason why you should see this if you're using site in standard way.

Rodyland
Hero Member
*****
Offline Offline

Activity: 499
Merit: 500


View Profile
June 26, 2011, 12:19:30 PM
 #3112

Anyone?

I asked you what browser do you use? It happen every time or only time to time?

Basically CSRF is protection to malicious javascripts, but there's no reason why you should see this if you're using site in standard way.

Sorry, didn't see your reply.  I just looked again and it's not me - you didn't reply.   But thanks for replying now.

I'm using firefox 4.0.1 on win7 64bit.  It happens every time. 

Beware the weak hands!
1NcL6Mjm4qeiYYi2rpoCtQopPrH4PyKfUC
GPG ID: E3AA41E3
slush (OP)
Legendary
*
Offline Offline

Activity: 1386
Merit: 1097



View Profile WWW
June 26, 2011, 04:02:58 PM
 #3113

Sorry, didn't see your reply.  I just looked again and it's not me - you didn't reply.   But thanks for replying now.

Ah, sorry, I know that I wrote you a reponse, but then obviously forgot to send the form Wink.

Quote
I'm using firefox 4.0.1 on win7 64bit.  It happens every time. 

What form/url is that? Can you catch post request somehow (for example using firebug) and send me a PM? I tested all forms but don't see anything wrong. Also application logs are empty. Weird...

max in montreal
Hero Member
*****
Offline Offline

Activity: 504
Merit: 500


View Profile
June 26, 2011, 04:56:52 PM
 #3114

on the statistics page we only go back so far...is it possible for me to see the stats for 3-4 weeks somewhere?
gmaxwell
Moderator
Legendary
*
Offline Offline

Activity: 4284
Merit: 8816



View Profile WWW
June 26, 2011, 05:38:19 PM
 #3115

For users of Diablo Miner:

If you're using latest DiabloMiner version and see enormous stale ratio, please downgrade or use another miner. Diablo introduced "ntime rolling" feature in his miner, but those shares will be rejected by all properly coded pools using stock bitcoind as backend. There are some good reasons to *not* use ntime rolling by default. For example, poclbm uses this feature only when pool provide special http header for allowing this. Accepting shares with rolled ntime may lead to accepting duplicate work in some cases, as I found back in January.

"properly coded pools using stock bitcoind as backend"

That is an oxymoron.

If you're using stock bitcoind as a backend for a non-trivally sized pool you're going to be losing work due to blocking getworks and time/extra_nonce update races.

The change to support rolling ntime is a one line patch to bitcoind.

slush (OP)
Legendary
*
Offline Offline

Activity: 1386
Merit: 1097



View Profile WWW
June 26, 2011, 07:41:43 PM
 #3116

If you're using stock bitcoind as a backend for a non-trivally sized pool you're going to be losing work due to blocking getworks and time/extra_nonce update races.

Afaik all pools are using bitcoind as backend, some with custom patches for better performance, as in my case.

Quote
The change to support rolling ntime is a one line patch to bitcoind.

It goes little complicated if you think about cheating users.

gmaxwell
Moderator
Legendary
*
Offline Offline

Activity: 4284
Merit: 8816



View Profile WWW
June 26, 2011, 08:57:52 PM
 #3117

It goes little complicated if you think about cheating users.

Does it?  The fact that the nonce changes doesn't create any cheating risk. So, e.g. if you just treat the few least significant bits of the timestamp as more nonce you're no worse off.


Luke has patches to make bitcoind handle ntime rolling in his public repository. I strongly suggest running them, because they also fix duplicate work that bitcoind will already issue without rolling. (because it's able to reset the extranonce twice)



Justsomeforumuser
Member
**
Offline Offline

Activity: 84
Merit: 10


View Profile
June 27, 2011, 12:27:34 AM
 #3118

Seems like an old friend is stopping by slush's pool again.
Not sure if it's just the pool being overloaded or an attack.

First time I saw the unhandled exception btw.

Listener for "Default": 26/06/2011 21:47:48, Problems communicating with bitcoin RPC
Listener for "Default": 26/06/2011 22:54:50, Problems communicating with bitcoin RPC
Listener for "Default": 26/06/2011 22:57:54, Problems communicating with bitcoin RPC
Listener for "Default": 26/06/2011 23:09:55, Problems communicating with bitcoin RPC
Listener for "Default": 27/06/2011 00:07:16, Unhandled exception (1040, 'Too many connections')
Listener for "Default": 27/06/2011 01:15:53, Problems communicating with bitcoin RPC



Ho-Hum.
3txx
Member
**
Offline Offline

Activity: 111
Merit: 11


View Profile
June 27, 2011, 01:48:41 AM
 #3119

my confirmed reward rate didn't change any more (since 4-5h) - anybody with the same problem?
datguywhowanders
Member
**
Offline Offline

Activity: 112
Merit: 10



View Profile
June 27, 2011, 01:51:01 AM
 #3120

Seems like an old friend is stopping by slush's pool again.
Not sure if it's just the pool being overloaded or an attack.

First time I saw the unhandled exception btw.

Listener for "Default": 26/06/2011 21:47:48, Problems communicating with bitcoin RPC
Listener for "Default": 26/06/2011 22:54:50, Problems communicating with bitcoin RPC
Listener for "Default": 26/06/2011 22:57:54, Problems communicating with bitcoin RPC
Listener for "Default": 26/06/2011 23:09:55, Problems communicating with bitcoin RPC
Listener for "Default": 27/06/2011 00:07:16, Unhandled exception (1040, 'Too many connections')
Listener for "Default": 27/06/2011 01:15:53, Problems communicating with bitcoin RPC




I've been seeing (hearing really as my fans die down and then wind back up again a few minutes later) a lot of problems communicating today as well.

Are we having issues or seeing another DDoS, Slush?

Donations Welcome: 163id7T8KZ6MevqT86DjrBF2kfCPrQsfZE
Pages: « 1 ... 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 [156] 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 ... 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!