Couple of infinite orders on NH and WH. They had ramped up to about 9PH earlier  . At current speeds about 3-4 more hours on the rental. |
|
|
|
I will try 118%
| User Name | Low Percentage | High Percentage | | justchillz | 49.90% | 50.89% | | Songminer | 61.28% | 62.27% | | zachmonroe | 85.30% | 86.29% | | rozo | 88.00% | 88.99% | | bit5norba | 90.00% | 90.99% | | dennishh | 91.00% | 91.99% | | borachinua | 92.00% | 92.99% | | mikestang | 93.00% | 93.99% | | philipma1957 | 94.00% | 94.99% | | apederzoli | 95.00% | 95.99% | | bctmke | 96.30% | 97.29% | | GoJonnyGo | 98.00% | 98.99% | | controlhosting | 99.00% | 99.99% | | traxor | 100.00% | 100.99% | | wardie | 101.00% | 101.99% | | dsppage | 102.00% | 102.99% | | abmonstein | 103.00% | 103.99% | | eghigo | 104.00% | 104.99% | | vh | 105.00% | 105.99% | | LASERminer | 106.00% | 106.99% | | YuenglingDude | 107.00% | 107.99% | | carlsberg112 | 108.00% | 108.99% | | OneInchWonder | 118.00% | 118.99% |
|
|
|
|
Glad to help  |
|
|
|
Ok... you need to put in your pool account name dot worker name. For example, on my pool, my username is "jonnybravo" and a worker I have is "rental" (yes, I know, creatively named). So, to test this, I must put Your worker name must exist on the pool, to pass the verification. The password you enter must also match. |
|
|
|
Hi, I am having a problem with the Pool Verificator, it fail everytime!!! "Received authorization result... Error: Failed to authorize. Wrong username or password." The user and password are the one registered in the pools. It happens for each pools I try to verify! I put there the user and password registered for the pools Example for http://www.bravo-mining.com/index.php I put my login and password details What's wrong? Since you're asking about my pool, let me try to help you. Can you provide me your username on my pool? Also, we probably want to move this discussion to my pool's thread: https://bitcointalk.org/index.php?topic=1330452.0 because I know the pool verification function works:  |
|
|
|
put me in for 108%-108.99% ..
carlsberg112
| User Name | Low Percentage | High Percentage | | justchillz | 49.90% | 50.89% | | Songminer | 61.28% | 62.27% | | zachmonroe | 85.30% | 86.29% | | OneInchWonder | 86.30% | 87.29% | | rozo | 88.00% | 88.99% | | bit5norba | 90.00% | 90.99% | | dennishh | 91.00% | 91.99% | | borachinua | 92.00% | 92.99% | | mikestang | 93.00% | 93.99% | | philipma1957 | 94.00% | 94.99% | | apederzoli | 95.00% | 95.99% | | bctmke | 96.30% | 97.29% | | GoJonnyGo | 98.00% | 98.99% | | controlhosting | 99.00% | 99.99% | | traxor | 100.00% | 100.99% | | wardie | 101.00% | 101.99% | | dsppage | 102.00% | 102.99% | | abmonstein | 103.00% | 103.99% | | eghigo | 104.00% | 104.99% | | vh | 105.00% | 105.99% | | LASERminer | 106.00% | 106.99% | | YuenglingDude | 107.00% | 107.99% | | carlsberg112 | 108.00% | 108.99% |
|
|
|
|
Hooray for more SPV mining fails... 408985 found by f2pool. 1569 tx, 25.22660666 BTCSame block found by my pool? At least 1641 tx and 25.23727213 BTC408986 found by Antpoo. 0 tx, 25 BTCSame block found by my pool? At least 211 tx and 25.04135543 BTC408987 found by bw. 0 tx, 25 BTCSame block found by my pool? At least 285 tx and 25.05622531 BTC2016-04-26 11:18:34 CreateNewBlock(): total size 998940 txs: 1641 fees: 23727213 sigops 5368
2016-04-26 11:18:39 UpdateTip: new best=00000000000000000137eab0f9dedc02db8ae78e62e6d8c1270f77adcd611c57 height=408985 log2_work=84.553381 tx=124843469 date=2016-04-26 11:17:57 progress=1.000000 cache=48.0MiB(8600tx)
2016-04-26 11:18:39 UpdateTip: 5 of last 100 blocks have unexpected version
2016-04-26 11:18:39 CreateNewBlock(): total size 289324 txs: 209 fees: 4121303 sigops 687
2016-04-26 11:18:41 UpdateTip: new best=00000000000000000101d9f2ac2d869085bb8726e1be5bc490c4d7cc9027bbb9 height=408986 log2_work=84.55342 tx=124843470 date=2016-04-26 11:18:38 progress=1.000000 cache=50.8MiB(9781tx)
2016-04-26 11:18:41 UpdateTip: 5 of last 100 blocks have unexpected version
2016-04-26 11:18:41 CreateNewBlock(): total size 289922 txs: 211 fees: 4135543 sigops 691
2016-04-26 11:18:56 UpdateTip: new best=000000000000000003293f83e0f81bb907923af1867a0a85f85becbd2af4e74f height=408987 log2_work=84.553459 tx=124843471 date=2016-04-26 11:18:46 progress=1.000000 cache=50.9MiB(9876tx)
2016-04-26 11:18:56 UpdateTip: 5 of last 100 blocks have unexpected version
2016-04-26 11:18:56 CreateNewBlock(): total size 347969 txs: 285 fees: 5622531 signs 981
Stop mining at pools that SPV mine and produce empty blocks. Point your hash here where you get more coins for your time. |
|
|
|
My new guess is 107% (hopefully discovered before this)
| User Name | Low Percentage | High Percentage | | justchillz | 49.90% | 50.89% | | Songminer | 61.28% | 62.27% | | carlsberg112 | 83.30% | 84.29% | | zachmonroe | 85.30% | 86.29% | | OneInchWonder | 86.30% | 87.29% | | rozo | 88.00% | 88.99% | | bit5norba | 90.00% | 90.99% | | dennishh | 91.00% | 91.99% | | borachinua | 92.00% | 92.99% | | mikestang | 93.00% | 93.99% | | philipma1957 | 94.00% | 94.99% | | apederzoli | 95.00% | 95.99% | | bctmke | 96.30% | 97.29% | | GoJonnyGo | 98.00% | 98.99% | | controlhosting | 99.00% | 99.99% | | traxor | 100.00% | 100.99% | | wardie | 101.00% | 101.99% | | dsppage | 102.00% | 102.99% | | abmonstein | 103.00% | 103.99% | | eghigo | 104.00% | 104.99% | | vh | 105.00% | 105.99% | | LASERminer | 106.00% | 106.99% | | YuenglingDude | 107.00% | 107.99% |
|
|
|
|
|
All,
The Datacenter in which my US database servers and backup bitcoin daemons are hosted has gone offline. I am working with the technicians to get an ETA of restored service.
In the meantime, I have shut down the US and EU stratum servers, so your miners/rentals will failover/report dead.
As soon as I know more, I'll post here.
Jonny
EDIT: apparently one of the network switches went down. They are working on resolving everything. As I find out more, I will update here.
EDIT2: And we're back in business. All servers are functioning as expected. Sorry for the downtime, folks.
|
|
|
|
Now that I've explained shares, let's take a look at the different reward mechanisms used by pools. When the pool finds a block, it has to be able to properly compensate the miners for their contributions. There are a number of mechanisms by which pools determine each miner's portion of the block reward. The three most popular methods are PPS, PROP and PPLNS. PPS means "pay per share". PROP means "proportional" and PPLNS means "pay per last N shares". Yes there are other variants out there, and I encourage you to research them. PPSThis payout mechanism pays out miners for every single share they submit. Very few pools offer this, and if they do, they charge their miners some pretty hefty fees. Why? Because all of the risk is on the pool operator. Regardless of whether or not a pool finds a block, the pool must be able to compensate its miners. Orphans, stales, bad luck rounds. These all mean the pool operator has to cover the expenses of paying miners from funds other than those generated by a block reward. As you can imagine, it becomes expensive very quickly. Have a 200% round? The pool operator better have an extra 25 BTC hanging around so the miners can be paid. PROPPopular with the alt coin pools, and newbie pool operators who don't know any better, this payout mechanism pays miners out according to how many shares they have submitted for a round. Here, a round is defined as the number of shares it took to find a block. So, you're asking yourself, "why is that so bad?". Let's take an extreme example. The pool has 10 miners contributing to it. The pool has just found a block, and starts accepting work on a new block. The very first share submitted by a miner solves this next block. According to PROP, that one miner reaps the entire block reward. Sure, he's happy, but the rest of the miners are not. Very often you will hear the term "pool hopping" associated with this payout mechanism. PPLNSLike PROP, this payout mechanism uses a ratio of miner shares to pool shares when determining the miner's compensation. However, unlike PROP, the shares cover more than one round. In my pool's case, the number of payable shares is equal to five times the current network difficulty. This value is the "N", and is a rolling window of shares that are payable. Each share has the potential to be paid out more than once, once, or even not at all. For example, because the last three blocks on my pool were found in well under the expected difficulty, every miner's shares were paid multiple times. This is, by far, the fairest mechanism for distributing block rewards to miners. It discourages pool hopping because of the "N" value. It gives miners the opportunity to make far greater than expected values for a given hash rate by the rolling window of shares being paid multiple times. OK... I've rambled on enough. Back to your regularly scheduled programming |
|
|
|
So, I posted this a while ago in -ck's solo pool thread when somebody asked about shares. Since I just got a PM from a miner on my pool asking about shares and how they relate to payments, I thought I'd post it again here. When you mine on a pool, you combine your hashing power with the other members of the pool in an attempt to solve a block. So, what are these shares? Well, mining hardware knows how to do exactly one thing: provide potential block solutions by performing double SHA256 hashes. Each execution of that function produces a result. For example, an Antminer S7 miner executes this function roughly 4.75 trillion times a second. This is the number you see when looking at a miner's hashing power. Usually it is expressed in values like "terra hashes per second (TH/s)". That S7 is about 4.75TH/s. Now, the vast majority of those shares are useless - they'll never possibly solve a block. Since we don't want to flood the network, or a pool, with such a giant amount of useless data, we assign an accepted minimum value that must be provided by the miner as a potential block solution. That value is referred to as a "difficulty 1 share". At any rate, you can use math to figure out how long you would expect it to take to find that baseline share (diff 1). The formula for doing so can be simplified to: 2^32 / hashrate = time to find a diff 1 share
Applying that formula, you can easily calculate that your S7 expects to find a diff 1 share every 0.00090420364126 seconds. Inverting that gives you how many diff 1 shares per second your S7 should find: 1105.94555735974321. Now that you have this, and you know the current network difficulty, you can figure out the expected time to solve a block: current diff / shares per second = time in seconds to find a block
Again, using the S7 as an example, at the current difficulty, you would expect to find a block after hashing for 161561576.41029279010546 seconds. Convert that into days and you'll see an S7 would expect to take 1869.92565289690729 days to find a block. Given this information, you can then figure out what your expected daily earnings are for an S7 because you know the current block reward is 25 BTC. Simply take 25 and divide it by the number of days to solve a block and you'll get 0.01336952 BTC a day. Putting all that together into a single formula: 25 / (current diff * 2^32 / hashrate / 86400) = expected earnings per day
If you want the more advanced version of that formula (one that doesn't approximate a diff 1 share to 2^32), here it is: (reward / (2^256 / (((2^224 - 2^208) / difficulty) * hashrate))) * 86400 = expected earnings per day
Now, with the math out of the way, you can see that even storage of difficulty 1 shares would be an absurd amount of data to track. This is where the concept of variable difficulty comes into the picture. The pool really wants to track only a certain number of shares per second. Looking above, you can see that the S7 produces over 1100 difficulty 1 shares per second. However, if I increase that difficulty, the expected number of shares per second decreases. Since I know I want to get, for example, 10 shares per minute, the pool simply changes the difficulty of accepted solutions to try and achieve that. Hope this helps you understand how shares work in a pool. |
|
|
|
That's the spirit! |
|
|
|
Johnny is it possible to change my guess from 104% to 84.3% (I did not notice that gap when I did the guess) so maybe I can toss 1-2PH for a couple of hours since I missed my spot last night. If no, it's not a problem. Thanks.
As much as I hate to see the open spot, I can't allow the change because it would be less than 10% higher than your previous guess.
I would not worry about forcing constant hashing it might be really hard to track it.
Cause a bad vibe if a winner loses due to a black out or something.
Yea, that's why I added the caveat of Johnny decides and his decision is final. He should be able to look at the pool logs and quickly determine if a user was mining here "full time" or not during the round. Blackouts and downtime do happen, so he can make the decision if the winner put the effort toward the pool to deserve to win. That's correct. There are factors beyond anyone's control: your power goes out, internet connection dies, pool downtime, etc. I will be examining the logs to determine the eligibility of any potential winner. I understand that everyone of you is taking a chance pointing your hash here. The pool is currently pretty small, and as a result, the variance you're going to experience while the pool is growing will be quite noticeable. I also realize this is an inherently tough market to break into as there are fewer and fewer home miners, and the vast majority of miners have already formed opinions about where they point their hash. These contests and giveaways are meant to be fun for everyone, and to attract, and most importantly keep, people mining here regularly. The more the base hash rate grows, the less variance will be experienced by miners. Less variant payouts make everyone happy . |
|
|
|
pick update to 106% pls
Done 98.5
Already taken - you get a range of 1%. Your available options at this point are 84.30 - 85.29 or anything above 107. | User Name | Low Percentage | High Percentage | | justchillz | 49.90% | 50.89% | | Songminer | 61.28% | 62.27% | | carlsberg112 | 83.30% | 84.29% | | zachmonroe | 85.30% | 86.29% | | OneInchWonder | 86.30% | 87.29% | | rozo | 88.00% | 88.99% | | YuenglingDude | 89.00% | 89.99% | | bit5norba | 90.00% | 90.99% | | dennishh | 91.00% | 91.99% | | borachinua | 92.00% | 92.99% | | mikestang | 93.00% | 93.99% | | philipma1957 | 94.00% | 94.99% | | apederzoli | 95.00% | 95.99% | | bctmke | 96.30% | 97.29% | | GoJonnyGo | 98.00% | 98.99% | | controlhosting | 99.00% | 99.99% | | traxor | 100.00% | 100.99% | | wardie | 101.00% | 101.99% | | dsppage | 102.00% | 102.99% | | abmonstein | 103.00% | 103.99% | | eghigo | 104.00% | 104.99% | | vh | 105.00% | 105.99% | | LASERminer | 106.00% | 106.99% |
Picks updated. Good luck everyone! |
|
|
|
101%  Welcome aboard. Well, that was a good try with about 7ph, no dice. That said please put me down for 102%
Thanks
Yeah, was fun to see the pool spike up to over 7PH . It also showed just how quickly 1% passes when you drop the hammer like that. Edit: I guess that would be 104% since 101% is already taken by wardie777 | User Name | Low Percentage | High Percentage | | justchillz | 49.90% | 50.89% | | Songminer | 61.28% | 62.27% | | LASERminer | 79.50% | 80.49% | | carlsberg112 | 83.30% | 84.29% | | zachmonroe | 85.30% | 86.29% | | OneInchWonder | 86.30% | 87.29% | | rozo | 88.00% | 88.99% | | YuenglingDude | 89.00% | 89.99% | | bit5norba | 90.00% | 90.99% | | dennishh | 91.00% | 91.99% | | borachinua | 92.00% | 92.99% | | mikestang | 93.00% | 93.99% | | philipma1957 | 94.00% | 94.99% | | apederzoli | 95.00% | 95.99% | | bctmke | 96.30% | 97.29% | | GoJonnyGo | 98.00% | 98.99% | | controlhosting | 99.00% | 99.99% | | traxor | 100.00% | 100.99% | | wardie | 101.00% | 101.99% | | dsppage | 102.00% | 102.99% | | abmonstein | 103.00% | 103.99% | | eghigo | 104.00% | 104.99% | | vh | 105.00% | 105.99% |
Picks updated. Good luck everyone! |
|
|
|
| User Name | Low Percentage | High Percentage | | justchillz | 49.90% | 50.89% | | Songminer | 61.28% | 62.27% | | LASERminer | 79.50% | 80.49% | | eghigo | 80.50% | 81.49% | | dsppage | 81.90% | 82.89% | | carlsberg112 | 83.30% | 84.29% | | zachmonroe | 85.30% | 86.29% | | OneInchWonder | 86.30% | 87.29% | | rozo | 88.00% | 88.99% | | YuenglingDude | 89.00% | 89.99% | | bit5norba | 90.00% | 90.99% | | dennishh | 91.00% | 91.99% | | borachinua | 92.00% | 92.99% | | mikestang | 93.00% | 93.99% | | philipma1957 | 94.00% | 94.99% | | apederzoli | 95.00% | 95.99% | | bctmke | 96.30% | 97.29% | | GoJonnyGo | 98.00% | 98.99% | | controlhosting | 99.00% | 99.99% | | traxor | 100.00% | 100.99% | | abmonstein | 103.00% | 103.99% | | vh | 105.00% | 105.99% |
Picks updated. Good luck everyone! |
|
|
|
new guess : 105%.
the percentage being close to each other seems fine as long as it was picked well in advance.
it seems to me gap of .2% is fine as long as folks are picking into the future, -gt 10% of the current share %.
that leaves it open to luck plus some space for rental without someone sneaking in while you're renting.
within 5-10% of your guess, you'll know know the percentage layout is now fixed and how to best structure rentals.
edit: i think an extended fair way is to earn .1% buffer credit per your 24h hash rate up to 1% or n%, but that may be getting a little complicated to manage.
Interesting thought on the "earn a buffer for every X days of constant mining". Would definitely be a bit of a pain to manage... but would add an interesting flair to things. Hmmm... | User Name | Low Percentage | High Percentage | | abmonstein | 47.00% | 47.99% | | justchillz | 49.90% | 50.89% | | Songminer | 61.28% | 62.27% | | LASERminer | 79.50% | 80.49% | | eghigo | 80.50% | 81.49% | | dsppage | 81.90% | 82.89% | | carlsberg112 | 83.30% | 84.29% | | zachmonroe | 85.30% | 86.29% | | OneInchWonder | 86.30% | 87.29% | | rozo | 88.00% | 88.99% | | YuenglingDude | 89.00% | 89.99% | | bit5norba | 90.00% | 90.99% | | dennishh | 91.00% | 91.99% | | borachinua | 92.00% | 92.99% | | mikestang | 93.00% | 93.99% | | philipma1957 | 94.00% | 94.99% | | apederzoli | 95.00% | 95.99% | | bctmke | 96.30% | 97.29% | | GoJonnyGo | 98.00% | 98.99% | | controlhosting | 99.00% | 99.99% | | traxor | 100.00% | 100.99% | | vh | 105.00% | 105.99% |
Picks updated. Good luck everyone! |
|
|
|
Yes, obviously if the pool is down for any reason, that time would not count against you As stated earlier, I'm still working on how the contest will run in future incarnations. I like the suggestions so far, and the discussion is helping to identify potential gotchas and to provide some good insights. My new guess will be 100% -- and I hope the block is solved prior to that...
| User Name | Low Percentage | High Percentage | | abmonstein | 47.00% | 47.99% | | justchillz | 49.90% | 50.89% | | Songminer | 61.28% | 62.27% | | vh | 75.00% | 75.99% | | LASERminer | 79.50% | 80.49% | | eghigo | 80.50% | 81.49% | | dsppage | 81.90% | 82.89% | | carlsberg112 | 83.30% | 84.29% | | zachmonroe | 85.30% | 86.29% | | OneInchWonder | 86.30% | 87.29% | | rozo | 88.00% | 88.99% | | YuenglingDude | 89.00% | 89.99% | | bit5norba | 90.00% | 90.99% | | dennishh | 91.00% | 91.99% | | borachinua | 92.00% | 92.99% | | mikestang | 93.00% | 93.99% | | philipma1957 | 94.00% | 94.99% | | apederzoli | 95.00% | 95.99% | | bctmke | 96.30% | 97.29% | | GoJonnyGo | 98.00% | 98.99% | | controlhosting | 99.00% | 99.99% | | traxor | 100.00% | 100.99% |
Picks updated. Good luck everyone! |
|
|
|
|
Yeah, you bring up good points. I haven't set anything in stone yet. Maybe we do 2 picks. Maybe you have to be mining the entire round to qualify.
|
|
|
|
Yup... You get the larger range |
|
|
|
|
Show Posts
