|
This pool is NOT running bitcoin XT, in case you're interested.
|
|
|
|
|
I suspect the bulk of the pools feel the way Kano and I do: We're all in favour of bigger blocks but most of us don't want XT and are not adopting it. We're waiting in the vain hope core dev gets off its arse and increases block size itself.
|
|
|
|
Everything would be fine, if pools simply sent out diff before first job. How hard is it to do that?
Oh wait... maybe the problem is that your own ckpool implementation DOESN'T do that thus doesn't follow stratum specifications.
Are you having fun yet? I guess you really never want this change merged in any form with that attitude. Remember you're the only proxy pool that is affected in any beneficial way due to constantly dropping connections and switching upstream pools and changing diff too often as a result. I guess I'll leave you to talk to Kano instead. |
|
|
|
Finally a responds from a Staff member, and then it is a meme?
Great job, you guys are doing, very professional ...
That's because there are already dozens of threads about this already. See any thread about Theymos censoring XT and so on... |
|
|
|
The cgminer has the "bug": apply the difficulty for current job: so L2 job has 1042 sharediff. this conflict with mining doc. Solutions: - fix the doc: "Applied to Every Next Job" -> "Applied to Every Current Job"
- fix cgminer (with the patch) and fix your pool: send the set_difficulty first and mining.notify next
Since Kano so often is so eloquent with his explanations (heh) I may as well elaborate. The issue is that following the standard destroys the startup of many devices by using diff1 until the next stratum update. Most of the low power controllers (like those in antminer S*) fall over trying to create that many shares and just about every pool would be seriously annoyed to get every miner sending their first 30 or 60 seconds of shares at diff1, especially with 5+ TH miners available. All pools would be affected by this. This is what I meant by the default behaviour of cgminer since stratum was first added is "robust". If you want to add the old/next diff idea back in you need to add a workaround for startup that veers off the standard. Standards are fine and all but real world workarounds for problems with the standard are essential (and a huge part of making cgminer practical solutions for today's mining). |
|
|
|
...bound to be faked. Don't be fooled by bullshit like that, even if you agree with what that person says. |
|
|
|
Hello,
Is there a problem with the stats? My hash-rate is 0 while the machine is fully pointed to the pool.
Thanks.
Nope, everything's working fine. Have you just started mining with a low hashrate device? It can take a while to get any shares and the diff adjust at the pool if you have something under 500GH. |
|
|
|
Thank you.
Do you know which pool software give the ability to point it to other pool?
ckpool in proxy mode can be pointed at another pool or a p2pool node |
|
|
|
|
One thread on this irrelevant tech is enough. /locked
|
|
|
|
Halo everyone,I using Dell R310 server Windows server 2012. When i try to run GUIminer.exe in solo mining, Why it shows nothing to mine on?? pls help me..
You resuscitated a 4 year old post for dead software doing dead mining that no one does today... you cannot mine bitcoin with CPUs or GPUs or guiminer in any meaningful fashion let alone in solo mode. Please do more reading. |
|
|
|
|
My point was the extra hashrate is likely luck chasers fooled by the clustering illusion, probably rentals.
|
|
|
|
Appreciated since 4.9.2 has been the stable release for a while and will be for some time to come, I expect. |
|
|
|
Hey, since yesterday i can't connect to any pool on my RPi using cgminer and two Antminer U3's.
I use this command: sudo ./cgminer --bmsc-options 115200:0.57 -o stratum+tcp://stratum.bitcoin.cz:3333 -u xxx.xxx -p xxx --bmsc-voltage 0800 --bmsc-freq 1286
It always puts out this:
Sorry i'm kinda nooby and i haven't got really good knowledge.
That's a bitmain forked version based on the use of options that don't exist in the official cgminer. You're on the official cgminer forum thread. Use the official cgminer linked in the top post before asking any questions, or seek help elsewhere for bitmain's version, thanks. |
|
|
|
In last year, some news said that it will come in this year, but now it seems to be late, now I would say I will expect it in next year. Just give them time so that they could make sure everything is OK.
Maybe it's some sort of christmas gift? Who knows. Which Christmas? /troll |
|
|
|
This is no more than a clustering illusion https://en.wikipedia.org/wiki/Clustering_illusionIf people are moving their hashrate due to apparent lucky streaks on a pool with a hop-proof pay scheme then they are fooling themselves. Having a huge mining operation does not make people smarter so even the largest mining operations that are using regular pools may be chasing luck. Or it's renters using large hashrates doing the same. |
|
|
|
[2015-08-10 01:03:51] Possible block solve diff 86271098089.769806 !
[2015-08-10 01:03:51] BLOCK ACCEPTED!
[2015-08-10 01:03:51] Solved and confirmed block 369164
Substantial fees indeed. Someone's got to be doing the right thing and be able to confirm as many transactions as possible as fast as possible, and ckpool is the tool to do it with  |
|
|
|
|
Show Posts
