|
962
|
Bitcoin / Pools / Re: [20 PH] ** 5x AVALON6 GIVEAWAY ** Kano CKPool (kano.is) [0.9% PPLNS] US,DE,SG,JP
|
on: February 09, 2016, 06:07:08 AM
|
Eligius tried to place 577 transactions into it but we won and placed 1156 transactions in the block. Double the transactions inserted and still won the race!
That's a great point, it's too bad that in close orphan races the number of transactions doesn't factor in. It would be a shame in any case, regardless of who was racing who, to have a block with less transactions beat out a block with more. |
|
|
|
|
965
|
Bitcoin / Pools / Re: [∞ YH] solo.ckpool.org 1% fee solo mining USA/DE servers 154 blocks solved!
|
on: February 03, 2016, 05:42:40 PM
|
Hmm that reminds me I've had this problem before. If you authed first on the DE pool you cannot auth on the main pool later on. I thought I'd fixed this bug but it seems to have returned. That would explain it. I'll look into it.
Is this related to a bug I posted about a couple weeks ago? Well, I guess I don't know if it's a bug or a flaw in the way the miner operates, but just wondering. The IP address of solo.ckpool.org changes after a DDoS and perhaps these devices almost never look up the IP address using a cached result for ages. In which case a restart might be required, either of cgminer or the whole device.
I have restarted the whole device 3 times (one of those was power off for 20+ minutes) and it still is in failover, I'll see if I can't flush its dns cache or something, thanks. I had the same bug a couple of weeks back, all I had to do was change the address I was mining to.
I could not locate any sort of dns reset in the S3 interface so I tried changing addresses and the pool was ALIVE again. I changed back to the old address thinking maybe I had cleared up the issue, but the old address reports the pool as DEAD. A new solo address for the US node it is then! Problem solved, thanks. |
|
|
|
|
969
|
Bitcoin / Pools / Re: [18 PH] ** 5x AVALON6 GIVEAWAY ** Kano CKPool (kano.is) [0.9% PPLNS] US,DE,SG,JP
|
on: February 02, 2016, 11:27:41 PM
|
I have now an amount of a little more than 30000 satoshi dust...when can my investors hope to see it in their poket?
When it's worth more than $1 Is there a way to see a total dust amount that has accrued in our account, or do we just need to manually add it up from the payments page? I just added mine up and I have 0.00531421 btc in dust outstanding, worth almost 2 whole dollars! This is actually more than a single S3 will earn per block on the pool right now. When it gets to 0.1 I might ask to have it sent to me, but less than that I don't see value in it just yet. I will have been mining at kano.is for 1 year on March 5. Well, March 5 is the first block I received a payment for, so probably started a day or two sooner.  I hope finding co-miners who are in the same situation than me...
I'm in that situation, since the pool has grown I'm just a dust miner that points a bit of "free electricity" hash to the pool, but I'm banking on the fact that one day btc will be worth a lot more than today, and at that time Kano will have figured out an expedient way to send out all the dust and we will all get a nice surprise in our wallets. The nice thing is that even running my S3+ for only a day for the Ava6 contest I'm going to receive payments for several blocks now until my average drops back down. kano just a little more above explained me that dust is paid if the amount of dust is worth $1
I think you need to re-read it, because that it not what he said. Don't expect to receive a dust payment from kano any time in the near future... |
|
|
|
|
971
|
Bitcoin / Bitcoin Discussion / Re: Bitcoin Core version 0.11.2 released
|
on: February 02, 2016, 11:15:34 PM
|
If there is no entry in the debug.log you might have to look at OS log files to find the reason for the crash. Lets hope its not needed.
Hopefully not, it's almost done syncing the blockchain... again... Funny thing it, core crashes very rarely while it's syncing, crashes much more often when it's up and running up-to-date. And never has a crash while syncing resulted in a corrupted file. |
|
|
|
|
975
|
Bitcoin / Hardware / Re: [Guide] Dogie's Comprehensive Bitmain Antminer S3 Setup [HD]
|
on: February 01, 2016, 01:02:32 AM
|
My S3 is set to factory default of 192.168.1.99 but I cannot connect to it via the browser using a direct connection to my pc.
What should my PC settings be?
Your pc must have an IP address of 192.168.1.XXX to be able to bring up the web gui interface. Or you must change the IP address on the S3 to be YYY.ZZZ.WWW.XXX where the YYY.ZZZ.WWW parts all match your PC. |
|
|
|
|
977
|
Bitcoin / Pools / Re: Lifetime pool luck for antpool vs kano.is or why aren't you mining with kano.is
|
on: February 01, 2016, 12:53:54 AM
|
|
This is a fascinating thread (well, as fascinating as statistical discussion go), thanks for starting it, Phil. I posted something to this effect in the Antpool thread when I first got into bitcoin about a year ago, I just couldn't understand why so many people where pointed to that pool (which only exists for Bitmain's benefit) when there were so many better choices out there, and even a year ago before I knew what I do today I figured out that kano.is was coded and run how a pool should be. I'm glad to see that reasoning is finally spreading its way out to the masses.
|
|
|
|
|
978
|
Bitcoin / Hardware / Re: ANTMINER U3 Discussion and Support Thread
|
on: February 01, 2016, 12:48:00 AM
|
|
I agree, the R1 with Crazyguy's firm ware was the only definitive thing that ever made a difference in my experiences with U3. They are so random how they behave, different for almost everybody, and even the same unit will behave different for one owner is the same setup. I had one that wouldn't hash, then it would, then it only would hash with 20% error, then it was fine again and the whole time I never did anything different to it.
|
|
|
|
|
Show Posts
