Only stratum mining is supported.

Edit: The algo may also be a problem. Only default scrypt has been tested and known to work.

He tried every lame excuse from market volatility to price spread without ever lifting a finger to investigate. When all his excuses
were proven wrong he locked the thread. He claimed to not know the code but never examined logs or let anyone else look at them.
He was clearly trying to cover up what he already knew was happening.

yaamp based pools are the only ones where the data is available to detect a skim. It can happen on any others without any way
for users to prove it. If PPLNS is used it adds another layer of obfuscation that prevents auditing.

Start here

https://bitcointalk.org/index.php?topic=1260863.msg16281552#msg16281552

20% disappears between coin maturing and being credited to balance.

Edit: I mean start reading there, the problem didn't start there. You've already proven it for yourself so
much of the discussion will be repetitive.

The skimming has probably been going on since day one and on his previous pool. It was only detected
because of the detailed stats available with yaamp.

Failover can be easilly implemented using a shell script and "cpuminer -r 0". It can do exactly as you suggest.

Why not both? I don't think the coin can support another fork (there's already zoin) but I don't
see the need to choose one up front.

Like many algos cryptonight was designed to be difficult to implement on GPUs.
It's only due to the strength of XMR that it's profitable to mine with a GPU
at this time.

That it consumes less power means the GPU is bottlenecked and can't perform at full
power. The low temps mean the cores are spending time idle waiting on data, not really
a good thing.

Optimization opportunities likely don't exist. With the current market there is plenty
of incentive to try but I haven't seen any evidence of a breakthrough yet.

The CPU miner also seems to be topped out. Wolf (included in cpuminer-opt) and Claymore
are pretty close in performance.

Happened once? Regularly? Restarting miner works?
What is CPU usage when this happens? Does pool still report a connection, what hashrate?
Try isolating the problem by trying other pools and algos. If it only happens at one pool I suspect
a pool problem.

One other issue with old HW is you're likely to be stuck using old mining SW that only support old algos
Code written for a new algo for a Pascal GPU likely won't work on older generations GPUs. Older
algos are also more likely to have ASIC miners available which destroys any profitibility in GPU and CPU mining.

GPU mining needs at minimum a PCIe slot and a Cuda or OpenCL GPU. The CPU and RAM are virtually irrelevent.
Any system with PCIe likely has a good enough CPU and enough RAM to GPU mine. This is likely the most viable
option for an old system, though it means the direct answer to your initial question is likely no.

CPU mining doesn't have a hard minimum but older CPUs are less capable. 2nd generation x86_64 CPUs (ie core2)
are fully supported by cpuminer-opt. Older CPUs are impaired by the lack of advanced features like AES and AVX which
significantly improve mining performance on many algos.

In short, CPU mining is not viable on old systems but if they support PCIe they can be used as a platform for
mining with the latest GPUs. Until it died a couple of months ago I was using a P4 2.8 GHz 32 bit PC, 2 GB RAM,
1 PCIe x16, 1 PCIe x1, as a 2 GPU rig. The only other upgrade was the power supply.

Mining on laptops should be avoided unless you intend to run them into the ground. They aren't designed for heavy duty use,
inadeqauate cooling.

It's not how the coins are created that is the issue, it's who creates them and how many. You seem to have answered your
own question, both POW and POS are susceptible to 51% attack under the same conditions.

Throttling is downclocking. What are the GPU temps? If they were too hot they would cool when you reboot.
If rebooting doesn't fix it the problem may be outside your rig like networking issues, pool issues etc.

Mining only matters to miners. The only connection between mining and the recent surge in price and volume
is the end of the slow start, meaning there is one fewer variable for investors to worry about.

Whether the surge is real or just a pump, to be followed by a dump, remains to be seen.

Sounds like a short tripping the PSU.  Remove all GPUs, use IGPU for display, and troubleshoot from there.

The issue with 32 bit is mainly feasibility, how much work is involved to develop and support 32 bit mining for how much it
wil produce: smaller architecture, no optimizations (maybe SSE2), lower memory bandwidth, less power efficient. But if you
want to pursue it I suggest cpuminer-multi as a starting point. I believe it still compiles in 32 bit and hasn't been poluted with
64bit optimizations.

I'm not really opposed to closed source but am a little reluctant to making comminments. I'm kinda liking just doiing my own
thing, when I want, how I want, if I want. But if there is something you think I can help with, PM me and we can probably work
it out.

Hi Crysx, howareya?

There's more than just compiling for Windows. 32 bit CPU miners are old and don't support newer algos. And 32 bit CPUs don't
support optimizations like AES, AVX. There is no market for any dev to put any effort to continue to support 32 bit miners.

If you really want to try 32 bit mining I believe cpuminer-multi is stil supported but there is no 32 bit binary provided so you
will need to compile it yourself.

It's probably time to get a 64 bit system.

That's bizarre.

No one has reported this with cpuminer-opt even though the stratum code was taken from multi-1.2.
Could you give it a try as another data point?

The interface to curl is the call to curl_easy perform. It would be useful to dump the curl parameter where this
is called to compare what works with what doesn't.

A hardware fault seem very unlikely since the problem occurs on all your blades. However, if you did one full
install and cloned the rest an install glitch would have been propagated to all blades. You could reinstall the OS
on one system to test this.

A video for THIS!?!?

git clone https://github.com/JayDDee/cpuminer-opt.git
cd cpuminer-opt
./build.sh

Yikes. Two identical systems, different results, and it crashes in a standard library.

Either the application is passing a bad pointer to curl or curl is corrupt. The easiest thing to try is to reinstall the curl
packages. You could also confirm the same compile options were used. If the entire process from source to compile
to run time environment to input data are identical it gets more complicated and hardware needs to be considered. Memtest maybe.

Edit: I assume you already tried getting a fresh copy of the source.

gdb can be used to get a backtrace to find out where the bad pointer is coming from.

Edit: Cryptoninght at Nicehash needs a protocol tweak but it shouldn't cause as crash. Try another pool to rule that out.

Ya, that too. Thanks Nik.

-a zcoin

-a lyra2v2 if you use ocminer version

It works for me, what's your command line?