If phoenix works best for you, just use phoenix and stratum proxy...
|
|
|
tealover, you see higher hashrate on old getwork interface? Or is is just by updating cgminer? I really doubt that it is because of stratum itself.
|
|
|
Stratum proxy 1.2.0 has been released. Changelog:
* Fixes major bug in C extension for calculating midstate (thanks verement for bug report & pull request). * Fixes network issues - proxy now actively reconnects after two minutes of pool inactivity (also disconnect miners to indicate connection issues). * Fixes get_version message.
Update is recommended for all proxy users.
|
|
|
Do you have any hardware reports in cgminer? Overheating/throttling? Looks like hw problem.
|
|
|
Stratum proxy 1.2.0 has been released. Changelog:
* Fixes major bug in C extension for calculating midstate (thanks verement for bug report & pull request). * Fixes network issues - proxy now actively reconnects after two minutes of pool inactivity (also disconnect miners to indicate connection issues). * Fixes get_version message.
|
|
|
I'm getting the no stratum notice too, even though I'm running the latest cgminer and have been on stratum for quite a while.
Now I don't understand your problem. cgminer looks ok ("Switching pool 0 ... to stratum+tcp ..."). Btw no need to run backup pools for api, api2 and api3 - all three IPs are using the same stratum backend...
|
|
|
corvid, can you post cgminer log somewhere (pastebin)?
|
|
|
That's absolutely out of scope of current device. The device even don't know what address it should "promote" over NFC. As I wrote before, at this stage of the project, our goal is to make wallet more secure, not more portable.
|
|
|
hm, maybe because phoenix != cgminer? They have different commandline options.
poclbm doesnt work for you?
|
|
|
Quick transfer of the address inside the device to smartphones and other things?
The device is supposed to be just a storage for private keys. It is unusable without computer (as it has no battery etc). Then you can use QR codes generated by the desktop wallet, so there's no need for NFC chip.
|
|
|
any chance to implement NFC chip inside?
For what purpose?
|
|
|
So...I updated all my miners to the latest cgminer but the Stratum column still says no for all of them. Is there something else I need to do?
That detection has some delay, it will disappear in next round.
|
|
|
Thanks ckolivas, good to know.
|
|
|
So current miners try GBT first, and if it has a Stratum HTTP header they switch to Stratum.
I have no idea how it works with GBT in miners. That X-Stratum is for getwork protocol...
|
|
|
If you recently had some issues during miner startup on Statum, please try it again now. I found some problem on balancer which is fixed now.
|
|
|
Just updated GUI Miner to 11/18/12 version, and your site still says I'm not using stratum...is there anything else I need to change?
Port blocking? I really have no idea, there's not too much things which can fail during subscription. Can you report it to poclbm thread? (not GUIminer thread, but poclbm!)Can you try it once again? I found there was load balancer misconfiguration which may introduce such problems.
|
|
|
No matter if I enter the info manually with a blank config, or copy the config over, it doesn't connect.
Please be sure you typed worker credentials correctly. Everything is case sensitive. If it still fails, can you report it to cgminer thread?
|
|
|
Hey, so I recently switched over to Stratum mining. My rejects have gone down from 1% to 0.1% but it seems NMC mining is broken. Before I'd get ~0.02 NMC almost every round (no reward only once every 10-20 rounds); now, half of the rounds give me "none" NMC. Any ideas? Or is it just a crazy string of coincidences?
It is just coincidence. As Stratum miner, you still collects namecoins as on getwork. Just the pool namecoin hashrate is going down with higher % of stratum miners, because stratum backend doesn't have merged mining.
|
|
|
Interesting thing. I am using cgminer and things were going well but now I have had a tremendous increase in rejected shares.
I quit the two and then restarted the proxy app (from slush) then cgminer. Seems to have fixed it. What was it about? How did my miner get hashes that were above the target?
There are some edge cases during network outage/reconnections, when proxy reconnects, but cgminer doesn't know about it. This ends up with sending garbled shares. I'm currently working on fix for proxy, should be available today.
|
|
|
|