Unless you are mining with multi machines or a very low-end machine, pool mining is not worth it.  Better off solo mining.

I'm hitting blocks virtually every other day on an iMac

My RaspberryPi3 is pointed at a pool and is scraping in VRM bit by bit (currently about 4 VRM over two weeks)

Thanks for making that clear

@testbug You need to change the Welcome message on the pool


Today I see the 1.337% fee is being imposed, which you stated would be free for 1 month for testers.

I don't mind the fee, but you should notify people before simply imposing or increasing the fee which you had previously said would be x for specified time.

Running Ubuntu 16.04 LTS I have found this miner to be great
Also works well on Mac OSX and RaspberryPi3 (Raspbian Jessie)

https://github.com/effectsToCause/veriumMiner

Simple steps to run it headless on a Linux server

cd ~/
sudo apt-get update && sudo apt-get upgrade
sudo apt-get install automake autoconf pkg-config libcurl4-openssl-dev libjansson-dev libssl-dev libgmp-dev
git clone https://github.com/effectsToCause/veriumMiner
cd veriumMiner
./autogen.sh
./configure CFLAGS="-march=native" --with-crypto --with-curl
make
./cpuminer -o stratum+tcp://poolinat0r.com:4443 -u USERNAME.WORKER -p PASSWORD -t NUMBER_OF_PROCESSORS_TO_USE -B

*NB - You should first make an account at http://vrm.poolinat0r.com/ and also create a worker


The last line you should substitute USERNAME / WORKER / PASSWORD and NUMBER_OF_PROCESSORS_TO_USE
The -B flag sets the miner to run in the background, so you can quit your session and it will still be running

To kill it if needed
sudo killall -9 cpuminer

To compile on MAC OSX simply run the following directly after running the ./autogen.sh command:
./nomacro.pl

Even have the above running on a RaspberryPi 3

Need to change the configure line to the following for Raspbian Jessie on RPi3
./configure CFLAGS="-mcpu=cortex-a53 -mfpu=neon-vfpv4" --with-crypto --with-curl  

Also, for RaspberryPi 3 max number of processors you can use without error is 2

HTH

Back to solo mining for me.  Return from the pool is now too low due to a couple of big monster pool munchers lol  Surely they should be solo mining.  Maybe a cap on the share percentage should be imposed to dissuade botnets, et al ?

I have 3 workers hitting vardiff with ~4.6kH/m

and my RaspberryPi3 is on the baby port lol

Then join a pool and get guaranteed VRM daily

Since the beginning of the month, I have mined ~100+ VRM using my Mac

Now it is getting a little harder, so I joined a pool to get guaranteed VRM

4444

In the image below from the last block, how is it possible for the top user to have 90+% of the share ?



Ignore the green row, that's me

The way I do it is to wait for a block to hit on each machine.  You then get an address

Export the private key for that address and import it to my main wallet, give it a label (e.g. linux 1.. etc)

Rinse and repeat for the other machines

In the main wallet, you then see when the other machines hit a block and their label is listed in the history.

Mining on the RPi 3

8 Core Intel(R) Xeon(R) CPU E5-2673 v3 @ 2.40GHz

Averaging about 2 kH/m on each box

Using the veriumMiner from effectsToCause I have hit 3 blocks on 2 separate machines running Ubuntu 16.04.1 LTS in 14 hours

Personally I have found more blocks/reward going solo

Yah, ignore Sir loin and his wife Dolores, they just trolling for attention.

Got it working on Ubuntu 16.0.4.1 LTS (on Azure) on 2 boxes

Hit one block last night and one a few minutes ago

~ 2kH/m on each box  /  Was previously ~ 1kH/m

Same error for me on Ubuntu 16.04.1 LTS / Mac OSC El Crapitan / RPi 3 :-)