Possibly to justify their upcoming 5 year guarantee: 2 X 3 = 5. ![Roll Eyes](https://bitcointalk.org/Smileys/default/rolleyes.gif) I think you need to check your math...
|
|
|
I dunno, kano, I prefer BFGMiner. I find your need for attention to be off-putting. Luke was just trying to give a community member something to look at for his project and you turned it into a ridiculous trainwreck of a thread. Stop trolling and live your life.
|
|
|
After using this pool and firing about 2.8GH/s at it for the past 3 weeks, I've got a few suggestions:
Website: I'm sure as you know, the site feels half-finished. Examples: 24h earnings (coming soon) and the instant payout not functioning. I would like to see some additional personal stats and pool-wide stats added. Personal stats that I would like to see are the planned 24h earnings, lifetime earned, and a payout history. Pool-wide stats that would be nice to see is a (nearly)instantaneous recording of the current pool hashing speed in addition to different graphs showing the pool speed, top 10 lifetime shares, etc.
Pool itself: Stratum is great, but why stick with the one protocol? I'd like to see GBT implementation as well.
For payouts: The payout system is flawed. You've mentioned it is run every 6 hours previously in this thread, but in practice I see this is not true. I've seen my payments sent out at approximately 24h intervals, despite the autopayout threshold being broken many times over. I have my threshold set low because I am not confident in the payment system of the pool, so I have it low to pay me my due shares as often as possible, so I'm not left without my true earnings. You need to improve the payout cycle, and tell users how and when it will pay out, and make sure the system actually does what you say it does.
The pool is a good start, but I'd like to see more from it.
|
|
|
Sounds good!
I just wanted to make sure you adjust the fee according to the difficulty, because according to the FAQ post in the beginning of the thread, the PPS price is a fixed amount. It should be somewhere in the region of 0.00000822247... if adjusted to difficulty, not the 0.00000726963... quoted in the FAQ post.
Thanks!
|
|
|
Rex has said it many times, he couldn't the blockchain code to play nice with each other, so he turned it off back in June.
|
|
|
Yep and a few days left before the change, so it could go even lower. Nice.
|
|
|
I wonder what happened to all the users? I'm the top hasher with 2.4 Gh/s? Also payouts have slowed down. I'm double my threshold and it's been almost 2 days since a payment.
|
|
|
Ack, wasn't aware that could happen. What is the reasoning behind that burst in blocks?
|
|
|
Hash rate is shooting up.
|
|
|
I see no reference to the new pgaset command in the documentation? How do we use this command? is it a flag we use on the executable, or one for the config file?
Looks great though!
|
|
|
I'm using the windows binary that is on your site.
|
|
|
Weird, my i0client won't sync with the block chain, so I can't confirm receipt of the coins. The client says I need to upgrade or others need to upgrade. I wonder what's changed.
|
|
|
MPBM is the way to go at the moment for software. BFGMiner, as was said by a previous poster, is very unstable. My boards get sick after about 15-30min of mining, then require a power cycle and new firmware upload.
|
|
|
My 4 boards arrived today, taxes were applied which is weird, but it was a good transaction, lots of extras included in the box. Thanks Bonks!
|
|
|
How do I use this with the ModMiner Quad? I currently use BFGMiner, but I prefer the webinterface of MPBM. It works great with my X6500s, now I want to add in my MMQ.
How do I do this?
|
|
|
Doh, should have checked the git before posting. Thanks LJR!
|
|
|
I don't want to make a github feature request until I know if this is feasible or not:
Can you make the FPGA clock setting a user-selectable setting? For example, my MMQ starts at 200mhz per card, and slowly steps up to 210mhz over the next half hour or so. it would be advantageous for me to have it automatically start at 210mhz, to avoid losing those "extra" hashes I'm not getting out of the chips at 200-210mhz. I realize this slow step-up is to avoid hardware errors and damage to the chips, but I have adequate cooling, the cards themselves never go over 35C. I'm getting my X6500s tomorrow, so I would also like to see it easily user selectable for that as well.
Is this even possible, or would this require extensive re-coding of bitstreams?
|
|
|
Even new units are overpriced these days. You'll be lucky to get half the price you're asking. Asics on the horizon, you won't even be able to sell it for that once they hit.
|
|
|
|