I don't promote anything...you are reading my posts and made stupid assumptions, so I am answering you.
No hard feelings buddy

lol read what you typed anyway; let's move on

Good launch? - algo changed only to make coin cpu-only, so botnet friendly.
No pools - again botnet friendly

I know few coins that started this way and usually some inside people were mining with pre-configured HW or botnets.
A month of testing and no pools at launch - that is suspicious.

we all can be suspicious but as far as i knwn the dev he is pretty transparent over things ^^, ever since with the old magicoin

edit: hopefully problem with the pool will be fixed soon

That's a good idea.
As the developer and the community have been transparent this fits in perfectly in.

Can someone explain me, what's the point?
I am mining with i7 since launch and no single block found.

lol.. with which miner ?

With the standard miner released at launch. It seems that for nearly every accepted share the next is rejected with "share above target".

I'm using a stratum proxy but I don't think that it is designed for this algo. I believe this algo is similar to cryptonight? If so, the stratum protocol for that algo is different from normal. I found this statement:

The rpc2_* functions does not just use JSON-RPC 2.0 instead of 1.0, they also uses different method names with different parameters from the "real" stratum protocol.

For example, exchanges between the proxy and a "real" stratum pool (sha-256, scrypt, x11, x13...) are:

Proxy                             Pool
mining.subscribe ------->
                      <-------- mining.subscribe response
mining.authorize ------->
                      <-------- mining.authorize response
                      <-------- set_difficulty notification
                      <-------- mining.notify notification
mining.submit    -------->
                      <-------- mining.submit response
mining.submit    -------->
                      <-------- mining.submit response
                      <-------- mining.notify notification
mining.submit    -------->
                      <-------- mining.submit response
mining.submit    -------->
                      <-------- mining.submit response
                      <-------- set_difficulty notification
                      <-------- mining.notify notification


With a cryptonight pool, it should be like that (If you could provide me a protocol dump of a real mining session to confirm):

Proxy                             Pool
login                 ------->
                      <-------- login response
getjob              ------->
                      <-------- getjob response
submit              -------->
                      <-------- submit response
submit              -------->
                     <-------- submit response
getjob              ------->
                      <-------- getjob response
submit              -------->
                      <-------- submit response

You can see that methods are not the same (and parameters are not the same at all). Even the flow control is not the same at all, thus I cannot integrate this properly in the proxy.


Don't know if this is correct or not as i don't know anything about programming!

What are your settings in the .bat file?