Pages:
Author

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

donator
Activity: 2352
Merit: 1060
between a rock and a block!
Blades are available for sale on my threads at 3.1 btc now for those interested.
they work flawlessly through bfgminer running as a proxy.  Thanks Luke for making it easy!!
legendary
Activity: 1680
Merit: 1045
Just sending a big thank you to luke and wizkid057. This pool and stats are useful and working very well with our gear over the last few days.


Thanks!  Doing the best we can.

I plan on adding more detail to the stats page to give more per-worker stats.  I'm also working on customization worker-down email notifications and things of the like.

Have fun! Smiley

-wk

looking forward to email notifications.
hero member
Activity: 546
Merit: 500
Owner, Minersource.net
Just wanted to say Im very impressed, and switched over my miners!
legendary
Activity: 1223
Merit: 1006
Just sending a big thank you to luke and wizkid057. This pool and stats are useful and working very well with our gear over the last few days.


Thanks!  Doing the best we can.

I plan on adding more detail to the stats page to give more per-worker stats.  I'm also working on customization worker-down email notifications and things of the like.

Have fun! Smiley

-wk
mrb
legendary
Activity: 1512
Merit: 1028
Just sending a big thank you to luke and wizkid057. This pool and stats are useful and working very well with our gear over the last few days.
legendary
Activity: 2576
Merit: 1186
I still keep getting diff 1.999989 or similar, looking forward to set my min diff manualy
This is due to your miner displaying 2 as bdiff instead of pdiff.
Setting mindiff won't change the fact that difficulties will still be rounded to a power-of-two pdiff.
hero member
Activity: 547
Merit: 531
First bits: 12good
I still keep getting diff 1.999989 or similar, looking forward to set my min diff manualy
sr. member
Activity: 476
Merit: 250
Hey I was wondering what the formula should be for determining min. difficulty setting? For example if I mine at 10 GH/s what would be best min. diff. setting?

The pool targets 32 shares per minute.  So, sticking with that...

(hashrate_in_hashes_per_second/4294967296)*60 = difficulty_1_shares_per_minute

Difficulty 2 would be triggered at 64 shares/min, Diff 4 @ 128, Diff 8 @ 256, etc.

So for you,

(10,000,000,000/4294967296)*60 = ~140 difficulty 1 shares/min

Then divide by 32 to get difficulty ~4.36 for 32 shares/min.  Round down to the nearest power of two >= 1, and you get difficulty 4.

This works for all hash rates.  Example, for someone with 10 Th/sec:

(10,000,000,000,000/4294967296)*60 = ~139,698 difficulty 1 shares/min ... / desired 32 = ~4366 difficuly for 32 shares/min... round down to nearest power of two to get difficulty 4096.

For hash rates under ~4.3Gh/sec, the pool will use difficulty 1.  I am, however, likely going to be increasing the pool-wide minimum difficulty soon (probably to 2 to start).

Keep in mind that the control panel setting for minimum difficulty has no effect as of yet since I'm still working on back end support for that feature.

-wk

Thanks that's exactly what I was looking for.
legendary
Activity: 1223
Merit: 1006
Hey I was wondering what the formula should be for determining min. difficulty setting? For example if I mine at 10 GH/s what would be best min. diff. setting?

The pool targets 32 shares per minute.  So, sticking with that...

(hashrate_in_hashes_per_second/4294967296)*60 = difficulty_1_shares_per_minute

Difficulty 2 would be triggered at 64 shares/min, Diff 4 @ 128, Diff 8 @ 256, etc.

So for you,

(10,000,000,000/4294967296)*60 = ~140 difficulty 1 shares/min

Then divide by 32 to get difficulty ~4.36 for 32 shares/min.  Round down to the nearest power of two >= 1, and you get difficulty 4.

This works for all hash rates.  Example, for someone with 10 Th/sec:

(10,000,000,000,000/4294967296)*60 = ~139,698 difficulty 1 shares/min ... / desired 32 = ~4366 difficuly for 32 shares/min... round down to nearest power of two to get difficulty 4096.

For hash rates under ~4.3Gh/sec, the pool will use difficulty 1.  I am, however, likely going to be increasing the pool-wide minimum difficulty soon (probably to 2 to start).

Keep in mind that the control panel setting for minimum difficulty has no effect as of yet since I'm still working on back end support for that feature.

-wk
sr. member
Activity: 476
Merit: 250
Hey I was wondering what the formula should be for determining min. difficulty setting? For example if I mine at 10 GH/s what would be best min. diff. setting?
legendary
Activity: 1223
Merit: 1006
What's going on today, 504 Gateway Timeout on the website?
Yeah it seems like the website is down but shares are still being accepted so all is most likely fine. Wizkid057 will be on it soon enough.

Web server is acting up. I'm going to migrate it to a better setup soon.
sr. member
Activity: 476
Merit: 250
What's going on today, 504 Gateway Timeout on the website?
Yeah it seems like the website is down but shares are still being accepted so all is most likely fine. Wizkid057 will be on it soon enough.
sr. member
Activity: 248
Merit: 252
What's going on today, 504 Gateway Timeout on the website?
newbie
Activity: 51
Merit: 0
Hey Wizkid and Luke-Jnr,

Been using Eligius for a few months now.

Just want to say - Great pool and great work! I'll send a donation over.
sr. member
Activity: 400
Merit: 250
the sun is shining, but the ice is still slippery
In the [Configurable Options] section: after inputting data into the sections that are appropriate to me I Submit Changes and the page returns blank (as if I made no changes / default)

Did you signed the configuration message with your Bitcoin QT client ?
After you input the signed message and push the Submit Changes, did you got Signature passes! or Signature fails! on the top part of the page right after Welcome, ?

I actually did not carry through in signing my address. I was more concerned with setting the minimum payout. Granted, at this rate (670 Mh/s) I will accumulate 0.15xxxBTC queued for payout in 2 months  Cry. I have a feeling I should not worry (as it states this is all in BETA stage) but wanted to clarify. Thanks a lot...

The only way to save the settings is by signing the settings string with your address.

Slightly stressful because I keep getting signature failed. I used a inputs.io addresss. Im pasting the data that lies in between the (-----BEGIN SIGNATURE----- data-----END BITCOIN SIGNED MESSAGE-----) in the signature section right?  Quite embarrassing granted this is elementary and Ive signed messages before. Anyways will have to play around with it a bit further. Thank you kindly...

I got it working. Not sure if its related but i unchecked the "Format Message" box and it worked. Thanks again!
full member
Activity: 154
Merit: 100
In the [Configurable Options] section: after inputting data into the sections that are appropriate to me I Submit Changes and the page returns blank (as if I made no changes / default)

Did you signed the configuration message with your Bitcoin QT client ?
After you input the signed message and push the Submit Changes, did you got Signature passes! or Signature fails! on the top part of the page right after Welcome, ?

I actually did not carry through in signing my address. I was more concerned with setting the minimum payout. Granted, at this rate (670 Mh/s) I will accumulate 0.15xxxBTC queued for payout in 2 months  Cry. I have a feeling I should not worry (as it states this is all in BETA stage) but wanted to clarify. Thanks a lot...

The only way to save the settings is by signing the settings string with your address.
sr. member
Activity: 400
Merit: 250
the sun is shining, but the ice is still slippery
In the [Configurable Options] section: after inputting data into the sections that are appropriate to me I Submit Changes and the page returns blank (as if I made no changes / default)

Did you signed the configuration message with your Bitcoin QT client ?
After you input the signed message and push the Submit Changes, did you got Signature passes! or Signature fails! on the top part of the page right after Welcome, ?

I actually did not carry through in signing my address. I was more concerned with setting the minimum payout. Granted, at this rate (670 Mh/s) I will accumulate 0.15xxxBTC queued for payout in 2 months  Cry. I have a feeling I should not worry (as it states this is all in BETA stage) but wanted to clarify. Thanks a lot...
full member
Activity: 154
Merit: 100
In the [Configurable Options] section: after inputting data into the sections that are appropriate to me I Submit Changes and the page returns blank (as if I made no changes / default)

Did you signed the configuration message with your Bitcoin QT client ?
After you input the signed message and push the Submit Changes, did you got Signature passes! or Signature fails! on the top part of the page right after Welcome, ?
sr. member
Activity: 400
Merit: 250
the sun is shining, but the ice is still slippery
A while back I remember reading a couple of posts that were relative to this question. After searching the hell out of the forum with no luck, Ill feel better if I ask so its clear.

1)
In the [Configurable Options] section: after inputting data into the sections that are appropriate to me I Submit Changes and the page returns blank (as if I made no changes / default)  Now I am aware of the notice:

You may set all options now, and they will take effect as backend support is completed!

Which leads me to believe that my config'ed options were saved but not showing. Am I wrong?

One of the reasons I was concerned of these options not being saved is adjusting my minimum payout. I know there has been a lot of discussion on minimum payouts, payment queues and I do not want to invoke friction or be flammed by mentioning this or perhaps missing a post or something in the FAQ. This leads me to my second question.

2)
I am a small time miner, I set my minimum payout to the lowest allowed (0.01048576) Now that I have exceeded this minimum balance I am concerned that I am still set at the default minimum (0.16777216). I know it can take time to see your address in the payout queue etc, etc etc I have read all of that but having the Estimated Position in Payout Queue staring in my face telling me that I still have 0.15 left till payout which will take at least another 1 month, 3 weeks, 2 days and 6 hours at current network difficulty of 112628548.67 is disheartening and lead me to inquire with all of your fine folks.

Last and not least, special thanks to LukeJr and Wizkid for their hard work in this pool. Special thanks to all the contributors that answer questions to other in this thread. I enjoy following the thread and mining on this pool over other pools. The clean cut basic interface yet specific graphs was something that attracted me and much more. Cheers
hero member
Activity: 547
Merit: 531
First bits: 12good
lol now i saw this block:
http://eligius.st/~wizkid057/newstats/blockinfo.php/00000000000000074ef0fb6f18e367b64fee580b6590c7e14c6a93d594390474

so fast that it was not included in payment, too bad the next are way above diff.

I have a suggestion for wizkid057 and luke, if possible to make a differend Eligius Offline Wallet that way we'll have access to that information, because from the current address http://blockchain.info/address/18d3HV2bm94UyY4a9DrPfoZ17sXuiDQq2B it is not clear what part of the funds are for the pool.



Pages:
Jump to: