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

It does not matter for cumulative return, but in practice - forget about solo mining. No one should mine solo unless you are in control of at least 1% world's hash power. Otherwise it is quite possible you mine your first solo block when block reward will be 12.5 BTC or even 6.25 BTC, or simply put - never

Your NMC address will start with a 'N'. It's not a Bitcoin address that you store namecoins in.
https://bitcointalksearch.org/topic/annnmc-namecoin-wallet-qt-with-integrated-name-registration-v375-236375
Download the namecoin client and create a new one, and then use that.

NMC address cannot start with "1", I believe. You should get it from your NMC client

You need an NMC address, not another BTC address.  If you don't have the NMC client running, you can just use your receive address for NMC from BTC-e/Cryptsy/cex.io

Ok, just to be clear.  The NMC address has to be a different address than the one I'm using for BTC right ?  I got my NMC address from the receive side of Electrum, signed it with the output string from Eligius and verified it with Electrum.  It passes on Electrum but not on Eligius.

My BTC address is 1Aynx4ZsKoGptWb2Z2aweCDJWduiGUj9DS
My NMC address is 1FGe2AqfRnj3c4JYjWL4etoVBtrXWFib4K

I get this message to sign with:

My Eligius - 2014-01-27 22:24:13 UTC - NMC_Address=1FGe2AqfRnj3c4JYjWL4etoVBtrXWFib4K
When I paste the reulting signature in the appropriate box on Eligius, it fails.  Every time.  However, it passes when I verify it with Electrum.

On the Configurable Options page where you set your NMC address, payout threshold, etc you place the NMC address you want. You then copy the text ("My Eligius - 2014-01-27 ...") and paste that into the big message box in the bitcoin-qt client. Select the Bitcoin address you're trying to sign for (IE, the one you're using on Eligius), and click sign message. Then copy and paste the resulting string back into the Eligius website.

Just tried it with chrome, same thing.

I thought I did but the whole thing has me confused now.  I put in my NMC address in the appropriate box, which I assume is different from my BTC mining address.  I copied and pasted the signing message to electrum, signed it and pasted the results in the signature box.  It fails every time.


I used Firefox but I'll try something else.  Thanks.

so I've been doing a lot of reading and trying to decide what to buy to get into mining, and I've been using this website: http://thegenesisblock.com/mining/ to help figure out costs and return... my question is are the statistics on that site calculated based entirely on the assumption of solo mining?

for example if I bought a mining rig off ebay that can do 100 or so GH/s, and get it all setup and running in feb, when I look up the gear in http://genesisblock.com/mining/ it basically says there is no way I'll recover my costs if I start in feb 2014.... but is that only if I'm solo mining?

right now the only pool I want to join is this pool if I get this mining operation going from my basement.

Thanks,
Kurt

Maybe some strange browser? Try it in another one clearing cookies/caches first

Makes sense. And in the interests of honest disclosure, I'm back on Eligus because the other pool I tried out was running my rigs at only about 70% capacity. All sorts of little hops between servers, resubmits, timeouts, and other related weirdness add up.

Eligius: They may pay with a bit of lag, but they pay in full. :-)

As to the BFL person: If you can flash your firmware to 1.2.9 you will get your speed back. I hack those things out the ears, lots of data in these two threads:

Hacking Jallies to 32gh: https://bitcointalksearch.org/topic/hacking-a-bfl-jalapeno-to-32gh-and-beyond-336782

Hacking BFL Single/25's to 50gh:  https://bitcointalksearch.org/topic/hacking-a-bfl-single25-to-48gh-and-beyond-424604

C

Are you sure you selected the correct address to sign with?

I'm hoping someone can help me with merged mining.  I cannot get the signature to pass when I add my nmc address.  I've used multiple programs to sign and verify including mtgox, bitcoin-qt, electrum, and just about every other app out there.  The sig passes on the application but fails on the website and I've even manually typed in every character rather than copy/paste and it still fails.  What am I doing wrong ?

Thanks, that's exactly what I was looking for. I suppose I could have asked if maximum reward is unpaid+everpaid+shelved, which is what seems to be the case.

I understand the general concept, with shares being stored and every time a block is found the most recent 25BTC worth of shares are paid.

Am I correct in my understanding that there are two separate queues, one for the shares and one for payouts? As shares are received, they are added to the share queue and each time a block is found 25BTC worth of shares are removed from the share queue and are are marked as unpaid balance. When your unpaid balance exceeds the minimum threshold, you enter the payout queue which is paid oldest accounts first. If this is the case, why is the payout queue so long (currently 525BTC) if the funds are all available to pay out those shares? Is it just that a portion is held in the offline wallet and to flush the payment queue would take a manual transaction?

Also, is there a place to view the current number and value of shelved shares?

However, note that over the same period, the pool has rewarded over 113 650 BTC, meaning that unpaid shares represent less that 2.5% of the pool earnings.

The unpaid shares accrued since the beginning of 2013 represent less that 2% of the pool earnings since then. And the pool was lucky since november, since, on average, all of the shares accrued since then have been paid.

Yes... And no.

Each time you submit a share, the pool records it in the share log, at it's straight PPS value. When a block is found, 25 BTC worth of shares (starting from the most recent) are paid.

If the pool is unlucky, and it took more shares than average to find the block, some of the shares submitted for that block cannot be paid (since the pool does not have the money to cover them). The pool "remembers" those shares; they are shelved.

If the pool gets lucky, and it took less shares than average to find a block, pool will have some BTC left after paying every share submitted for that block. It will therefore pay whats left to the most recent shelved shares.


However, paying everybody like that in every block would be a problem: First, small miners would only get micropayments in every block; and it would be dust that accumulates in their wallet (and increases their fees when they use the coins). Second, some clients have a bug in which that cannot support a too big amount of outputs per transaction. (Doing payments like that in Eligius would cause more than 5000 output per transaction)

Therefore, Eligius implements a sort of tradeoff. Instead of directly paying the shares when they are found; it internally computes which shares are to be paid, and which shares are not (yet), without actually sending the money to the miner. Instead, it holds onto them until a given amount is accumulated (chosen by the miner), at which time the pool will send the coins.

Therefore, it means that even if the pool were to empty it's payout queue, it does not mean that everybody's shares ever submitted have been paid. It does mean, however, that nobody has accumulated enough rewarded-but-unpaid shares to be paid. (In those cases, the pool sends the block reward to an offline wallet, from which the miners will be paid when the payout queue gets long enough.)


Thus, about the graphs and stats:
The everpaid line is amount of BTC the pool has ever sent to you.
The unpaid+everpaid line is that amount, plus the value of all the shares the pool has rewarded to you, but has not set the actual money yet, because you have not met your treshold. (the unpaid amount is the amount marked in the "unpaid balance" in the table above the graph)
The maximum reward line is the total value of all the shares you ever submitted to the pool, including those it does not have the funds to pay yet.

If the pool gets lucky, "unpaid+everpaid" will get closer to "maximum reward", and may even touch it. However, they would not "meet" at the same time for all users, depending when that user joined. Most recent shelved shares being paid first, the pool would have to be lucky a lot longer to pay all the way back to 2012, when the pool began, than to pay all the shares of somebody who started one month ago.


However, nobody's payment will ever go above "maximum reward": once all your shares have been paid, all the extra coins go to paying other who have to yet been fully paid. Finally even if the pool were to clear it's whole backlog, then it would hold onto the extra coins until less lucky times. (in any case, such event would be extremely unlikely: In the beginning, Eligius suffered from pretty severe bad luck, and thus has accumulated an hefty amount of unpaid shares. According to my calculations, the pool has acumulated over 2800 BTC worth of unpaid shares, which means it would need to find something like 112 blocks RIGHT NOW to pay them all)

Dears,

I've got some questions during my mining for a long while, it would be great if I can get the answer form here.

I have several blades which get connection with Eligius pool via independence miner proxy, and I use the same wallet without separating them into individual worker.
And I made my own SW to calculate my total hashrate from each proxy, however, there is always 10% ~ 20% gap between my calculation and my status in pool.
The bigger hash power I have, comes with the bigger gap.

Is there anyone has same issue as me or is there anything I can do for  improvement?
Thank you.

Check out this thread for more details - sounds like 3 less cores are enabled if you dropped that much.

https://bitcointalksearch.org/topic/bfl-labs-60-ghs-single-tweaking-help-for-monkey-brained-stupid-people-258643

It looks like there were/are several large miners waiting for payout.  Last night when I checked, there was at least one miner waiting for over 30BTC of payout (including one whole block to himself), and several others in the 10+ BTC range. 

Payouts are more random/variable than earnings because every user can set their own payout threshold, which mostly scales up depending on hashrate.  If I were running 100TH then I wouldn't want to be paid out every 0.04 BTC.  But if I were running 60GH then of course 0.04 BTC is a reasonable payout threshold. 

I think most people probably set theirs for every 12-24 hours.  In any case, some of the high rollers have relatively high payout thresholds (which makes perfect sense), and when those are hit then it takes a while to clear them out.

Is that it? I've noticed over the last month or so that although variance on the pool is low, payout variance seems to be all over the place. Granted I'm only a 220gh setup here, but I have seen the payouts being delayed.

Perhaps it's the impact of very large miners?

C