Re: [ANN][VRM] Verium PoWT Reserve | Commodity | scrypt² | CPU mining
Good news!
Thank you
So far we have 6 registrations/tester for the pool.
As a bonus for all the testers, investing hashrate and energy i would like to offer you 1 month 0% pool fees if you want to mine more on my pool. Of course you don't have too but maybe you want to
effectstocause has spotted some problems with email notifications/registration email. I have unlocked all registered persons (sry for that) and i will have a look on the emails this evening.
Here is a screen of the pool, we didn't find a block yet but let's hope the settings are right
http://i.imgbox.com/VEHfZSgp.jpg
Informations:
- Personal share rate: kh/m
- Pool share rate: kh/m (got fixed this evening, that you effectstocause for informing me
)- Shares: Because the difficulty is so low, it seems like MPOS has some problems with showing the shares. Every submitted share (atleast for me) is about 0.002 of 1 share. I will have a look on this and change it to a more reliable value, because i know we all want too see on pools, that we are actually transmitting shares
- Pool workers: this is actually showing the right amount of miners
- Global Hashrate: MPOS has some configs for receiveing the current global hashrate. Sadly, on Verium (i am not blameing the devs
) this command got removed. I have some ideas how to get global hashrate, but so far please use your own wallet for global hashrate checks I have a linux machine (cpuminer-verium) and windows machine connected currently (windows using generic miner with -a scrypt:1058476) connected to pool fine!
For fun of it compiled cpuminer-verium on Raspberry Pi B+ and it is submitting shares, but in the worker configuration tab it has an X next to it, most likely hashrate is too low!
http://i.imgbox.com/VEHfZSgp.jpg
Now all that's left is to find some blocks together =)
To be honest I really hope getting listed on an exchange is delayed as much as possible because it gives us time for us early adopters to mine the hell out of it first.
It's a double edged sword IMO if the early mine goes too long and people think they've 'missed out'
EDIT:
@testbug
Incase it helps, my miner logs indicate that the rejected shares happen right after a new block is issued - so most likely the miners are submitting a couple of shares for the old block which are getting rejected - I have similar reject rate to pool as whole so far.
http://i.imgbox.com/ECBChRR8.png
