Anyone else failing to have their payment sent out? My threshold was 1.0 and it failed to send. So I put it at 1.3, which is how many coins were in my Slush account, saved, and still it fails to pay. Now I'm holding 1.4.
Do you have correct wallet address filled in profile? |
|
|
|
Hi slush, I'm trying to reset my password. I insert the email and i click on the button, but nothing is in my email. Could you check, please?
That looks like you registered account with another email, so password recovery didn't find an account. I know that password recovery need a little better error handling... |
|
|
|
The trial of Sierra Chart has run out for me and now this doesn't work any more.  I can start it up and see the historical data but it doesn't update in real time any more. I get this error message: "Downloads are not enabled. Your current service package does not support this function. Select Help >> Purchase to upgrade your package."This is common mistake. Don't use "Data services" or "Historical data" download. Just start sierrachartfeed.exe and select "Open intraday file" from menu, as is described in my 'howto'. |
|
|
|
|
Yes, mtgox websocket interface is still down, so you have to use -w parameter. Delay is definitely under 30 seconds, it is probably between 5-10 seconds (polling lags between SC-bitcoincharts-mtgox).
Bitcoincharts isn't using mtgox's websocket but older polling interface, so it works most of the time.
|
|
|
|
How about that bad luck on Slush's pool today!
Are you celebrating 2 minutes blocks in the same way as hating the long rounds?  |
|
|
|
Anyone else having problems connecting?
And when it's connected, doing work, getting disconnected?
I restarted balancer daemon at this time. Should work since this restart. |
|
|
|
i have compared the numbers. my normally reward is .01, so i would mention if the counter changes. now, everything is back to normal and it wouldn't be that tragic to loose .3 btc. i just wanted to report, there's maybe a problem.
Reward calculation works without any problem, there is just small latency between time when block is 'confirmed' on stats page and writing block reward to confirmed rewards... |
|
|
|
What's the format for a domain or IP range?
For example can I enter *.pool.provider.net ?
No, I cannot do DNS resolve for every incoming IP (and definitely not in time of DDoS  ). Please use domain/dyndns or static IP. Subnets are not yet supported. |
|
|
|
Random question: Did anyone think to take dynamic IP addresses into account when putting together this whitelist? Having your IP address change and then suddenly having your connection refused kinda sucks. In actuality, there's better ways of mitigating against DDoS attacks than creating a whitelist. However, some of these ways would end up adding some overhead so I can see why you did what you did. Still, when my miners go blank because of my dynamic IP address, that's indication that some other method needs to be thought of.
As already mentioned, you can use domain/dyndns solution, pool is resolving actual IP. Subnets/masks are not supported yet. However whitelist is not enabled by default, so don't worry that you'll lose some shares in normal run. |
|
|
|
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 know about "too many connections" and I'm solving that, but the rest might be normal network issue on the route... |
|
|
|
on the statistics page we only go back so far...is it possible for me to see the stats for 3-4 weeks somewhere?
Try ?history=1000 as argument of stats page... |
|
|
|
on an update, the blocks are being confirmed as we speak, rewards are updating, albeit slowly Blocks are processed once per hour, so small delay is expected. |
|
|
|
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. The change to support rolling ntime is a one line patch to bitcoind.
It goes little complicated if you think about cheating users. |
|
|
|
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 . 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... |
|
|
|
This is important for CPU miners, since their payout is very small. All major pools (deepbit, btcguid, slush) should switch to pay in full.
bitcoind used on my pool has some major custom changes, so it is not just about "download&install". I'm moving my patches to .23 in those days, but I have to be absolutely sure that it doesn't break anything... |
|
|
|
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. |
|
|
|
|
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.
|
|
|
|
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... |
|
|
|
That's why I'm talking that I failed in description for *average* user :-). |
|
|
|
Then which info is determined by the pool server and which info is up to the mining software to generate?
mining software - nonce and (in some cases) ntime pool - everything else merkle root - hash done from transactions included in blocks. Because coinbase transaction is unique for pool, then merkle root is different for every pool. That's the reason why your attack won't work. |
|
|
|
|
Show Posts
