[40+ PH] SlushPool (slushpool.com); World's First Mining Pool

[slush]

New version 1.5.1 does not work for me . I use diablominer and old proxy 1.2.0 ...

Can you be a bit more specific? Any error message, screenhot? I'll fix it... I'm bit surprised, because I didn't change mining core itself.

[1475180643]

1475180643

[1475180643]

1475180643

[1475180643]

1475180643

[1475180643]

1475180643

[Bitcoin.Greece]

New version 1.5.1 does not work for me . I use diablominer and old proxy 1.2.0 ...

Can you be a bit more specific? Any error message, screenhot? I'll fix it... I'm bit surprised, because I didn't change mining core itself.

You have email with screenshots
If you need more info let me know

[slush]

I just released stratum proxy 1.5.2, which fixes problems with Diablo miner in Windows build.
1.5.2 also works with RPCminer, proxy just must be started with --old-target parameter!

[Bitcoin.Greece]

I just released stratum proxy 1.5.2, which fixes problems with Diablo miner in Windows build.
1.5.2 also works with RPCminer, proxy just must be started with --old-target parameter!

Working perfectly now ... Thanks

[slush]

In recent days I've been working hardly on vardiff support for the pool. Today I finished and tested basic framework, which will run Variable Difficulty engine for Stratum pool in near future and I'd like to run it on production server in this minimal implementation just to offer user-defined difficulty for miners. Avalon started shipping their ASIC miners already, so user-defined difficulty is definitely useful future and it is awaited by many pool users.

I'd like to test user-defined difficulty in closed beta with few interested people with some powerful rigs (at least 8 GHash/s). If you have such rig and you want to help me test this feature, please PM me. I'll give some of you access to testing website/stratum API. All shares mined against this interface will be credited as usual + some small bonus. Thank you!

[slush]

Getwork interface has been down for few minutes because of datacenter maintenance. It is working again, sorry for troubles.

[slush]

Bitcoin network seems to be overflooded a bit, some today's pool payouts are still unconfirmed, hopefully they'll confirm soon. I just set up tx fees for pool payouts, so next payouts should go thru easily.

[Mike Hearn]

The reason transactions are failing to confirm fast is because we hit the soft block size limit.

Slush, another way to help is not only to try and outbid others with your payout transactions, it's to set your own block size limit to something like 1mb instead of 250kb:

https://bitcointalk.org/index.php?topic=149668.0

You can also try excluding SatoshiDice transactions to free up space. With bitcoin 0.8 block propagation should be fast even with larger blocks, so this would hopefully not have much effect on your orphan rate.

[slush]

I changed maxblocksize already, but I'm waiting with bitcoind restart to tomorrow when i'll do pool update about user-defined difficulty, to keep downtime to minimum.

[disclaimer201]

I'm waiting for a 1st confirmation of a 5 btc transaction (not pool related) for over 8 hours now. So, the issue is clearly with the btc network.

[slush]

Testing of new version is going well, I'll release it in few hours!

[server]

Testing of new version is going well, I'll release it in few hours!

Thanks !!

Would it be possible to show some proxy performance stats in future versions ? (and optional .log the current "INFO" ?)

[Bitcoin.Greece]

What is the "Suggested difficulty" for the miners .... ?

[slush]

What is the "Suggested difficulty" for the miners .... ?

It gives a possibility to slow down submission rate for fast mining rigs (in terms of GHashes or more). It improves network efficiency, lower communication overhead and lower pool load.

It's still just an option on website, it's not working yet. I'm working on release right now and I'll do full announcement soon...

[qbits]

Slush, great job introducing "your_shares" column in the statistics. When will this field be included in Json files?
Thx.

[slush]

Slush, great job introducing "your_shares" column in the statistics. When will this field be included in Json files?
Thx.

Actually I just forget to update json format . Very soon...

[slush]

User-defined (choosable) difficulty released!

I just made probably the biggest update of Stratum pool since stratum mining has been introduced. Now all Stratum miners can define their own difficulty for each worker. Until now, miners were generating difficulty-1 shares and they had been credited by one share in pool database. Now miners can work on higher difficulty, say 5, which means that it is 5x harder to find a share, but pool will credit the worker for five shares in database for every share submission.

This feature is aimed to ASIC miners and big mining operations, because it drastically optimized communication overhead. You can have 1Thash/s miner connected to the pool and network communication will consume less than 10kB/minute...

Downside of this feature is that it slightly increases variance in share submissions, which may increase variance in block rewards. However, it definitely doesn't affect overall mining income in longer timeframe like one day. It is still important to don't set the difficulty too high. Thanks to my calculations, having 10-20 share submissions per minute will give you very low variance.

How to change worker difficulty:
There's a new option on worker edit form (web profile -> edit worker). You have two options. First is to put difficulty to input box manually. This is aimed mostly to advanced users, who want fine-tune their settings. For most of others there's simple dropdown list. Just select hashrate range which fits your mining rig and pool automatically converts your selection to appropriate difficulty number. Once you change the settings, pool will apply this difficulty in two minutes even on existing stratum connections (no need of miner restart).

If you're using more miners behind stratum mining proxy, then all miners will use the highest difficulty of connected workers. It's not a bug, it's a feature :-). Please consider model case of one very slow (difficulty 1) and one very fast (difficulty 10) miner behind the proxy: the difficulty will be set to 10, which means that the slow one will need quite a long time to generate share. But when it happen (it happen with 10x lower probability than on difficulty 1), the submission will be still credited for 10 shares! For getting stable block reward, the important is the rate of submissions, not *which* miner generated it. Actually I encourage users to use stratum mining proxies if they have more miners on the same location, because it help optimize network overhead (because all miners re-use the single connection).

I'm also sorry that introducing such important feature took me too much time, but I'm currently busy with more Bitcoin projects (like Trezor). I'm still happy that I finished the project before #1 batch of Avalon ASIC miners come to their owners...

P.S. During the update I also changed block size limits on stratum servers (as Gavin and Mike asked me). Pool now creates blocks up to 500kB instead of previous limit of 250kB to help the network with increased traffic.

[Evan]

Slush I am having a problem with the pool with 1 of my cards:

2013-03-08 15:58:56: Listener for "Default": api2.bitcoin.cz:8332 08/03/2013 15:58:56, Verification failed, check hardware! (0:0:Redwood, 854ebb5a)
2013-03-08 16:01:13: Listener for "Default": api2.bitcoin.cz:8332 08/03/2013 16:01:13, Verification failed, check hardware! (0:0:Redwood, 3183ec2b)
2013-03-08 16:02:30: Listener for "Default": api2.bitcoin.cz:8332 08/03/2013 16:02:30, Verification failed, check hardware! (0:0:Redwood, 47e5dd77)
2013-03-08 16:04:40: Listener for "Default": api2.bitcoin.cz:8332 08/03/2013 16:04:40, Verification failed, check hardware! (0:0:Redwood, 4fd58290)
2013-03-08 16:08:56: Listener for "Default": api2.bitcoin.cz:8332 08/03/2013 16:08:56, Verification failed, check hardware! (0:0:Redwood, 2c2c4891)
2013-03-08 16:10:15: Listener for "Default": api2.bitcoin.cz:8332 08/03/2013 16:10:15, Verification failed, check hardware! (0:0:Redwood, d203069d)
2013-03-08 16:10:26: Listener for "Default": api2.bitcoin.cz:8332 08/03/2013 16:10:26, Verification failed, check hardware! (0:0:Redwood, f78cf4f2)
2013-03-08 16:11:19: Listener for "Default": api2.bitcoin.cz:8332 08/03/2013 16:11:19, Verification failed, check hardware! (0:0:Redwood, f7073cc2)
2013-03-08 16:13:01: Listener for "Default": api2.bitcoin.cz:8332 08/03/2013 16:13:01, Verification failed, check hardware! (0:0:Redwood, c935d101)
2013-03-08 16:13:36: Listener for "Default": api2.bitcoin.cz:8332 08/03/2013 16:13:36, Verification failed, check hardware! (0:0:Redwood, ca7ae314)
2013-03-08 16:15:14: Listener for "Default": api2.bitcoin.cz:8332 08/03/2013 16:15:14, Verification failed, check hardware! (0:0:Redwood, a14357d9)
2013-03-08 16:16:40: Listener for "Default": api2.bitcoin.cz:8332 08/03/2013 16:16:40, Verification failed, check hardware! (0:0:Redwood, ea73bd8d)
2013-03-08 16:16:49: Listener for "Default": api2.bitcoin.cz:8332 08/03/2013 16:16:49, Verification failed, check hardware! (0:0:Redwood, ea42a3fc)
2013-03-08 16:16:59: Listener for "Default": api2.bitcoin.cz:8332 08/03/2013 16:16:59, Verification failed, check hardware! (0:0:Redwood, f9a0ee29)
2013-03-08 16:18:05: Listener for "Default": api2.bitcoin.cz:8332 08/03/2013 16:18:05, Verification failed, check hardware! (0:0:Redwood, 937d93ee)
2013-03-08 16:18:12: Listener for "Default": api2.bitcoin.cz:8332 08/03/2013 16:18:12, Verification failed, check hardware! (0:0:Redwood, c4b25d79)
2013-03-08 16:18:39: Listener for "Default": api2.bitcoin.cz:8332 08/03/2013 16:18:39, Verification failed, check hardware! (0:0:Redwood, 1ca834b8)
2013-03-08 16:19:25: Listener for "Default": api2.bitcoin.cz:8332 08/03/2013 16:19:25, Verification failed, check hardware! (0:0:Redwood, b7ebc3f0)
2013-03-08 16:21:35: Listener for "Default": api2.bitcoin.cz:8332 08/03/2013 16:21:35, Verification failed, check hardware! (0:0:Redwood, 3fdaf310)
2013-03-08 16:21:52: Listener for "Default": api2.bitcoin.cz:8332 08/03/2013 16:21:52, Verification failed, check hardware! (0:0:Redwood, 16865cc7)
2013-03-08 16:25:18: Listener for "Default": api2.bitcoin.cz:8332 08/03/2013 16:25:18, Verification failed, check hardware! (0:0:Redwood, b80e1f9e)
2013-03-08 16:25:26: Listener for "Default": api2.bitcoin.cz:8332 08/03/2013 16:25:26, Verification failed, check hardware! (0:0:Redwood, d19a1157)
2013-03-08 16:26:59: Listener for "Default": api2.bitcoin.cz:8332 08/03/2013 16:26:59, Verification failed, check hardware! (0:0:Redwood, 83ecf93a)
2013-03-08 16:28:58: Listener for "Default": api2.bitcoin.cz:8332 08/03/2013 16:28:58, Verification failed, check hardware! (0:0:Redwood, 6ef74650)
2013-03-08 16:30:16: Listener for "Default": api2.bitcoin.cz:8332 08/03/2013 16:30:16, Verification failed, check hardware! (0:0:Redwood, 9d343a7e)
2013-03-08 16:30:31: Listener for "Default": api2.bitcoin.cz:8332 08/03/2013 16:30:31, Verification failed, check hardware! (0:0:Redwood, a32b1614)
2013-03-08 16:31:09: Listener for "Default": api2.bitcoin.cz:8332 08/03/2013 16:31:09, Verification failed, check hardware! (0:0:Redwood, 0c633d11)
2013-03-08 16:31:48: Listener for "Default": api2.bitcoin.cz:8332 08/03/2013 16:31:48, Verification failed, check hardware! (0:0:Redwood, 05e3be0a)
2013-03-08 16:31:49: Listener for "Default": api2.bitcoin.cz:8332 08/03/2013 16:31:49, Verification failed, check hardware! (0:0:Redwood, 83a7e1c6)

What is this?

[slush]

Slush I am having a problem with the pool with 1 of my cards:

2013-03-08 15:58:56: Listener for "Default": api2.bitcoin.cz:8332 08/03/2013 15:58:56, Verification failed, check hardware! (0:0:Redwood, 854ebb5a)
2013-03-08 16:01:13: Listener for "Default": api2.bitcoin.cz:8332 08/03/2013 16:01:13, Verification failed, check hardware! (0:0:Redwood, 3183ec2b)

This is not related to the pool, it usually indicates some hardware error, because gpu generates invalid shares. Or it may be a bug in GPU drivers. Is it overclocked? Is temperature OK? Did you tried to restart your machine?

[laughingbear]

Mine was shut down too. I had to kill the proxy, and use guiminer to get it back online