[4+ EH] Slush Pool (slushpool.com); Overt AsicBoost; World First Mining Pool

[cablepair]

Hi guys,

we are mining namecoins here, so I thought I would let you know that I contacted mtgox to ask if they would add namecoin support for trading. The guy at helpdesk opened a feature request ticket for me.

https://support.mtgox.com/entries/21098553-add-namecoin

Just go there and click "Me too!".

I like that idea. Maybe that will help bolster them and (hopefully) increase their value.

There's a guy who came up with a webpage that will let you display .bit addresses in a normal browser without any add-ons. I read it somewhere in the forum and tried it out. Works like a charm. This way you could at least have a .bit webpage with whatever service or info and people will be able to view it redirected via that page. Now this might increase the namecoin price. I'd switch to a .bit domain and finally leave my overpriced 1&1 hoster if I knew I am not the only one being able to find my web presence.

its http://www.bitviewer.net

and credit goes to me - I came up with it, kahl just copied what I did and made his own site as a complete copy

 
sorry to spam your thread slush - much love and respect brother but I had to set this straight

[cbeast]

11155    2012-03-12 03:45:29    0:00:03    Processing...    170757    99 confirmations left
11154    2012-03-12 03:45:18    0:31:16    Processing...    170756    98 confirmations left

[slush]

For your information, I just applied patches for supporting BIP 30 (https://en.bitcoin.it/wiki/BIP_0030).

[slush]

11155    2012-03-12 03:45:29    0:00:03    Processing...    170757    99 confirmations left
11154    2012-03-12 03:45:18    0:31:16    Processing...    170756    98 confirmations left

There are four time windows every hour where blocks are processing - at 05, 15, 30 and 45 minute. Block 11154 was found at 45 minute, so it waited to 05 of the next hour. And you reported the issue two minutes before pool started calculating the round :-).

[slush]

Wow, 150% luck over the past 24 hours. I'm buying a lottery ticket this week!

After many strange days, 30 day average finally moved back to 100%...

[disclaimer201]

Wow, 150% luck over the past 24 hours. I'm buying a lottery ticket this week!

After many strange days, 30 day average finally moved back to 100%...

I was starting to wonder if there was some technical problem for the months-long 90something% 30-day average.

[slush]

No, there were just few days with extra bad luck, and because the average is "simple moving", it means that it took 30 days to disappear from the stats. 90day average is currently over 99%, which is pretty fine.

[CheezWiz]

What exactly is the metric for a "100% day"?
1 block per hour?

[digital]

What exactly is the metric for a "100% day"?
1 block per hour?

I think it actually has to do with the CDF value.  I think that if the majority of the blocks found for the day have a cdf of less than 100% than the luck is good.  If the majority is over 100% then the luck is bad.

I could be way off, but that seems right based on all the stats up there...

[tinman951]

What exactly is the metric for a "100% day"?
1 block per hour?

I think it actually has to do with the CDF value.  I think that if the majority of the blocks found for the day have a cdf of less than 100% than the luck is good.  If the majority is over 100% then the luck is bad.

I could be way off, but that seems right based on all the stats up there...

To get 100%:

The actual amount of shares that are mined for that block would equal the difficulty.  So today the difficulty is 1496978; the 100% day would need to have all the blocks of the day having 1496978 shares per block.  It isn't really related to time (correct me if I'm wrong).

I think that when the luck says 100%+ it is a good day.  When it is below 100% it is bad.  See slush's stats page http://mining.bitcoin.cz/stats/

[slush]

tinman951 is right, pool luck is calculated from block shares and current block's difficulty. >100% means that pool is more lucky than it should be in long term average, <100% is the oposite. Short term luck vary a lot, usually in tens of percents to both directions, but long term pool luck (30day or similar) tends to be at 100%, which is expected.

[organofcorti]

What exactly is the metric for a "100% day"?
1 block per hour?

I think it actually has to do with the CDF value.  I think that if the majority of the blocks found for the day have a cdf of less than 100% than the luck is good.  If the majority is over 100% then the luck is bad.

I could be way off, but that seems right based on all the stats up there...

The cdf can't be over 100%

[digital]

Yeah, after I looked a little closer, I figured out that if the cdf is under 63% for a lot of blocks then the luck is good, if it's over 63% for a lot of blocks then the luck is bad...

[stoppots]

Hi folks,

I'm wondering why I'm seeing severely reduced performance from my 5-GPU miner when connecting to this pool?  I get a constant 1650MH/s reported by Diablo when I'm on DeepBit (although DeepBit reports slightly less) but anywhere from 700-1300 on Slush, with a current 10-round hashrate of only 1161 (that's confirmed by submitted shares as well as Diablo reported hashrate).  LOTS of fluctuation in hashing speed, peaking well below what I know the miner can do (and no, it's not stales, which are currently ~0.3%).  If it helps my username is the same over there as here; PM me if you need more info than that.

Thanks!

Wat would cause my hashrate being reported by the pool to be over a 1/3 less than the total Mhash/sec shown within my miner for the last
1 1/2hrs of a 3hr round?

But then when the new block started my hashrate was being reported to be the same as wat my miner was showing plus 2-4 Mh/s more.

[slush]

I'm aware of issue with processing blocks and payouts, I'll fix it within few hours..

Edit: It's fixed now, all pending payouts were sent.

[MrTeal]

I'm wondering if someone can help me connect to Slush's pool through Tor. I have the Tor client set up and running, and am able to download the blockchain in the client by setting the client to use a sock4 proxy. However, I'm having no luck with setting up GUIMiner to connect. I get a "Problems communicating with bitcoin RPC" error when trying to connect to host pool57wkuu5yuhzb.onion on port 8332. Are those the correct settings, and do I have to edit some kind of config file to set guiminer to use a socks proxy?

[malevolent]

I'm wondering if someone can help me connect to Slush's pool through Tor. I have the Tor client set up and running, and am able to download the blockchain in the client by setting the client to use a sock4 proxy. However, I'm having no luck with setting up GUIMiner to connect. I get a "Problems communicating with bitcoin RPC" error when trying to connect to host pool57wkuu5yuhzb.onion on port 8332. Are those the correct settings, and do I have to edit some kind of config file to set guiminer to use a socks proxy?

No idea but are you using poclbm or other miner?

BTW. Why did slush go down just now?

EDIT: ok, it is up running again.

[MrTeal]

I'm wondering if someone can help me connect to Slush's pool through Tor. I have the Tor client set up and running, and am able to download the blockchain in the client by setting the client to use a sock4 proxy. However, I'm having no luck with setting up GUIMiner to connect. I get a "Problems communicating with bitcoin RPC" error when trying to connect to host pool57wkuu5yuhzb.onion on port 8332. Are those the correct settings, and do I have to edit some kind of config file to set guiminer to use a socks proxy?

No idea but are you using poclbm or other miner?

BTW. Why did slush go down just now?

EDIT: ok, it is up running again.

It's using poclbm, and is the Feb update to Guiminer.

edit: my poclbm.ini file is

{
    "profiles": [
        {
            "username": "XXXXX",
            "balance_auth_token": "",
            "name": "Default",
            "hostname": "pool57wkuu5yuhzb.onion",
            "external_path": "",
            "affinity_mask": 1,
            "flags": "",
            "autostart": false,
            "device": 0,
            "password": "XXXX",
            "port": "8332"
        }
    ],
    "bitcoin_executable": "C:\\Program Files\\Bitcoin\\bitcoin.exe",
    "show_console": false,
    "show_summary": true,
    "show_opencl_warning": true,
    "console_max_lines": 5000,
    "start_minimized": false,
    "window_position": [
        882,
        567,
        845,
        256
    ]
}

[slush]

BTW. Why did slush go down just now?
EDIT: ok, it is up running again.

There was middle-sized coordinated attack against the pool. It took me few minutes to locate source of flooding, so pool was down for a moment. I'm sorry for connection issues.

[slush]

I'm wondering if someone can help me connect to Slush's pool through Tor. I have the Tor client set up and running, and am able to download the blockchain in the client by setting the client to use a sock4 proxy. However, I'm having no luck with setting up GUIMiner to connect. I get a "Problems communicating with bitcoin RPC" error when trying to connect to host pool57wkuu5yuhzb.onion on port 8332. Are those the correct settings, and do I have to edit some kind of config file to set guiminer to use a socks proxy?

If GUIminer already included latest poclbm, which is optimizing mining over Tor, then everything what you need is to use host "pool57wkuu5yuhzb.onion" and configure poclbm to use proxy on 127.0.0.1:9050 (local Tor socks proxy).