To my knowledge, stratum don't keep its socket open(am I wrong?), thus scalability shouldn't be much of an issue here if the computer is fast enough. This could be profiled to get a better idea.
Let me be clear - stratum is not the issue here, it is just a communication protocol for the actual mining and it is NOT stratum or p2pool's stratum implementation that is the problem. You need to get a firm grasp of what is involved in mining, pooled mining and the p2pool share chain first before you can understand where the problems are. Let that not stop you from starting on the bits you do understand though since you have to start somewhere when helping out with an established project you're new to. |
|
|
|
|
Mainline cgminer reports solved blocks normally, but when bitmain made their drivers for their cgminer fork they broke that functionality.
|
|
|
|
As far as rewriting goes:
Stratum being a "human readable protocol"(json based), it's string manipulation in the end, python should be good enough.
The stratum protocol bits are just string manipulation but that part alone is only one tiny component of writing pool software. It was good enough in the days when only one client was expected to connect to a p2pool instance, but if you want p2pool to be useful it needs to attract big miners to push the hashrate which means hundreds if not thousands of clients for a local p2pool instance. It does not remotely scale. There are far more fundamental problems that need addressing in the modern world of mining than the mostly cosmetic startup exception issue. |
|
|
|
CK your last cgminer binary will not work with the Jan 2015 Bitmain S3 firmware. the cgminer that is part of the Jan 2015 firmware is version 4.70 not 4.6. Do you know if this has the fix in it.
No it doesn't. |
|
|
|
is the pool down? I can not view the website. My in house is all dead rolled over to the next pool. My nice hash rentals show I am hashing at your pool.
Pool's fine. I suspect you have an issue somewhere between your miners and the pool. Try mtr if you have linux tools (10% loss is normal) mtr --report -w stratum.kano.is |
|
|
|
So.. Con, thanks for your great work, and your solo mining initiative. Kudos. It has been fun. No blocks to the rescue though  [ 161dYoTJBxvY7gpqqsc6E6HryAgymbqsdh ] Hey.. Sayonara dudes! You're most welcome and I certainly don't bemoan anyone for bailing when the stakes are so high. いろいろお世話になりました。さようなら。 |
|
|
|
Buyers of hashing power at NiceHash/WestHash are not only mining Bitcoin, they are also (sometimes) mining various other coins. Some of them are still at very low difficulty, switching jobs very fast, etc. Unfortunately manufacturers of ASIC miners are putting very weak controllers in their miners (saving a few $ in a machine, worth hundreds even thousands of $  ) with non-optimized software and are thus unable to process large number of shares/jobs/work-restarts. A typical example was KnC Titan (not SHA256, but an Scrypt miner) which was only able to mine Litecoins until the controller software was properly optimized. Recent example of a SHA256 miner that is having a few issues with rejects is AntMiner S5, hopefully Bitmain will improve it soon. If manufacturers would put a multi-core Raspberry Pie 2 in their miners (with a good controller software - I'm not talking only about cgminer/bfgminer, but also drivers, etc. handling of low difficulty coins, switching jobs very fast, proper handling of flushwork, etc.) there would be no issues. For example, there are no issues with sgminer mining any GPU based coin, running on PC (which always has a decent CPU). Probably there is also room for improvement in cgminer itself for these issues. Scrypt miners have nothing to do with this, and I object to you blaming cgminer or the hardware for these issues. 3 second restarts will cause a loss of 10-15% of hashrate no matter how powerful the controller. You are mining shitcoins and miners are losing income as a result, thinking the bonuses will make up for it somehow. Being aware of the issues and planning to tackle them is good but please choose your scapegoats wisely. |
|
|
|
Prior to the arrival of my ASIC mining gear I wanted to try to connect to the pool as a test, just to see if I could do it. All I have available to use as a miner is the gpu on my graphics card. I don't expect to accomplish anything with just a single gpu obviously, I only wanted to see if I could connect to the pool. I tried using GUIMiner to connect, but am not having any luck. This is what I'm seeing: 2015-02-18 23:10:52: Running command: poclbm.exe What am I do wrong? Everything, probably. Yes, everything. poclbm is totally unmaintained and almost certainly does not even have a compliant stratum implementation, and setting up and getting GPU mining working has absolutely nothing in common with ASIC mining so it's a useless learning experience. If you want to see if you can connect, just grab the latest cgminer and connect to the pool without any hardare at all. Anyway your username should just be a btc address with or without a worker extension (not sure what the ":1x3" is you put there). |
|
|
|
So normal CGminer has submit stale on by default correct?
I know CK provided a fix for the S3, what do we do about the S5? (Assuming we need corrective action)
Is it safe to say that Spondoolies did this the correct way, that is submit stale is on by default?
S5 binary also available here (antminer's fork binaries still screw this up): http://ck.kolivas.org/apps/cgminer/antminer/Spondoolies do the right thing here. |
|
|
|
I have been mining on this pool for months now and I must admin, no issues so far. Payments are regular.
I simply don't understand why bother mining elsewhere. If you look at the 30 day chart, you see that NiceHash pays 1.5% more than Bitcoin mining. It is pay per share pool and it has 2% fee. That makes it -0.5% less than Bitcoin mining or in other words - as a 0.5% fee PPS pool. No other pool can survive this on long term. And I didn't consider the 10 fold payment increase that lasted whole week in december.
I don't even set p parameter. Because on long term, NiceHash pays more and additional pool switching just causes troubles with my antminers.
Whoever thinks that there are better paying pools out there should do the math and recalculate again.
Since nicehash is actually a proxy pool, you are not mining directly on the actual upstream pool. You are assuming there is no hit to performance by doing this. I've been trying to help someone with a large farm debug why they take a massive reject hit which far more than offsets the fee at certain times on nicehash and the fact it's a proxy pool is the only valid explanation. I've seen it do some funky mining with restarts every 3 seconds - no mining hardware can work efficiently with that. |
|
|
|
|
Just as a data point, this is the best share so far while we wait for someone to crack a block: 15096516797.15045
|
|
|
|
If it's something virginal that's required then BFL gear is out if this thread is anything to go by: BFL fucked us over again |
|
|
|
I am currently pointing an old S1 to this pool and crossing my fingers, according the address it seems to either have gotten donations or some users have actually hit. Good luck! As the topic says the pool's solved 27 blocks so far. |
|
|
|
|
Must be just about time for someone to find one...
|
|
|
|
Is there an active pool with >=100% over it's lifetime Funny you should ask that... yes. |
|
|
|
join one of the many PPLNS pools and deal with the shitty luck runs where you only get 85% payouts go right ahead.
Don't forget the good luck runs where you get 200% payouts. Remember it all evens out to 100% in the end. |
|
|
|
Deleted the duplicate thread but kept your one reply below. Please don't post the same question twice. Hmm, I'm not sure what your problem is. The Avalon Nano doesn't seem like a very common stick miner (it was a little late to the party). According to the bitcoin wiki you need these settings in your bfgminer bat (it looks a little different from what you have): bfgminer.exe ^
-S ICA:\\.\COMn ^
-o stratum+tcp://stratum.ozco.in:80 -O mikeqin.avalon:1234 ^
--set-device ICA:baud=115200 ^
--set-device ICA:reopen=timeout ^
--set-device ICA:work_division=1 ^
--set-device ICA:fpga_count=1 ^
--set-device ICA:probe_timeout=100 ^
--set-device ICA:timing=0.22 ^
--api-listen ^
2>log It's also possible you need the USB to UART driver (if you haven't installed it). https://www.silabs.com/products/mcu/Pages/USBtoUARTBridgeVCPDrivers.aspxI wouldn't suggest you buying any more of these miners if you want to ramp up your hashrate, it would be better to go for an 'entry level' miner like an antminer S1, S3, or prospero X1. It'll cost the same for a much higher speed, you can get an S3+ (450GH) for about 0.4btc, or an S1 (180GH) for nearly free. |
|
|
|
|
Show Posts
