Topic: [NR 1]: Triplemining.com || 1 BTC(or more) jackpot every week - page 6. (Read 25131 times)

can you try again one more time ? :/ i made some adjustments

support really tried but we werent able to find the cause.. other pools are working fine its just triplemining so i dont think its any traffic blocking unless they specifically block triplemining

So you've talked to support and they've been unable to help?  Here's a clue for support: the communication problems seem to happen at the user level, for instance, I've seen my account have communication problems (and go to 0 h/s upon restarting the client) while the account of the user in my pool continued to function, the user in my pool has seen the same behavior when my account was functioning.  The best part is, due to my job, I also know that there is at least one major ISP on the Internet has been "unilaterally blocking traffic."  This comes from McAffe, but it could explain the issue if it were location -related and not account-related.  It would also explain why I have actually seen fairly regular trouble with at least three different mining pools lately.  DDoS attacks by someone anti-bitcoin would explain the same, though, so who knows.

well ive officially given up on triplemining.. have had "problems communicating with bitcoin RPC" for a week now and noone knows why

I hear what you're saying. It just reminded me that I had a general question about stales vs other words.

I'm not sure, but I think there could be some terminology overlap or confusion.  I'm not sure if there is a difference between "stale," "invalid," and "rejected" shares, assuming all three even exist.  When I speak of "invalid," "rejected," or "orphaned" blocks, though, I'm talking about groups of shares, I'm saying when a block that a pool spent 5 days finding doesn't get confirmed, but considered whatever it is considered instead, then there is no payout, so our miners wouldn't get paid out for that block unless the pool itself ate the 49-50 (depending on whether or not they also paid the 1% to the jackpot/minipool owners) BTC loss.  Presumably a no fee pool can't possibly afford that kind of risk, so something should be documented regarding what will be done instead, it could help prevent negative word of mouth (or at least allow a defense to it) should TripleMining end up in such a situation early in its development.

It's under the workers page.

Also, I was wondering for a long time... what's the difference between a "Stale", "Invalid", and a "Rejected" share? I know what a stale is. What are the other two?

I'm not seeing it.  By done do you mean will do, or am I looking in the wrong place?  Also, since my edit took over my original post, what happens if this pool finds a block that is orphaned or invalid?

Done

I agree 100%.  I think MrSam can get this done, he's in charge of HTML.

Hopefully this hasn't already been asked (I read this entire thread, but I got tired of reading the thread at http://forum.bitcoin.org/index.php?topic=23663)...  What happens in a small pool like this if we find an invalid block?  I was thinking about (and doing a very little bit of) mining with triplemining, but I'd hate to see multiple days worth of estimated income disappear due to an invalid block.  One pool that I looked at stated that all shares would be counted toward the next block if an invalid block was found, which makes sense to me, but would make payouts look bad for the block following the invalid one due to the number ~doubled of shares.  On another pool, an appropriate donation % gets shares for invalid blocks paid, but that pool is so large that an invalid block barely affects me (although I donate anyway and have found that the invalid blocks seem to about equal the donations, which is unfortunate for the pool, but fortunate for me).

EDIT:  I forgot to include this thought in my original post...  I saw discussion about stale and rejected shares on the main thread mentioned above.  I also saw that features were being added based on discussion/requests fairly regularly.  Personally, wherever I mine, I would like to see counters for rejected and invalid shares along with counters for shares found.

Seems like everything crashes when a new block is found.

Thanks, no offense taken. I think I may just switch over to triplemining, people are certainly embracing the idea.  I just have a couple things I wanted to clarify, since I haven't seem to have found a definitive answer.  

First, in that example... Nevermind, I saw you've already answered this question in another thread.

Also, where is your cut here MrSam? I mean the website is great, professionally designed, probably gets lots of traffic, and you've got no ads.  You're offering features that all the other pools charge for, but you only charge 1% (which can be earned back).  I don't know what the back-end for a mining pool requires, but I imagine you need to run some kind of central server to manage all the nodes, track stats, etc.  On top of all the setup costs there's the labor you're putting in and the risk you're taking by potentially attracting the kind of attention Deepbit and BTC Guild have been getting lately.  How do you plan to sustain it?  I get that your business model may be a kind of trade secret, so it's cool if you don't want to go into it, but that's the last part that seemed fishy to me.

Heh, I guess right now deepbit is kinda like the devil we know, they put their cut right on the front page, anyone can see where the catch is there ;-)

True; but the pool with 2Gh/s would reward its miners with 25x the payout because there are less miners to divide the 50 BTC between.  Larger pools solve blocks more frequently but divide the block between a great number of people.  Smaller pools solve blocks less frequently but divide the block between smaller numbers of people.

Given enough time, everything averages out, but a smaller pools will have a higher variance than a larger pool (meaning you might make more BTC within a limited amount of time, but you might also make less).

Wouldn't a newer pool be less likely to find a block? I understand that it's pretty much luck, but the pool speed has to have a huge play in things. It seems like a pool with 50Gh/s would be mine a block faster than a pool with say 2Gh/s

Upon request, I created a Triple Mining IRC channel.  Come join us for some chat!

I'd much rather have my 100%, thank you very much.

I do appreciate the idea, however.

Considering today has been a weird day for deepbit and btc guild... also after a couple hours of reading. Me and a friend are devoting 1.4GH/s to triple, always in support of new ideas.

well id be happy to keep mining but im having connection problems since 2 days

I'm starting to lose members of my minipool, leaving due to our failure to find a block.  We better find one soon, otherwise TripleMining will be finished before it ever got a chance to get started.