Is this still ongoing?
Yes. It has been a month! Please pay to my inputs.io!
Still haven't received anything, and saw you had posted, so I figured I would mention it again. You must SERIOUSLY suck at math. Let me break it down for you: First post: July 23 July 23 + 30 days = August 22 (because July had 31 days). August 22 != August 21. L2math.
|
|
|
By the way, just wanted to add in that my payment should be done today. I'd also like to continue on for another month so locking that in, .
|
|
|
If I make a thread that just so happens to get a thousand+ reads, I don't get a promotion? If he did that some of us would be rich right now, lol.
|
|
|
So much for withdraw within 24 hours Can't wait until it's automatic. Should be pretty easy to get automatic withdrawing to Inputs... a couple site owners said it took less than a couple minutes to get their systems fully up and running with it.
|
|
|
Anyways, I'm done with the conversation. Clearly there's people here who are ignorant to anything other than *beliefs* and refuse to take any evidence into consideration. Guess this is why PMB's are so popular as well, huh? Which is funny because I dealt with the SAME thing there, when I brought up the math to prove that the current PMB's (at least at that time) would NEVER be able to provide a 100% ROI, regardless as to if you waited 1 year or 5000 years. People sat around arguing with me about how I'm wrong and this and that, and what happens? Less than 10 days later one of them started to tank and people called the PMB hoster a scammer because people FINALLY started to realize that they would never achieve ROI.
It's a little depressing that people sit around arguing this crap all day long, when in the future you're going to turn around and accept the fact that the data has been right all along, and then start acting like YOU'RE the one that figured it all out and feeling like you've been getting screwed the entire time. It's happened at least 2x on this forum that I know of (of which I've PERSONALLY been the one trying to enlighten people) and looks like it's going to happen again.
With that said, I'm out. Please don't PM me when you finally come to your senses and realize you were wrong the entire time. I've done what I feel is my duty; what you do or think from here on out is all you. Leave me out of it.
FYI, Cverity, I've run into the same problem as him. I've had 6.6 MH/s pointed at the pool for weeks now. It's not hours, or even days. I just stay here because it's easier than fighting the market/dealing with crap and I can just take what's given and move on.
|
|
|
I have mined at three other pools before joining middlecoin a few days ago. So far, I'm seeing less profit than the other pools I had mined before. Why is that? Could it be because the difficulty of 512 is too high for my miners? I have 4 GPU's: 1x6950, 1x7790, 1x7850, 1x7950. On other pools, I got about 1300 KH/S. Here, I'm getting 1000 KH/S. The other pools operated with vardiff; here, there's only one difficulty of 512.
You can talk statistics and probability and whatnot all day and night long. I can tell you from my day-to-day experience that this pool with a high diff set at 512 runs very inefficiently for me. Probably because of my gpus can't hash fast enough for the pool. I am going to have to return back to wemineltc.
All your post does is show that the statistics and probability are *correct*. The people that keep arguing otherwise have yet to show any math to back it up, other than "you must not know anything about math." We've shown charts. We've broken things down into small pieces. We've used various analogies. The people arguing that we're wrong are still doing so without giving ANY reason why other than because they simply don't believe anything that's said, regardless as to how much proof there is to back it up. These are the same people who would say "a gallon couldn't possibly be the equivalent of 4 quarts. Sure, you can sit here and show me all day long. You can even show me the conversion factor and math that proves it. But you're still wrong because I simply choose not to believe that proof matters; what I think is all that matters. And I need nothing to back it up because I believe what I want and you're all wrong."
|
|
|
Yeah... that's how I feel too. I'm still waiting for an answer on my dice in box scenario. I can't wait to hear about all the "lost sixes" due to switching the box.
If you really want to use dice, at least do it properly: We have a guy who offers up a new game: rolling dice. Here's how it works: Each person is able to roll dice. For one, the deal is that if they roll a 1, they get $1. For the other, the deal is that if they roll a 1 4x, they get $4. The stipulation is that every 10 rolls, the number they have to go for changes. Roller 1 goes and gets: 1, 3, 6, 5, 2, 1, 4, 5, 6, 2 So he gets $2. Roller 2 goes and gets: 1, 2, 3, 6, 1, 3, 1, 5, 2, 3 So he gets $0. Now it's time for the next game! We now start over again, with the requirement being a roll of 3: Roller 1 goes and gets: 1, 3, 2, 6, 3, 5, 3, 2, 3, 1 He gets $4 Roller 2 goes and he gets: 1, 6, 5, 5, 3, 1, 2, 5, 6, 5 He gets $4 What's the difference here? The first guy got MORE because he could get PARTIAL amounts, rather than having to rely on the FULL amount. He has the SAME chance to get 4/4 as the other guy does to get 1/1, with the stipulation being that the first guy could also get 3/4 and be paid 3/4 the amount, while the second ONLY gets paid if he hits that 1/1. The second guy will therefore always come out behind.
|
|
|
[...] lose a share [...]
How are you supposed to 'lose' a share if it doesn't get rejected? Did it get stuck somewhere in the depth of the transistors? Because you COULD have submitted 3x 128 diff shares already. If a 512 diff share should take 1m, a 128 diff share should take 15s. Therefore if it takes you 63s to find a 512 diff share (note: this would have been stale/rejected since the block changed) you could have submitted 3x 128's that were accepted in that time.
|
|
|
The problem with that reasoning is that it still assumes past hashing somehow has an affect on the future. And that an average has anything to do with interval (there's a reason standard deviation exists, you might want to look it up before you keep throwing around the word "statistics" with any air of authority)
Do you believe that in any given second your odds of getting a share are better or worse than any other second? If not, why would it matter when you switch?
Now, someone answer me this time. If I'm throwing dice in a box and I get a point for every six I throw, does it matter if someone keeps swapping in different boxes? if not, how does this differ from hashing?
Let's try this another way then. Based on the average submission time, you would submit 4x 128 shares in the same time it would take 1x 512 shares. Nobody can really doubt this; that's the entire concept behind the share difficulty. Would you rather lose 1x 128 share or 1x 512? Because when the switch happens you lose whichever share you were on. I would MUCH rather lose the 128 (512/128 = 25% so it's only 25% the amount of losing 512). Utilizing this concept: 1024 shares have gone by. You got one of the 512's on time. Your loss was 512. 1024 shares have gone by. This time you were on 128's. Your last share was rejected. Your loss was 128. I seriously can't fathom how anyone could possibly argue that this isn't true. And this is based on the long-term because that's what an average is. Every time we lose a share, we are losing the equivalent of up to 512 shares, as opposed to a maximum of 128. The longer this goes on doesn't mean the less impact it has. On the contrary, it means the impact is GROWING. Now instead of 10x 128 shares (1,280) lost it's 10x 512 (5,120). Now instead of 100x 128 shares (12,800) it's 100x 512 (51,200). The number continues to go up with every passing minute.
|
|
|
Its not gamblers fallacy to predict the expected outcome of a series of events given a probability.
Like saying, given a set of 5 coin clips, we predict 3.125% of the time it will be all heads.
Gamblers fallacy would be:
I just had 4 heads, I am due for tails now!
or
I just had 4 heads, I am on a steak and will get heads
Calling probability gamblers fallacy is a complete reversal of the situation, the casino relies on probability to even out variance and ensure their profit over time.
When we predict the average time to find block, we are like the casino predicting the number of times the dealer wins on a game OVER TIME.
In other words, it is not gamblers fallacy to say given a hashrate of x, and a difficulty of y, we RELIABLY EXPECT it to take Z seconds to find a share.
Correct. I'm not speaking of probability of the expected outcome of a series of events that have not happened yet. I'm directing that link to anyone that thinks that they calculated part of a share and lost something when we move to a new block. Well if anyone really thinks that, excellent use of the fallacy. Nobody has calculated "part" of a share. What I was saying earlier, getting accused of gamblers fallacy in the process, is that when you statistically are expected to only get a share 80% of the time on a given block, due to the race condition between you finding your share and the pool finding a block, it is FUNCTIONALLY the same (over time) to say it is "AS IF" you lose 20% of your hashpower, or, put another way, 20% of each share/total shares. Different ways of mentally imagining the scenario, each mathematically correct, while technically there is no partial share. What people aren't realizing is that the system is set up to give a rate of x%. That's mathematical. If your rate is below that, for it to become accurate it then has to boost above it. Ex. there are two blocks. The blockchain has a time of 30s. Block 1: 15s Block 2: 30s For the average (average means add all three and divide by the total number) to equal 30 ((15+30+x)/3=30) you would need the last one to be: Block 3: 45s This is an ongoing process. If every block was above 30s, it would be impossible for the average to be 30s. That's just not how math works. The average is the average; if you change it, the average is no longer the average. For some reason, a lot of people here somehow can't grasp that concept. So why does this matter? You have a hash rate that statistically will take 1m to submit a share. A block is found in 30s. Statistically, you will submit a share on a very small number of the blocks. For every block you DO submit one on, statistically speaking there are a MINIMUM of two more that you didn't. Why? Block 1: 60s Block 2: x Block 3: x (60 + x + x) / 3 = 20, x = 20 If the block took longer than 60s to be found, the number of blocks you would miss would go up even more. Let's say one was two minutes: (120 + x + x + x + x + x) / 6 = 20, x = 20 Now you got a submit on one block but you missed 5 more in the process. In other words, STATISTICALLY (mathematically proven, by the sheer nature of what an average is) you will always lose more than you gain. There's no other possible way to view it. If it were any other way, the average would no longer be the average and the entire concept of Bitcoin (and its derivatives) would be thrown out the window as being a failed concept.
|
|
|
I'll ask again since nobody replied the last time...
If difficulty doesn't matter, why do pools even have a choice on what difficulty to go with? Why is there VarDiff? Since difficulty is meaningless, people who spent all the time developing those systems (as well as those who implemented them into their miners) wasted their time on something that supposedly means absolutely nothing.
Since difficulty has no real value, every pool/miner should be set at a hard-coded 1024 or 2048 or (insert difficulty here). We clearly have no need for more than one option.
|
|
|
Making a transaction now has a cool progress bar thanks to NProgress So now we can watch in agony as our Bitcoins are sucked from our wallet into someone else's? YES! o.O. That's like buying something from the store and the cashier having to wave your money in your face and do a dance with it before they finally take it away, never to return to you. Now I'm depressed, . Look for the lawsuit in the mail for induced depression and the pain & suffering associated with it. ALL UR BITCOINS R BELONG TO ME!
|
|
|
I was able to submit 3 pieces of writing for this round (verified via the analytics files) which accumulate to more than 1,000 words. Each piece had 1 unique page view. However I am not on the receiver list. Can someone clarify why that is?
What's your username there? I don't see you on the list... I am the first one on the list, http://devtome.com/doku.php?id=wiki:user:devguy (Apheration) Please send Alyssa85 a pm here for further clarification (you're in her group).
|
|
|
I was able to submit 3 pieces of writing for this round (verified via the analytics files) which accumulate to more than 1,000 words. Each piece had 1 unique page view. However I am not on the receiver list. Can someone clarify why that is?
What's your username there? I don't see you on the list...
|
|
|
Forgot the /2 part, because you'll be at a random point of progress on the share each time a block changes, averaging to half complete
The is the point of misunderstanding. There is no progress. Each hash is an independent random trial. If you only do one hash per block, that hash has the same chance as a hash done by a miner with the strongest rig. He will do many more hashes, so will have higher odds, but each hash, done by anyone is equal. GPUs and (probably) ASICS have a "scan-time". They can't do one hash. They have to lots of hashes all at once. The scan time is how long to do an entire run. The lost hashing power is something like (network latency + scan-time/2) / (block time) There technically IS a progress. If you flip a quarter 50x you can expect that you will get heads 25x and tails 25x. If you got heads 49x, you can reasonably expect that over the next hundreds/thousands/millions you will end up getting more tails than heads because statistically they should be about equal. The same thing here. If you had a lot of 10s blocks when the average should be 30s, you can reasonably expect that you are going to have an equal number of 50s blocks. Otherwise the AVERAGE is lower than the average; you can't possibly have a lower average than average. That's like saying 2=6. It's just not mathematically possible.
|
|
|
No. This "loss/waste of hashpower" happens both when we change coins AND when a block changes. In that said 5-10 minutes, we might burn through 4-5 blocks, or we might get 1 block, or none, or whatever, depending on the coin.
Okay, I think I see what you are saying but if you average a share every minute and you are on a 15s average block coin, and they mine this coin for 5 minutes then the difficulty doesn't matter. 5 minute duration 512 difficulty - 1 minute/avg - 5 shares 256 difficulty - 30 second/avg - 10 shares (worth half of the 512 difficulty shares in terms of payout value) Whether your average share time is greater than the average block time doesn't matter. They both start at zero and have a chance to hit with every second that ticks. Just because the clock ticked 59 times and you didn't get a share, it does not mean that the 60th time has any higher chance to hit than the 1st. No, when the block changes you lose all progress on that block that didn't get included in a share. Thats where the waste comes in. You are half way through a share when the block is found, the "half" share that you have just gets thrown out. Say you cut the diff in half. Guess what? That half a share that got thrown out? Thats ONE share now, and it gets submitted, and you get credit for it. This. I don't see why people keep trying to say difficulty doesn't matter. If it didn't, why is there even a difficulty to begin with? Why is there VarDiff? If all of this were really irrelevant there would be no need for any of that.
|
|
|
I am still staying out of this converstaion as I REALLY dont understand it all..
But one thing someone said a few pages back that I did not understand that I would like to understand is someone said something like H20 dont care as he will make the same no matter what.. What does that mean exactly? Is not what H20 makes based on what we make and if we make more he makes more?
When you find a block it is submitted instantly (this is unrelated to "shares"). Therefore it doesn't matter whether difficulty is 1 or 50 billion, if anyone finds a block it is submitted. The only people affected by difficulty are the miners, since the same number of blocks are submitted regardless (and his fee is therefore the same regardless). Hope that clarifies that point.
|
|
|
Just because it AVERAGES a certain time does not mean that it MUST TAKE that same time.
Example: Calculations say that you should get a block once every 2 hours. You mine for 6 hours and hit 3 blocks. Every single block hits EXACTLY 120 minutes apart. This is typical behavior of mining, right? No? Well hell, how could that be?!
Average: calculated by adding a group of numbers together and dividing the total by the amount of numbers You're basing your views on a short period of time. Just because someone won the lottery with a single ticket in no way means everyone who buys one ticket is going to win the lottery. It means ONE person did on their first try. Learn what averaging is: Average block time is 30s Someone finds block in 15s. To equal this out, a block will statistically take 45s. If you're submitting blocks every minute or so (on *average* -- seriously, you need to look that word up) on a block that has a 30s block generation time *on average* -- again, look this word up -- you're getting screwed. This is basic mathematics. Just because you want to use this flawed vision that "it doesn't matter because it's just the lottery" is irrelevant. It is what it is. Take some classes on statistical probability and maybe you'll start to understand what words like "average" mean and how they relate to things, because as it is you're pushing your ignorant ideas on to others who know better. Math doesn't lie; people do.
|
|
|
The exact same thing applies to mining in a pool with different difficulties. Diff 512 or 128 does not matter. On average, you will get paid the same. It does not really matter if you submit 10 x "512-shares" or 40 x "128-shares" (conceptually).
Your "concept" is highly flawed. If you submitted 10x 512-shares and 40x 128-shares, they WOULD be equal. But here's how it works: Scenario A: 128 A 07:41 128 A 07:42 128 A 07:43 128 A 07:44 128 A 07:45 128 A 07:46 128 A 07:47 128 A 07:48 128 R 07:49 Scenario B: 512 A 07:44 512 R 07:49 What's the difference here? With A you got 8x 128 submitted on time. That gives you a share count of (128*8=1024). With B, you got 1x 512 submitted on time. That gives you a share count of (1*512=512). Therefore, while your GPU's worked at the SAME speed, you got half the share count. Now, on things like LTC where the block time is large anyways, this is not such a big problem. But let's look at a fast-block coin: Scenario A) fast miner: 512 A 08:13 B1 512 A 08:13 B2 512 R 08:14 B3 512 A 08:14 B4 512 A 08:14 B5 512 R 08:14 B6 Now a slow miner: 512 R 08:14 B1 512 R 08:15 B2 512 R 08:15 B3 512 R 08:16 B4 512 R 08:16 B5 512 A 08:17 B6 The fast miner got credit for 4/6 blocks. The second miner got credit for 1/6 blocks. Therefore the slower miner is being screwed out of the vast majority of all earnings. For 5/6 of these blocks, the slow miner got absolutely nothing, despite using power and wear&tear on their GPU.
|
|
|
Update! Dot.tk is still offline. Lucky for you guys, this is actually a good thing. There are a couple things coming as a result of this:
1) I am moving to a real domain (yep, you read that right!) 2) CoinFaucets is going through a massive overhaul in how it works (spoiler alert: the new system will support *all* faucet types on a single system; simply click a button to go from one faucet type to another! For example, FTC, BTC and LTC).
I expect to have the new site done "soonish" and when it is, I will be announcing the resurrection of the greatest Faucet Rotator there is! Essentially the site is being re-written from the ground up so I can add the features people have been asking about, :p.
Thanks for your support, all!
|
|
|
|