[1200 TH] EMC: 0 Fee DGM. Anonymous PPS. US & EU servers. No Registration!

[stoppots]

Very impressed with the many features and feedback eclipse offers. Keep up the good work.

[jjshabadoo]

I'd like to see a 24 hour, 7 day and one month hash rate average per worker. This was my favorite feature of yourbtc.net.

Even if not for each individual worker, just for your total account.

Hash rate and maybe BTC generated per worker also with same parameters(24hrs 7days 1 month)also.

awesome pool man. I'm up to about 10 GH/s with two accounts so far and looking to add more.

[Inaba]

Jjjim - Yes, I have 35 workers, so I feel your pain.  I will try to get that fixed asap.  For some reason the <div> tag is causing the cell to wrap... not sure why.

stoppots - Thanks!  If there's anything you'd like to see, let me know!

jjsabadoo - I will be adding some of that to the new stats page I am trying to put together, at least as an overall.  I will see what I can do about doing stuff for individual workers, too.

[Inaba]

My Workers should no long be wrapping the text.

[jjiimm_64]

My Workers should no long be wrapping the text.

works....  thank you, thank you, thank you....

question about the stale number.

my top row sorted by since reset is.  62925 (0)  5779 (36)    1276554 (6470)

if the number in parans are stales, how is it possible to have more stales since block found then since reset?

[Inaba]

Reset stales are not really active yet, since i need to restart the getwork server to make it live and I have not done that yet.  Additionally, resetting them is not possible at the moment due to the way hashrate is calculated, so I have to recode some stuff to make share resets resettable anyway.

[gnar1ta$]

Inaba, how is the Pay to Script vote handled with pooled mining? I'm assuming the decision is yours?

[Inaba]

I'm sorry I don't understand your question.  What do you mean by Pay to Script?

[gnar1ta$]

https://en.bitcoin.it/wiki/BIP_0016
I'm sure thee is a thread in technical discussion that's way over my head, but Coinlab posted this:

Especially of note  is that Gavin asked miners who agreed with the proposal to add the string “P2SH” in blocks they mine; he will count blocks mined during January to determine how the BitCoin mining community ‘votes’ on this issue. This is an interesting and novel development in BitCoin governance, and we look forward to seeing how this ‘voting’ mechanism evolves.

I was just wondering if it is going in our blocks.

[Inaba]

Ah... hmm... no I don't see that happening by the timeframe he has put forth.  With the way merged mining is handled now, upgrading bitcoind is somewhat complicated and it's not going to happen prior to February most likely.  

I'm also unsure (even though it doesn't affect EMC at the moment) how that would affect how PSJ handles both BTC work generation (and subsequently work submittal) and how that would interact with the merged mining in PSJ.  As I am still moving toward (albeit slowly) a PSJ test roll out, it will also be an issue going forward.  

In either case, it doesn't seem as it will affect end users one way or another as far as mining goes - but it would be a handy change for bitcoin in general.  But the timeframe is just too short.  

[kano]

just add it on the end of the coinbase - 5 extra characters '0x04' and 'P2SH'
(although it could be '0x06' '/P2SH/' the wording isn't really clear )

[Inaba]

But that would imply that the bitcoind would be ready to process those transactions and it wouldn't.  Or do I misunderstand the BIP?

To gracefully upgrade and ensure no long-lasting block-chain split occurs, more than 50% of miners must support full validation of the new transaction type and must switch from the old validation rules to the new rules at the same time.
To judge whether or not more than 50% of hashing power supports this BIP, miners are asked to upgrade their software and put the string "/P2SH/" in the input of the coinbase transaction for blocks that they create.
On February 1, 2012, the block-chain will be examined to determine the number of blocks supporting pay-to-script-hash for the previous 7 days.

Just adding the appearance of support would be counterproductive, to my understanding.  

[gnar1ta$]

I think the appearance of support in the blocks will be the deciding factor on implementing the function.  Your just saying yes I would like this change added by signing P2SH into our blocks. That was my understanding anyway, but like I said, it's a bit over my knowledge level.

[P_Shep]

So an invalid block? What does that mean? An error during the calculation somewhere?

[P_Shep]

Oh, and I'm finding if I click on the number of shares I submitted for a block, I get taken to the login page. If then I login and go back to the block stats and click the # shares it then takes me to the graph.

[Inaba]

An invalid block means we found a block at nearly the same time as another source.  In this case, it seems to be P2Pool.  It happens fairly rarely, but everyone experiences it the more blocks you mine.  More sources validated P2Pools solution than our solution and thus P2Pools was accepted over ours.  

As far as the login thing - does this happen every time or just the first time?

miners are asked to upgrade their software and put the string "/P2SH/" in the input of the coinbase transaction for blocks that they create.

I'm not sure that is the case - it would seem bitcoind needs to be upgraded as well.

I am in support of the feature, but I'm not sure I can support the timeframe required to implementation and testing prior to a live rollout.

[P_Shep]

I see.

The login: I guess it happens the first time each time I login. So in order to access the Shares graph, I have to login twice.

[Inaba]

Hmm... I'm not sure why that is.  I will look into it.

[Inaba]

I have added a new feature:

EMC now supports the use of Yubikeys for two factor authentication.  Activating your Yubikey on EMC is a one time, one way process.  Once it's active, it can not be deactivated.  In addition to your traditional user name and password, you can choose to activate the Yubikey option by putting in an OTP in the Yubikey box under My Account.  Once you do this, you will not be able to disable or otherwise remove your requirement for a Yubikey, and neither will an attacker!  

Additionally, I have enabled the stale share counter under "reset."  Resetting your shares will now also reset your stale count.

[rjk]

I have added a new feature:

EMC now supports the use of Yubikeys for two factor authentication.  Activating your Yubikey on EMC is a one time, one way process.  Once it's active, it can not be deactivated.  In addition to your traditional user name and password, you can choose to activate the Yubikey option by putting in an OTP in the Yubikey box under My Account.  Once you do this, you will not be able to disable or otherwise remove your requirement for a Yubikey, and neither will an attacker! 

Additionally, I have enabled the stale share counter under "reset" but there is currently no way to reset it.  I will be addressing that soon, but I wanted to mention it since I'm sure people will be a little confused as to why they can't reset their stale counts.

This is awesome. This pool just keeps adding sweet features.