Button "Lost Password" is there just for anturage? I haven't found any code serves this event...
It's just a relic from mining pool v1.... Looks like it was a stub. I'll get to it in the next version. Which reminds me.... v3 features not yet in repo: Memcached support No more shares_history (what a nightmare that was) Improved block handling. Dynamic stats/setting caching (more responsive/less overhead) Process locking Drastically improved cronjobs. Live round stats. Just to name a few improvements.... Looking forward to seeing how you have tackled this.... im in the midst of dealing with these same issues... especially the whole shares_history nightmare and the associated monster queries. |
|
|
|
Just to chime in and be "that guy":
While I completely agree and have said the same thing in IRC quite a bit about a lot of the smaller pools crying "DDoS", technically they ARE being DDoS'd.
The difference is, they're not being DDoS'd in a HOSTILE manner (ie: When BTC Guild was being hammered offline for DAYS by hundreds of thousands of computers, maxing out the pipes of all our servers). The smaller pools are being DDoS'd by legit traffic that can't be handled without pushpoold and bitcoind patchs, not to mention separate frontends (run on a separate line from the pool itself).
Technically a botnet miner taking your pool offline IS a DDoS. It is a distributed load that is denying service due to being unable to respond adequately. Trust me, and Tycho can chime in too (slush likely as well): If you get targetted by a hostile DDoS like what hit us a few weeks ago, you'll know. You'll know because most (if not all) of the smaller pools out there are not running on a host that will tolerate the attack and will swiftly nullroute your IP address for 24 hours automatically.
+1 |
|
|
|
This is exactly what i have suspected for a long time. Technically your explanation is not 100% spot on but the general idea of what you are saying is indeed correct. This has been annoying me as well. Thanks for finally pointing out the elephant in the room  |
|
|
|
Posting to note that I've brought 1gh/s on board, my username is the same on MF: Xurious. I'm barely hitting the 1gh/s at the moment, this damnable 95f weather is killing my rigs. Hmmm....strange i havent seen you over 750 or so yet... can you post a screenshot or something showing me this? I would say I'm sorry, but I can't apologize for the transformer outside my house blowing TWICE in the last 24 hours. They finally put a new fancy one up! (It's made me a very unhappy person. Power went down about 10 minutes after I joined MF with full power.) Hashrate is back over 1gh/s with room to spare! Indeed.... very easily breaking 1GH now Your account has been toggled to early adopter I woke up to the sound of the fan on one of my 5970s grinding to a halt this morning. It was not a pleasant way to wake up. I hurriedly stumbled over to the computer, half asleep and half alarmed, to shut it down. Awww too bad! Lucky you heard it and didnt burn the house down! D IN OTHER NEWS...
FYI: Conditions for special promotion for early adopter accounts has been updated and modified. |
|
|
|
Where can i check ny number of share submitted and total shares per block?
total submitted is to your left. Add past and current round and you have your total. block stats are coming.... we are young... please bear with us. Stats are the icing on the cake and better icing is being worked on. |
|
|
|
I guess the word "extra" made me think there was a base donation. Maybe the second line should display the total % being donated instead of just the the additional donation %. It might already be like that, it's hard to tell because I am an early adopter. I would also remove the term fees from the second line. I understand that technically it's all fees in the pool code but semantically it's not the same thing.
Maybe I am also just making this overly complicated, english is not my primary language. IMHO the second line should just state "You are donating X%" or "You are donating X% of your mined bitcoins" All excellent points! You are right about that donating of your fees string. Doesnt make much sense now that i think of it. Have a look at it now... should be clearer i hope. The other comments i will wait to reply on because what i say now will be invalid by the weekend. We are re-doing how this is done now and i think everyone will like the new way better. |
|
|
|
Posting to note that I've brought 1gh/s on board, my username is the same on MF: Xurious. I'm barely hitting the 1gh/s at the moment, this damnable 95f weather is killing my rigs. Hmmm....strange i havent seen you over 750 or so yet... can you post a screenshot or something showing me this? |
|
|
|
Connected to this pool this morning before I read all the info about it. Wanted to see the stability over 12 hours first, so I used 1/2 a 5870. I'll switch fully over now, it may not be completely free but I like the concept!
Have I missed something casually perusing these forums? Why must it be 120 blocks? That's a relatively long time.
Welcome! Simply because we are a new pool and dont have the reserves to front the 50 BTC ourselves yet. Until 120 confirms there can always be a risk that the block we found can be orphaned and we receive no money for it. At the moment, making no profit, we havent yet decided to take that risk. We arent the only ones who work this way, btw. Most other pools are similar. |
|
|
|
Added DTD (donations to date) stat at the top as suggested (good idea, btw!) Click on it for more info! I was under the impression that the early adopters were not paying the pool 0.5% administration fees but that we were still giving 1% to charity. No thats not the case. 0% fees is 0% fees. There really is and was no catch to that. We arent making anything right now (in fact we are at a loss if you dont count the bounty) the idea was that the early adopters would help bootstrap the pool and that the latecomers would be the ones that the opensource devs and writers could benefit from. We are currently trying to come up with a better approach that will make everyone much happier. We will of course keep you up to date. |
|
|
|
hi guys! First 0.50 BTC donation paid out! You can see it here: http://blockexplorer.com/tx/b179b5523f444ba08ff62b18d58cb919a59f4a5a7b89175b4b641650f41b919eI had to cover this one mostly out of my own pocket since we are on 0% fees for most of our active miners but full disclosure, we should have a bounty incoming for this to help reimburse me and cover some of the upcoming blocks till donations and new miners can help cover it. I will shortly have a page up and available documenting where your donations end up and who they are sent to. (More full disclosure: Im one of the 19 developers on the list so i made 0.026 BTC of that money back!) hehe..  In other news, Ive brought some of the stats back that were gone for awhile and changed how they work a bit. It should be pretty clear how it works if you look closely at your stats bar on the left. More will be coming as i get the time.... lots of irons in the fire right now and again thanks to all of you making this a possibility. Mainframe rocks! |
|
|
|
AnnihilaT, since you are looking for suggestions. I think it would be nice if the pool had a payout history page. Maybe you could also add a public payout page showing the donations history. I have no doubt about your integrity but I think it would be a nice way to advertise and gain trust from miners.
Yeah for the donations.. We have plans to do that for sure and im testing the code on a test platform right now. Maybe this weekend. RE: payout history - what are you looking for here? you mean personal payout history per user? Im not sure people want their payouit information publicly available?  |
|
|
|
I do believe that this pool has potential, which is why I stuck with it through the first very unlucky week. And then wham - 3 blocks in a single day.
I will create a couple of banners for the frontend and forum sigs. I'm no PHP developer, but I'll have a look at the code anyway and see if I can contribute any ideas on how to improve.
Very cool of you! Im curious! Thanks for helping out and always open to any help we can get. much appreciated. |
|
|
|
All, Thanks for bearing with us. As you should be able to see things should be back to normal and blocks 1 & 2 have been confirmed and paid for. The issue we ran into was a silly one that was a combination of factors but the main one being that i had tweaked our DB server for higher load but had forgotten to restart the daemon so it would parse the new configurations settings for them to take effect. When we hit the first payout, our DB server basically took a shit trying to parse that huge first round and do calculations because the server itself was misconfigured (actually default configured and without my tweaks). I brought everything down for a bit to preserve integrity of the data and then solved the issue and brought everything back slowly piece by piece. There was no data loss but we stopped accepting shares for about 30-45 mins which might have kicked some of your miners to backup pools. At any rate, thats one mistake that should not happen again and the next confirm round for block 2 went as planned. One last thing i had to do when restoring everything back to how it should have been and testing to make sure it was ok was to set everyones auto payout thresholds to 0 so that nothing nasty would trigger while i was running tests. You will have to log in and reset these to the payout triggers you had before and you can either do a manual payout or you can also just change the threshold back and wait 5 minutes or so until the next stats run and then you should see your payment go out automatically. Thanks for bearing with us... As Vladimir says.... growing pains We plan on slowly bring more stats and more data into the website as we get time. We want to be transparent but since this is not our full time jobs (yet?) it will take a bit of time to bring in new features. Betters stats and explanation of them is a high priority for us as well tho. Cheers, Anni |
|
|
|
Guys, there were issues....  im on it. |
|
|
|
Slowly transfer my GPU power to this pool.  WElcome |
|
|
|
All, For the coming "first" payout for the first confirmed block, I will be in bed (4am my time)... im trusting the tests i have done and am going to let everything run automagically as coded but if anything goes seriously wrong i will be around 4-5 hours later to fix things when i wake up. backups of data are secure and everything can be restored if something goes wrong. It's not my intention to worry anyone but just to reassure that since its a new pool there could be issues and if there are any we have disaster recovery plans in place to cope with any situation. If there are problems, we will fix them and make it right. Lets keep our fingers crossed! Nite all! |
|
|
|
|
Hit the second block already! Can we do three in a day ?
|
|
|
|
|
Update: We just found our 2nd block!
I Would also like to thank everyone for their support during that first difficult round. We holding steady at around 65 GH/s at the moment.
Cheers!
|
|
|
|
basically we define a round as the period of time between payouts so you won't see round stats change till we hit 120 confirms on this first block.
What happens if another block is found before the first one has 120 confirms? How are the payout shares calculated then? in case the last post didnt answer this one directly, we know and track which shares belong to which block and payout them out accordingly. Its just our statistics that follow a somewhat non tradtional approach. The data is all there in the databases appropriately its just how you choose to interpret and display this data which can be left up to preference. |
|
|
|
Hi guys, Sorry this is my fault for not explaining well enough.... i was at the eye doctor replying on my phone so i didnt maybe explain it as well as i should have. When i say that we define a round as periods between payouts i meant this ONLY for the purpose of generating statistics. CERTAINLY NOT for calculating payouts. If it took 100,000 shares to find block one then the round shares counter will keep going until 120 confirms are reach for that first block and a payout is done. Right before payout on block 1 the counter might say 350,000 round shares (block 1 plus shares towards block 2). but calculations are done only on that 100,000 shares alone and only those who contributed to that 100,000 shares are paid out of that block. After block 1 is paid out, the 100,000 shares which contributed to finding that block will removed from the current round leaving that 150,000 shares towards block 2. So you will see the round shares not reset to 0 after we have the first block confirmed -rather you will see them drastically reduce (its gonna be something like $current_number - the 5.8 million it took to get us to that first block). One other thing to note which i know will cause confusion. Your round estimate at the moment is taking into consideration the entire amount of round shares so you can expect that it too will change when the first block is confirmed. I understand it might be a bit confusing and we have plans to work on this to make it better as we get the time. I also think that the biggest oddities and confusion will only be apparent until we have the first confirmed block. After that it should make more sense how the stats are done. Open to any discussion or ideas about this and appreciate the feedback! Cheers, Anni |
|
|
|
|
Show Posts
