Each account now shows when you are logged in at the left under your username what your account type is and what your pool and donate fee percentages are set to.
Cheers, Anni
|
|
|
As usual your correct Anni... The shares always seems to report accurate....it was just the MHash/sec and miners connected that would be off every once in a while....it was the slow test miner I had connected..... We officially opened our new mining pool site using your software and also support forums for bitcoins that is opened to the public..... The site and forums is located at www.coolcoin.netIf you want to see this front end code in action plz stop by and check us out! Thanks again for all your help and the great running front end software Anni! Peace! lol! you really didnt edit much visually did you You could at least change the background images you know Its templated so you can customize it
|
|
|
Then you can collect small fees (0.5% per block) and eventually make it all back.
Just look at the mainframe pool, where vladimir tested this offer out. http://forum.bitcoin.org/index.php?topic=24650.0As soon as he was away, the pool dropped back to nothingness. If you want to have Vlad on your pool, even with perfect 0% luck (unrealistic, as variance is that big!) prepare to pay him ~2 BTC/day additional to the ~20 BTC he anyways would get in the long run. Well nothingness might be a bit strong. The pool is still running great and is still available for those looking for an alternative. What really has hurt Mainframe is a very unlucky first round. I still see new users signing up every day but i think people are just waiting to see that first block solved and paid before jumping in completely. Our attempt was to try and hit that first block as quickly as possible and reduce some variance for the miners while the pool is young and growing and we have just run into horrible luck in the first round. A shame really.
|
|
|
What you should call your service is variance stabilization. Only a simple minded fool doesn't see this kind of service can be very valuable for a small pool operator who wishes to grow. Not worth PPS+10% imo, but definitely 2-3%. The faster your pool solves blocks, the more people will join creating a snowball effect Ultimately you don't even need the original 50ghash/s from Vladimir because you have momentum on your own. Then you can collect small fees (0.5% per block) and eventually make it all back. The less ghash/s you have the bigger the variance swings will be. In the worst case (like http://btcpool24.com ) everyone will leave after the first unlucky round due to low hash rate & high difficulty, and your entire pool dies. You'll never see a cent from block fees because none will be found. +1 This is indeed the real logic behind what Vlad is doing. In the beginning its the variance that hurts a small pool and discourages miners from joining. Thanks for pointing this out.
|
|
|
A related question would be - how does the "auto" payout mode work? Pay per every block found?
Also I second the request to have the fixed donation % visible somewhere in the profile.
Let's put a mention of the pool in the user signatures! I just did, we should spread the word around!
This is a good question. More or less, yes, it happens for every found block. To be more accurate it is triggered for every found block with 120 confirms. Ill explain in more detail. A discovered block will need 120 network confirms before its paid out to your site wallet/balance. Every few minutes the site software is checking for new blocks found and updating the number of confirmations on our own found blocks. When the number of confirms on our own found blocks becomes greater than 119, this triggers a full count of every shares contributed to that block, calculates the payout per user, and updates their wallet balance with the confirmed reward. Immediately thereafter, we check to see if any user has a balance of greater than 0.10 BTC in their wallet and if so check to see if the threshold amount is lower than the amount in their wallet. If so, we send them their balance otherwise the balance remains in their site wallet which can be manually cashed out at any time. Keep in mind that even amounts lower than 0.10 BTC can always be withdrawn with the Manual Payout / Instant method. Its only that automatic payment can only be triggered from 0.10 BTC or higher. If you have lower balance than that you just need to log in and manually pay yourself out from your balance. Fixed donation percent is a good idea and will be added in soon! Thanks for the suggestions!
|
|
|
Can you please consider changing the autopayout to 0.1 minimum.
Also, how do i know if im on 0% fees?
Hi Kripz, Considered and done. Threshold settings down to 0.10 BTC are now supported. 1 BTC minimum indeed didnt make alot of sense. Your account is 0% fee Early adopter type. Its a good idea to give an indication of this so i will code that in a bit later today as well.
|
|
|
And SuperVlad is back! At least for the moment
|
|
|
@AnnihilaT - Maybe you should add to the thread topic that a small percentage of the mined coins are going to the developers. It might attract more people.
Did this in the beginning without much interest. But im willing to try again. Main thread topic has been edited. BTW, full disclosure: the idea wasnt mine. There is credit in the original post for the guy who came up with the idea and i had a pool just about to come online when he posted his idea. We thought it was a good cause and agreed to set our pool up this way. Doesnt seem to be alot of interest tho on a wide scale for donating back to the bitcoin developers or else it just needs some more time for the news to get out
|
|
|
agreed. :/ just bad luck.
|
|
|
I can verify that this is legit.... Vladimir had 50 GH pointed at my pool for the whole weekend. He can do what he says.
But your pools now has 3GH... so whats the point... it didnt bring in any extras hashers Wont argue with you there.... just saying that he can deliver what he says he can.
|
|
|
I can verify that this is legit.... Vladimir had 50 GH pointed at my pool for the whole weekend. He can do what he says.
|
|
|
Please do not be upset. Please understand I am operating a business and as such manage risks. There are risks which I am not prepared to take for long.
I understand Im not upset... was surprised to see you point so much power at us for that long.... im quite surprised actually that we didnt solve a block. You point 50GH at us for the whole weekend....odd!
|
|
|
sorry but I can stay only for so long...
awwww.... too bad :/ Thanks for the 3 million shares you could spare tho!
|
|
|
Unfortunately this will NOT stop a thread from constantly appearing under "Show new replies to your posts".
Once you've posted in a thread, you'll always see it there if anyone posts to it. The only way to make them stop is to delete all of your posts in that thread.
-Rob
thats a shame.... discourages commenting in a thread you dont want to be bothered with for the rest of your membership
|
|
|
Maybe im an idiot but i cant find this option anywhere!
|
|
|
Joel makes a very good point here. Im inclined to agree that stales arent really as big of an issue as many people make them out to be. I think its more a psychological issue and a misunderstanding of how things are working that cause people to be so concerned about it. a huge high percentage of stales could indicate something is wrong with your mining client but in general i dont think its anything to be overly concerned about.
|
|
|
I have a interesting new problem..hehe...seems the stats will show correctly one moment, then when I come back later it will show 0 except for the bitcoin to usd ...that part seems always accurate....any idea what might be causing the mining workers and MHash/sec stats to work one minute and then show 0 the next???
Peace!
Are already counted shares also not correct when this happens? Are you mining with a really slow card? If a share isnt submitted within 10 mins the worker will be considered dead by the stats calcualations.
|
|
|
If anyone is having issues let me know... Everything still looks good from my end... that first block MUST be just around the corner...
|
|
|
Is this the "auth.cred_cache.expire" : 75, option? And if not how do I get pushpool do keep it longer, or is the problem somewhere else on the host?
I dont think so... i think this option is how long it caches the authentication credentials (login/pass) for the worker but could be horribly wrong Havent looked at that part of the code yet. check config.c in the src and that should give you a clue. maybe also check that your system time is correct and you not drifting crazily? i dunno... im outta ideas for ya man.... that option i mentioned solved my issue (started when someone joined the pool with 30 GH/s)
|
|
|
yes I did, this is frustrating. I have no clue where this comes from.
can you post your server.josn file (edit the passwords and usernames out tho)
|
|
|
|