[NR 1]: Triplemining.com || 1 BTC(or more) jackpot every week

[MrSam]

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.

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

Done

[1713968746]

1713968746

[1713968746]

1713968746

[1713968746]

1713968746

[1713968746]

1713968746

[1713968746]

1713968746

[1713968746]

1713968746

[The00Dustin]

Done

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?

[PandaMiner]

Done

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?

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?

[The00Dustin]

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 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.

[PandaMiner]

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

[lechuck]

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

[The00Dustin]

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

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.

[lechuck]

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

[MrSam]

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

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.

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

[FractalUniverse]

looks like we have just found a block after solving mere 27244 shares !! anyone can confirm?

[The00Dustin]

looks like we have just found a block after solving mere 27244 shares !! anyone can confirm?

"Needs 92 confirmations"...   No, nobody can confirm, not until/unless our block is included in (or used by?) 92 more blocks...  I think that implies we already got 28 confirmations, though, which is a pretty good start.

[lechuck]

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

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.

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

nope.. still no luck sroy..

2011-07-15 13:15:20: Running command: poclbm.exe --user=eos666_1 --pass=xxxxxx -o eu.triplemining.com -p 8344 -d1 --verbose -v -w 128
2011-07-15 13:15:20: Listener for "Default" started
2011-07-15 13:15:24: Listener for "Default": 15/07/2011 13:15:24, Problems communicating with bitcoin RPC
2011-07-15 13:15:25: Listener for "Default": 15/07/2011 13:15:25, Problems communicating with bitcoin RPC
2011-07-15 13:15:26: Listener for "Default": 15/07/2011 13:15:26, Problems communicating with bitcoin RPC
2011-07-15 13:15:28: Listener for "Default" shutting down
2011-07-15 13:15:34: Running command: poclbm.exe --user=eos666_1 --pass=xxxxxx -o eu.triplemining.com -p 8344 -d1 --verbose -v -w 128
2011-07-15 13:15:34: Listener for "Default" started
2011-07-15 13:15:35: Listener for "Default": 15/07/2011 13:15:35, Problems communicating with bitcoin RPC
2011-07-15 13:15:36: Listener for "Default": 15/07/2011 13:15:36, Problems communicating with bitcoin RPC
2011-07-15 13:15:37: Listener for "Default": 15/07/2011 13:15:37, Problems communicating with bitcoin RPC
2011-07-15 13:15:38: Listener for "Default": 15/07/2011 13:15:38, Problems communicating with bitcoin RPC
2011-07-15 13:15:39: Listener for "Default": 15/07/2011 13:15:39, Problems communicating with bitcoin RPC
2011-07-15 13:15:40: Listener for "Default": 15/07/2011 13:15:40, Problems communicating with bitcoin RPC
2011-07-15 13:15:42: Listener for "Default": 15/07/2011 13:15:42, Problems communicating with bitcoin RPC
2011-07-15 13:15:43: Listener for "Default": 15/07/2011 13:15:43, Problems communicating with bitcoin RPC
2011-07-15 13:15:44: Listener for "Default": 15/07/2011 13:15:44, Problems communicating with bitcoin RPC
2011-07-15 13:15:45: Listener for "Default": 15/07/2011 13:15:45, Problems communicating with bitcoin RPC
2011-07-15 13:15:46: Listener for "Default": 15/07/2011 13:15:46, Problems communicating with bitcoin RPC
2011-07-15 13:15:47: Listener for "Default": 15/07/2011 13:15:47, Problems communicating with bitcoin RPC
2011-07-15 13:15:48: Listener for "Default": 15/07/2011 13:15:48, Problems communicating with bitcoin RPC
2011-07-15 13:15:49: Listener for "Default": 15/07/2011 13:15:49, Problems communicating with bitcoin RPC
2011-07-15 13:15:50: Listener for "Default": 15/07/2011 13:15:50, Problems communicating with bitcoin RPC
2011-07-15 13:15:51: Listener for "Default": 15/07/2011 13:15:51, Problems communicating with bitcoin RPC
2011-07-15 13:15:52: Listener for "Default": 15/07/2011 13:15:52, Problems communicating with bitcoin RPC
2011-07-15 13:15:53: Listener for "Default": 15/07/2011 13:15:53, Problems communicating with bitcoin RPC
2011-07-15 13:15:54: Listener for "Default": 15/07/2011 13:15:54, Problems communicating with bitcoin RPC
2011-07-15 13:15:56: Listener for "Default": 15/07/2011 13:15:56, Problems communicating with bitcoin RPC
2011-07-15 13:15:57: Listener for "Default" shutting down

[The00Dustin]

Can I get a more detailed explanation of how the jackpot system works?  For instance, is it once per calendar week or once within 7 days after the previous jackpot falls?  I ask because we just found another block and it didn't fall.  The calendar week isn't over yet, but it has been almost 7 full days since the last jackpot (which was still promotional) fell, and if our luck changed, this block could take 5 days, which would even put us in another a new calendar week.

[PandaMiner]

Dustin, Since the server is in a different time zone, I think we still need several hours before there being MORE than 7 days since last jackpot.  But I feel it's close.

And yes, we just found ANOTHER block only after 15 hrs.  This is getting good!

[The00Dustin]

For the record, I wasn't implying that it has been more than 7 days.  I was implying that if the jackpot is tied to the find of the block and there are no more blocks found within 7 days that the jackpot wouldn't happpen within 7, and might not even happen within the calendar week falling after the last jackpot, this is true regardless of your definition of the calendar week because you never know whether the next block will be found in 25,000 hashes or 5,500,000 hashes, I have seen blocks take over 8,000,000 hashes.  Anyway, I'm not even suggesting there's a problem, I am just curious as to how it works, I mean, perhaps it drops when a random block is confirmed (as opposed to when a random block is found), or perhaps it drops at a random time altogether, but can tell who was mining when the block it randomly chooses to be connected to was found.

[ChrisLandin]

Hi all.

Im new to the forum and would just like to say I feel very fortunate to be mining with Triplemining. Ive been mining for around a month now with a different pool and in the last week ive moved to Triplemining and the move has been fantastic for me personally. I dont have huge hashing power yet ive made multiple coins in four days where in my previous pool I would have got this amount in over a week!!

Keep up the good work

[PandaMiner]

Yeah, but last week was a doosey. (was a long time.. check the stats)

But cool. Glad to have you on board.

[ChrisLandin]

Yeah, but last week was a doosey. (was a long time.. check the stats)

But cool. Glad to have you on board.

What does doosey mean haha?

[PandaMiner]

I may not be spelling it correctly, but suffice it to say, that we had a period of 5½ days w/o hitting a block. Once we did, the shares weren't worth a lot. But we're making up for those days this week it seems.  Just don't get your hopes up of it being like this all the time.

Well, you could. But since you're new, you should wait a whole month before deciding for sure.

[ChrisLandin]

I totally agree with you there. I studied the stats and I see where you are coming from so maybe I just hit upon Triplemining at the right time. Lets hope not though. I like the layout of the site and the returns so far have been very good to me for my setup. A lot more than I was previously earning.

Today we have generated another 2 blocks but the current one is taking a while longer but thats the probability factor of bitcoin mining. You can get a quick block or a pig of one that takes for ever.

Just out of interest panda what hardware are you running??

I put my miner together out of old hardware I had laying about the place,

so im running a E7200cpu, foxconn x 48 motherboard with 2gb ram and 1 x 5870 and 2 x 5850's.

Its drawing 740w from the wall so in the uk its costing me like £2 to run and a coin is around the £8.40 mark at the moment so a canny profit.