I do know my s5's have never found a bitcoin block in the year I've owned them.
Now i have a s7 pointed here, hopefully it finds a block for the pool someday.
The reality is that an S7 is expected to find a block every 4.7 years under the current difficulty. Think about that for a second. 4.7 years. So sadly, no, your S7 is unlikely to hit a block here (or anywhere). And this is a good illustration of why most miners, especially the smaller ones, prefer pools to solo; a small solo miner can hash for months or years without getting any payout at all. don't be such a bummer. the same s7 would have a 1 in 2 chance in 2.3 years, 1 in 4 in 1.15 year, 1 in 16 every 3.4 months, a 1 in 54 every month, a 1:233 every week. |
|
|
|
I created a second account on kano to keep my rental activity separate from my real iron...is there a way I can pull in the new account workers into my CKPool app with my others?
not yet. lower on the todo queue, but in on todo. |
|
|
|
With growing support from leading companies such as Coinbase which are running various tests to evaluate the efficiency of Bitcoin Classic and the 2 megabyte Classic chain, it is highly likely that the Classic chain could co-exist with the core chain in the future. If this happens, wallet platforms and exchanges will support both chains and verify the transactions from the Core and Classic chains.
However, Coinbase CEO Brian Armstrong recently emphasized that historically, when a split chain occurred, the minority was eliminated in a matter of hours. Armstrong predicts that the same would happen for the Core chain if Classic becomes activated.
Antpool, the largest mining pool, just mined their first #bitcoin classic blockhttps://blockchain.info/block/000000000000000006968c648240001fd7d856f9732646763225b084f72404eb … - classic officially in production there are dozens of versions of bitcoin software, all of which are in production: core will reject classic 2mb. classic will accept core 1mb, can and does generate core 1mb block. at the current pace, anyone tossing out a classic 2mb block will be the minority chain, and will be eliminated in a matter of hours. i always wonder what kind of checks are in place. if someone tosses out a rogue 2mb block, antpool is kind of screwed. |
|
|
|
Well guys, as much as I love mining with my one S7 (and this pool is awesome!!) , 14.5 cents per Kw is just too expensive for me to hang in there. It's really fun watching those payments come in, but alas, my little noise maker is now for sale on eBay via a 3 day auction.  I will keep mining here until it sells and I hope to come back again after the halving if newer, more efficient hardware becomes available. C'mon little S7! Crack a block for team Kano before you get packed up! It's the most efficient miner on the field, in terms of hash to electricity. It will still be in the profit range for a while longer, esp on kano.is. Short of bailing out, I thought i saw somewhere that you can probably run it at half power (non powered boards) to cut your electricity bill in half if that's the only part bothering you. Still a nice upgrade from the S5 in that mode. |
|
|
|
18 blocks in a 1hr period.  edit: just to keep it in the realm on on topic, we did get 2 of the 18. does this burst and silence across the network always been like this or is it a natural effect of increase difficulty? |
|
|
|
3 out of four of the last blocks same user. Rockin' !
should we be suspicious or thankful? suspicious is saved for those with 1+PH and haven't found a block  this is how it should be done. |
|
|
|
|
haha, did he qualify for both ends?
|
|
|
|
|
contest high cdf spot looks like it just opened up. if that s7 has any block busting power, now is the time to activate it.
|
|
|
|
From the article http://www.coindesk.com/bitcoin-price-400-network-disruption/Still, the digital currency experienced sharp gyrations this week amid news that the network was exceeding its capacity for transactions, a development that resulted in users paying sometimes substantially higher fees. We're seeing a lot of delays lately. If block size isn't increase to handle more transactions, it will just come at a cost of higher fees to handle the traffic via prioritizations. Of course I have the option to increase the fees, but I never had to do that before to get it across within 2hrs or less. Dont think just as a miner as we love higher fees for fatter blocks but think of the overall bitcoin market investments. If you're running a business, the delay and sometimes rejection due to delays can have a huge impact on your business, making you think twice about increasing your usage or expanding with bitcoins. It does have a huge impact on the BTC prices when the network is not efficient on handling the growing traffics. I guarantee you, as soon as we get a solution agreed upon, BTC prices will sky rocket. I'm willing to bet the farm on that. Failure to agree on that solution is what's keeping BTC down. P.S How many of you guys are seeing delays of 6-12hrs lately? I'm definitely seeing more and more of that. Even Nice Hash acknowledge that as well as many other companies. back to your original pool related question: https://bitcointalk.org/index.php?topic=789369.msg13566071;topicseen#msg13566071 |
|
|
|
Hi Kano
Slush pool email out to all the members about voting whether to stay at current 1MB, go to 2MB or 8MB Block size. What is your take on this and what direction is the pool going with that? Seems like bitcoin network have been really really slow lately unless people are willing to pay 4x fees or higher and we're already at this 1MB limitation with so many blocks in the 970+KBs. I'm hoping we can get over this hump fast as even a temporary solution of 2MB will help get BTC prices stabilize and hopefully go pass $450 easily. I'm sure you have better idea and directions on this and if you can shed some light for us, would be appreciate it.
the bitcoin network's average bitcoin's block size is mainly heading up because kano.is is solving more blocks.  |
|
|
|
I'm actually Glad that the feature / function is back. I was pinging Zach just about the same thing a few days ago where that 5ND picture wasn't available for my Dashboard. I only had 3 out of the 4 features shown ( Hash rate, workers and percentage of pool but not the one Avg5ND one). Unfortunately it's not very close either. It's about 400TH off on what my payout is.
P.S CONGRATS ON THE BLOCK FINALLY!!! Whew!
5Nd is just a tad over 1day right now. You can hit the api to get a 24h hash to get a decent rough estimate for a while. edit: actually that will probably be the same as what zach is showing. if you are trying to accurately predict future payout, it might not happen. 2nd edit: i can imaging a real time 5Nd per-worker hash will be very difficult to compute (pool hash rate dependent) which is why it's only done on block solve. |
|
|
|
|
notification was just starting to look better too. thought i could look away for a moment and bam. should be okay now. force close out the app and open it again. just in case. my failover logic didn't kick in correctly.
|
|
|
|
Noob question..... What is CDF?
Cumulative Distribution Function (CDF)...it shows the probability that a block will be found after a given number of submitted shares. The faster the block is the smaller that number gets... I believe it's also used as a pool safety check mechanism. Like flipping quarter and looking for a tail. Getting two heads in a row is not uncommon. Actually pretty normal. After 5-6 flips, your CDF approaches 1, where you should have hit at least one tail by now. It will never reach 1, but after 10 flips CDF approaches very close to 1, as a safety mechanism you (or pool owner) start analyzing if you're flipping a rigged double-sided/defective quarter. |
|
|
|
Another nice block with high fees  I like the number 400400 Ok rookie question, how can you tell if it has high fees and what determines if a block has high fees vs a block that has lower fees. Coming from Antpool I never cared about that, but since this pool shares the fees I guess I am interested. Thanks when visiting the block page : https://www.kano.is/index.php?k=pblocksyou'll see rewards over 25. short version: the fees comes from pending btc transactions the pool stuff into the block on solving. here's a link that ck provided once https://data.bitcoinity.org/bitcoin/blocksize/30d?t=lsort by average size descending to see the pools average. better for bitcoin, better for us. |
|
|
|
|
Notification is hosed. Current library i'm using doesn't handle growth well. Please excuse the extra noise or lack of while i sort it out.
|
|
|
|
I didn't receive last 4 blocks notification! this from mine or everyone ?
Thanks for nice app.this is really handy!
well that coincides with my last change. got some other reports that it's intermittent, though it should be identical outside a string length change. log shows messages making their way to the apn handoff. rolled-back last modification until i can trace why apple is not delivering those. |
|
|
|
|
new block detection and notification (beta testing) looks good so far.
releasing with careful supervision.
beta tester will see one less notification, other users will see new format.
|
|
|
|
A stupid question
If I have 1 x S7 with 4.7Th/s hash
and 10 x S3's with 4.7 Th/s hash total
am I theoretically more likely to get a block with the S7 - rather than on any of the S3's?
Is the quality? speed or whatever other better on an S7?
Thanks
others category: electricity cost aside, you can have more options testing out different setups with 10x S3. solo mining one? 10 x S3 will generate more heat during those cold nights. https://bitcointalk.org/index.php?topic=1297331.0electricity cost most likely spoils any leverage they have over the S7. |
|
|
|
Meanwhile Regarding the pool wallet. I've had a good think about how I do it and what changes I could make. It's actually not all that difficult to do as I do already with one change, combine them once a day rather than send each one when it's due. I like the process I have at the moment of checks and balances - that are beyond what many may expect - but I could simply continue that to get to the point where I'm happy with each individual result, but not send the result, then later run another process that picks a set of payouts from earlier in the process and combines them all, once a day. That way I already know they've passed all inspections, and it's just dependent on me creating a new step that can add the earlier data correctly - so dust payouts are combined, and dust only not sent if the combination is below 10k satoshi. Yeah I really don't want a pool bank for everyone, and I think this change would fit in well, and reduce the number of transactions and the payout division caused by our average expected more than one block a day. Any comments? (Edit: if anyone didn't notice, the last address in each payout is the total dust in each, which has always been more than zero except once) misc comments: 1 - if (big if) anyone has been doing independent auditing, then that will be a bit harder to pair in/out via blocktrail BTC(n). i like the way it is now, but okay with either since more daily blocks (eventually) mean more payout to manage and more dust (many of us don't want to accept we're insignificant yet although we see it coming with diff changes). 2 - maybe a good time to also add confirmed payouts to user payment page if this happens? 3 - side note: iphone app's payout notifications will move to optional config soon but could temporarily glitch until i see the new transaction and make a slight adjust for value verification. edit - random idea: if you do keep 1-to-1 as due, maybe you can consider using that last dust address as a get out of jail free card to payout a dust user if > some value. |
|
|
|
|
Show Posts
