[OLD] Eligius: ASIC, no registration, no fee CPPSRB BTC + 105% PPS NMC, 877 #

[stevang]

I don't understand what you 're saying Luke-Jr? I just don't know what your Roll?? Time or how you call it means. I am just using a mining software and dont know every single code line of it or which exact header it sends.

Can i still use Phoenix with Eligius now? is there a list of accepted mining software?

I am officially confused.

[Luke-Jr]

Can i still use Phoenix with Eligius now? is there a list of accepted mining software?

You can still use all miners with Eligius. This change should only affect those that have broken implementations of the rollntime extension. Phoenix doesn't support this at all. Since it is a helpful feature, I would recommend switching to poclbm if you can get the same hashrate out of it (it's usually better once you find the right settings).

[DiabloD3]

Can i still use Phoenix with Eligius now? is there a list of accepted mining software?

You can still use all miners with Eligius. This change should only affect those that have broken implementations of the rollntime extension. Phoenix doesn't support this at all. Since it is a helpful feature, I would recommend switching to poclbm if you can get the same hashrate out of it (it's usually better once you find the right settings).

Except poclbm is generally slower than DiabloMiner.

[Dargo]

Can i still use Phoenix with Eligius now? is there a list of accepted mining software?

You can still use all miners with Eligius. This change should only affect those that have broken implementations of the rollntime extension. Phoenix doesn't support this at all. Since it is a helpful feature, I would recommend switching to poclbm if you can get the same hashrate out of it (it's usually better once you find the right settings).

So if we use phoenix, we are missing out on a useful feature, but there won't be any hit to mining efficiency, is that correct? I'll try to figure this out on my own, but if anyone can summarize the utility of this useful feature, that would be most appreciated. I checked the wiki, but there was just enough technical jargon to make me fall shy of understanding.

[Luke-Jr]

So if we use phoenix, we are missing out on a useful feature, but there won't be any hit to mining efficiency, is that correct?

rollntime improves efficiency drastically (ie, like 0.8 accept/getwork to over 5 accept/getwork for me). Phoenix doesn't support it, no matter what a pool does.

[twmz]

Can i still use Phoenix with Eligius now? is there a list of accepted mining software?

You can still use all miners with Eligius. This change should only affect those that have broken implementations of the rollntime extension. Phoenix doesn't support this at all. Since it is a helpful feature, I would recommend switching to poclbm if you can get the same hashrate out of it (it's usually better once you find the right settings).

So if we use phoenix, we are missing out on a useful feature, but there won't be any hit to mining efficiency, is that correct? I'll try to figure this out on my own, but if anyone can summarize the utility of this useful feature, that would be most appreciated. I checked the wiki, but there was just enough technical jargon to make me fall shy of understanding.

Correct.  Things won't be an worse for you than they have been in the past.  

Besides increasing efficiency (which really only matters directly to pool operators or to those with super tight bandwidth or high bandwidth costs), ntime rolling helps protect miners from communication delays on the pool they are using.

Miners incrementing the timestamp (aka ntime rolling) are not as dependent on the pool being able to respond promptly to requests for new work units every 10-20 seconds.  If a pool is stressed due to load or if there are network problems, a non-ntime-rolling miner will become idle occasionally (you may have seen warning messages about this from time to time).  In contrast, with the same load or network problems, an ntime-rolling miner will just happily increment the timestamp and keep looking for additional shares.  

So if you mine at a pool that routinely is overloaded or has network problems, you'll find more shares per hour (on average) with an ntime rolling miner which will translate into you getting paid more.

[Dargo]

Thanks Luke-Jr. I'll probably stick with phoenix for now since I don't tend to get many idle miner warnings.

[stevang]

Can i still use Phoenix with Eligius now? is there a list of accepted mining software?

You can still use all miners with Eligius. This change should only affect those that have broken implementations of the rollntime extension. Phoenix doesn't support this at all. Since it is a helpful feature, I would recommend switching to poclbm if you can get the same hashrate out of it (it's usually better once you find the right settings).

So if we use phoenix, we are missing out on a useful feature, but there won't be any hit to mining efficiency, is that correct? I'll try to figure this out on my own, but if anyone can summarize the utility of this useful feature, that would be most appreciated. I checked the wiki, but there was just enough technical jargon to make me fall shy of understanding.

Correct.  Things won't be an worse for you than they have been in the past.  

Besides increasing efficiency (which really only matters directly to pool operators or to those with super tight bandwidth or high bandwidth costs), ntime rolling helps protect miners from communication delays on the pool they are using.

Miners incrementing the timestamp (aka ntime rolling) are not as dependent on the pool being able to respond promptly to requests for new work units every 10-20 seconds.  If a pool is stressed due to load or if there are network problems, a non-ntime-rolling miner will become idle occasionally (you may have seen warning messages about this from time to time).  In contrast, with the same load or network problems, an ntime-rolling miner will just happily increment the timestamp and keep looking for additional shares.  

So if you mine at a pool that routinely is overloaded or has network problems, you'll find more shares per hour with an ntime rolling miner which will translate into you getting paid more.

That i do understand Thanks for explaining.

well, as i always got the best results from Phoenix yet, i stick with it. i tried almost every other mining software around. at least the one that does not need compiling software on linux. Is there a list with best parameters/ options related to the GPU Model for Diablo or poclbm?

[anodyne]

Can i still use Phoenix with Eligius now? is there a list of accepted mining software?

You can still use all miners with Eligius. This change should only affect those that have broken implementations of the rollntime extension. Phoenix doesn't support this at all. Since it is a helpful feature, I would recommend switching to poclbm if you can get the same hashrate out of it (it's usually better once you find the right settings).

Except poclbm is generally slower than DiabloMiner.

Right now I'm seeing over 380 shares sent in the last hour on the ~410MH poclbm miner on my desktop machine. I haven't seen anything near that efficiency with any other client/pool combination.

[DiabloD3]

Can i still use Phoenix with Eligius now? is there a list of accepted mining software?

You can still use all miners with Eligius. This change should only affect those that have broken implementations of the rollntime extension. Phoenix doesn't support this at all. Since it is a helpful feature, I would recommend switching to poclbm if you can get the same hashrate out of it (it's usually better once you find the right settings).

Except poclbm is generally slower than DiabloMiner.

Right now I'm seeing over 380 shares sent in the last hour on the ~410MH poclbm miner on my desktop machine. I haven't seen anything near that efficiency with any other client/pool combination.

Shares generated is an essentially random value. According to statistics, you should get about 344 shares in an hour at 410 mhash.

[Luke-Jr]

Artefact2 has requested new indexes on the webserver SQL for his new graphs v3.0, so web-side SQL is down while it makes the indexes. This mainly means hashrates are showing 0.

I have also just deployed step 2 of my anti-stale improvements. Please report if you get any "invalid-time" rejected shares, or if your miner shows "idle" (especially around longpolls). Older versions of DiabloMiner have a bug, and are currently being exempted from the new behaviour (which makes it less effective for everyone), so if you use DM please upgrade to the latest version.

[Luke-Jr]

New poll for theoretical (unplanned) reward system change

[Luke-Jr]

Please document any feature requests and required core (ie, not web-specific) features, including features we already have at: http://eligius.st/wiki/index.php/Internal_requirements

If you wish to get involved with the software development side of the rewrite, contact me privately on IRC.

[Luke-Jr]

The forum messed up the last poll, so please re-vote here!

[Xephan]

In the previous Eligius thread (http://forum.bitcoin.org/index.php?topic=6667.0), linked in the bitcoin wiki (https://en.bitcoin.it/wiki/Comparison_of_mining_pools), there is a struck out comment about a transaction fee of "0.00004096 BTC per 512 bytes", but this is still in the wiki.

At the same time, I also read from some other threads that Luke has a transaction-free node to accept transaction and there is this https://en.bitcoin.it/wiki/Free_transaction_relay_policy which lists eligius as the only transaction-fee free pool.

Since there is some conflicting information, can Luke please confirm if that eligius will accept zero fee custom transaction even for small amounts like 0.0001 BTC?

[anodyne]

I'm pretty sure the "free" in the policy should be read as "not restricted to standard rules", rather than "free from transaction fees".

[Luke-Jr]

In the previous Eligius thread (http://forum.bitcoin.org/index.php?topic=6667.0), linked in the bitcoin wiki (https://en.bitcoin.it/wiki/Comparison_of_mining_pools), there is a struck out comment about a transaction fee of "0.00004096 BTC per 512 bytes", but this is still in the wiki.

At the same time, I also read from some other threads that Luke has a transaction-free node to accept transaction and there is this https://en.bitcoin.it/wiki/Free_transaction_relay_policy which lists eligius as the only transaction-fee free pool.

Since there is some conflicting information, can Luke please confirm if that eligius will accept zero fee custom transaction even for small amounts like 0.0001 BTC?

"Free transaction relay policy" is in reference to the network which relays transactions without prejudice against low/no fee or non-standard transactions. Eligius is clearly listed as having a 0.2 TBC minimum transaction fee, as published elsewhere.

[Xephan]

"Free transaction relay policy" is in reference to the network which relays transactions without prejudice against low/no fee or non-standard transactions. Eligius is clearly listed as having a 0.2 TBC minimum transaction fee, as published elsewhere.

Ok, so this means the no-fee transactions will get relayed but in order to be processed in a block, there must be a 0.2 Tera Bitcoin transaction fee? That amount is huge so I must be misunderstanding what you mean by "TBC", could you clarify that? Thanks!

[Luke-Jr]

"Free transaction relay policy" is in reference to the network which relays transactions without prejudice against low/no fee or non-standard transactions. Eligius is clearly listed as having a 0.2 TBC minimum transaction fee, as published elsewhere.

Ok, so this means the no-fee transactions will get relayed but in order to be processed in a block, there must be a 0.2 Tera Bitcoin transaction fee? That amount is huge so I must be misunderstanding what you mean by "TBC", could you clarify that? Thanks!

Link: Helpful summary of all Bitcoin units

0.2 TBC is equivalent to 0.00004096 BTC

[Xephan]

Link: Helpful summary of all Bitcoin units

Thanks for that link, the one I found earlier didn't have such a long list... although the first thing that came to mind when I saw that was "Bitcoin needs less confusing denominations!"

0.2 TBC is equivalent to 0.00004096 BTC

That's cool, way better than the current 0.005

I'll transfer my main miner to eligius just to support this