Author

Topic: [4+ EH] Slush Pool (slushpool.com); Overt AsicBoost; World First Mining Pool - page 869. (Read 4382653 times)

legendary
Activity: 1386
Merit: 1097
77%?!  And here I am getting happy when users on Stratum have speed exceeding 50% (which only happens once in a blue moon).

LOL, I'm being pretty aggressive in Stratum propagation. Getwork users have pretty annoying message on website profile, thankfully lot of them really update after they noticed it.
hero member
Activity: 622
Merit: 500
www.cryptobetfair.com
for all of you that think namecoins are worthless, i would love to have them, use   NATBojEf4QC5kgyYc2jNvJ8Sq484UpqgYB  as your deposit address in the pool website.  No sense in them going to waste.

Why didnt i think of that...

lol

Itll help us solve more blocks too
legendary
Activity: 1750
Merit: 1007
I recenty switched from api.bitcoin.cz:8332 to stratum.bitcoin.cz:3333 using cgminer
and noticed that namecoin reward dropped to "none". Coincidence?

77% of pool hashrate are already over stratum, which means that only 23% of miners are mining for NMC. That means namecoin reward are going to be lower and loweer...

77%?!  And here I am getting happy when users on Stratum have speed exceeding 50% (which only happens once in a blue moon).
hero member
Activity: 490
Merit: 500
for all of you that think namecoins are worthless, i would love to have them, use   NATBojEf4QC5kgyYc2jNvJ8Sq484UpqgYB  as your deposit address in the pool website.  No sense in them going to waste.

Why didnt i think of that...

lol
hero member
Activity: 622
Merit: 500
www.cryptobetfair.com
for all of you that think namecoins are worthless, i would love to have them, use   NATBojEf4QC5kgyYc2jNvJ8Sq484UpqgYB  as your deposit address in the pool website.  No sense in them going to waste.
legendary
Activity: 1386
Merit: 1097
so wouldn't it be better (from the miner's point of view) to stay on getwork rather than switching to stratum? NMC is maybe not much value, but probably more than tx fees, isn't it?

Tx fees have much higher value than collected namecoins. I don't think there's any motivation to stay on getwork. I'm also going to switch down getwork interface in few months, because stratum infrastructure is already pretty mature and there's no technical reason to keep getwork alive.
newbie
Activity: 8
Merit: 0
77% of pool hashrate are already over stratum, which means that only 23% of miners are mining for NMC. That means namecoin reward are going to be lower and loweer...

so wouldn't it be better (from the miner's point of view) to stay on getwork rather than switching to stratum? NMC is maybe not much value, but probably more than tx fees, isn't it?
legendary
Activity: 1386
Merit: 1097
I recenty switched from api.bitcoin.cz:8332 to stratum.bitcoin.cz:3333 using cgminer
and noticed that namecoin reward dropped to "none". Coincidence?

77% of pool hashrate are already over stratum, which means that only 23% of miners are mining for NMC. That means namecoin reward are going to be lower and loweer...
legendary
Activity: 1386
Merit: 1097
But i think the mining proxy will connect to your pool with one worker account then, dont it?

No, it proxies usernames as well.

Quote
Cant you just raise the allowed connections to 25? (-;

There's really no reason, 20+ workers is already pretty big operation and using Stratum proxy is logical step. It optimizes network usage.
sr. member
Activity: 266
Merit: 250
The first 20 Miners connect to the pool correctly with stratum, the last two does not!

There's firewall rule to not allow more than 20 connections from one subnet. Please install mining proxy (http://mining.bitcoin.cz/mining-proxy-howto), it will take 5 minutes and you can add as many machines to your mining operation as you want.

Thank you Slush.
But i think the mining proxy will connect to your pool with one worker account then, dont it?
If so thats bad, because i want to use me 22 units seperate because of statistics for every units.
Cant you just raise the allowed connections to 25? (-;

Reagards
Daniel
legendary
Activity: 1540
Merit: 1001
Oh that's disappointing Sad. So as a miner who also wants to support & collect namecoins I need to switch to another pool? Is there any chance Stratum can support merged mining?

Maybe I'll implement merged mining again, but not in any near future. AFAIK there's no Stratum powered pool which do NMC merged mining.

I'm pretty sure bitminter does.

M
legendary
Activity: 1386
Merit: 1097
Oh that's disappointing Sad. So as a miner who also wants to support & collect namecoins I need to switch to another pool? Is there any chance Stratum can support merged mining?

Maybe I'll implement merged mining again, but not in any near future. AFAIK there's no Stratum powered pool which do NMC merged mining.
newbie
Activity: 36
Merit: 0
Hey, so I recently switched over to Stratum mining. My rejects have gone down from 1% to 0.1% but it seems NMC mining is broken. Before I'd get ~0.02 NMC almost every round (no reward only once every 10-20 rounds); now, half of the rounds give me "none" NMC. Any ideas? Or is it just a crazy string of coincidences?

It is just coincidence. As Stratum miner, you still collects namecoins as on getwork. Just the pool namecoin hashrate is going down with higher % of stratum miners, because stratum backend doesn't have merged mining.

Oh that's disappointing Sad. So as a miner who also wants to support & collect namecoins I need to switch to another pool? Is there any chance Stratum can support merged mining?
legendary
Activity: 1386
Merit: 1097
The first 20 Miners connect to the pool correctly with stratum, the last two does not!

There's firewall rule to not allow more than 20 connections from one subnet. Please install mining proxy (http://mining.bitcoin.cz/mining-proxy-howto), it will take 5 minutes and you can add as many machines to your mining operation as you want.
sr. member
Activity: 266
Merit: 250
Hey my Pool-Friends!

I have a problem.
Ive got 22 Miners worers which are mining wirg bfgminer 2.9.1.
The have all the same config except the user (this is bitdaniel.01 till bitdaniel.21).

The first 20 Miners connect to the pool correctly with stratum, the last two does not!

Sometimes the last 10 dont connect via Stratum.

Address is stratum+tcp://stratum.bitcoin.cz:3333

Regards
Daniel
legendary
Activity: 1386
Merit: 1097
I'm sorry for short downtime of pool in recent 10 minutes. It was because of failed update, now is pool fully operating again.
newbie
Activity: 34
Merit: 0
Actually, you don't need to care about hashrate *approximation* provided by the pool. It doesn't affect your income, it's just fancy feature, which is inaccurate by design.
OK, many thanks... BTW, i read https://bitcointalksearch.org/topic/m.50002 before asking, but i don't undestand fully... as you can see, my worker connected 24/7...
legendary
Activity: 1386
Merit: 1097
1) if i split my worker to 10 workers - each 500Mh/s, will it make the accepted shares more stable ?

No, because your share submission rate will be still the same.

Quote
2) what will happened in the April when i will have worker 50 Gh/s ? should i think to split it to 100 workers each 500 Mh/s ?

no

Quote
what speed is optimal for the pool now ?

More the better :-).

ACtually, you don't need to care about hashrate *approximation* provided by the pool. It doesn't affect your income, it's just fancy feature, which is inaccurate by design.
newbie
Activity: 34
Merit: 0
BUT, observed that when the round is over and a new started -  for about the first 5-10 minutes, shows the performance drop to 4000-4500 Gh/s and later, after the period - shows again about 5200-5400.

"* The calculation is based on the number of shares so far, which may not be accurate for slow workers."

I should add: "it is inaccurate on the beginning of the round also for fast workers".

1) if i split my worker to 10 workers - each 500Mh/s, will it make the accepted shares more stable ? 2) what will happened in the April when i will have worker 50 Gh/s ? should i think to split it to 100 workers each 500 Mh/s ?

which speed is optimal for the pool now ?
legendary
Activity: 1386
Merit: 1097
The problem is the target - when I connect to the pool using getwork protocol, the miner reports current target as:
Target = 00000000ffffffffffffffffffffffffffffffffffffffffffffffffffffff
but when I use the Stratum proxy, the miner reports truncated target:
Target = 00000000ffff00000000000000000000000000000000000000000000000000

Yes, I know there's some miner who has such problem. The easier solution is just to rewrite target in the proxy to 00000000fff...fffff . Then it should work good enough.

Of course the cleanest solution is to fix that miner.

Quote
My question for Slush's Stratum proxy therefore is - why is the pool returning full (untruncated) target in "getwork" response, but Stratum proxy is returning different target (truncated) in "getwork" response. Is this possible to fix, so that my miner does not see any difference, whether connecting to the pool directly, or via the proxy?

To be honest, that "full" target used by getwork pools was my mistake introduced two years ago, which everybody copy&pasted into their pool implementations. Real diff1 is 00000000ffff00000000000000000000000000000000000000000000000000, which I fixed in Stratum protocol. Fortunately normal getwork miners works with this without a problem, except your one...
Jump to: