Topic: [OLD] Eligius: ASIC, no registration, no fee CPPSRB BTC + 105% PPS NMC, 877 # - page 120. (Read 458370 times)

Sounds like CPPSRB doing what it is supposed to during an unlucky round: shares not in the top 25 BTC of the share log are shelved.

Yo, what's going on?

I'm hashing strong but the slope peaked and I'm not getting any coins.

EDIT: phone induced typo

As of right now, this would probably be for the best, as it is the least bandwidth intense.

Alright..so if I understand correctly you recommend stratum+tcp for the time being?

Thanks for the update. 

Greetings Miners!

After some discussion and pouring over the data, it has come to my attention that the Eligius pool is using a LOT of bandwidth.  So, in an effort to mitigate this somewhat, I'm going to be making some minor changes.

First, I've temporarily disabled secure stratum (mining.get_transactions) to save a bit.  We were outputting anywhere from 50-125MB of data per stratum work restart (every 55 seconds), and thats pretty crazy.

Second, and this is more long term, I'm going to be giving each mining protocol it's own host name so that I can associate each with it's own IP address, if needed.

So, I'm going to shoot for roughly two weeks from now (weekend of June 1st) to implement the following:

• Secure and Blind Stratum mining on stratum+tcp://stratum.mining.eligius.st:3334 (or 3333)
• Getwork mining on http://mining.eligius.st:8337 will continue, and a new hostname, http://getwork.mining.eligius.st:8337 will be added for completeness.  (I will also include the X-Stratum header to direct any stratum supporting getwork miners to the stratum protocol)
• GBT (getblocktemplate/decentralized) mining on it's own hostname and port, separate from getwork, at http://gbt.mining.eligius.st:9337 (note the port!)
• The existing default host, mining.eligius.st:8337, will continue to work and provide getwork only.  Port 3334 of the same will work for some time, however I will be notifying those miners I can contact using that port to switch to the new host as soon as possible, and eventually, if needed, shut down 3334 on that host.

These changes are not yet in full effect, however the new hostnames and ports already exist so you can start updating your miner's configurations now.
The major changes will take effect on or about the weekend of June 1, 2013.

Currently GBT mining accounts for the majority of the pool's bandwidth usage.  While I agree that GBT has a future, it definitely needs some tweaks to make it more viable for pooled mining long term.  With block sizes near 1MB we're using near 1TB of bandwidth per day serving miners block templates, which is pretty crazy.  GBT currently lacks a few things that would make it more viable, such as caching transaction data, binary protocol (not ASCII-hex), etc, so that bandwidth usage is closer to that of other protocols.  GBT currently supports gzip compression, however, which will make it even more useful once there is some caching in place.

Secure stratum suffers from similar drawbacks, and even more so than GBT because the updates are more frequent, and there is no compression at all.  So, it uses huge bursts of bandwidth every minute or so.

Both ideals are great for bitcoin I believe, however some more client-side verification of the data (against a local bitcoind, or manual inspection even) seems like a prerequisite to keeping the protocols as the default for mining, as there is no real difference to the miner at this point in time in which protocol they choose aside from bandwidth usage (lowest currently being blind-stratum).

So, I'm not disabling any of the protocols, I just need to be able to delegate resources more accurately, which requires partitioning the protocols to their own hostnames.

I will do my best to make sure no miner is cut off from these changes by making the existing mining.eligius.st:8337/3334 address support both getwork and stratum for as long as possible, but, please update your miner configurations as soon as possible to reflect the new hostnames above, depending on your preference of protocol.

Secure stratum will remain disabled until these changes are in full effect.  I will keep an eye on the adoption of the new hostnames and if it seems too many miners will be negatively effected by a change, I will revisit this.

Any questions/comments/concerns, please feel free to reply or contact me otherwise.

Thank you again for flying Eligius Mining Airlines!

-wk

I got my ASICMiner blades mining in Eligius through stratum proxy. No problems.

Averaging 12.2 per blade now that I have enough hours to measure, so slightly above the advertised 10-12 GH/s per blade.

Any idea what the issue was with the pool between (05-17-2013) 12:50-20:30 ?

I looked at every account (highest hash rate being #1) 1-50 and also hash rates 500-600MH/s(just a random range pick). And 2 in about 5 have the same dip in hash rate(I only used hashers with a normally steady hash rate for this comparison). The top 10(IIRC) hashers showed no dip in hash rate.  My 3 Hour rate dropped from ~850MH/s to ~230MH/s at the trough(17:40).

Also as of the moment. I'm showing avg:850MH/s Client Side(Just restated about 1.5Hrs ago with a older version of BFG to try and see it it helps). and a 744MH/s 22 Minute average on the website/status page side.

ty for your report

At current difficulties I reach the payout queue (0.16777216 BTC, a.k.a. 100 "tonal bitcoins") in about 5 days. Depending on luck and speed of block confirmation I'll then wait another day or so to actually get my payout.

how much you gain per day ? I don't understand very well the reward system on eligius

I'm not sure what feedback you're looking for, but I'm only running about 520 Mh/sec and Eligius has been good to me. I've maintained a very steady hash rate since the recent problems have been resolved and I get my payouts like I should.

Any feedback by babies miners(~600mh/s) on this pool ?

Thanks

Apparently you have to provide some password. Guess providing 'x' works...likely anything other than that will work too.

Since your pool doesn't required password (I read it on the faq)

"bfgminer -o mining.eligius.st:8337 -u YourAddress -p x"

what's represent "-p x" ?

I'm missing something ?

Thanks in advance

You can use the stratum proxy with Eligius. Also I believe bfgminer has support coming for the ASIC miner blades which would eliminate the need for the proxy.

-Wk

I intend to favour Eligius if it gives me similar performance as the rest. I got 2 ASICMiner blades in the fixed price auction (you can see my nick there https://bitcointalksearch.org/topic/asicminer-fixed-price-auction-50-block-erupter-blades-everyone-won-see-op-201753 )

AFAICS I will need to run a Stratum proxy because they only support the older getawork protocol and they would be inefficient if run directly. I only found it documented here:

http://mining.bitcoin.cz/mining-proxy-howto for Slush.  

Any ideas? Maybe Eloipool? https://bitcointalksearch.org/topic/ann-eloipool-fast-python3-pool-server-software-gbtstratumdyntargetproxy-61731

I have no experience about this. If someone wrote a decent guide, maybe we can get some of these ASICMiner blades that are actually shipping in volume now to point here at Eligius.

Honestly, it doesn't matter. Obviously the added hash power overall will help the pool, and could help the pool get lucky enough to get to paying some SMPPS extra credit. But it doesn't directly help you with your SS or EC.

But please do point your miners in any case! The more hash power the lower the variance the better things are for everyone!

-wk

I have a related question, since you said "unlikely" instead of "no": will it change things if I point more mining rigs to this same address?

I use different addresses to keep a clearer record of mining performance. I expect a couple of ASIC blades and I haven't decided where to point them yet.